From: Kerin Millar <kerframil@fastmail.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] QEMU setup questions
Date: Thu, 25 Jul 2013 05:16:21 +0100 [thread overview]
Message-ID: <51F0A695.6090407@fastmail.co.uk> (raw)
In-Reply-To: <20130725032451.GA26319@waltdnes.org>
On 25/07/2013 04:24, Walter Dnes wrote:
> Thanks to all who replied. sys-firmware/seabios needed the "binary"
> flag and sys-firmware/ipxe needed the "qemu" and "vmware" flags. It's
> starting now, and most of my problems are solved.
>
> I still have permission problems as a regular user with qemu-kvm, but
> qemu-system-i386 works. Root can start qemu-kvm. "modprobe kvm-intel"
> from a root xterm, followed by "qemu-kvm blahblahblah" from a regular
> user (i.e. "waltdnes") fails...
>
> Could not access KVM kernel module: Permission denied
> failed to initialize KVM: Permission denied
>
> Before anybody asks...
>
> # grep kvm /etc/group
> kvm:x:78:waltdnes,user2
1) What are the permissions of the device node mentioned in my previous
response?
2) Does the groups command show that you're in the group right now?
>
>
> One more question... I rebuilt qemu with sdl enabled, and now have the
> Gentoo install ISO booting up in a window via sdl with...
>
> qemu-system-i386 -cpu qemu32 -m 3072 -hda sda.raw -cdrom installx86.iso -boot d
>
> But the screen refreshes are somewhat slow. I'd prefer to do it with
> vnc. What is the way to boot up and connect with vnc now? Starting
> with...
>
> qemu-system-i386 -vnc :0 -cpu qemu32 -m 3072 -hda sda.raw -cdrom installx86.iso -boot d
>
> ...gives no output at all. "ps -ef" shows the qemu process is present.
Of course. You've asked it to couple the display with its embedded VNC
server. You'll need to connect with a VNC client to see it.
> I've installed tightvnc, but documentation is almost non-existant.
> Google turns up tons of download sites and instructions for Windows,
> complete with screen captures of cutsie-wootsie dialogue windows. I need
> just 2 things please...
>
> 1) What vnc parameters to enter into the qemu commandline?
>
The parameters you used look fine. Display ":0" should translate to TCP
port 5900, meaning that qemu should be listening on port 5900. You can
check with netstat or ss.
> 2) What "vncviewer" or "vncconnect" parameters do I use to get to the
> qemu session?
Assuming both server and client are run locally, connecting to either
"localhost:0" or "localhost:5900" should work.
>
> I just had a scary thought... the vnc "help" mentions connecting to
> the the client display. But the install cd boots up to a text console.
> Please don't tell me that tightvnc can't connect to a plain text
> console.
>
It can.
--Kerin
next prev parent reply other threads:[~2013-07-25 4:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 9:50 [gentoo-user] QEMU setup questions Walter Dnes
2013-07-24 10:53 ` William Kenworthy
2013-07-24 10:57 ` Kerin Millar
2013-07-24 13:16 ` Neil Bothwick
2013-07-24 13:47 ` Kerin Millar
2013-07-25 3:24 ` Walter Dnes
2013-07-25 4:16 ` Kerin Millar [this message]
2013-07-25 8:54 ` Walter Dnes
2013-07-25 9:17 ` Kerin Millar
2013-07-25 9:26 ` J. Roeleveld
2013-07-25 9:34 ` Kerin Millar
2013-07-25 22:57 ` Walter Dnes
2013-07-25 23:35 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F0A695.6090407@fastmail.co.uk \
--to=kerframil@fastmail.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox