qemu 0.13.0: threaded vnc and boot=once are broken

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



So I've been using QEMU/KVM 0.12.5 happily to boot both various Linux
distributions and Windows XP. I upgraded to 0.13.0 (tip of stable-0.13
branch) to get virtio-serial (which recent libguestfses require).
I configured with --enable-vnc-thread because a quick perusal of relevant
list discussions suggested that it had only been disabled because of
poor Windows threading support in qemu, and that it might reduce
blocking a bit.  However, upon upgrading, I find that my normal
XP-booting command-line no longer works (and neither do my command-lines
for Fedora et al, I suspect):

/usr/bin/qemu-system-x86_64 -M pc-0.12 -cpu qemu32 -enable-kvm -m 4096 -smp 2 -name activated-windows -vnc spindle:9 -boot once=d -drive file=/vm/windows/activated.img,if=ide,index=0,boot=on,cache=writeback,serial=8402:1CFE -cdrom /dev/cdrom -net nic,macaddr=52:54:00:4b:f7:7f,vlan=0,model=ne2k_pci,name=eth0 -net tap,vlan=0,ifname=windows,script=/sbin/qemu-windows-full.ifup,downscript=/sbin/qemu-windows-full.ifdown -parallel none -usb -usbdevice tablet -k en-gb -vga std -rtc base=localtime -soundhw ac97 -runas windows-vm -pidfile /var/run/qemu/windows.pid -serial mon:telnet::10404,server,nowait

yields:

,----
| Starting SeaBIOS (version pre-0.6.1-20100713_085324-titi=
| 
| 
| 
| gPXE (http://etherboot.org) - 0:00.0 CD00 PCI2.10 PnP BBS PMMDFE0@10 CD00
| 
| Booting from CD/DVD...
| 
| 1023MB medium detected
| 
| Boot failed: Could not read from CDROM (code 0004)
| No bootable device.
`----

i.e., qemu has treated my '-boot once=d' as a '-boot d', even though
that was install-time-only and it should have done a '-boot c'.

So, I take the -boot out (it's not really necessary anymore), only to
get this on qemu's stderr:

qemu: qemu_mutex_lock: Invalid argument

Running with -sdl instead of -vnc fixes this. Configuring without
--enable-vnc-thread fixes it too. So it looks like --enable-vnc-thread
may be disabled by default because it is broken, as well. One comment
suggested that commit ac71103dc6b408775ae72067790ab367912f75ec may fix
this, but this was cherry-picked for 0.13.x without solving the problem
(for me at least).


(An unjustifiably snarky aside: has anyone considered actual release
notes? It is terribly hard to figure out what effect the vast flood of
qemu changes between versions will actually have short of reading the
entire git log and mailing list archives: the ten-line qemu 0.13
'release notes' didn't even *mention* VNC threading, for instance.
What's the point of adding a feature if nobody's told it exists? qemu
already has so very many nifty features that there's not much chance of
people stumbling over new features by chance. It gives everyone a little
bit of egoboo to see their feature in lights, as well. :) )
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux