[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
Works for me. F31 KVM guest is installing on Q9550 box.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
Invalid
Status in qemu package in Ubuntu:
Invalid
Status in seabios package in Ubuntu:
Fix Released
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
Verification new packages to be installed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
Log file for f31wks guest
** Attachment added: "Log file for f31wks guest"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337553/+files/fedora31wks.log
** Attachment removed: "PPA packages installed"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337552/+files/report.install.ppa
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
** Attachment added: "Check PPA [2} installed"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337555/+files/ppa2installed.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
No luck when testing [2]. Reports are attached
** Attachment added: "PPA packages installed"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337552/+files/report.install.ppa
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
Seems to work fine on i4790 (Haswell) box.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
Penryn's architecture confirmed
** Attachment added: "/proc/cpuinfo file uploaded"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336211/+files/cpuinfo.penryn
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
Done on Penryn's box
** Attachment added: "Requested reporting submitted"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336044/+files/Penryn.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
Thanks a lot . I will do it at my earliest convenience this night.
Haswell i4770 is installed on small server 32 GB. Department's policy
doesn't allow me to test Ubuntu whichever release on bare metal. I
could test only on outdated CPU's box and it seems to be a core reason.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
I've got the same issue starting guest via virt-install even with serial
console.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
Reproduced via attempt to install KVM Guest F31 Server on Ubuntu 20.04
(bare metal)
** Attachment added: "/var/log/libvirt/qemu/fedora31.log - attempt to launch
F31 Server VM via Virt-manager on Ubuntu 20.04"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336017/+files/fedora31.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package in Ubuntu:
Incomplete
Bug description:
Symptom:
Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in
resume
self._backend.resume()
File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume
if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self)
libvirt.libvirtError: internal error: unable to execute QEMU command 'cont':
Resetting the Virtual Machine is required
---
As outlined here:
https://bugs.launchpad.net/qemu/+bug/1813165/comments/15
After upgrade, all KVM guests are in a default pause state. Even after
forcing them off via virsh, and restarting them the guests are paused.
These Guests are not nested.
A lot of diganostic information are outlined in the previous bug
report link provided. The solution mentioned in previous report had
been allegedly integrated into the downstream updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
[Qemu-devel] [Bug 1063281] Re: qemu-kvm-1.2.0+noroms cannot be rebuilt with spice and usb redirection enabled at a time
** Project changed: qemu = qemu-kvm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1063281
Title:
qemu-kvm-1.2.0+noroms cannot be rebuilt with spice and usb redirection
enabled at a time
Status in qemu-kvm:
New
Bug description:
View:-
https://launchpad.net/~bderzhavets/+archive/lib-usbredir89
Fragment from debian/control
Source: qemu-kvm
Section: misc
Priority: optional
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
XSBC-Original-Maintainer: Michael Tokarev m...@tls.msk.ru
Uploaders: Guido Günther a...@sigxcpu.org, Jan Lübbe jlue...@debian.org
Build-Depends: debhelper (= 8), pkg-config, texinfo, python,
libaio-dev,
libasound2-dev,
libattr1-dev,
libbluetooth-dev,
libbrlapi-dev,
libcap-dev,
libcurl4-gnutls-dev,
libglib2.0-dev,
libgnutls-dev,
libjpeg-dev,
libncurses5-dev,
libpci-dev,
libpulse-dev,
libpng12-dev,
libspice-server-dev (= 0.10.1),
libspice-protocol-dev (= 0.10.1),
librados-dev, librbd-dev,
libsasl2-dev,
libsdl1.2-dev,
libusbredirhost-dev,
linux-libc-dev (= 2.6.32),
uuid-dev,
xfslibs-dev,
zlib1g-dev,
device-tree-compiler [powerpc],
libfdt-dev [powerpc]
Fragment from build log :-
https://launchpadlibrarian.net/118497302/buildlog_ubuntu-quantal-amd64.qemu-kvm_1.2.0%2Bnoroms-1ubuntu4_BUILDING.txt.gz
mkdir -p build/
cd build ../configure \
--with-pkgversion=qemu-kvm-1.2.0+noroms-1ubuntu4, Debian \
--target-list=x86_64-softmmu i386-softmmu x86_64-linux-user
i386-linux-user \
--prefix=/usr \
--with-confsuffix=/qemu \
--datadir=/usr/share \
--sysconfdir=/etc \
--libexecdir=/usr/lib \
--extra-cflags=-g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2
-Wall \
--extra-ldflags=-Wl,-Bsymbolic-functions -Wl,-z,relro \
--disable-strip \
--disable-xen \
--disable-guest-agent \
--enable-spice \
--enable-usb-redir \
--audio-drv-list=pa,alsa,sdl,oss \
--enable-docs \
--audio-card-list=ac97 es1370 sb16 cs4231a adlib gus hda \
`sed 's/#.*//' ../debian/optional-features` \
--enable-kvm --disable-blobs \
\
|| { echo == config.log ==; cat config.log; echo == config.log end
==; exit 1; }
Install prefix/usr
BIOS directory/usr/share/qemu
..
spice support yes
rbd support yes
xfsctl supportyes
nss used no
usb net redir no
OpenGL supportno
libiscsi support no
build guest agent no
seccomp support no
..
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu-kvm/+bug/1063281/+subscriptions
[Qemu-devel] [Bug 1063281] [NEW] qemu-kvm-1.2.0+noroms cannot be rebuilt with spice and usb redirection enabled at a time
Public bug reported:
View:-
https://launchpad.net/~bderzhavets/+archive/lib-usbredir89
Fragment from debian/control
Source: qemu-kvm
Section: misc
Priority: optional
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
XSBC-Original-Maintainer: Michael Tokarev m...@tls.msk.ru
Uploaders: Guido Günther a...@sigxcpu.org, Jan Lübbe jlue...@debian.org
Build-Depends: debhelper (= 8), pkg-config, texinfo, python,
libaio-dev,
libasound2-dev,
libattr1-dev,
libbluetooth-dev,
libbrlapi-dev,
libcap-dev,
libcurl4-gnutls-dev,
libglib2.0-dev,
libgnutls-dev,
libjpeg-dev,
libncurses5-dev,
libpci-dev,
libpulse-dev,
libpng12-dev,
libspice-server-dev (= 0.10.1),
libspice-protocol-dev (= 0.10.1),
librados-dev, librbd-dev,
libsasl2-dev,
libsdl1.2-dev,
libusbredirhost-dev,
linux-libc-dev (= 2.6.32),
uuid-dev,
xfslibs-dev,
zlib1g-dev,
device-tree-compiler [powerpc],
libfdt-dev [powerpc]
Fragment from build log :-
https://launchpadlibrarian.net/118497302/buildlog_ubuntu-quantal-amd64.qemu-kvm_1.2.0%2Bnoroms-1ubuntu4_BUILDING.txt.gz
mkdir -p build/
cd build ../configure \
--with-pkgversion=qemu-kvm-1.2.0+noroms-1ubuntu4, Debian \
--target-list=x86_64-softmmu i386-softmmu x86_64-linux-user
i386-linux-user \
--prefix=/usr \
--with-confsuffix=/qemu \
--datadir=/usr/share \
--sysconfdir=/etc \
--libexecdir=/usr/lib \
--extra-cflags=-g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2
-Wall \
--extra-ldflags=-Wl,-Bsymbolic-functions -Wl,-z,relro \
--disable-strip \
--disable-xen \
--disable-guest-agent \
--enable-spice \
--enable-usb-redir \
--audio-drv-list=pa,alsa,sdl,oss \
--enable-docs \
--audio-card-list=ac97 es1370 sb16 cs4231a adlib gus hda \
`sed 's/#.*//' ../debian/optional-features` \
--enable-kvm --disable-blobs \
\
|| { echo == config.log ==; cat config.log; echo == config.log end
==; exit 1; }
Install prefix/usr
BIOS directory/usr/share/qemu
..
spice support yes
rbd support yes
xfsctl supportyes
nss used no
usb net redir no
OpenGL supportno
libiscsi support no
build guest agent no
seccomp support no
..
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1063281
Title:
qemu-kvm-1.2.0+noroms cannot be rebuilt with spice and usb redirection
enabled at a time
Status in QEMU:
New
Bug description:
View:-
https://launchpad.net/~bderzhavets/+archive/lib-usbredir89
Fragment from debian/control
Source: qemu-kvm
Section: misc
Priority: optional
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
XSBC-Original-Maintainer: Michael Tokarev m...@tls.msk.ru
Uploaders: Guido Günther a...@sigxcpu.org, Jan Lübbe jlue...@debian.org
Build-Depends: debhelper (= 8), pkg-config, texinfo, python,
libaio-dev,
libasound2-dev,
libattr1-dev,
libbluetooth-dev,
libbrlapi-dev,
libcap-dev,
libcurl4-gnutls-dev,
libglib2.0-dev,
libgnutls-dev,
libjpeg-dev,
libncurses5-dev,
libpci-dev,
libpulse-dev,
libpng12-dev,
libspice-server-dev (= 0.10.1),
libspice-protocol-dev (= 0.10.1),
librados-dev, librbd-dev,
libsasl2-dev,
libsdl1.2-dev,
libusbredirhost-dev,
linux-libc-dev (= 2.6.32),
uuid-dev,
xfslibs-dev,
zlib1g-dev,
device-tree-compiler [powerpc],
libfdt-dev [powerpc]
Fragment from build log :-
https://launchpadlibrarian.net/118497302/buildlog_ubuntu-quantal-amd64.qemu-kvm_1.2.0%2Bnoroms-1ubuntu4_BUILDING.txt.gz
mkdir -p build/
cd build ../configure \
--with-pkgversion=qemu-kvm-1.2.0+noroms-1ubuntu4, Debian \
--target-list=x86_64-softmmu i386-softmmu x86_64-linux-user
i386-linux-user \
--prefix=/usr \
--with-confsuffix=/qemu \
--datadir=/usr/share \
--sysconfdir=/etc \
--libexecdir=/usr/lib \
--extra-cflags=-g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2
-Wall \
--extra-ldflags=-Wl,-Bsymbolic-functions -Wl,-z,relro \
--disable-strip \
--disable-xen \
--disable-guest-agent \
--enable-spice \
--enable-usb-redir \
--audio-drv-list=pa,alsa,sdl,oss \
--enable-docs \
--audio-card-list=ac97 es1370 sb16 cs4231a adlib gus hda \
`sed 's/#.*//'
[Qemu-devel] [Bug 998435] Re: qemu-kvm-spice doesn't support spice/qxl installs
Serge, I suspect this was meant to only affect the ubuntu qemu-kvm-spice (and related) packages, not upstream qemu, right? I believe it's not a problem to verify. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/998435 Title: qemu-kvm-spice doesn't support spice/qxl installs Status in QEMU: Confirmed Status in “qemu-kvm-spice” package in Ubuntu: Confirmed Bug description: Been setup as follows :- boris@boris-P5Q-E:~$ dpkg -l | grep spice ii gir1.2-spice-client-glib-2.0 0.9-0ubuntu1 GObject for communicating with Spice servers (GObject-Introspection) ii gir1.2-spice-client-gtk-2.00.9-0ubuntu1 GTK2 widget for SPICE clients (GObject-Introspection) ii gir1.2-spice-client-gtk-3.00.9-0ubuntu1 GTK3 widget for SPICE clients (GObject-Introspection) ii libspice-client-glib-2.0-1 0.9-0ubuntu1 GObject for communicating with Spice servers (runtime library) ii libspice-client-glib-2.0-dev 0.9-0ubuntu1 GObject for communicating with Spice servers (development files) ii libspice-client-gtk-2.0-1 0.9-0ubuntu1 GTK2 widget for SPICE clients (runtime library) ii libspice-client-gtk-2.0-dev0.9-0ubuntu1 GTK2 widget for SPICE clients (development files) ii libspice-client-gtk-3.0-1 0.9-0ubuntu1 GTK3 widget for SPICE clients (runtime library) ii libspice-client-gtk-3.0-dev0.9-0ubuntu1 GTK3 widget for SPICE clients (development files) ii libspice-protocol-dev 0.10.1-1 SPICE protocol headers ii libspice-server-dev0.10.0-1 Header files and development documentation for spice-server ii libspice-server1 0.10.0-1 Implements the server side of the SPICE protocol ii python-spice-client-gtk0.9-0ubuntu1 GTK2 widget for SPICE clients (Python binding) ii qemu-kvm-spice 1.0.50-2012.03-0ubuntu2 Full virtualization on amd64 hardware Spice/QXL install doesn't work on Ubuntu 12.04 . View also https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494 It doesn't look like duplicate of bug mentioned above. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/998435/+subscriptions
[Qemu-devel] [Bug 998435] Re: qemu-kvm-spice doesn't support spice/qxl installs
Alon, I testedF16 and W7. Installs attempted via VIrtManager (spice/qx l, spice/vga) poped up black screen for ever. F17 (beta) requires several minutes to activate SPICE/QXL install window, and behaves same way during runtime. Any Spice-Gtk build mentioned in #1 does it in few seconds doing F17 (beta) install ( runtime). As wrote MikeB ( view https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494) just spice/cirrus work for install and runtime in case of W7. I also believe there is an issue in spice-gtk 0.9 build via Debian Unstable. It has nothing to do with spice enabled qemu version. All my spice-gtk builds for ubuntu 12.04 mentioned in #1 are done in different way and work fine. Thanks, Boris -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/998435 Title: qemu-kvm-spice doesn't support spice/qxl installs Status in QEMU: New Bug description: Been setup as follows :- boris@boris-P5Q-E:~$ dpkg -l | grep spice ii gir1.2-spice-client-glib-2.0 0.9-0ubuntu1 GObject for communicating with Spice servers (GObject-Introspection) ii gir1.2-spice-client-gtk-2.00.9-0ubuntu1 GTK2 widget for SPICE clients (GObject-Introspection) ii gir1.2-spice-client-gtk-3.00.9-0ubuntu1 GTK3 widget for SPICE clients (GObject-Introspection) ii libspice-client-glib-2.0-1 0.9-0ubuntu1 GObject for communicating with Spice servers (runtime library) ii libspice-client-glib-2.0-dev 0.9-0ubuntu1 GObject for communicating with Spice servers (development files) ii libspice-client-gtk-2.0-1 0.9-0ubuntu1 GTK2 widget for SPICE clients (runtime library) ii libspice-client-gtk-2.0-dev0.9-0ubuntu1 GTK2 widget for SPICE clients (development files) ii libspice-client-gtk-3.0-1 0.9-0ubuntu1 GTK3 widget for SPICE clients (runtime library) ii libspice-client-gtk-3.0-dev0.9-0ubuntu1 GTK3 widget for SPICE clients (development files) ii libspice-protocol-dev 0.10.1-1 SPICE protocol headers ii libspice-server-dev0.10.0-1 Header files and development documentation for spice-server ii libspice-server1 0.10.0-1 Implements the server side of the SPICE protocol ii python-spice-client-gtk0.9-0ubuntu1 GTK2 widget for SPICE clients (Python binding) ii qemu-kvm-spice 1.0.50-2012.03-0ubuntu2 Full virtualization on amd64 hardware Spice/QXL install doesn't work on Ubuntu 12.04 . View also https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494 It doesn't look like duplicate of bug mentioned above. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/998435/+subscriptions
[Qemu-devel] [Bug 998435] Re: qemu-kvm-spice doesn't support spice/qxl installs
It has nothing to do with spice enabled qemu version. Not exactly :- boris@boris-P5Q-E:~$ sudo /usr/bin/kvm-spice -cpu host -enable-kvm -name W7 -m 2048 -drive file=/dev/sda7,if=virtio,media=disk,aio=native,cache=off -net nic,model=rtl8139 -net user -localtime -usb -vga qxl -spice port=5900 ,disable-ticketing -cdrom /home/boris/win7.iso -boot d do_spice_init: starting 0.10.0 spice_server_add_interface: SPICE_INTERFACE_MIGRATION spice_server_add_interface: SPICE_INTERFACE_KEYBOARD spice_server_add_interface: SPICE_INTERFACE_MOUSE Could not open option rom 'kvmvapic.bin': No such file or directory spice_server_add_interface: SPICE_INTERFACE_QXL red_worker_main: begin ensure_display_channel_created: create display channel ensure_cursor_channel_created: create cursor channel -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/998435 Title: qemu-kvm-spice doesn't support spice/qxl installs Status in QEMU: New Bug description: Been setup as follows :- boris@boris-P5Q-E:~$ dpkg -l | grep spice ii gir1.2-spice-client-glib-2.0 0.9-0ubuntu1 GObject for communicating with Spice servers (GObject-Introspection) ii gir1.2-spice-client-gtk-2.00.9-0ubuntu1 GTK2 widget for SPICE clients (GObject-Introspection) ii gir1.2-spice-client-gtk-3.00.9-0ubuntu1 GTK3 widget for SPICE clients (GObject-Introspection) ii libspice-client-glib-2.0-1 0.9-0ubuntu1 GObject for communicating with Spice servers (runtime library) ii libspice-client-glib-2.0-dev 0.9-0ubuntu1 GObject for communicating with Spice servers (development files) ii libspice-client-gtk-2.0-1 0.9-0ubuntu1 GTK2 widget for SPICE clients (runtime library) ii libspice-client-gtk-2.0-dev0.9-0ubuntu1 GTK2 widget for SPICE clients (development files) ii libspice-client-gtk-3.0-1 0.9-0ubuntu1 GTK3 widget for SPICE clients (runtime library) ii libspice-client-gtk-3.0-dev0.9-0ubuntu1 GTK3 widget for SPICE clients (development files) ii libspice-protocol-dev 0.10.1-1 SPICE protocol headers ii libspice-server-dev0.10.0-1 Header files and development documentation for spice-server ii libspice-server1 0.10.0-1 Implements the server side of the SPICE protocol ii python-spice-client-gtk0.9-0ubuntu1 GTK2 widget for SPICE clients (Python binding) ii qemu-kvm-spice 1.0.50-2012.03-0ubuntu2 Full virtualization on amd64 hardware Spice/QXL install doesn't work on Ubuntu 12.04 . View also https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494 It doesn't look like duplicate of bug mentioned above. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/998435/+subscriptions
[Qemu-devel] [Bug 998435] Re: qemu-kvm-spice doesn't support spice/qxl installs
Normal start in my system :- boris@boris-System-Product-P5Q3:~$ sudo /usr/bin/kvm -cpu host -enable-kvm -name WIN7 -m 2048 -drive file=/dev/sda7,if=ide,media=disk,aio=native,cache=off -net nic,model=rtl8139 -net user -localtime -usb -vga qxl -spice port=5900,disable-ticketing -cdrom /home/boris/win7.iso -boot d do_spice_init: starting 0.10.1 spice_server_add_interface: SPICE_INTERFACE_MIGRATION spice_server_add_interface: SPICE_INTERFACE_KEYBOARD spice_server_add_interface: SPICE_INTERFACE_MOUSE spice_server_add_interface: SPICE_INTERFACE_QXL red_worker_main: begin display_channel_create: create display channel cursor_channel_create: create cursor channel -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/998435 Title: qemu-kvm-spice doesn't support spice/qxl installs Status in QEMU: New Bug description: Been setup as follows :- boris@boris-P5Q-E:~$ dpkg -l | grep spice ii gir1.2-spice-client-glib-2.0 0.9-0ubuntu1 GObject for communicating with Spice servers (GObject-Introspection) ii gir1.2-spice-client-gtk-2.00.9-0ubuntu1 GTK2 widget for SPICE clients (GObject-Introspection) ii gir1.2-spice-client-gtk-3.00.9-0ubuntu1 GTK3 widget for SPICE clients (GObject-Introspection) ii libspice-client-glib-2.0-1 0.9-0ubuntu1 GObject for communicating with Spice servers (runtime library) ii libspice-client-glib-2.0-dev 0.9-0ubuntu1 GObject for communicating with Spice servers (development files) ii libspice-client-gtk-2.0-1 0.9-0ubuntu1 GTK2 widget for SPICE clients (runtime library) ii libspice-client-gtk-2.0-dev0.9-0ubuntu1 GTK2 widget for SPICE clients (development files) ii libspice-client-gtk-3.0-1 0.9-0ubuntu1 GTK3 widget for SPICE clients (runtime library) ii libspice-client-gtk-3.0-dev0.9-0ubuntu1 GTK3 widget for SPICE clients (development files) ii libspice-protocol-dev 0.10.1-1 SPICE protocol headers ii libspice-server-dev0.10.0-1 Header files and development documentation for spice-server ii libspice-server1 0.10.0-1 Implements the server side of the SPICE protocol ii python-spice-client-gtk0.9-0ubuntu1 GTK2 widget for SPICE clients (Python binding) ii qemu-kvm-spice 1.0.50-2012.03-0ubuntu2 Full virtualization on amd64 hardware Spice/QXL install doesn't work on Ubuntu 12.04 . View also https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494 It doesn't look like duplicate of bug mentioned above. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/998435/+subscriptions
[Qemu-devel] [Bug 998435] Re: qemu-kvm-spice doesn't support spice/qxl installs
Spice/VGA install doesn't work as well . It's not duplicate https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/998435 Title: qemu-kvm-spice doesn't support spice/qxl installs Status in QEMU: New Bug description: Been setup as follows :- boris@boris-P5Q-E:~$ dpkg -l | grep spice ii gir1.2-spice-client-glib-2.0 0.9-0ubuntu1 GObject for communicating with Spice servers (GObject-Introspection) ii gir1.2-spice-client-gtk-2.00.9-0ubuntu1 GTK2 widget for SPICE clients (GObject-Introspection) ii gir1.2-spice-client-gtk-3.00.9-0ubuntu1 GTK3 widget for SPICE clients (GObject-Introspection) ii libspice-client-glib-2.0-1 0.9-0ubuntu1 GObject for communicating with Spice servers (runtime library) ii libspice-client-glib-2.0-dev 0.9-0ubuntu1 GObject for communicating with Spice servers (development files) ii libspice-client-gtk-2.0-1 0.9-0ubuntu1 GTK2 widget for SPICE clients (runtime library) ii libspice-client-gtk-2.0-dev0.9-0ubuntu1 GTK2 widget for SPICE clients (development files) ii libspice-client-gtk-3.0-1 0.9-0ubuntu1 GTK3 widget for SPICE clients (runtime library) ii libspice-client-gtk-3.0-dev0.9-0ubuntu1 GTK3 widget for SPICE clients (development files) ii libspice-protocol-dev 0.10.1-1 SPICE protocol headers ii libspice-server-dev0.10.0-1 Header files and development documentation for spice-server ii libspice-server1 0.10.0-1 Implements the server side of the SPICE protocol ii python-spice-client-gtk0.9-0ubuntu1 GTK2 widget for SPICE clients (Python binding) ii qemu-kvm-spice 1.0.50-2012.03-0ubuntu2 Full virtualization on amd64 hardware Spice/QXL install doesn't work on Ubuntu 12.04 . View also https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494 It doesn't look like duplicate of bug mentioned above. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/998435/+subscriptions
[Qemu-devel] [Bug 998435] Re: qemu-kvm-spice doesn't support spice/qxl installs
Samples of working PPAs may be viewed at :- https://launchpad.net/~bderzhavets/+archive/lib-usbredir67 - spice-gtk 0.9 https://launchpad.net/~bderzhavets/+archive/lib-usbredir71 - spice-gtk 0.11 https://launchpad.net/~bderzhavets/+archive/lib-usbredir73 - spice-gtk 0.12 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/998435 Title: qemu-kvm-spice doesn't support spice/qxl installs Status in QEMU: New Bug description: Been setup as follows :- boris@boris-P5Q-E:~$ dpkg -l | grep spice ii gir1.2-spice-client-glib-2.0 0.9-0ubuntu1 GObject for communicating with Spice servers (GObject-Introspection) ii gir1.2-spice-client-gtk-2.00.9-0ubuntu1 GTK2 widget for SPICE clients (GObject-Introspection) ii gir1.2-spice-client-gtk-3.00.9-0ubuntu1 GTK3 widget for SPICE clients (GObject-Introspection) ii libspice-client-glib-2.0-1 0.9-0ubuntu1 GObject for communicating with Spice servers (runtime library) ii libspice-client-glib-2.0-dev 0.9-0ubuntu1 GObject for communicating with Spice servers (development files) ii libspice-client-gtk-2.0-1 0.9-0ubuntu1 GTK2 widget for SPICE clients (runtime library) ii libspice-client-gtk-2.0-dev0.9-0ubuntu1 GTK2 widget for SPICE clients (development files) ii libspice-client-gtk-3.0-1 0.9-0ubuntu1 GTK3 widget for SPICE clients (runtime library) ii libspice-client-gtk-3.0-dev0.9-0ubuntu1 GTK3 widget for SPICE clients (development files) ii libspice-protocol-dev 0.10.1-1 SPICE protocol headers ii libspice-server-dev0.10.0-1 Header files and development documentation for spice-server ii libspice-server1 0.10.0-1 Implements the server side of the SPICE protocol ii python-spice-client-gtk0.9-0ubuntu1 GTK2 widget for SPICE clients (Python binding) ii qemu-kvm-spice 1.0.50-2012.03-0ubuntu2 Full virtualization on amd64 hardware Spice/QXL install doesn't work on Ubuntu 12.04 . View also https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494 It doesn't look like duplicate of bug mentioned above. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/998435/+subscriptions
[Qemu-devel] [Bug 998435] [NEW] qemu-kvm-spice doesn't support spice/qxl installs
Public bug reported: Been setup as follows :- boris@boris-P5Q-E:~$ dpkg -l | grep spice ii gir1.2-spice-client-glib-2.0 0.9-0ubuntu1 GObject for communicating with Spice servers (GObject-Introspection) ii gir1.2-spice-client-gtk-2.00.9-0ubuntu1 GTK2 widget for SPICE clients (GObject-Introspection) ii gir1.2-spice-client-gtk-3.00.9-0ubuntu1 GTK3 widget for SPICE clients (GObject-Introspection) ii libspice-client-glib-2.0-1 0.9-0ubuntu1 GObject for communicating with Spice servers (runtime library) ii libspice-client-glib-2.0-dev 0.9-0ubuntu1 GObject for communicating with Spice servers (development files) ii libspice-client-gtk-2.0-1 0.9-0ubuntu1 GTK2 widget for SPICE clients (runtime library) ii libspice-client-gtk-2.0-dev0.9-0ubuntu1 GTK2 widget for SPICE clients (development files) ii libspice-client-gtk-3.0-1 0.9-0ubuntu1 GTK3 widget for SPICE clients (runtime library) ii libspice-client-gtk-3.0-dev0.9-0ubuntu1 GTK3 widget for SPICE clients (development files) ii libspice-protocol-dev 0.10.1-1 SPICE protocol headers ii libspice-server-dev0.10.0-1 Header files and development documentation for spice-server ii libspice-server1 0.10.0-1 Implements the server side of the SPICE protocol ii python-spice-client-gtk0.9-0ubuntu1 GTK2 widget for SPICE clients (Python binding) ii qemu-kvm-spice 1.0.50-2012.03-0ubuntu2 Full virtualization on amd64 hardware Spice/QXL install doesn't work on Ubuntu 12.04 . View also https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494 It doesn't look like duplicate of bug mentioned above. ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/998435 Title: qemu-kvm-spice doesn't support spice/qxl installs Status in QEMU: New Bug description: Been setup as follows :- boris@boris-P5Q-E:~$ dpkg -l | grep spice ii gir1.2-spice-client-glib-2.0 0.9-0ubuntu1 GObject for communicating with Spice servers (GObject-Introspection) ii gir1.2-spice-client-gtk-2.00.9-0ubuntu1 GTK2 widget for SPICE clients (GObject-Introspection) ii gir1.2-spice-client-gtk-3.00.9-0ubuntu1 GTK3 widget for SPICE clients (GObject-Introspection) ii libspice-client-glib-2.0-1 0.9-0ubuntu1 GObject for communicating with Spice servers (runtime library) ii libspice-client-glib-2.0-dev 0.9-0ubuntu1 GObject for communicating with Spice servers (development files) ii libspice-client-gtk-2.0-1 0.9-0ubuntu1 GTK2 widget for SPICE clients (runtime library) ii libspice-client-gtk-2.0-dev0.9-0ubuntu1 GTK2 widget for SPICE clients (development files) ii libspice-client-gtk-3.0-1 0.9-0ubuntu1 GTK3 widget for SPICE clients (runtime library) ii libspice-client-gtk-3.0-dev0.9-0ubuntu1 GTK3 widget for SPICE clients (development files) ii libspice-protocol-dev 0.10.1-1 SPICE protocol headers ii libspice-server-dev0.10.0-1 Header files and development documentation for spice-server ii libspice-server1 0.10.0-1 Implements the server side of the SPICE protocol ii python-spice-client-gtk0.9-0ubuntu1 GTK2 widget for SPICE clients (Python binding) ii qemu-kvm-spice 1.0.50-2012.03-0ubuntu2 Full virtualization on amd64 hardware Spice/QXL install doesn't work on Ubuntu 12.04 . View also https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494 It doesn't look like duplicate of bug mentioned above. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/998435/+subscriptions
[Qemu-devel] [Bug 811593] [NEW] Loading kernel 3.0.0-5-generic under Xen 4.1 doesn't create /dev/xen/gntdev
Public bug reported: To fix the issue i added to /etc/modules : xen-gntdev xen-netback xen-blkback Otherwise , lsmod | grep xen doesn't report all three of them loaded. It's impossible to create PV domain. Usual report vif(0) cannot be connected, hotplug scripts not working I would guess system kernel' s .config is incorrect. Working configuration (after Dom0 kernel gets loaded) should look like : # ls -l /dev/xen total 0 crw--- 1 root root 10, 55 2011-07-16 18:33 evtchn crw--- 1 root root 10, 56 2011-07-16 18:33 gntdev # lsmod | grep xen xen_evtchn 13172 1 xenfs 18311 1 xen_blkback23177 0 [permanent] xen_netback27854 0 [permanent] xen_gntdev 17676 0 ** Affects: ubuntu-xen Importance: Undecided Status: New ** Summary changed: - Loading kernel 3.0.0-5-generic under Xen 4.1 doesn't create /dev/xen/gnttab + Loading kernel 3.0.0-5-generic under Xen 4.1 doesn't create /dev/xen/gntdev ** Description changed: To fix the issue i added to /etc/modules : xen-gntdev xen-netback xen-blkback Otherwise , lsmod | grep xen doesn't report all three of them loaded. It's impossible to create PV domain. Usual report vif(0) cannot be connected, hotplug scripts not working I would guess system kernel' s .config is incorrect. - Working config should look like : + Working configuration (after Dom0 kernel gets loaded) should look like : # ls -l /dev/xen total 0 crw--- 1 root root 10, 55 2011-07-16 18:33 evtchn crw--- 1 root root 10, 56 2011-07-16 18:33 gntdev # lsmod | grep xen - xen_evtchn 13172 1 - xenfs 18311 1 + xen_evtchn 13172 1 + xenfs 18311 1 xen_blkback23177 0 [permanent] xen_netback27854 0 [permanent] xen_gntdev 17676 0 ** Project changed: qemu = ubuntu-xen -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/811593 Title: Loading kernel 3.0.0-5-generic under Xen 4.1 doesn't create /dev/xen/gntdev Status in Xen for Ubuntu: New Bug description: To fix the issue i added to /etc/modules : xen-gntdev xen-netback xen-blkback Otherwise , lsmod | grep xen doesn't report all three of them loaded. It's impossible to create PV domain. Usual report vif(0) cannot be connected, hotplug scripts not working I would guess system kernel' s .config is incorrect. Working configuration (after Dom0 kernel gets loaded) should look like : # ls -l /dev/xen total 0 crw--- 1 root root 10, 55 2011-07-16 18:33 evtchn crw--- 1 root root 10, 56 2011-07-16 18:33 gntdev # lsmod | grep xen xen_evtchn 13172 1 xenfs 18311 1 xen_blkback23177 0 [permanent] xen_netback27854 0 [permanent] xen_gntdev 17676 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-xen/+bug/811593/+subscriptions
[Qemu-devel] [Bug 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
@Serge, I am getting error when build in PPA :- make[2]: Entering directory `/build/buildd/spice-gtk-0.6/po' cd .. \ CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \ /bin/bash ./config.status config.status: creating po/Makefile.in ./config.status: line 1509: gawk: command not found = ?? config.status: error: could not create po/Makefile.in make[2]: *** [stamp-it] Error 127 make[2]: Leaving directory `/build/buildd/spice-gtk-0.6/po' make[1]: *** [distclean-recursive] Error 1 make[1]: Leaving directory `/build/buildd/spice-gtk-0.6' dh_auto_clean: make -j1 distclean returned exit code 2 make: *** [clean] Error 29 dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules clean gave error exit status 2 Locally it doesn't happen. # which gawk /usr/bin/gawk -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
apt-get install gobject-introspection libgirepository1.0-dev ./configure --prefix=/usr --build=x86_64-linux-gnu \ --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share \ --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/bin \ --with-python --disable-static --enable-introspection . . . . . . Spice-Gtk 0.6 == prefix: /usr c compiler: gcc -std=gnu99 c++ compiler: g++ Coroutine:ucontext Audio:pulse Target: SASL support: yes Gtk: 2.0 Now type 'make' to build spice-gtk make checkinstall --install=no dpkg -i --force-overwrite ./spice-gtk_0.6-1_amd64.deb Libraries and binaries been overwritten are exactly the same as before. Spice session via Virt-Manager ( video qxl) is manageable via keyboard before logging in (F14,Natty VM's). Mouse pointer appears and works stable during all the time after login. -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
# dpkg -i --force-overwrite ./spice-gtk_0.6-1_amd64.deb Generates :- root@boris-System-P5Q3:/usr/src/SPICE_GTK_0.6/WORK/usr# ls -CR .: bin include lib share ./bin: snappy spicy ./include: spice-client-glib-2.0 spice-client-gtk-2.0 spice-controller ./include/spice-client-glib-2.0: channel-cursor.h channel-main.h spice-audio.h spice-client.h spice-types.h channel-display.h channel-playback.h spice-channel-enums.h spice-glib-enums.h spice-util.h channel-inputs.h channel-record.hspice-channel.hspice-session.h ./include/spice-client-gtk-2.0: spice-grabsequence.h spice-widget-enums.h spice-widget.h ./include/spice-controller: spice-controller.h ./lib: girepository-1.0 libspice-client-gtk-2.0.la libspice-controller.so libspice-client-glib-2.0.lalibspice-client-gtk-2.0.so libspice-controller.so.0 libspice-client-glib-2.0.solibspice-client-gtk-2.0.so.1 libspice-controller.so.0.0.0 libspice-client-glib-2.0.so.3 libspice-client-gtk-2.0.so.1.1.0 pkgconfig libspice-client-glib-2.0.so.3.0.2 libspice-controller.lapython2.7 ./lib/girepository-1.0: SpiceClientGLib-2.0.typelib SpiceClientGtk-2.0.typelib ./lib/pkgconfig: spice-client-glib-2.0.pc spice-client-gtk-2.0.pc spice-controller.pc ./lib/python2.7: dist-packages ./lib/python2.7/dist-packages: SpiceClientGtk.la SpiceClientGtk.so ./share: doc gir-1.0 gtk-doc locale vala ./share/doc: spice-gtk ./share/doc/spice-gtk: ABOUT-NLS AUTHORS COPYING doc NEWS README THANKS TODO ./share/doc/spice-gtk/doc: Makefile Makefile.am Makefile.in reference ./share/doc/spice-gtk/doc/reference: html Makefile.am spice-gtk-docs.xml spice-gtk-sections.txt Makefile Makefile.in spice-gtk-overrides.txt spice-gtk.types ./share/doc/spice-gtk/doc/reference/html: api-index-deprecated.html home.png SpiceChannel.html SpiceInputsChannel.html api-index-full.htmlindex.htmlSpiceCursorChannel.html SpiceMainChannel.html api-reference.html index.sgmlSpiceDisplayChannel.html SpicePlaybackChannel.html application-support.html left.png SpiceDisplay.html SpiceRecordChannel.html ch01.html object-tree.html spice-gtk.devhelp SpiceSession.html ch02.html right.png spice-gtk.devhelp2style.css ch03.html SpiceAudio.html spice-gtk-Utilities.html up.png ./share/gir-1.0: SpiceClientGLib-2.0.gir SpiceClientGtk-2.0.gir ./share/gtk-doc: html ./share/gtk-doc/html: spice-gtk ./share/gtk-doc/html/spice-gtk: api-index-deprecated.html home.png SpiceChannel.html SpiceInputsChannel.html api-index-full.htmlindex.htmlSpiceCursorChannel.html SpiceMainChannel.html api-reference.html index.sgmlSpiceDisplayChannel.html SpicePlaybackChannel.html application-support.html left.png SpiceDisplay.html SpiceRecordChannel.html ch01.html object-tree.html spice-gtk.devhelp SpiceSession.html ch02.html right.png spice-gtk.devhelp2style.css ch03.html SpiceAudio.html spice-gtk-Utilities.html up.png ./share/locale: fr ./share/locale/fr: LC_MESSAGES ./share/locale/fr/LC_MESSAGES: spice-gtk.mo ./share/vala: vapi ./share/vala/vapi: spice-protocol.vapi -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: spice-gtk-0.6-1ubuntu1_0.6-1_amd64.deb https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2138919/+files/spice-gtk-0.6-1ubuntu1_0.6-1_amd64.deb -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
PPA Building qemu-kvmspice based on current /virt/kvm/qemu-kvm.git for Ubuntu 11.04 :- https://launchpad.net/~bderzhavets/+archive/git-spice is ready . In meantime build is based on unstable mater branch. -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Also in meantime git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git contains commits:- commit 196a778428989217b82de042725dc8eb29c8f8d8 Author: Gerd Hoffmann kra...@redhat.com Date: Wed Apr 27 16:06:10 2011 +0200 spice: drop obsolete iothread locking We don't use qemu internals from spice server context any more. Thus we don't also need to grab the iothread mutex from spice server context. And we don't have to temporarely release the lock to avoid deadlocks. Drop all the calls. Signed-off-by: Gerd Hoffmann kra...@redhat.com commit 075360945860ad9bdd491921954b383bf762b0e5 Author: Gerd Hoffmann kra...@redhat.com Date: Wed Apr 27 15:50:32 2011 +0200 spice: don't call displaystate callbacks from spice server context. This patch moves the displaystate callback calls for setting the cursor and the mouse pointer from spice server to qemu (iothread) context. This allows us to simplify locking. Signed-off-by: Gerd Hoffmann kra...@redhat.com commit e0c64d08d11736dcea7c5a6373e3e7f62db51d9e Author: Gerd Hoffmann kra...@redhat.com Date: Wed Apr 27 15:21:51 2011 +0200 spice: don't create updates in spice server context. This patch moves the creation of spice screen updates from the spice server context to qemu iothread context (display refresh timer to be exact). This way we avoid accessing qemu internals (display surface) from spice thread context which in turn allows us to simplify locking. Signed-off-by: Gerd Hoffmann kra...@redhat.com commit 14da8345b2f7c21bab20fd12b755a61d6277f171 Author: Jes Sorensen jes.soren...@redhat.com Date: Tue Feb 1 15:53:23 2011 +0100 Make spice dummy functions inline to fix calls not checking return values qemu_spice_set_passwd() and qemu_spice_set_pw_expire() dummy functions needs to be inline, in order to handle the case where they are called without checking the return value. Signed-off-by: Jes Sorensen jes.soren...@redhat.com Signed-off-by: Gerd Hoffmann kra...@redhat.com So , git clone git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git creates a directory allows to build tar ball for debian qemu-kvm packages , which work with no QXL patching at all. -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: Packages been built https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2132690/+files/qemu-kvm_051711-0ubuntu1_amd64.deb -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: qemu_051711-0ubuntu1_amd64.deb https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2132691/+files/qemu_051711-0ubuntu1_amd64.deb -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: qemu-common_051711-0ubuntu1_all.deb https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2132692/+files/qemu-common_051711-0ubuntu1_all.deb -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
In this case, qemu-kvm and QEMU are very much related but this bug does not happen to affect QEMU. In meantime, yes due to the most recent 3 commits .View :- http://cgit.freedesktop.org/spice/qemu/log/?h=spice.v35 12 days spice: drop obsolete iothread lockingspice.v35 Gerd Hoffmann 2 -14/+0 12 days spice: don't call displaystate callbacks from spice server context. Gerd Hoffmann 4 -13/+29 12 days spice: don't create updates in spice server context. Gerd Hoffmann 3 -27/+54 -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Please, view one more time #50. -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
@Serge, I have a hard time stomaching '32-bit support was dropped'. Is there an archived mailing list message saying more about that? View: http://lists.freedesktop.org/archives/spice- devel/2010-November/001738.html Can you build a 32-bit package (on a 32-bit host) with -Werror? No. I cannot -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Responding # 56 qemu-kvm.c does not exist in QEMU. Changed in qemu: status: Confirmed → Invalid However , root@boris-System-P5Q3:~# lsmod | grep kvm kvm_intel 56851 8 kvm 367707 1 kvm_intel root@borus-System-P5Q3:~# virsh qemu-monitor-command --hmp VF15RC 'info kvm' kvm support: enabled Number 8 might decrease or en-crease when i stop and start domains. I will try upload snapshot -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: Snapshot 1 https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2128636/+files/KVM1.png -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: Snapshot 2 https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2128637/+files/KVM2.png -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
General directions i have been following :- http://www.linux- kvm.org/page/FAQ#How_can_I_check_that_I.27m_not_falling_back_to_QEMU_with_no_hardware_acceleration.3F How to access the QEMU monitor through libvirt View :- http://blog.vmsplice.net/2011/03/how-to-access-qemu-monitor-through.html -- 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: Invalid Status in “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
@Serge, I saw that. It doesn't happen when i extract source on local box via *.dsc file and build with 64-bit glibc. I would guess it was attempt to compile with 32-bit version of glibc. 32-bit support on spice.v35 was dropped. -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
I commited build in mentioned PPA via diff -Nru qemu-kvm-0.14.0+spice-v35/configure qemu-kvm-0.14.0+spicev35/configure --- qemu-kvm-0.14.0+spice-v35/configure 2011-05-12 05:36:32.0 + +++ qemu-kvm-0.14.0+spicev35/configure 2011-05-13 09:17:01.0 + @@ -2484,7 +2484,7 @@ if test -z $werror ; then if test $z_version = 50 -a \ $linux = yes ; then -werror=yes +werror=no else werror=no fi Actually , disabling -Werror to build qemu-common_0.14.0+spicev35-0ubuntu1_all.deb. qemu-kvm, qemu amd64 packages may be built with -Werror with no problems. Please , DON'T install packages from https://launchpad.net/~bderzhavets/+archive/git-spice in 32-bit environment. -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Finally, i got it. https://launchpadlibrarian.net/71622307/buildlog_ubuntu-natty-amd64 .qemu-kvm_0.14.0%2Bspicev35-0ubuntu1_BUILDING.txt.gz Log is clean https://launchpadlibrarian.net/71622306/buildlog_ubuntu-natty-i386.qemu- kvm_0.14.0%2Bspicev35-0ubuntu1_BUILDING.txt.gz qemu-common_0.14.0+spicev35-0ubuntu1_all.deb has nothing to do with -Werror chroot-autobuild/build/buildd/qemu-common_0.14.0+spicev35-0ubuntu1_all.deb: drwxr-xr-x root/root 0 2011-05-13 09:45 ./ drwxr-xr-x root/root 0 2011-05-13 09:45 ./usr/ drwxr-xr-x root/root 0 2011-05-13 09:45 ./usr/share/ drwxr-xr-x root/root 0 2011-05-13 09:45 ./usr/share/apport/ drwxr-xr-x root/root 0 2011-05-13 09:45 ./usr/share/apport/package-hooks/ -rw-r--r-- root/root 350 2011-05-13 09:15 ./usr/share/apport/package-hooks/source_qemu-kvm.py drwxr-xr-x root/root 0 2011-05-13 09:45 ./usr/share/qemu/ -rwxr-xr-x root/root 1024 2011-05-13 09:44 ./usr/share/qemu/multiboot.bin drwxr-xr-x root/root 0 2011-05-13 09:14 ./usr/share/qemu/keymaps/ -rw-r--r-- root/root 2587 2011-05-13 09:14 ./usr/share/qemu/keymaps/fr -rw-r--r-- root/root 2576 2011-05-13 09:14 ./usr/share/qemu/keymaps/no -rw-r--r-- root/root 1354 2011-05-13 09:14 ./usr/share/qemu/keymaps/pt-br -rw-r--r-- root/root 2699 2011-05-13 09:14 ./usr/share/qemu/keymaps/hr -rw-r--r-- root/root 934 2011-05-13 09:14 ./usr/share/qemu/keymaps/fr-ca -rw-r--r-- root/root 11421 2011-05-13 09:14 ./usr/share/qemu/keymaps/bepo -rw-r--r-- root/root 1866 2011-05-13 09:14 ./usr/share/qemu/keymaps/hu -rw-r--r-- root/root 2672 2011-05-13 09:14 ./usr/share/qemu/keymaps/pl -rw-r--r-- root/root 3064 2011-05-13 09:14 ./usr/share/qemu/keymaps/is -rw-r--r-- root/root 1105 2011-05-13 09:14 ./usr/share/qemu/keymaps/nl -rw-r--r-- root/root 3123 2011-05-13 09:14 ./usr/share/qemu/keymaps/th -rw-r--r-- root/root 609 2011-05-13 09:14 ./usr/share/qemu/keymaps/en-us -rw-r--r-- root/root 2735 2011-05-13 09:14 ./usr/share/qemu/keymaps/fr-be -rw-r--r-- root/root 2649 2011-05-13 09:14 ./usr/share/qemu/keymaps/tr -rw-r--r-- root/root 1096 2011-05-13 09:14 ./usr/share/qemu/keymaps/lt -rw-r--r-- root/root 906 2011-05-13 09:14 ./usr/share/qemu/keymaps/fo -rw-r--r-- root/root 293 2011-05-13 09:14 ./usr/share/qemu/keymaps/modifiers -rw-r--r-- root/root 2450 2011-05-13 09:14 ./usr/share/qemu/keymaps/pt -rw-r--r-- root/root 2462 2011-05-13 09:14 ./usr/share/qemu/keymaps/it -rw-r--r-- root/root 2366 2011-05-13 09:14 ./usr/share/qemu/keymaps/mk -rw-r--r-- root/root 2293 2011-05-13 09:14 ./usr/share/qemu/keymaps/sl -rw-r--r-- root/root 1115 2011-05-13 09:14 ./usr/share/qemu/keymaps/et -rw-r--r-- root/root43 2011-05-13 09:14 ./usr/share/qemu/keymaps/nl-be -rw-r--r-- root/root 2467 2011-05-13 09:14 ./usr/share/qemu/keymaps/de -rw-r--r-- root/root 1008 2011-05-13 09:14 ./usr/share/qemu/keymaps/sv -rw-r--r-- root/root 2581 2011-05-13 09:14 ./usr/share/qemu/keymaps/en-gb -rw-r--r-- root/root 2239 2011-05-13 09:14 ./usr/share/qemu/keymaps/ar -rw-r--r-- root/root 2576 2011-05-13 09:14 ./usr/share/qemu/keymaps/da -rw-r--r-- root/root 2236 2011-05-13 09:14 ./usr/share/qemu/keymaps/es -rw-r--r-- root/root 2685 2011-05-13 09:14 ./usr/share/qemu/keymaps/fi -rw-r--r-- root/root 2554 2011-05-13 09:14 ./usr/share/qemu/keymaps/ru -rw-r--r-- root/root 2140 2011-05-13 09:14 ./usr/share/qemu/keymaps/ja -rw-r--r-- root/root 2077 2011-05-13 09:14 ./usr/share/qemu/keymaps/common -rw-r--r-- root/root 2840 2011-05-13 09:14 ./usr/share/qemu/keymaps/lv -rw-r--r-- root/root 2471 2011-05-13 09:14 ./usr/share/qemu/keymaps/fr-ch -rw-r--r-- root/root 2533 2011-05-13 09:14 ./usr/share/qemu/keymaps/de-ch -rwxr-xr-x root/root 1024 2011-05-13 09:45 ./usr/share/qemu/linuxboot.bin drwxr-xr-x root/root 0 2011-05-13 09:45 ./usr/share/doc/ drwxr-xr-x root/root 0 2011-05-13 09:45 ./usr/share/doc/qemu-common/ -rw-r--r-- root/root 15720 2011-05-13 09:20 ./usr/share/doc/qemu-common/changelog.Debian.gz -rw-r--r-- root/root 4079 2011-05-13 09:15 ./usr/share/doc/qemu-common/copyright drwxr-xr-x root/root 0 2011-05-13 09:45 ./usr/bin/ -rwxr-xr-x root/root 270 2011-05-13 09:15 ./usr/bin/qemu-ifdown -rwxr-xr-x root/root 138 2011-05-13 09:15 ./usr/bin/qemu-ifup drwxr-xr-x root/root 0 2011-05-13 09:45 ./etc/ lrwxrwxrwx root/root 0 2011-05-13 09:45 ./usr/share/qemu/vgabios.bin - ../vgabios/vgabios.bin lrwxrwxrwx root/root 0 2011-05-13 09:45 ./usr/share/qemu/vgabios-qxl.bin - ../vgabios/vgabios.qxl.bin lrwxrwxrwx root/root 0 2011-05-13 09:45 ./usr/share/qemu/vgabios-vmware.bin - ../vgabios/vgabios.vmware.bin lrwxrwxrwx root/root 0 2011-05-13 09:45 ./usr/share/qemu/vgabios-stdvga.bin - ../vgabios/vgabios.stdvga.bin lrwxrwxrwx root/root 0 2011-05-13 09:45
[Qemu-devel] [Bug 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
I386 build constantly fails in my PPA https://launchpad.net/~bderzhavets/+archive/git-spice. Build on local box ( Q9550,8 GB ) Ubuntu 11.04 (64-bit) debuild -rfakeroot -b -k930900E6 | tee build-v35.log doesn't have any problems with ./hw/qxl.c. I attached log and packages ** Attachment added: Buid log https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2125644/+files/build-v35.log -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: qemu-common_0.14.0+spice-v35-0ubuntu1_all.deb https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2125646/+files/qemu-common_0.14.0%2Bspice-v35-0ubuntu1_all.deb -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: qemu_0.14.0+spice-v35-0ubuntu1_amd64.deb https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2125645/+files/qemu_0.14.0%2Bspice-v35-0ubuntu1_amd64.deb -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: qemu-kvm_0.14.0+spice-v35-0ubuntu1_amd64.deb https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2125647/+files/qemu-kvm_0.14.0%2Bspice-v35-0ubuntu1_amd64.deb -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Build spice-gtk-0.6 on Ubuntu 11.04 ( --with-pyton) # cd /root/spice-gtk-0.6 # ./configure --prefix=/usr --build=x86_64-linux-gnu \ --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share \ --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/bin \ --with-python . . . configure: Spice-Gtk 0.6 == prefix: /usr c compiler: gcc -std=gnu99 c++ compiler: g++ Coroutine:ucontext Audio:pulse Target: SASL support: yes Gtk: 2.0 Now type 'make' to build spice-gtk # make # find . -name SpiceClientGtk* -print ./gtk/SpiceClientGtk_la-spice-client-gtk-module.defs.o ./gtk/SpiceClientGtk.la ./gtk/SpiceClientGtk_la-spice-client-gtk-module.o ./gtk/.deps/SpiceClientGtk_la-spice-client-gtk-module.Plo ./gtk/.deps/SpiceClientGtk_la-spice-client-gtk-module.defs.Plo ./gtk/SpiceClientGtk_la-spice-client-gtk-module.lo ./gtk/.libs/SpiceClientGtk_la-spice-client-gtk-module.defs.o ./gtk/.libs/SpiceClientGtk.la ./gtk/.libs/SpiceClientGtk_la-spice-client-gtk-module.o ./gtk/.libs/SpiceClientGtk.a ./gtk/.libs/SpiceClientGtk.so ./gtk/.libs/SpiceClientGtk.lai ./gtk/SpiceClientGtk_la-spice-client-gtk-module.defs.lo # make install (Doing so, i understand potential problems with spicec installed via PPA) .. -- test -z /usr/bin || /bin/mkdir -p /usr/bin /bin/bash ../libtool --mode=install /usr/bin/install -c spicy snappy '/usr/bin' libtool: install: /usr/bin/install -c .libs/spicy /usr/bin/spicy libtool: install: /usr/bin/install -c .libs/snappy /usr/bin/snappy test -z /usr/lib/python2.7/dist-packages || /bin/mkdir -p /usr/lib/python2.7/dist-packages /bin/bash ../libtool --mode=install /usr/bin/install -c SpiceClientGtk.la '/usr/lib/python2.7/dist-packages' libtool: install: warning: relinking `SpiceClientGtk.la' libtool: install: (cd /root/spice-gtk-0.6/gtk; /bin/bash /root/spice-gtk-0.6/libtool --silent --tag CC --mode=relink gcc -std=gnu99 -pthread -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/python2.7 -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pygtk-2.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -g -O2 -module -avoid-version -fPIC -o SpiceClientGtk.la -rpath /usr/lib/python2.7/dist-packages SpiceClientGtk_la-spice-client-gtk-module.lo SpiceClientGtk_la-spice-client-gtk-module.defs.lo libspice-client-gtk-2.0.la libspice-client-glib-2.0.la -pthread -L/usr/lib/x86_64-linux-gnu -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lm -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 ) libtool: install: /usr/bin/install -c .libs/SpiceClientGtk.soT /usr/lib/python2.7/dist-packages/SpiceClientGtk.so libtool: install: /usr/bin/install -c .libs/SpiceClientGtk.lai /usr/lib/python2.7/dist-packages/SpiceClientGtk.la libtool: install: /usr/bin/install -c .libs/SpiceClientGtk.a /usr/lib/python2.7/dist-packages/SpiceClientGtk.a libtool: install: chmod 644 /usr/lib/python2.7/dist-packages/SpiceClientGtk.a libtool: install: ranlib /usr/lib/python2.7/dist-packages/SpiceClientGtk.a libtool: finish: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/sbin ldconfig -n /usr/lib/python2.7/dist-packages -- . . . . . . Virt-manager 0.8.6 opens Spice Window session for F14 as expected. Spice Client (spice-gtk - 0.6-0ubuntu1 ) installed via Serge's PPA works fine. -- 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 “libvirt” package in Ubuntu: Triaged 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
[Qemu-devel] [Bug 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
In spice session activated via virt-manager guest may run only in VGA mode. Setting video to QXL causes mouse to disappear in VM's window. -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
I cannot upload packages to PPA :- root@boris-System-P5Q3:~/KVMQEMU14# dput ppa:bderzhavets/spice2 qemu-kvm_0.14.0+noroms-0ubuntu7_amd64.changes Checking signature on .changes gpg: Signature made Sat 07 May 2011 02:27:25 PM MSD using RSA key ID 930900E6 gpg: Good signature from Boris Derzhavets (Development key) bderzhav...@yahoo.com Good signature on /root/KVMQEMU14/qemu-kvm_0.14.0+noroms-0ubuntu7_amd64.changes. Uploading to ppa (via ftp to ppa.launchpad.net): Uploading qemu-common_0.14.0+noroms-0ubuntu7_all.deb: done. Uploading qemu-kvm_0.14.0+noroms-0ubuntu7_amd64.deb: done. Uploading qemu_0.14.0+noroms-0ubuntu7_amd64.deb: done. Uploading kvm_84+dfsg-0ubuntu16+0.14.0+noroms+0ubuntu7_amd64.deb: done. Uploading qemu-kvm_0.14.0+noroms-0ubuntu7_amd64.changes: 2k/3k550 Changes file must be signed with a valid GPG signature: Verification failed 3 times: [(7, 9, u'No public key'), (7, 9, u'No public key'), (7, 9, u'No public key')] : Permission denied. Note: This error might indicate a problem with your passive_ftp setting. Please consult dput.cf(5) for details on this configuration option. Please, advise. -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Similar issues mentioned here :- https://answers.launchpad.net/launchpad/+question/152715 -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
It's done now as PPA :- https://launchpad.net/~bderzhavets/+archive/spice2 -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Uncompress regular Natty qemu-kvm package :- qemu-kvm_0.14.0+noroms-0ubuntu4.diff.gz qemu-kvm_0.14.0+noroms-0ubuntu4.dsc qemu-kvm_0.14.0+noroms.orig.tar.gz # dpkg-source -x qemu-kvm_0.14.0+noroms-0ubuntu4.dsc # cd qemu-kvm_0.14.0+noroms-0ubuntu4 Edit debian/rules and comment following line ( per Serge Hallyn) # $(MAKE) -f debian/rules unpatch to get patching to work !! That's a reason why hack spice-qxl-locking-fix-for-qemu-kvm.patch didn't work originally. Change ./configure part of debian/rules adding --enable-spice :- config-host.mak: $(QUILT_STAMPFN) dh_testdir ./configure \ --target-list=x86_64-softmmu i386-softmmu x86_64-linux-user i386-linux-user \ --prefix=/usr \ --interp-prefix=/etc/qemu-binfmt/%M \ --disable-blobs \ --disable-strip \ --enable-spice \ $(conf_arch) Save Edit debian/patches/series:- larger_default_ram_size.patch Detect-and-use-GCC-atomic-builtins-for-locking.patch # spice-qxl-locking-fix-for-qemu-kvm.patch 0001-qxl-spice-display-move-pipe-to-ssd.patch 0002-qxl-implement-get_command-in-vga-mode-without-locks.patch 0003-qxl-spice-remove-qemu_mutex_-un-lock_iothread-around.patch 0004-hw-qxl-render-drop-cursor-locks-replace-with-pipe.patch Save and copy required patches to debian/patches. Edit debian/control like in SPICE2 PPA:- Build-Depends: bcc, bzip2, debhelper (= 7), device-tree-compiler [powerpc], iasl, libaio-dev, libasound2-dev, libcelt051-dev, libcurl4-gnutls-dev, libgnutls-dev, libncurses5-dev, libpci-dev, libpixman-1-dev, libpulse-dev, libsasl2-dev, libsdl1.2-dev (= 1.2.14), libssl-dev, libx11-dev, nasm, perl, pkg-config, quilt (= 0.40), libspice-server-dev, spice-protocol-dev, sysv-rc (= 2.86.ds1-14.1ubuntu2), texi2html, texinfo, uuid-dev, zlib1g-dev Save. # touch -f debian/chagelog # cd .. # dpkg-buildpackage -rfakeroot -b -us -uc # cd .. Remove regular qemu-kvm package via Synaptic Manager Install been built just now :- root@boris-System-P5Q3:~/QEMU14# dpkg -i ./qemu_0.14.0+noroms-0ubuntu4_amd64.deb \ qemu-common_0.14.0+noroms-0ubuntu4_all.deb root@boris-System-P5Q3:~/QEMU14# ls -l /usr/bin/kvm* lrwxrwxrwx 1 root root18 2011-05-06 15:24 /usr/bin/kvm - qemu-system-x86_64 lrwxrwxrwx 1 root root 8 2011-05-06 15:24 /usr/bin/kvm-img - qemu-img lrwxrwxrwx 1 root root 8 2011-05-06 15:24 /usr/bin/kvm-nbd - qemu-nbd -rwxr-xr-x 1 root root 11792 2011-02-22 16:34 /usr/bin/kvm_stat root@boris-System-P5Q3:~/QEMU14# ls -l /usr/bin/qemu* -rwxr-xr-x 1 root root 3520568 2011-05-06 15:08 /usr/bin/qemu -rwxr-xr-x 1 root root 2014976 2011-05-06 15:08 /usr/bin/qemu-i386 -rwxr-xr-x 1 root root 270 2011-05-06 14:04 /usr/bin/qemu-ifdown -rwxr-xr-x 1 root root 138 2011-02-22 16:34 /usr/bin/qemu-ifup -rwxr-xr-x 1 root root 350640 2011-05-06 15:08 /usr/bin/qemu-img -rwxr-xr-x 1 root root 362928 2011-05-06 15:08 /usr/bin/qemu-io -rwxr-xr-x 1 root root 338384 2011-05-06 15:08 /usr/bin/qemu-nbd lrwxrwxrwx 1 root root 4 2011-05-06 15:24 /usr/bin/qemu-system-i386 - qemu -rwxr-xr-x 1 root root 3590968 2011-05-06 15:08 /usr/bin/qemu-system-x86_64 -rwxr-xr-x 1 root root 2055128 2011-05-06 15:08 /usr/bin/qemu-x86_64 Done. -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Sorry, for typo in package name ( qemu-kvm) . I've upgraded version in debian/changelog. root@boris-System-P5Q3:~/QEMU14# ls -l *.deb |grep -v 0ubuntu4_ -rw-r--r-- 1 root root 19494 2011-05-06 16:45 kvm_84+dfsg-0ubuntu16+0.14.0+noroms+0ubuntu5_amd64.deb -rw-r--r-- 1 root root 18958 2011-05-06 16:45 qemu_0.14.0+noroms-0ubuntu5_amd64.deb -rw-r--r-- 1 root root 37758 2011-05-06 16:41 qemu-common_0.14.0+noroms-0ubuntu5_all.deb -rw-r--r-- 1 root root 3512986 2011-05-06 16:45 qemu-kvm_0.14.0+noroms-0ubuntu5_amd64.deb root@boris-System-P5Q3:~/QEMU14# dpkg -i ./qemu-kvm_0.14.0+noroms-0ubuntu5_amd64.deb \ qemu_0.14.0+noroms-0ubuntu5_amd64.deb \ qemu-common_0.14.0+noroms-0ubuntu5_all.deb (Reading database ... 141175 files and directories currently installed.) Preparing to replace qemu-kvm 0.14.0+noroms-0ubuntu4 (using .../qemu-kvm_0.14.0+noroms-0ubuntu5_amd64.deb) ... Unpacking replacement qemu-kvm ... Preparing to replace qemu 0.14.0+noroms-0ubuntu4 (using qemu_0.14.0+noroms-0ubuntu5_amd64.deb) ... Unpacking replacement qemu ... Preparing to replace qemu-common 0.14.0+noroms-0ubuntu4 (using qemu-common_0.14.0+noroms-0ubuntu5_all.deb) ... Unpacking replacement qemu-common ... Setting up qemu-common (0.14.0+noroms-0ubuntu5) ... Setting up qemu-kvm (0.14.0+noroms-0ubuntu5) ... Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Processing triggers for man-db ... Setting up qemu (0.14.0+noroms-0ubuntu5) ... # dpkg -l | grep qemu ii qemu 0.14.0+noroms-0ubuntu5 dummy transitional package from qemu to qemu-kvm ii qemu-common 0.14.0+noroms-0ubuntu5 qemu common functionality (bios, documentation, etc) ii qemu-kvm 0.14.0+noroms-0ubuntu5 Full virtualization on i386 and amd64 har root@boris-System-P5Q3:~/QEMU14# ls -l /usr/bin/qemu* -rwxr-xr-x 1 root root 3520568 2011-05-06 16:45 /usr/bin/qemu -rwxr-xr-x 1 root root 2014976 2011-05-06 16:45 /usr/bin/qemu-i386 -rwxr-xr-x 1 root root 270 2011-05-06 14:04 /usr/bin/qemu-ifdown -rwxr-xr-x 1 root root 138 2011-02-22 16:34 /usr/bin/qemu-ifup -rwxr-xr-x 1 root root 350640 2011-05-06 16:45 /usr/bin/qemu-img -rwxr-xr-x 1 root root 362928 2011-05-06 16:45 /usr/bin/qemu-io -rwxr-xr-x 1 root root 338384 2011-05-06 16:45 /usr/bin/qemu-nbd lrwxrwxrwx 1 root root 4 2011-05-06 16:48 /usr/bin/qemu-system-i386 - qemu -rwxr-xr-x 1 root root 3590968 2011-05-06 16:45 /usr/bin/qemu-system-x86_64 -rwxr-xr-x 1 root root 2055128 2011-05-06 16:45 /usr/bin/qemu-x86_64 -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
What is ITP ? -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
git clone git://git.freedesktop.org/git/spice/qemu cd qemu/ git checkout -b spice.v35 origin/spice.35 Allows to build qemu-kvm-spice_0.14.0+noroms-0ubuntu4qxl3_amd64.deb with patches larger_default_ram_size.patch # Detect-and-use-GCC-atomic-builtins-for-locking.patch # 0001-qxl-spice-display-move-pipe-to-ssd.patch # 0002-qxl-implement-get_command-in-vga-mode-without-locks.patch # 0003-qxl-spice-remove-qemu_mutex_-un-lock_iothread-around.patch # 0004-hw-qxl-render-drop-cursor-locks-replace-with-pipe.patch Package seems to work OK with SPICE2 PPA -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
** Attachment added: qemu-kvm-spice based spice.v35 https://bugs.launchpad.net/qemu/+bug/723871/+attachment/2111482/+files/qemu-kvm-spice_0.14.0%2Bnoroms-0ubuntu4qxl3_amd64.deb -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
@Serge, Sorry, but answer is no. I just learned how dh_make and dpkg-buildpackage works , picked up your's debian folder. Updated debian/patches/series and changelog . built new debian package ( based on new qemu-kvm-spice-0.14.0+noroms_0ubuntu4qxl3.orig.tar.gz) due to three recent commits to upstream branch spice.v35 were done by Gerd Hoffmann and seemed to solve the issue. My major concern is port to Ubuntu spice-gtk 0.6 ( with python bindings) . It requires GLIBC 2.14 (gtk2-devel = 2.14). I've installed via alienating 6 fedora's packages ( i.e. ignoring dependencies ) /usr/lib64/python2.7/dist-packages/SpiceClientGtk.so and VM's window got opened. Fixing complains one by one i got stuck when libc.so.6 was reported too old ( GLIBC 2.13) . You are going to switch to 2.14 only on 11.10 as far as i know. So , i should wait for alpha. -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Disabling AppArmor really allows libvirt to go with no problems. -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Just disabling libvirtd profile is enough as well :- # apparmor_parser -R /etc/apparmor.d/usr.sbin.libvirtd # ln -s /etx/apparmor.d/usr.sbin.libvirtd /etc/apparmor.d/disable/ -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Thanks for advice. My primary target was to make sure , that it's not libvirt 8.8.1 on Ubuntu 11.04 issue. -- 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 “libvirt” package in Ubuntu: Triaged 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Packages installed via ppa:serge-hallyn/spice2 have been tested positive for F14, W7 KVMs installs and runtime. qemu-kvm-spice (0.14.0+noroms-0ubuntu4qxl2) natty is based on the most recent RH's QXL patches set for qemu-kvm-0.14.tar.gz as far as i could see. -- 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.
Re: [Qemu-devel] [Bug 769986] [NEW] Binaries installed via ppa:serge-hallyn/spice still are affected by bug 723871
Packages installed via ppa:serge-hallyn/spice2 have been tested positive for F14, W7 KVMs installs and runtime. qemu-kvm-spice (0.14.0+noroms-0ubuntu4qxl2) is based on the most recent RH's QXL patches set for qemu-kvm-0.14.tar.gz as far as i could see.
[Qemu-devel] [Bug 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
@Serg, I started getting execution denied errors in VirtManager or same in terminal after virsh start W7 , when updated XML as follows emulator/usr/bin/kvm-spice/emulatror . . . . . graphics type='spice' port='5930' autoport='no' listen='0.0.0.0'/ video model type='qxl' vram='32768' heads='1'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video When i attempted to fool libvirt and replace symlink kvm-spice or binary it's referencing i got another execution denied error when spice-server started. Fedora's libvirt doesn't have any problems of such kind ( even F14's libvirt in the very early times ) Install libvirt-0.8.8-4.fc15.src.rpm shows following patches in SOURCES :- libvirt-0.8.8-avoid-resetting-errors.patch libvirt-0.8.8-read-only-checks.patch libvirt-0.8.8-kernel-boot-index.patch libvirt-0.8.8-threadsafe-libvirtd-error-reporting.patch It's hard to understand what part of code ( in patches ) is responsible for spice-server behaviour. Once again RH's support is pretty much desired. -- 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
root@boris-System-P5Q3:/usr/bin# cp qemu-system-x86_64-spice qemu-system-x86_64 root@boris-System-P5Q3:/usr/bin# cp qemu-x86_64-spice qemu-x86_64 root@boris-System-P5Q3:~# cat W7.xml domain type='kvm' nameW7S/name memory2097152/memory currentMemory2097152/currentMemory vcpu2/vcpu os type arch='x86_64' machine='pc-0.14'hvm/type boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='localtime'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='block' device='disk' driver name='qemu' type='raw'/ source dev='/dev/sdb7'/ target dev='hda' bus='ide'/ address type='drive' controller='0' bus='0' unit='0'/ /disk controller type='ide' index='0' address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='52:54:00:d7:d7:c6'/ source bridge='br0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' target port='0'/ /serial console type='pty' target type='serial' port='0'/ /console input type='tablet' bus='usb'/ input type='mouse' bus='ps2'/ graphics type='spice' port='5930' autoport='no' listen='0.0.0.0'/ sound model='ac97' address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /sound video model type='qxl' vram='32786' heads='1'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' address type='pci' domain='0x' bus='0x00' slot='0x05' function='0x0'/ /memballoon /devices /domain root@boris-System-P5Q3:~# virsh define W7.xml Domain W7S defined from W7.xml root@boris-System-P5Q3:~# virsh start W7S error: Failed to start domain W7S error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/1 do_spice_init: starting 0.8.1 do_spice_init: statistics shm_open failed, Permission denied -- 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Current patches on F15:- [root@fedora15a SOURCES]# ls -l total 5360 -rw-r--r--. 1 root root4618 Mar 30 01:58 0001-qxl-spice-display-move-pipe-to-ssd.patch -rw-r--r--. 1 root root 10176 Mar 30 01:58 0002-qxl-implement-get_command-in-vga-mode-without-locks.patch -rw-r--r--. 1 root root5073 Mar 30 01:58 0003-qxl-spice-remove-qemu_mutex_-un-lock_iothread-around.patch -rw-r--r--. 1 root root7783 Mar 30 01:58 0004-hw-qxl-render-drop-cursor-locks-replace-with-pipe.patch -rw-r--r--. 1 root root1733 Mar 30 01:58 0005-char-Split-out-tcp-socket-close-code-in-a-separate-f.patch -rw-r--r--. 1 root root 22320 Mar 30 01:58 0006-char-Add-a-QemuChrHandlers-struct-to-initialise-char.patch -rw-r--r--. 1 root root1913 Mar 30 01:58 0007-iohandlers-Add-enable-disable_write_fd_handler-funct.patch -rw-r--r--. 1 root root2182 Mar 30 01:58 0008-char-Add-framework-for-a-write-unblocked-callback.patch -rw-r--r--. 1 root root6678 Mar 30 01:58 0009-char-Update-send_all-to-handle-nonblocking-chardev-w.patch -rw-r--r--. 1 root root2583 Mar 30 01:58 0010-char-Equip-the-unix-tcp-backend-to-handle-nonblockin.patch -rw-r--r--. 1 root root2000 Mar 30 01:58 0011-char-Throttle-when-host-connection-is-down.patch -rw-r--r--. 1 root root1650 Mar 30 01:58 0012-virtio-console-Enable-port-throttling-when-chardev-i.patch -rw-r--r--. 1 root root5036 Mar 30 01:58 0013-spice-qemu-char.c-add-throttling.patch -rw-r--r--. 1 root root2822 Mar 30 01:58 0014-spice-qemu-char.c-remove-intermediate-buffer.patch -rw-r--r--. 1 root root2807 Mar 30 01:58 0015-chardev-Allow-frontends-to-notify-backends-of-guest-.patch -rw-r--r--. 1 root root1592 Mar 30 01:58 0016-virtio-console-notify-backend-of-guest-open-close.patch -rw-r--r--. 1 root root1536 Mar 30 01:58 0017-spice-chardev-listen-to-frontend-guest-open-close.patch -rw-r--r--. 1 root root1784 Mar 30 01:58 0018-spice-qemu-char-Fix-flow-control-in-client-guest-dir.patch -rw-r--r--. 1 root root 40 Mar 30 01:58 80-kvm.rules -rw-r--r--. 1 root root2202 Mar 30 01:58 ksm.init -rw-r--r--. 1 root root 168 Mar 30 01:58 ksm.sysconfig -rw-r--r--. 1 root root3442 Mar 30 01:58 ksmtuned -rw-r--r--. 1 root root 478 Mar 30 01:58 ksmtuned.conf -rw-r--r--. 1 root root1968 Mar 30 01:58 ksmtuned.init -rwxr-xr-x. 1 root root 284 Mar 30 01:58 kvm.modules -rw-r--r--. 1 root root1155 Mar 30 01:58 pc-add-a-Fedora-13-machine-type-for-backward-compat.patch -rw-r--r--. 1 root root1748 Mar 30 01:58 qemu-fix-non-PCI-target-build.patch -rwxr-xr-x. 1 root root3199 Mar 30 01:58 qemu.init -rw-rw-r--. 1 root root 5320696 Feb 24 19:11 qemu-kvm-0.14.0.tar.gz -rw-r--r--. 1 root root1045 Mar 30 01:58 qemu-vhost-fix-dirty-page-handling.patch I believe there is no the one http://patchwork.ozlabs.org/patch/84704/ you have been using -- 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
View also http://lists.fedoraproject.org/pipermail/virt/2011-March/002572.html Per Alon Levy :- here is a new patchset, it's basically the old plus first patch of reverting gerd's (cpu_single_env hackage) and last one removing all the locks, after being convinced by hans (cc'ed) and uri that it should work. Tested with rhel qemu-kvm, which should be identical (tm) to fedora qemu-kvm. On account of being too lame to figure out how to add the patches to qemu.spec and doing a scratch build right now.. -- 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 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl
Packages from ppa:serge-hallyn/spice have been installed on Ubuntu 11.04 Beta 2. Bug with -vga qxl is still in place :- root@NattyNarwhal:/usr/tmp# /usr/bin/kvm-spice -cpu host -enable-kvm -name VF14 -m 2048 \ -drive file=/usr/tmp/disk.qcow2,if=virtio,media=disk,aio=native \ -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=5900,disable-ticketing do_spice_init: starting 0.8.0 spice_server_add_interface: SPICE_INTERFACE_KEYBOARD spice_server_add_interface: SPICE_INTERFACE_MOUSE spice_server_add_interface: SPICE_INTERFACE_QXL red_worker_main: begin kvm-spice: pci_add_option_rom: failed to find romfile pxe-virtio.bin handle_dev_destroy_surfaces: handle_dev_destroy_surfaces: handle_dev_input: start reds_handle_main_link: reds_show_new_channel: channel 1:0, connected successfully, over Non Secure link reds_main_handle_message: net test: invalid values, latency 0 roundtrip 9651. assuming highbandwidth reds_show_new_channel: channel 4:0, connected successfully, over Non Secure link red_dispatcher_set_cursor_peer: handle_dev_input: cursor connect reds_show_new_channel: channel 2:0, connected successfully, over Non Secure link red_dispatcher_set_peer: handle_dev_input: connect handle_new_display_channel: jpeg disabled handle_new_display_channel: zlib-over-glz disabled reds_show_new_channel: channel 3:0, connected successfully, over Non Secure link inputs_link: kvm-spice: /build/buildd/qemu-kvm-spice-0.14.0+noroms/qemu-kvm.c:1724: kvm_mutex_unlock: Assertion `!cpu_single_env' failed. Aborted This issue has been fixed on Fedora 15 on 03 /18/2001 . In meantime , view patches in qemu-0.14.0-7.fc14.src.rpm :- http://repos.fedorapeople.org/repos/jforbes/virt-preview/fedora-14/SRPMS/ . . . . . . . qemu-0.14.0-7.fc14.src.rpm 07-Apr-2011 21:46 5.1M . . . . . . . . -- 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 769986] [NEW] Binaries installed via ppa:serge-hallyn/spice still are affected by bug 723871
Public bug reported: Packages from ppa:serge-hallyn/spice have been installed on Ubuntu 11.04 Beta 2. Bug with -vga qxl is still in place :- root@NattyNarwhal:/usr/tmp# /usr/bin/kvm-spice -cpu host -enable-kvm -name VF14 -m 2048 \ -drive file=/usr/tmp/disk.qcow2,if=virtio,media=disk,aio=native \ -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=5900,disable-ticketing do_spice_init: starting 0.8.0 spice_server_add_interface: SPICE_INTERFACE_KEYBOARD spice_server_add_interface: SPICE_INTERFACE_MOUSE spice_server_add_interface: SPICE_INTERFACE_QXL red_worker_main: begin kvm-spice: pci_add_option_rom: failed to find romfile pxe-virtio.bin handle_dev_destroy_surfaces: handle_dev_destroy_surfaces: handle_dev_input: start reds_handle_main_link: reds_show_new_channel: channel 1:0, connected successfully, over Non Secure link reds_main_handle_message: net test: invalid values, latency 0 roundtrip 9651. assuming highbandwidth reds_show_new_channel: channel 4:0, connected successfully, over Non Secure link red_dispatcher_set_cursor_peer: handle_dev_input: cursor connect reds_show_new_channel: channel 2:0, connected successfully, over Non Secure link red_dispatcher_set_peer: handle_dev_input: connect handle_new_display_channel: jpeg disabled handle_new_display_channel: zlib-over-glz disabled reds_show_new_channel: channel 3:0, connected successfully, over Non Secure link inputs_link: kvm-spice: /build/buildd/qemu-kvm-spice-0.14.0+noroms/qemu-kvm.c:1724: kvm_mutex_unlock: Assertion `!cpu_single_env' failed. Aborted Option -vga std works fine as 723871 This issue has been fixed on Fedora 15 on 03/18/2011 . In meantime, view patches in qemu-0.14.0-7.fc14.src.rpm :- http://repos.fedorapeople.org/repos/jforbes/virt-preview/fedora-14/SRPMS/ . . . . . . . . qemu-0.14.0-7.fc14.src.rpm 07-Apr-2011 21:46 5.1M ** Affects: qemu Importance: Undecided Status: New ** Tags: qemu spice -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/769986 Title: Binaries installed via ppa:serge-hallyn/spice still are affected by bug 723871 Status in QEMU: New Bug description: Packages from ppa:serge-hallyn/spice have been installed on Ubuntu 11.04 Beta 2. Bug with -vga qxl is still in place :- root@NattyNarwhal:/usr/tmp# /usr/bin/kvm-spice -cpu host -enable-kvm -name VF14 -m 2048 \ -drive file=/usr/tmp/disk.qcow2,if=virtio,media=disk,aio=native \ -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=5900,disable-ticketing do_spice_init: starting 0.8.0 spice_server_add_interface: SPICE_INTERFACE_KEYBOARD spice_server_add_interface: SPICE_INTERFACE_MOUSE spice_server_add_interface: SPICE_INTERFACE_QXL red_worker_main: begin kvm-spice: pci_add_option_rom: failed to find romfile pxe-virtio.bin handle_dev_destroy_surfaces: handle_dev_destroy_surfaces: handle_dev_input: start reds_handle_main_link: reds_show_new_channel: channel 1:0, connected successfully, over Non Secure link reds_main_handle_message: net test: invalid values, latency 0 roundtrip 9651. assuming highbandwidth reds_show_new_channel: channel 4:0, connected successfully, over Non Secure link red_dispatcher_set_cursor_peer: handle_dev_input: cursor connect reds_show_new_channel: channel 2:0, connected successfully, over Non Secure link red_dispatcher_set_peer: handle_dev_input: connect handle_new_display_channel: jpeg disabled handle_new_display_channel: zlib-over-glz disabled reds_show_new_channel: channel 3:0, connected successfully, over Non Secure link inputs_link: kvm-spice: /build/buildd/qemu-kvm-spice-0.14.0+noroms/qemu-kvm.c:1724: kvm_mutex_unlock: Assertion `!cpu_single_env' failed. Aborted Option -vga std works fine as 723871 This issue has been fixed on Fedora 15 on 03/18/2011 . In meantime, view patches in qemu-0.14.0-7.fc14.src.rpm :- http://repos.fedorapeople.org/repos/jforbes/virt-preview/fedora-14/SRPMS/ . . . . . . . . qemu-0.14.0-7.fc14.src.rpm 07-Apr-2011 21:46 5.1M
Re: [Qemu-devel] Re: [fedora-virt] Fedora Virt status
fake.qcow2 has nothing to do with performance issue during install on F14. W7 boot up is device is always LV ( like on SL 6 ) Boris. --- On Fri, 1/14/11, Richard W.M. Jones rjo...@redhat.com wrote: From: Richard W.M. Jones rjo...@redhat.com Subject: Re: [Qemu-devel] Re: [fedora-virt] Fedora Virt status To: Boris Derzhavets bderzhav...@yahoo.com Cc: Cole Robinson crobi...@redhat.com, v...@lists.fedoraproject.org, Justin M. Forbes jmfor...@linuxtx.org, qemu-devel@nongnu.org Date: Friday, January 14, 2011, 6:00 PM You shouldn't use local files (esp. not qcow2) for performance testing. What does it look like if you use an LV for disk? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v
[Qemu-devel] Re: [fedora-virt] Fedora Virt status (XML for SL6)
I switched cache to none for boot up device via virt-manager before W7 install on F14. It didn't help me. I've already responded to Cole regarding this attempt. Please, view thread. Boris. --- On Sat, 1/15/11, Richard W.M. Jones rjo...@redhat.com wrote: From: Richard W.M. Jones rjo...@redhat.com Subject: Re: [fedora-virt] Fedora Virt status (XML for SL6) To: v...@lists.fedoraproject.org, qemu-devel@nongnu.org Date: Saturday, January 15, 2011, 5:49 AM On Fri, Jan 14, 2011 at 12:17:42PM -0800, Boris Derzhavets wrote: disk type='block' device='disk' driver name='qemu' type='raw' cache='none'/ This one (SL6) has cache=none, but the Fedora 14 XML you posted does not. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html ___ virt mailing list v...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/virt
[Qemu-devel] Re: [fedora-virt] Fedora Virt status (XML for SL6)
Issue :- Your's the most advanced KVM System F14 performs W7 (x64/x86) install on IDE boot up device (LV) much slower then RHEL 6 does (SL 6 does) Both systems have cache set to none for IDE boot up device before install starts up. Boris. --- On Sat, 1/15/11, Richard W.M. Jones rjo...@redhat.com wrote: From: Richard W.M. Jones rjo...@redhat.com Subject: Re: [fedora-virt] Fedora Virt status (XML for SL6) To: Boris Derzhavets bderzhav...@yahoo.com Cc: v...@lists.fedoraproject.org, qemu-devel@nongnu.org Date: Saturday, January 15, 2011, 8:22 AM On Sat, Jan 15, 2011 at 03:15:05AM -0800, Boris Derzhavets wrote: Please, view thread. I've read every part of the thread(s). You don't make it easy to follow what you're talking about. I would suggest: (1) Organize your thoughts and experiments logically. (2) When you have done (1), post a thorough description of the problem in Bugzilla, giving precise steps to reproduce and all information necessary. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/
[Qemu-devel] Re: [fedora-virt] Fedora Virt status
Boris can you help me to parse this ... SL6 = Scientific Linux 6? Yes, I work with SL6 alpha 4 And you're saying that Windows 7 is much faster on SL6 than on Fedora 14? Installation itself . Packages deployment phase is much faster on SL 6 ( alpha 4), even if I don't pre-load viostor.sys ( option working only on SL 6 ) Are virtio-blk and virtio-net drivers installed in the Windows guest? Yes. Please, view for details :- http://bderzhavets.wordpress.com/2011/01/08/set-up-rh-virtio-scsi-driver-on-windows-xp-kvm-at-kvm-qemu-instance-on-f14/ XML profiles for F14 and SL6 will be sent to you a bit latter. I cannot reboot box right now. Boris. --- On Fri, 1/14/11, Richard W.M. Jones rjo...@redhat.com wrote: From: Richard W.M. Jones rjo...@redhat.com Subject: Re: [fedora-virt] Fedora Virt status To: Boris Derzhavets bderzhav...@yahoo.com Cc: v...@lists.fedoraproject.org, Justin M. Forbes jmfor...@linuxtx.org, qemu-devel@nongnu.org Date: Friday, January 14, 2011, 12:40 PM On Thu, Jan 13, 2011 at 08:27:17AM -0800, Boris Derzhavets wrote: Windows 7 KVM install runs unbelievably fast on SL 6 ( alpha 3) vs F14 with the most recent libvirt stuff : Boris can you help me to parse this ... SL6 = Scientific Linux 6? And you're saying that Windows 7 is much faster on SL6 than on Fedora 14? P.S. It happens no matter of pre-install loading Virtio SCSI driver, which is also possible only on SL6 via virtio-win.1.1.16.noarch.rpm. Not sure what 'Virtio SCSI' is. Are virtio-blk and virtio-net drivers installed in the Windows guest? What does the libvirt XML for this guest look like (from both SL6 and Fedora 14)? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/
[Qemu-devel] Re: [fedora-virt] Fedora Virt status (XML for F14)
XML on F14 [root@fedora14b Downloads]# uname -a Linux fedora14b 2.6.35.10-74.fc14.x86_64 #1 SMP Thu Dec 23 16:04:50 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux [root@fedora14b Downloads]# virsh version Compiled against library: libvir 0.8.7 Using library: libvir 0.8.7 Using API: QEMU 0.8.7 Running hypervisor: QEMU 0.13.0 [root@fedora14b Downloads]# cat W7V64.xml domain type='kvm' id='10' nameW7V64/name uuidcb736260-fecf-db68-8d87-e3c394c9c934/uuid memory4194304/memory currentMemory4194304/currentMemory vcpu2/vcpu os type arch='x86_64' machine='pc-0.13'hvm/type boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='localtime'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/qemu-kvm/emulator disk type='file' device='cdrom' driver name='qemu' type='raw'/ source file='/mnt/root/Downloads/virtio-win-1.1.16.iso'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' unit='0'/ /disk disk type='block' device='disk' driver name='qemu' type='raw'/ source dev='/dev/vg_kvms/vm01'/ target dev='vda' bus='virtio'/ alias name='virtio-disk0'/ address type='pci' domain='0x' bus='0x00' slot='0x06' function='0x0'/ /disk controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='52:54:00:2b:bb:99'/ source bridge='br0'/ target dev='vnet0'/ model type='virtio'/ alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/1'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/1' source path='/dev/pts/1'/ target type='serial' port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5900' autoport='yes'/ sound model='ac97' alias name='sound0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /sound video model type='vga' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x05' function='0x0'/ /memballoon /devices /domain Boris. P.S. I did mount SL 6 / folder on /mnt. But /mnt/etc/libvirtd/qemu appears to be empty. --- On Fri, 1/14/11, Scott Dowdle dow...@montanalinux.org wrote: From: Scott Dowdle dow...@montanalinux.org Subject: Re: [fedora-virt] Fedora Virt status To: Boris Derzhavets bderzhav...@yahoo.com Cc: v...@lists.fedoraproject.org, qemu-devel@nongnu.org Date: Friday, January 14, 2011, 2:47 PM Boris, - Original Message - XML profiles for F14 and SL6 will be sent to you a bit latter. I cannot reboot box right now. You don't have to reboot the box to look at the xml configs. On the vm host machine just look at/copy the VM config files in /etc/libvirtd/qemu/ (or something like that, I'm going from memory). TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work]
[Qemu-devel] Re: [fedora-virt] Fedora Virt status (XML for SL6)
[root@ServerSL6APH ~]# uname -a Linux ServerSL6APH 2.6.32-71.14.1.el6.x86_64 #1 SMP Wed Jan 12 11:40:37 CST 2011 x86_64 x86_64 x86_64 GNU/Linux [root@ServerSL6APH ~]# virsh version Compiled against library: libvir 0.8.1 Using library: libvir 0.8.1 Using API: QEMU 0.8.1 Running hypervisor: QEMU 0.12.1 [root@ServerSL6APH ~]# virsh dumpxml W7VIRT64 W7VIRT64.xml [root@ServerSL6APH ~]# cat W7VIRT64.xml domain type='kvm' id='1' nameW7VIRT64/name uuid393221ea-201c-1799-5299-2213e2aaa805/uuid memory4194304/memory currentMemory4194304/currentMemory vcpu2/vcpu os type arch='x86_64' machine='rhel6.0.0'hvm/type boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='localtime'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='floppy' driver name='qemu' type='raw' cache='none'/ target dev='fda' bus='fdc'/ alias name='fdc0-0-0'/ address type='drive' controller='0' bus='0' unit='0'/ /disk disk type='block' device='disk' driver name='qemu' type='raw' cache='none'/ source dev='/dev/sdb9'/ target dev='vda' bus='virtio'/ alias name='virtio-disk0'/ address type='pci' domain='0x' bus='0x00' slot='0x05' function='0x0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw'/ target dev='hdc' bus='ide'/ readonly/ alias name='ide0-1-0'/ address type='drive' controller='0' bus='1' unit='0'/ /disk controller type='fdc' index='0' alias name='fdc0'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='52:54:00:cd:d6:fb'/ source bridge='br0'/ target dev='vnet0'/ model type='virtio'/ alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/0'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/0' source path='/dev/pts/0'/ target port='0'/ alias name='serial0'/ /console input type='tablet' bus='usb' alias name='input0'/ /input input type='mouse' bus='ps2'/ graphics type='vnc' port='5900' autoport='yes'/ sound model='ac97' alias name='sound0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /sound video model type='vga' vram='9216' heads='1'/ alias name='video0'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x06' function='0x0'/ /memballoon /devices seclabel type='dynamic' model='selinux' labelsystem_u:system_r:svirt_t:s0:c179,c357/label imagelabelsystem_u:object_r:svirt_image_t:s0:c179,c357/imagelabel /seclabel /domain Boris. --- On Fri, 1/14/11, Dennis Jacobfeuerborn denni...@conversis.de wrote: From: Dennis Jacobfeuerborn denni...@conversis.de Subject: Re: [fedora-virt] Fedora Virt status (XML for F14) To: Boris Derzhavets bderzhav...@yahoo.com Cc: Scott Dowdle dow...@montanalinux.org, v...@lists.fedoraproject.org, qemu-devel@nongnu.org Date: Friday, January 14, 2011, 3:05 PM On 01/14/2011 09:03 PM, Boris Derzhavets wrote: P.S. I did mount SL 6 / folder on /mnt. But /mnt/etc/libvirtd/qemu appears to be empty. Have you tried virsh dumpxml vm-name on the SL6 system? Regards, Dennis
Re: [Qemu-devel] Re: [fedora-virt] Fedora Virt status
Newer virt-manager versions also allow setting this in the UI. I just set IDE Disk1 cashe mode none before install. No relief Boris. --- On Fri, 1/14/11, Cole Robinson crobi...@redhat.com wrote: From: Cole Robinson crobi...@redhat.com Subject: Re: [Qemu-devel] Re: [fedora-virt] Fedora Virt status To: Boris Derzhavets bderzhav...@yahoo.com Cc: Richard W.M. Jones rjo...@redhat.com, v...@lists.fedoraproject.org, Justin M. Forbes jmfor...@linuxtx.org, qemu-devel@nongnu.org Date: Friday, January 14, 2011, 3:16 PM On 01/14/2011 01:09 PM, Boris Derzhavets wrote: Boris can you help me to parse this ... SL6 = Scientific Linux 6? Yes, I work with SL6 alpha 4 And you're saying that Windows 7 is much faster on SL6 than on Fedora 14? Installation itself . Packages deployment phase is much faster on SL 6 ( alpha 4), even if I don't pre-load viostor.sys ( option working only on SL 6 ) Probably cache related. In RHEL6 we default to cache=none, not so in Fedora. Use 'virsh edit' to stick driver name='qemu' cache='none'/ in your disk block, and restart the guest. Newer virt-manager versions also allow setting this in the UI. - Cole Are virtio-blk and virtio-net drivers installed in the Windows guest? Yes. Please, view for details :- http://bderzhavets.wordpress.com/2011/01/08/set-up-rh-virtio-scsi-driver-on-windows-xp-kvm-at-kvm-qemu-instance-on-f14/ XML profiles for F14 and SL6 will be sent to you a bit latter. I cannot reboot box right now. Boris. --- On Fri, 1/14/11, Richard W.M. Jones rjo...@redhat.com wrote: From: Richard W.M. Jones rjo...@redhat.com Subject: Re: [fedora-virt] Fedora Virt status To: Boris Derzhavets bderzhav...@yahoo.com Cc: v...@lists.fedoraproject.org, Justin M. Forbes jmfor...@linuxtx.org, qemu-devel@nongnu.org Date: Friday, January 14, 2011, 12:40 PM On Thu, Jan 13, 2011 at 08:27:17AM -0800, Boris Derzhavets wrote: Windows 7 KVM install runs unbelievably fast on SL 6 ( alpha 3) vs F14 with the most recent libvirt stuff : Boris can you help me to parse this ... SL6 = Scientific Linux 6? And you're saying that Windows 7 is much faster on SL6 than on Fedora 14? P.S. It happens no matter of pre-install loading Virtio SCSI driver, which is also possible only on SL6 via virtio-win.1.1.16.noarch.rpm. Not sure what 'Virtio SCSI' is. Are virtio-blk and virtio-net drivers installed in the Windows guest? What does the libvirt XML for this guest look like (from both SL6 and Fedora 14)? Rich.
Re: [Qemu-devel] Re: [fedora-virt] Fedora Virt status
Set up Virtio for boot up disk is a post install procedure on F14. Boris. --- On Fri, 1/14/11, Richard W.M. Jones rjo...@redhat.com wrote: From: Richard W.M. Jones rjo...@redhat.com Subject: Re: [Qemu-devel] Re: [fedora-virt] Fedora Virt status To: Boris Derzhavets bderzhav...@yahoo.com Cc: Cole Robinson crobi...@redhat.com, v...@lists.fedoraproject.org, Justin M. Forbes jmfor...@linuxtx.org, qemu-devel@nongnu.org Date: Friday, January 14, 2011, 4:33 PM On Fri, Jan 14, 2011 at 12:39:39PM -0800, Boris Derzhavets wrote: Newer virt-manager versions also allow setting this in the UI. I just set IDE Disk1 cashe mode none before install. I thought you said they were using virtio? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top
Re: [Qemu-devel] Re: [fedora-virt] Fedora Virt status
I thought you said they were using virtio? * Post installation procedure for W7 (x64) Rawhide Libvirt on F14 * 1. Original setup on IDE device. 2. Shutdown 3. Add fake.qcow2 disk AS Virtio 4. Add CDROM virtio-win-1.1.16.iso 5. Load KVM 6. Update broken SCSI Driver ( in Device Manager ) via attached RH's CD 7. Shutdown 8. Remove fake.qcow2 disk 9. Remove IDE boot up device, say /dev/sdb9 10. Add Virtio boot up device - same /dev/sdb9 11. Load KVM with Virtio boot up device. SL 6 allows to load viostor.sys from floppy virtio-win-1.1.16.vfd during install and detect Virtio defined boot up device. F14 loads driver , but fails to detect boot up Virtio device in installation phase. Boris. --- On Fri, 1/14/11, Richard W.M. Jones rjo...@redhat.com wrote: From: Richard W.M. Jones rjo...@redhat.com Subject: Re: [Qemu-devel] Re: [fedora-virt] Fedora Virt status To: Boris Derzhavets bderzhav...@yahoo.com Cc: Cole Robinson crobi...@redhat.com, v...@lists.fedoraproject.org, Justin M. Forbes jmfor...@linuxtx.org, qemu-devel@nongnu.org Date: Friday, January 14, 2011, 4:33 PM On Fri, Jan 14, 2011 at 12:39:39PM -0800, Boris Derzhavets wrote: Newer virt-manager versions also allow setting this in the UI. I just set IDE Disk1 cashe mode none before install. I thought you said they were using virtio? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top
[Qemu-devel] Re: [fedora-virt] Fedora Virt status
Windows 7 KVM install runs unbelievably fast on SL 6 ( alpha 3) vs F14 with the most recent libvirt stuff : [root@fedora14b ~]# rpm -qa|grep libvirt libvirt-python-0.8.7-1.fc14.x86_64 libvirt-0.8.7-1.fc14.x86_64 libvirt-client-0.8.7-1.fc14.x86_64 Boris. P.S. It happens no matter of pre-install loading Virtio SCSI driver, which is also possible only on SL6 via virtio-win.1.1.16.noarch.rpm. --- On Wed, 1/12/11, Justin M. Forbes jmfor...@linuxtx.org wrote: From: Justin M. Forbes jmfor...@linuxtx.org Subject: [fedora-virt] Fedora Virt status To: v...@lists.fedoraproject.org Cc: qemu-devel@nongnu.org Date: Wednesday, January 12, 2011, 5:12 PM Fedora 14 - We have 79 open bugs, 9 of which have fixes in awaiting updates. - 1 bug has been closed in the last week - Virt-preview has been opened for Fedora 14, more details below Fedora 15 - Upcoming Deadlines: 2011-01-25 Feature Submission Deadline (2 Weeks!) 2011-02-08 Feature Freeze--Planning Development Ends 2011-02-08 Branch Fedora 15 from Rawhide-- Branch Freeze 2011-02-15 Software String Freeze 2011-02-15 Alpha Change Deadline 2011-03-01 Alpha Release 2011-03-15 Software Translation Deadline 2011-03-22 Beta Change Deadline Features 100% Complete 2011-04-05 Beta Release 2011-04-25 Final Change Deadline 2011-04-26 Compose 'Final' RC 2011-05-10 Fedora 15 Final Release - Feature submission deadline is fast approaching, let's get those feature submissions done. == Virt Preview Repository == The virt-preview repository is now active for F14 users wishing to run the latest F15 virt packages on their stable F14 systems. F13 virt-preview users will still get the latest F14 packages. For details on how to run enable virt-preview, please see: https://fedoraproject.org/wiki/Virtualization_Preview_Repository Also note that virt-preview for F14 and later releases will live on the new(ish) repos.fedorapeople.org site. == Bugs of importance: == - 662380 Encrypted disks do not work Using virsh to create the encrypted disk, resulting disk is unusable. - 655280 libvirt does not support vendor/product based USB device passthrough with QEMU - 656943 KVM guest crashes if vmware vga option is used Reports of qemu crashing when a vga option is passed, using debian guests - 589130 USB disk not marked as removable USB Mass storage devices are not marked as removable to a guest. Bug has been filed upstream as well there is some debate as to what is the correct behavior here. ___ virt mailing list v...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/virt
