I have a virt-io based virtual machine with worked fine under app-emulation/qemu-kvm-0.11.1. Today I upgraded to 0.12.1 and it will not start. I get the following error (via libvirt): error: Failed to start domain kdestable error: internal error unable to start guest: char device redirected to /dev/pts/2 rom: requested regions overlap (rom vapic.bin. free=0x0000000000000600, addr=0x0000000000000000) rom loading failed Argh.. I have no idea what this means so I cannot debug beyond that. I only know that downgrading qemu-kvm fixes it. I have tried various permutations of the new USE flags that 0.12.1 introduces, but I still get the same error.
Created attachment 213715 [details] emerge --info
Same here after upgrading to 0.12.1. All it says is rom: requested regions overlap (rom vgabios.bin. free=0x0000000000002300, addr=0x0000000000000000) rom loading failed [ebuild R ] app-emulation/qemu-kvm-0.12.1 USE="alsa gnutls ncurses sdl -bluetooth -esd -hardened -pulseaudio -sasl -vde" QEMU_SOFTMMU_TARGETS="i386 x86_64 -arm -cris -m68k -microblaze -mips -mips64 -mips64el -mipsel -ppc -ppc64 -ppcemb -sh4 -sh4eb -sparc -sparc64" QEMU_USER_TARGETS="i386 x86_64 -alpha -arm -armeb -cris -m68k -microblaze -mips -mipsel -ppc -ppc64 -ppc64abi32 -sh4 -sh4eb -sparc -sparc32plus -sparc64"
Can you give us "emerge -pv qemu-kvm", the command used to start qemu-kvm and if you can start it manually with something like "/usr/bin/qemu-system-x86_64 -enable-kvm <your args>"?
The output of "emerge -pv qemu-kvm" is already in my last comment. :-) The script for launching my windows VM is #!/bin/sh qemu-system-x86_64 \ -net nic,macaddr=46:0e:b3:53:9f:3a \ -net user \ -localtime \ -balloon virtio \ -m 1024M \ -usb \ -usbdevice tablet \ -sdl \ -vga std \ -no-frame \ -enable-kvm \ ~/kvm/windows.qcow2 > ~/.qemu-kvm.log I tried leaving out options one by one, and it seems the option "-vga std" is the culprit. Without it qemu starts, but of course then I can only have a resolution of 1280x1024 with 16 bit color depth.
The -vga std issue has been reported to upstream, but I don't see any email addressing it.
Please test and report back with 0.12.1.1 I myself just tested it with -vga std and could not see any issues.
(In reply to comment #6) > Please test and report back with 0.12.1.1 > > I myself just tested it with -vga std and could not see any issues. > I'm getting following error with 0.12.1 and 0.12.1.1: I'm using Virt-manager + libvirt on my Gentoo ~amd64 System, if you need further information let me know. With 0.11.1 all is working fine, when I create a symlink /usr/bin/kvm -> /usr/bin/qemu-system-x86_64 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup self._backend.create() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 300, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: monitor socket did not show up.: Connection refused
(In reply to comment #7) > (In reply to comment #6) > > Please test and report back with 0.12.1.1 > > > > I myself just tested it with -vga std and could not see any issues. > > > > I'm getting following error with 0.12.1 and 0.12.1.1: > > I'm using Virt-manager + libvirt on my Gentoo ~amd64 System, if you need > further information let me know. > With 0.11.1 all is working fine, when I create a symlink /usr/bin/kvm -> > /usr/bin/qemu-system-x86_64 > > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain > vm.startup() > File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup > self._backend.create() > File "/usr/lib64/python2.6/site-packages/libvirt.py", line 300, in create > if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) > libvirtError: monitor socket did not show up.: Connection refused > Sorry here is an update: Version 0.12.1.1 is working for me fine. I had to add under Image section of the VM-xmls type='raw', now all is working.
Ditto for me. 0.12.1.1 works again with -vga std.
Two different bugs here. The original reporter had an issue with boot=on in the -drive option. While comment #2 was an issue with -vga std. Everyone should make sure they've got qemu-kvm-0.12.1.1 and virt-manager 0.8.2 for all the appropriate fixes.
Virt-Manager 0.8.2 + qemu-kvm 0.12.1.1 is working fine for me.
