[gentoo-user] QEMU setup questions

[gentoo-user] QEMU setup questions

[Walter Dnes]

  So I emerged QEMU, which pulled in some dependancies.  Things are not
going well...

1) The following warning shows up in elog...

> WARN: pretend
> You have decided to compile your own SeaBIOS. This is not supported
> by upstream unless you use their recommended toolchain (which you are
> not).  If you are intending to use this build with QEMU, realize you
> will not receive any support if you have compiled your own SeaBIOS.
> Virtual machines subtly fail based on changes in SeaBIOS.

  I don't see any USE flags about this.


2) I download a Gentoo install ISO, and create a 7 gig raw file sda.raw,
and start qemu-kvm

$ qemu-kvm -hda sda.raw -cdrom installx86.iso -boot d
Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied

but... but... but... I am a member of group "kvm".


3) su to root and retry to start QEMU

# qemu-kvm -hda sda.raw -cdrom installx86.iso -boot d
qemu-system-x86_64: pci_add_option_rom: failed to find romfile "pxe-e1000.rom"
VNC server running on `127.0.0.1:5900'

So root has sufficient permission, but there's a problem with the BIOS,
possibly related to item 1) above

Note; I can run as regular user, either of the 2 commands...
$ qemu-system-i386 -hda sda.raw -cdrom installx86.iso -boot d
$ qemu-system-x86_64 -hda sda.raw -cdrom installx86.iso -boot d
This doesn't run into permission problem 2), but still runs into the
rom not found problem 3).

4) At least VNC is running.  I emerged tigervnc and tried it

$ vncviewer 

TigerVNC Viewer 64-bit v1.2.0 (20130723)
Built on Jul 23 2013 at 21:36:16
Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
X_ChangeGC: BadFont (invalid Font parameter) 0x0

...and the dialog box is all blanks, presumably because of the missing
fonts.


  I had QEMU working a few years ago, and I don't remember running into
all these problems.  What gives?

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] QEMU setup questions

[William Kenworthy]

On 24/07/13 17:50, Walter Dnes wrote:
>   So I emerged QEMU, which pulled in some dependancies.  Things are not
> going well...
> 
> 1) The following warning shows up in elog...
> 
>> WARN: pretend
>> You have decided to compile your own SeaBIOS. This is not supported
>> by upstream unless you use their recommended toolchain (which you are
>> not).  If you are intending to use this build with QEMU, realize you
>> will not receive any support if you have compiled your own SeaBIOS.
>> Virtual machines subtly fail based on changes in SeaBIOS.
> 
>   I don't see any USE flags about this.
> 
> 
> 2) I download a Gentoo install ISO, and create a 7 gig raw file sda.raw,
> and start qemu-kvm
> 
> $ qemu-kvm -hda sda.raw -cdrom installx86.iso -boot d
> Could not access KVM kernel module: Permission denied
> failed to initialize KVM: Permission denied
> 
> but... but... but... I am a member of group "kvm".
> 
> 
> 3) su to root and retry to start QEMU
> 
> # qemu-kvm -hda sda.raw -cdrom installx86.iso -boot d
> qemu-system-x86_64: pci_add_option_rom: failed to find romfile "pxe-e1000.rom"
> VNC server running on `127.0.0.1:5900'
> 
> So root has sufficient permission, but there's a problem with the BIOS,
> possibly related to item 1) above
> 
> Note; I can run as regular user, either of the 2 commands...
> $ qemu-system-i386 -hda sda.raw -cdrom installx86.iso -boot d
> $ qemu-system-x86_64 -hda sda.raw -cdrom installx86.iso -boot d
> This doesn't run into permission problem 2), but still runs into the
> rom not found problem 3).
> 
> 4) At least VNC is running.  I emerged tigervnc and tried it
> 
> $ vncviewer 
> 
> TigerVNC Viewer 64-bit v1.2.0 (20130723)
> Built on Jul 23 2013 at 21:36:16
> Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
> See http://www.tigervnc.org for information on TigerVNC.
> X_ChangeGC: BadFont (invalid Font parameter) 0x0
> 
> ...and the dialog box is all blanks, presumably because of the missing
> fonts.
> 
> 
>   I had QEMU working a few years ago, and I don't remember running into
> all these problems.  What gives?
> 

its working ok for me - what versions of qemu/seabios/kernel?

I have:
*  sys-firmware/seabios
      Latest version available: 1.7.2.1
"binary" USE flag set for upstream compiled binaries
...

using the binary USE flag (upstream compiled)
*  app-emulation/qemu
      Latest version available: 1.4.2
...

and kernel 3.10.1

Cant help with the perms as I am running as root on dedicated hardware


BillK

Re: [gentoo-user] QEMU setup questions

[Kerin Millar]

