[Qemu-devel] [Bug 393430] Re: kvm: use PulseAudio instead of ALSA
The Debian big referenced suggested using ALSA over OSS, this bug is related to favouring PA over ALSA. The Debian issue was resolved with: --- kvm-79+dfsg/debian/rules +++ kvm-82+dfsg/debian/rules @@ -141,7 +141,9 @@ config.status: configure dh_testdir # Add here commands to configure the package. - ./configure --prefix=/usr + ./configure --prefix=/usr \ +--audio-drv-list=alsa oss sdl \ +--audio-card-list=ac97 adlib cs4231a gus build-arch: patch config.status build-arch-stamp However, the current debian qemu-kvm package contains: --audio-drv-list=alsa oss sdl pa \ --audio-card-list=ac97 es1370 sb16 cs4231a adlib gus hda \ Neither of these configure options are set in debian/rules. This probably requires further investigation. Thanks. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/393430 Title: kvm: use PulseAudio instead of ALSA Status in QEMU: Incomplete Status in “kvm” package in Ubuntu: Incomplete Status in “kvm” package in Debian: Fix Released Bug description: Binary package hint: kvm kvm in jaunty prefers to use OSS drivers rather than ALSA: # dpkg -l | grep kvm ii kvm1:84+dfsg-0ubuntu11Full virtualization on i386 and amd64 hardwa # kvm -audio-help | grep ^Name Name: oss Name: alsa Name: sdl Name: pa Name: none Name: wav # Because of that, once a virtual machine with working audio card starts, the kvm grabs the audio card entirely for itself. Any subsequent operations on audio card either from the host machine, or from the other audio-enabled virtual machines lock up (apparently awaiting on on access to the audio card). The bug is echo of the corresponding debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508018 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/393430/+subscriptions
[Qemu-devel] [Bug 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
@Serge, I had to re-target your branch (and merge) against 0.14.0~rc1 +noroms-0ubuntu4 as *ubuntu3 had already been uploaded for a different fix, and the package-importer failed to suck it in. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/723871 Title: qemu-kvm-0.14.0 Aborts with -vga qxl Status in QEMU: Confirmed Status in “qemu-kvm” package in Ubuntu: Fix Released Bug description: Host CPU is Core i7 Q820. KVM is from 2.6.35-gentoo-r5 kernel (x86_64). Host has spice-0.7.2 and spice-protocol-0.7.0. Guest is Windows XP SP3 with qxl driver 0.6.1, virtio-serial 1.1.6 and vdagent 0.6.3. qemu-kvm is started like so: qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid -drive file=/home/rick/qemu/hds/wxp.raw,if=virtio,media=disk,aio=native,snapshot=on -m 768 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl -device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice port=1234,disable-ticketing -monitor stdio and crashes with: qemu-system-x86_64: /home/rick/qemu/src/qemu-kvm-0.14.0/qemu-kvm.c:1724: kvm_mutex_unlock: Assertion `!cpu_single_env' failed. Aborted If I use -no-kvm, it works fine. If I use -vga std, it works fine. -enable-kvm and -vga qxl crashes.
[Qemu-devel] [Bug 524447] Re: virsh save is very slow
Changing to libvirt as commentary here, and on the upstream bug report by Cole indicate a fix has been commit that improves this performance. ** Package changed: qemu-kvm (Ubuntu) = libvirt (Ubuntu) ** Also affects: libvirt via https://bugzilla.redhat.com/show_bug.cgi?id=599091 Importance: Unknown Status: Unknown -- virsh save is very slow https://bugs.launchpad.net/bugs/524447 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in libvirt virtualization API: Unknown Status in QEMU: Invalid Status in “libvirt” package in Ubuntu: Confirmed Bug description: As reported here: http://www.redhat.com/archives/libvir-list/2009-December/msg00203.html virsh save is very slow - it writes the image at around 1MB/sec on my test system. (I think I saw a bug report for this issue on Fedora's bugzilla, but I can't find it now...) Confirmed under Karmic.
[Qemu-devel] [Bug 524447] Re: virsh save is very slow
Re-introducing qemu-kvm, as commentary on qemu-devel mailing list suggest there could be a timing concern meaning poor performance. Leaving Libvirt on this report, as upstream libvirt have quoted improved performance adjusting the block size for dd. However, Qemu feel that the real issue is in the qemu/kvm code. Thanks. ** Also affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu-kvm (Ubuntu) Status: New = Confirmed ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided = Wishlist -- virsh save is very slow https://bugs.launchpad.net/bugs/524447 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in libvirt virtualization API: Unknown Status in QEMU: Invalid Status in “libvirt” package in Ubuntu: Confirmed Status in “qemu-kvm” package in Ubuntu: Confirmed Bug description: As reported here: http://www.redhat.com/archives/libvir-list/2009-December/msg00203.html virsh save is very slow - it writes the image at around 1MB/sec on my test system. (I think I saw a bug report for this issue on Fedora's bugzilla, but I can't find it now...) Confirmed under Karmic.
[Qemu-devel] [Bug 391879] Re: migrate exec ignores exit status
This is a bug and has been reported upstream, it is unlikely to be fixed at the distribution level and therefore anyone interested in working on this bug should contribute a patch to the upstream project. This will then filter down to Ubuntu when it is merged mainline. Marking Won't Fix against the Ubuntu package. Thanks for reporting this bug. ** Changed in: qemu-kvm (Ubuntu) Status: Confirmed = Won't Fix -- migrate exec ignores exit status https://bugs.launchpad.net/bugs/391879 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in “qemu-kvm” package in Ubuntu: Won't Fix Bug description: Binary package hint: kvm Using migrate exec:cat foo; false in the monitor results in the state of the VM being written to foo, as expected, and the VM then being stopped. This is surprising, as I think it stands to reason that in case of a failed migrate-exec process, which is what a non-zero exit status implies to me, the VM should continue. == Version information $ lsb_release -rd Description:Ubuntu 9.04 Release:9.04 $ apt-cache policy kvm kvm: Installed: 1:84+dfsg-0ubuntu11 Candidate: 1:84+dfsg-0ubuntu11 Version table: *** 1:84+dfsg-0ubuntu11 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status
[Qemu-devel] [Bug 241119] Re: usb_add of a Creative ZEN unrecognized in guest
** Also affects: qemu Importance: Undecided Status: New -- usb_add of a Creative ZEN unrecognized in guest https://bugs.launchpad.net/bugs/241119 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in “qemu-kvm” package in Ubuntu: Confirmed Bug description: Binary package hint: kvm This happens when I add my Creative ZEN to a virtual machine running XP. The device is recognised well at first and drivers are installed correctly. But when trying to connect windows crashes with the classic blue screen It complains about something like usbohci.sys, I can't read well because it crashes too fast. I have also tried with another virtual machine running Vista, same results. Any help would be really appreciated! I'm using the module kvm-amd with Ubuntu 8.04 The USB device has the following ID: 041e:4157 Creative Technology, Ltd kvm: Installed: 1:62+dfsg-0ubuntu7 Candidate: 1:62+dfsg-0ubuntu7 Version table: *** 1:62+dfsg-0ubuntu7 0 500 http://archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status
