public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] QEMU setup questions
Date: Wed, 24 Jul 2013 18:53:25 +0800	[thread overview]
Message-ID: <51EFB225.3090905@iinet.net.au> (raw)
In-Reply-To: <20130724095025.GA24229@waltdnes.org>

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



  reply	other threads:[~2013-07-24 10:53 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 [this message]
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
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=51EFB225.3090905@iinet.net.au \
    --to=billk@iinet.net.au \
    --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