On 24/07/2013 10:50, Walter Dnes wrote:
>    So I emerged QEMU, which pulled in some dependancies.  Things are not
> going well...
>
> 1) The following warning shows up in elog...
>
>> WARN: pretend
>> You have decided to compile your own SeaBIOS. This is not supported
>> by upstream unless you use their recommended toolchain (which you are
>> not).  If you are intending to use this build with QEMU, realize you
>> will not receive any support if you have compiled your own SeaBIOS.
>> Virtual machines subtly fail based on changes in SeaBIOS.
>    I don't see any USE flags about this.
The "binary" flag is an IUSE default but you're preventing the flag from 
being enabled somehow.
>
> 2) I download a Gentoo install ISO, and create a 7 gig raw file sda.raw,
> and start qemu-kvm
>
> $ qemu-kvm -hda sda.raw -cdrom installx86.iso -boot d
> Could not access KVM kernel module: Permission denied
> failed to initialize KVM: Permission denied
>
> but... but... but... I am a member of group "kvm".
Check that KVM support is available in the kernel (CONFIG_KVM_INTEL or 
CONFIG_KVM_AMD as appropriate). Another thing to bear in mind is that 
older kernels are unable to load the module on an on-demand basis. I 
can't remember exactly in which version they changed that. You should 
end up with the following device node:

# ls -l /dev/kvm
crw-rw---- 1 root kvm 10, 232 Dec  2  2012 /dev/kvm

