Bug#803036: qemu-system-x86: Qemu guest hangs 100% CPU on IO
> Not by me, and it is very unlikely the release team can be convinced the > result is safe. These patches applies on top of event loop refactoring > happened during 2.4 release cycle and requires relatively large number > of other changes all over. Okay, does that mean this is going to put into the "will not fix" category? > I will provide backports of current version to stable (and current > version is already in stable-backports). Wheezy only receives > "backports" from jessie. Do you have any idea when a backport of 2.4 is likely to end up in Jessie/Backports? It would be useful to know if there is some kind of workaround that could be implemented in the meantime. Thanks, Gavin On 2015-10-28 14:53, Michael Tokarev wrote: > 28.10.2015 17:41, Gavin Pidgley пишет: > >> Is it possible that these changes can be backported? > > Not by me, and it is very unlikely the release team can be convinced the > result is safe. These patches applies on top of event loop refactoring > happened during 2.4 release cycle and requires relatively large number > of other changes all over. > >> I can see 2.4 is available in "testing", but won't be released for the >> foreseeable future and I presume 2.4 itself it unlikely to get backported to >> Wheezy anyhow. > > I will provide backports of current version to stable (and current > version is already in stable-backports). Wheezy only receives > "backports" from jessie. > > Thanks, > > /mjt
Bug#803036: qemu-system-x86: Qemu guest hangs 100% CPU on IO
Is it possible that these changes can be backported? I can see 2.4 is available in "testing", but won't be released for the foreseeable future and I presume 2.4 itself it unlikely to get backported to Wheezy anyhow. It would be greatly appreciated if these specific fixes can be backported at least, as it's causing us issues on our production environment and upgrading doesn't look like it will be an option for some time. Thanks, Gavin On 2015-10-28 13:46, Michael Tokarev wrote: > 26.10.2015 11:54, Gavin Pidgley wrote: > >> Package: qemu-system-x86 Version: 2.1+dfsg-12~bpo70+1 Severity: important >> Dear Maintainer, We are seeing guests lockup/hang with qemu. The guests hang >> with 100% CPU usage. The problem seems to be storage/IO related, but there >> is not necessarily high IO happening on the host at the time the guest hangs. > > There were some revork in this layer for 2.4 version, which is not easily to > backport to 2.1. This _might_ be the issue you're expiriencing, or it might > be a different one. There were several reports about qemu locking up on slow > I/O, but it is very difficult to debug, and reportedly after the rework the > lockups stopped from occuring. > > That's what I have in mind: > > https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg05294.html [1] > > Thanks, > > /mjt Links: -- [1] https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg05294.html
Bug#803036: qemu-system-x86: Qemu guest hangs 100% CPU on IO
Package: qemu-system-x86 Version: 2.1+dfsg-12~bpo70+1 Severity: important Dear Maintainer, We are seeing guests lockup/hang with qemu. The guests hang with 100% CPU usage. The problem seems to be storage/IO related, but there is not necessarily high IO happening on the host at the time the guest hangs. At the time of the crash, the VNC console is not responsive and the only way to resolve is to forcefully power off the guest and back on. This guest shown below is running Debian Wheezy, but it seems to affect other guests operating systems such as Windows, CentOS etc. The hosts storage where guest disk images are stored is OCFS2 formatted running over iSCSI. Guests that have a disk cache of cache='writeback' and the qcow2 disk image file created with qemu-img -o preallocation=metadata seem to be less frequently affected, but none the less are still affected. We have also tried virtio-blk, virtio-scsi, scsi and standard IDE for the disk controller on the guest, but doesn't seem to improve things. qemu-system-x86_64 -enable-kvm -name guest1 -S -machine pc- i440fx-2.1,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 973bf27b-04f9-61dd-9272-de2467b599d5 -no- user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/guest1.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device lsi,id=scsi0,bus=pci.0,addr=0x4 -drive file=/mnt/vm/guest1.img,if=none,id =drive-scsi0-0-0,format=qcow2,cache=none -device scsi-hd,bus=scsi0.0,scsi- id=0,drive=drive-scsi0-0-0,id=scsi0-0-0,bootindex=1 -netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=42 -device virtio-net- pci,netdev=hostnet0,id=net0,mac=52:54:00:9a:36:10,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:9 -device cirrus- vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon- pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on A backtrace of a hung guest shows: (gdb) bt #0 0x7f6ce44fed5c in __lll_lock_wait () from /lib/x86_64-linux- gnu/libpthread.so.0 #1 0x7f6ce44fa3a9 in _L_lock_926 () from /lib/x86_64-linux- gnu/libpthread.so.0 #2 0x7f6ce44fa1cb in pthread_mutex_lock () from /lib/x86_64-linux- gnu/libpthread.so.0 #3 0x7f6cea9849f9 in ?? () #4 0x7f6cea9313bb in ?? () #5 0x7f6cea66ebed in main () (gdb) info threads Id Target Id Frame 3Thread 0x7f6cdac4a700 (LWP 29599) "qemu-system-x86" 0x7f6ce4236de1 in ppoll () from /lib/x86_64-linux-gnu/libc.so.6 2Thread 0x7f6c993ff700 (LWP 29601) "qemu-system-x86" 0x7f6ce44fc344 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 * 1Thread 0x7f6cea49b900 (LWP 29596) "qemu-system-x86" 0x7f6ce44fed5c in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0 (gdb) thread apply all bt Thread 3 (Thread 0x7f6cdac4a700 (LWP 29599)): #0 0x7f6ce4236de1 in ppoll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f6cea931f1b in ?? () #2 0x7f6cea933230 in ?? () #3 0x7f6cea924fdd in ?? () #4 0x7f6cea8925b6 in ?? () #5 0x7f6cea899676 in ?? () #6 0x7f6cea8998c5 in ?? () #7 0x7f6cea891bb7 in ?? () #8 0x7f6cea824929 in ?? () #9 0x7f6cea824078 in ?? () #10 0x7f6cea823f98 in ?? () #11 0x7f6cea6b2c79 in ?? () #12 0x7f6cea6b89bf in ?? () #13 0x7f6cea679163 in ?? () #14 0x7f6cea6b1cf5 in ?? () #15 0x7f6cea69d25c in ?? () #16 0x7f6ce44f7b50 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #17 0x7f6ce424195d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #18 0x in ?? () Thread 2 (Thread 0x7f6c993ff700 (LWP 29601)): #0 0x7f6ce44fc344 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64 -linux-gnu/libpthread.so.0 #1 0x7f6cea984c19 in ?? () #2 0x7f6cea920b7b in ?? () #3 0x7f6cea920f50 in ?? () #4 0x7f6ce44f7b50 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #5 0x7f6ce424195d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x in ?? () Thread 1 (Thread 0x7f6cea49b900 (LWP 29596)): #0 0x7f6ce44fed5c in __lll_lock_wait () from /lib/x86_64-linux- gnu/libpthread.so.0 #1 0x7f6ce44fa3a9 in _L_lock_926 () from /lib/x86_64-linux- gnu/libpthread.so.0 #2 0x7f6ce44fa1cb in pthread_mutex_lock () from /lib/x86_64-linux- gnu/libpthread.so.0 #3 0x7f6cea9849f9 in ?? () #4 0x7f6cea9313bb in ?? () #5 0x7f6cea66ebed in main () Host system information: Linux 3.14-0.bpo.2-amd64 #1 SMP Debian 3.14.15-2~bpo70+1 (2014-08-21) x86_64 GNU/Linux qemu-kvm 1:2.1+dfsg-12~bpo70+1 amd64 qemu-system-x861:2.1+dfsg-12~bpo70+1 amd64 Though not quite the same situation, google yeilds similar problems: https://lists.gnu.org/archi
Bug#773706: fixed in libvirt 1.2.9-7
Thanks, could you advise if version 1.2.9-7 will be added into the wheezy-backports repo soon? Kind regards, Gavin On Wed, 24 Dec 2014 10:21:13 + =?utf-8?q?Guido_G=C3=BCnther?= wrote: Source: libvirt Source-Version: 1.2.9-7 We believe that the bug you reported is fixed in the latest version of libvirt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 773...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guido Günther (supplier of updated libvirt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 24 Dec 2014 10:33:31 +0100 Source: libvirt Binary: libvirt-bin libvirt-clients libvirt-daemon libvirt-daemon-system libvirt0 libvirt0-dbg libvirt-doc libvirt-dev libvirt-sanlock Architecture: source amd64 all Version: 1.2.9-7 Distribution: unstable Urgency: medium Maintainer: Debian Libvirt Maintainers Changed-By: Guido Günther Description: libvirt-bin - programs for the libvirt library libvirt-clients - programs for the libvirt library libvirt-daemon - programs for the libvirt library libvirt-daemon-system - Libvirt daemon configuration files libvirt-dev - development files for the libvirt library libvirt-doc - documentation for the libvirt library libvirt-sanlock - library for interfacing with different virtualization systems libvirt0 - library for interfacing with different virtualization systems libvirt0-dbg - library for interfacing with different virtualization systems Closes: 769600 770202 773503 773706 773855 773856 773858 Changes: libvirt (1.2.9-7) unstable; urgency=medium . * [d7df883] CVE-2014-8131: Fix possible deadlock and segfault in qemuConnectGetAllDomainStats() (Closes: #773858) * [d0085e0] qemu: bulk stats: Fix logic in monitor handling * [b5e081c] CVE-2014-8135: storage: fix crash caused by no check return before set close (Closes: #773855) * [a5452de] CVE-2014-8136: qemu: migration: Unlock vm on failed ACL check in protocol v2 APIs (Closes: #773856) * [5aaafc9] qemu: Fix crash in tunnelled migration (Closes: #773503) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#773706: libvirt-daemon: Unable to use virtlockd as /usr/lib/libvirt/lock-driver/lockd.so
Package: libvirt-daemon Version: 1.2.9-6~bpo70+1 Severity: important Dear Maintainer, It is not possible to use the libvirtd locking debain with libvirt, as libvirt is unable to start when setting lock_manager = "lockd" in /etc/libvirt/qemu.conf Libvirt is unable to start and the error below is show in the libvirtd.log Initialization of QEMU state driver failed: Plugin /usr/lib/libvirt/lock- driver/lockd.so not accessible: No such file or directory A quick search of the filesystem for lockd.so show that it is not present. Architecture: amd64 Source: libvirt Version: 1.2.9-6~bpo70+1 Could you advise? Kind regards, Gavin -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i686 i386 Kernel: Linux 3.12-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libvirt-daemon depends on: ii libapparmor12.7.103-4 ii libaudit0 1:1.7.18-1.1 ii libavahi-client30.6.31-2 ii libavahi-common30.6.31-2 ii libblkid1 2.20.1-5.3 ii libc6 2.13-38+deb7u4 ii libcap-ng0 0.6.6-2 ii libdbus-1-3 1.6.8-1+deb7u4 ii libdevmapper1.02.1 2:1.02.74-8 ii libfuse22.9.0-2+deb7u1 ii libgcrypt11 1.5.0-5+deb7u1 ii libgnutls26 2.12.20-8+deb7u2 ii libnetcf1 0.1.9-2 ii libnl1 1.1-7 ii libnuma12.0.8~rc4-1 ii libparted0debian1 2.3-12 ii libpcap0.8 1.3.0-1 ii libpciaccess0 0.13.1-2 ii libsasl2-2 2.1.25.dfsg1-6+deb7u1 ii libselinux1 2.1.9-5 ii libssh2-1 1.4.2-1.1 ii libsystemd-daemon0 44-11+deb7u4 ii libudev0175-7.2 ii libvirt01.2.9-6~bpo70+1 ii libxenstore3.0 4.1.4-3+deb7u2 ii libxml2 2.8.0+dfsg1-7+wheezy1 ii libyajl22.0.4-2 Versions of packages libvirt-daemon recommends: ii libxml2-utils 2.8.0+dfsg1-7+wheezy1 ii netcat-openbsd 1.105-7 ii qemu1.1.2+dfsg-6a+deb7u3 ii qemu-kvm1.1.2+dfsg-6+deb7u3 Versions of packages libvirt-daemon suggests: ii libvirt-daemon-system 1.2.9-6~bpo70+1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665487: Error upgrading dovecot with managesieved
Same issue here. See logs: Stopping IMAP/POP3 mail server: dovecot. Unpacking replacement dovecot-managesieved ... doveconf: Error: Module is for different version 2.0.18: /usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so doveconf: Error: Module is for different version 2.0.18: /usr/lib/dovecot/modules/settings/libmanagesieve_settings.so doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 12: Unknown setting: managesieve_notify_capability Starting IMAP/POP3 mail server: dovecotdoveconf: Error: Module is for different version 2.0.18: /usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so doveconf: Error: Module is for different version 2.0.18: /usr/lib/dovecot/modules/settings/libmanagesieve_settings.so doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 12: Unknown setting: managesieve_notify_capability failed! invoke-rc.d: initscript dovecot, action "start" failed. dpkg: warning: subprocess old post-removal script returned error exit status 1 dpkg - trying script from the new package instead ... doveconf: Error: Module is for different version 2.0.18: /usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so doveconf: Error: Module is for different version 2.0.18: /usr/lib/dovecot/modules/settings/libmanagesieve_settings.so doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 12: Unknown setting: managesieve_notify_capability Starting IMAP/POP3 mail server: dovecotdoveconf: Error: Module is for different version 2.0.18: /usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so doveconf: Error: Module is for different version 2.0.18: /usr/lib/dovecot/modules/settings/libmanagesieve_settings.so doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 12: Unknown setting: managesieve_notify_capability failed! invoke-rc.d: initscript dovecot, action "start" failed. dpkg: error processing /var/cache/apt/archives/dovecot-managesieved_1%3a2.0.18-1_amd64.deb (--unpack): subprocess new post-removal script returned error exit status 1 configured to not write apport reports Starting IMAP/POP3 mail server: dovecot. Restarting IMAP/POP3 mail server: dovecot. Preparing to replace dovecot-sieve 1:2.0.15-1 (using .../dovecot-sieve_1%3a2.0.18-1_amd64.deb) ... Unpacking replacement dovecot-sieve ... Starting IMAP/POP3 mail server: dovecot. Preparing to replace dovecot-pgsql 1:2.0.15-1 (using .../dovecot-pgsql_1%3a2.0.18-1_amd64.deb) ... Unpacking replacement dovecot-pgsql ... Starting IMAP/POP3 mail server: dovecot. Preparing to replace dovecot-sqlite 1:2.0.15-1 (using .../dovecot-sqlite_1%3a2.0.18-1_amd64.deb) ... Unpacking replacement dovecot-sqlite ... Starting IMAP/POP3 mail server: dovecot. Preparing to replace dovecot-gssapi 1:2.0.15-1 (using .../dovecot-gssapi_1%3a2.0.18-1_amd64.deb) ... Unpacking replacement dovecot-gssapi ... Preparing to replace dovecot-pop3d 1:2.0.15-1 (using .../dovecot-pop3d_1%3a2.0.18-1_amd64.deb) ... Stopping IMAP/POP3 mail server: dovecot. Unpacking replacement dovecot-pop3d ... Starting IMAP/POP3 mail server: dovecot. Preparing to replace dovecot-ldap 1:2.0.15-1 (using .../dovecot-ldap_1%3a2.0.18-1_amd64.deb) ... Unpacking replacement dovecot-ldap ... Starting IMAP/POP3 mail server: dovecot.
