| 1 |
On 24/07/2013 10:50, Walter Dnes wrote: |
| 2 |
> So I emerged QEMU, which pulled in some dependancies. Things are not |
| 3 |
> going well... |
| 4 |
> |
| 5 |
> 1) The following warning shows up in elog... |
| 6 |
> |
| 7 |
>> WARN: pretend |
| 8 |
>> You have decided to compile your own SeaBIOS. This is not supported |
| 9 |
>> by upstream unless you use their recommended toolchain (which you are |
| 10 |
>> not). If you are intending to use this build with QEMU, realize you |
| 11 |
>> will not receive any support if you have compiled your own SeaBIOS. |
| 12 |
>> Virtual machines subtly fail based on changes in SeaBIOS. |
| 13 |
> I don't see any USE flags about this. |
| 14 |
The "binary" flag is an IUSE default but you're preventing the flag from |
| 15 |
being enabled somehow. |
| 16 |
> |
| 17 |
> 2) I download a Gentoo install ISO, and create a 7 gig raw file sda.raw, |
| 18 |
> and start qemu-kvm |
| 19 |
> |
| 20 |
> $ qemu-kvm -hda sda.raw -cdrom installx86.iso -boot d |
| 21 |
> Could not access KVM kernel module: Permission denied |
| 22 |
> failed to initialize KVM: Permission denied |
| 23 |
> |
| 24 |
> but... but... but... I am a member of group "kvm". |
| 25 |
Check that KVM support is available in the kernel (CONFIG_KVM_INTEL or |
| 26 |
CONFIG_KVM_AMD as appropriate). Another thing to bear in mind is that |
| 27 |
older kernels are unable to load the module on an on-demand basis. I |
| 28 |
can't remember exactly in which version they changed that. You should |
| 29 |
end up with the following device node: |
| 30 |
|
| 31 |
# ls -l /dev/kvm |
| 32 |
crw-rw---- 1 root kvm 10, 232 Dec 2 2012 /dev/kvm |
| 33 |
|
| 34 |
> |
| 35 |
> 3) su to root and retry to start QEMU |
| 36 |
> |
| 37 |
> # qemu-kvm -hda sda.raw -cdrom installx86.iso -boot d |
| 38 |
> qemu-system-x86_64: pci_add_option_rom: failed to find romfile "pxe-e1000.rom" |
| 39 |
> VNC server running on `127.0.0.1:5900' |
| 40 |
> |
| 41 |
> So root has sufficient permission, but there's a problem with the BIOS, |
| 42 |
> possibly related to item 1) above |
| 43 |
> |
| 44 |
> Note; I can run as regular user, either of the 2 commands... |
| 45 |
> $ qemu-system-i386 -hda sda.raw -cdrom installx86.iso -boot d |
| 46 |
> $ qemu-system-x86_64 -hda sda.raw -cdrom installx86.iso -boot d |
| 47 |
> This doesn't run into permission problem 2), but still runs into the |
| 48 |
> rom not found problem 3). |
| 49 |
> |
| 50 |
> 4) At least VNC is running. I emerged tigervnc and tried it |
| 51 |
> |
| 52 |
> $ vncviewer |
| 53 |
> |
| 54 |
> TigerVNC Viewer 64-bit v1.2.0 (20130723) |
| 55 |
> Built on Jul 23 2013 at 21:36:16 |
| 56 |
> Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt) |
| 57 |
> Seehttp://www.tigervnc.org for information on TigerVNC. |
| 58 |
> X_ChangeGC: BadFont (invalid Font parameter) 0x0 |
| 59 |
> |
| 60 |
> ...and the dialog box is all blanks, presumably because of the missing |
| 61 |
> fonts. |
| 62 |
VNC servers and clients vary in their capabilities rather more than they |
| 63 |
ought to. I would suggest tightvnc as I've found that to work splendidly |
| 64 |
with qemu. |
| 65 |
|
| 66 |
--Kerin |
Archives