>
> 3) su to root and retry to start QEMU
>
> # qemu-kvm -hda sda.raw -cdrom installx86.iso -boot d
> qemu-system-x86_64: pci_add_option_rom: failed to find romfile "pxe-e1000.rom"
> VNC server running on `127.0.0.1:5900'
>
> So root has sufficient permission, but there's a problem with the BIOS,
> possibly related to item 1) above
>
> Note; I can run as regular user, either of the 2 commands...
> $ qemu-system-i386 -hda sda.raw -cdrom installx86.iso -boot d
> $ qemu-system-x86_64 -hda sda.raw -cdrom installx86.iso -boot d
> This doesn't run into permission problem 2), but still runs into the
> rom not found problem 3).
>
> 4) At least VNC is running.  I emerged tigervnc and tried it
>
> $ vncviewer
>
> TigerVNC Viewer 64-bit v1.2.0 (20130723)
> Built on Jul 23 2013 at 21:36:16
> Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
> Seehttp://www.tigervnc.org  for information on TigerVNC.
> X_ChangeGC: BadFont (invalid Font parameter) 0x0
>
> ...and the dialog box is all blanks, presumably because of the missing
> fonts.
VNC servers and clients vary in their capabilities rather more than they 
ought to. I would suggest tightvnc as I've found that to work splendidly 
with qemu.

--Kerin

Re: [gentoo-user] QEMU setup questions

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

On Wed, 24 Jul 2013 11:57:41 +0100, Kerin Millar wrote:

> >> WARN: pretend
> >> You have decided to compile your own SeaBIOS. This is not supported
> >> by upstream unless you use their recommended toolchain (which you are
> >> not).  If you are intending to use this build with QEMU, realize you
> >> will not receive any support if you have compiled your own SeaBIOS.
> >> Virtual machines subtly fail based on changes in SeaBIOS.  
> >    I don't see any USE flags about this. 

> The "binary" flag is an IUSE default but you're preventing the flag
> from being enabled somehow.

That's the sort of fun you get with USE="-*" :P

> > 2) I download a Gentoo install ISO, and create a 7 gig raw file
> > sda.raw, and start qemu-kvm
> >
> > $ qemu-kvm -hda sda.raw -cdrom installx86.iso -boot d
> > Could not access KVM kernel module: Permission denied
> > failed to initialize KVM: Permission denied

Is the problem with reading the module file or loading it? If you
modprobe the kvm module as root first, can you then run it as a user? You
may want to add the module to /etc/conf.d/modules.


-- 
Neil Bothwick

To most people solutions mean finding the answers.  But to chemists
solutions are things that are still all mixed up.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] QEMU setup questions

[Kerin Millar]

On 24/07/2013 14:16, Neil Bothwick wrote:
> On Wed, 24 Jul 2013 11:57:41 +0100, Kerin Millar wrote:
>
>>>> WARN: pretend
>>>> You have decided to compile your own SeaBIOS. This is not supported
>>>> by upstream unless you use their recommended toolchain (which you are
>>>> not).  If you are intending to use this build with QEMU, realize you
>>>> will not receive any support if you have compiled your own SeaBIOS.
>>>> Virtual machines subtly fail based on changes in SeaBIOS.
>>>     I don't see any USE flags about this.
>
>> The "binary" flag is an IUSE default but you're preventing the flag
>> from being enabled somehow.
>
> That's the sort of fun you get with USE="-*" :P

Indeed. I'd advocate this as a safer alternative:

USE_ORDER="env:pkg:conf:pkginternal:repo:env.d"

--Kerin

Re: [gentoo-user] QEMU setup questions

[Walter Dnes]

  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


  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.
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?

2) What "vncviewer" or "vncconnect" parameters do I use to get to the
qemu session?

  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.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] QEMU setup questions

[Kerin Millar]

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

[gentoo-user] QEMU setup questions

[Walter Dnes]

On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
> 
> > 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.

  Thanks.  That helped me to get it working.

  I stumbled over the solution to my final problem by accident.  When
booting off the install cd, you have 15 seconds to "hit any key", or
else it'll try to boot off the "hard drive".  Given that I haven't
installed yet, it'll try to boot off the blank pseudo "hard drive", and
fail.  Pressing any key will stop the timer.  I prefer to type in...

gentoo net.ifnames=0

...to give myself "a predictable interface name", namely eth0.  The
timer stops after I hit the "g", and I can take my time typing the rest
of the command.  If you don't mind whatever ifname udev generates, you
can simply hit enter.  The drill *FOR INSTALL ONLY* under vnc is like
so...

* open up 2 terminals side-by-each
* in one type the command like the following *BUT DO NOT HIT <ENTER>*
vncviewer localhost:2

* in the other terminal, type a command like so, and hit <ENTER>
qemu-system-i386 -vnc :2 -cpu qemu32 -m 3072 -hda sda.raw -cdrom installx86.iso -boot d

* *IMMEDIATELY* go over to the other terminal and hit <ENTER> to
  activate vncviewer

* *AS SOON AS VNCVIEWER POPS UP* either hit <ENTER> for default install
  parameters, or start typing your own install command.

* *DO NOT PANIC* when the vncviewer screen goes dark for several seconds
  as the install checks out its environment.

* One more minor annoyance and workaround... the initial vncviewer
  screen is a 720x400 xterm.  The install thinks it's in a 1024x768
  framebuffer, so you get the bottom and right edges of the output
  clipped.  As soon the penguin logo appears, you can close the xterm
  containing the vncviewer output, and open another vncviewer with the
  same command as the original.  This new copy senses the correct
  "screensize" and you can go on with your install.


  I still haven't figured out why only root can run qemu-kvm.  I
"solved" that problem with an entry in /etc/sudoers.d and it is
definitely faster.

  If I specify a video card type for the guest, then the driver has to
be emerged on the guest; is that correct?

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] QEMU setup questions

[Kerin Millar]

On 25/07/2013 09:54, Walter Dnes wrote:
> On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
>>
>>> 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.
>
>    Thanks.  That helped me to get it working.
>
>    I stumbled over the solution to my final problem by accident.  When
> booting off the install cd, you have 15 seconds to "hit any key", or
> else it'll try to boot off the "hard drive".  Given that I haven't
> installed yet, it'll try to boot off the blank pseudo "hard drive", and
> fail.  Pressing any key will stop the timer.  I prefer to type in...

Just as on a real PC you can issue Ctrl+Alt+Del to have it reboot again 
(without respawning qemu). Look for the three-finger-salute icon on the 
toolbar.

>
> gentoo net.ifnames=0
>
> ...to give myself "a predictable interface name", namely eth0.  The
> timer stops after I hit the "g", and I can take my time typing the rest
> of the command.  If you don't mind whatever ifname udev generates, you
> can simply hit enter.  The drill *FOR INSTALL ONLY* under vnc is like
> so...
>
> * open up 2 terminals side-by-each
> * in one type the command like the following *BUT DO NOT HIT <ENTER>*
> vncviewer localhost:2
>
> * in the other terminal, type a command like so, and hit <ENTER>
> qemu-system-i386 -vnc :2 -cpu qemu32 -m 3072 -hda sda.raw -cdrom installx86.iso -boot d
>
> * *IMMEDIATELY* go over to the other terminal and hit <ENTER> to
>    activate vncviewer
>
> * *AS SOON AS VNCVIEWER POPS UP* either hit <ENTER> for default install
>    parameters, or start typing your own install command.
>
> * *DO NOT PANIC* when the vncviewer screen goes dark for several seconds
>    as the install checks out its environment.
>
> * One more minor annoyance and workaround... the initial vncviewer
>    screen is a 720x400 xterm.  The install thinks it's in a 1024x768
>    framebuffer, so you get the bottom and right edges of the output
>    clipped.  As soon the penguin logo appears, you can close the xterm
>    containing the vncviewer output, and open another vncviewer with the
>    same command as the original.  This new copy senses the correct
>    "screensize" and you can go on with your install.

That's odd. The VNC client should dynamically change the size of its 
window as appropriate.

>
>
>    I still haven't figured out why only root can run qemu-kvm.  I
> "solved" that problem with an entry in /etc/sudoers.d and it is
> definitely faster.
>
>    If I specify a video card type for the guest, then the driver has to
> be emerged on the guest; is that correct?
>

That's correct if you want optimal performance in X.org. The best option 
is -vga vmware in conjunction with x11-drivers/xf86-video-vmware.

--Kerin

Re: [gentoo-user] QEMU setup questions

[J. Roeleveld]

On Thu, July 25, 2013 11:17, Kerin Millar wrote:
> On 25/07/2013 09:54, Walter Dnes wrote:
>> On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote

>>    I stumbled over the solution to my final problem by accident.  When
>> booting off the install cd, you have 15 seconds to "hit any key", or
>> else it'll try to boot off the "hard drive".  Given that I haven't
>> installed yet, it'll try to boot off the blank pseudo "hard drive", and
>> fail.  Pressing any key will stop the timer.  I prefer to type in...
>
> Just as on a real PC you can issue Ctrl+Alt+Del to have it reboot again
> (without respawning qemu). Look for the three-finger-salute icon on the
> toolbar.

Which toolbar?

>> * One more minor annoyance and workaround... the initial vncviewer
>>    screen is a 720x400 xterm.  The install thinks it's in a 1024x768
>>    framebuffer, so you get the bottom and right edges of the output
>>    clipped.  As soon the penguin logo appears, you can close the xterm
>>    containing the vncviewer output, and open another vncviewer with the
>>    same command as the original.  This new copy senses the correct
>>    "screensize" and you can go on with your install.
>
> That's odd. The VNC client should dynamically change the size of its
> window as appropriate.

Not all VNC-clients do this.
Which do you use?

--
Joost

Re: [gentoo-user] QEMU setup questions

[Kerin Millar]

On 25/07/2013 10:26, J. Roeleveld wrote:
> On Thu, July 25, 2013 11:17, Kerin Millar wrote:
>> On 25/07/2013 09:54, Walter Dnes wrote:
>>> On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
>
>>>    I stumbled over the solution to my final problem by accident.  When
>>> booting off the install cd, you have 15 seconds to "hit any key", or
>>> else it'll try to boot off the "hard drive".  Given that I haven't
>>> installed yet, it'll try to boot off the blank pseudo "hard drive", and
>>> fail.  Pressing any key will stop the timer.  I prefer to type in...
>>
>> Just as on a real PC you can issue Ctrl+Alt+Del to have it reboot again
>> (without respawning qemu). Look for the three-finger-salute icon on the
>> toolbar.
>
> Which toolbar?
>
>>> * One more minor annoyance and workaround... the initial vncviewer
>>>    screen is a 720x400 xterm.  The install thinks it's in a 1024x768
>>>    framebuffer, so you get the bottom and right edges of the output
>>>    clipped.  As soon the penguin logo appears, you can close the xterm
>>>    containing the vncviewer output, and open another vncviewer with the
>>>    same command as the original.  This new copy senses the correct
>>>    "screensize" and you can go on with your install.
>>
>> That's odd. The VNC client should dynamically change the size of its
>> window as appropriate.
>
> Not all VNC-clients do this.
> Which do you use?

TightVNC but on Windows. I haven't used the Linux version in some time
and incorrectly assumed feature parity. Sorry about that. Regarding the
absence of a toolbar, pressing F8 should expose a menu with a
Ctrl-Alt-Del option.

--Kerin

Re: [gentoo-user] QEMU setup questions

[Walter Dnes]

On Thu, Jul 25, 2013 at 11:26:36AM +0200, J. Roeleveld wrote

> Not all VNC-clients do this.
> Which do you use?

  In my case, it's tightvnc, which does not auto-resize.  And in linux
tightvnc, {F8} brings up the dialogue.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] QEMU setup questions

[Walter Dnes]

On Thu, Jul 25, 2013 at 10:17:41AM +0100, Kerin Millar wrote
> That's correct if you want optimal performance in
> X.org. The best option is -vga vmware in conjunction with
> x11-drivers/xf86-video-vmware.

  The last time I used qemu a few years ago, I ended up running wine
from the guest as an X client, using the host's display.  The display
was native, and faster than the emulation.  I also didn't have to build
the full-blown X-server on the guest.  Here are my latest scripts/commands

1) The install startup script

#!/bin/bash
sudo /usr/bin/qemu-kvm \
 -vga vmware \
 -vnc :2 \
 -redir tcp:60022::22 \
 -cpu qemu32 \
 -m 3072 \
 -hda sda.raw -hdb sdb.raw -cdrom installx86.iso -boot d

2) Launching vncviewer

vncviewer localhost:2

3) ssh from the guest to the host

ssh root@localhost

4) ssh from the host to the guest

ssh -p 60022 root@localhost

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications