Control: reassign -1 linux-image-3.2.0-4-amd64/3.2.46-1
07.08.2013 14:20, Vladimir Kudrya wrote:
Package: qemu-kvm Version: 1.1.2+dfsg-6 Severity: important Dear Maintainer, I have set up several virtual machines with libvirt and mirrored lvm storage. When attempting to create a snapshot of VM's disk I get 'general protection fault: 0000 [#1] SMP' When I try to remove the snapshot after reboot with lvremove, whole lvm i/o freeze with any associated tasks Aug 7 08:15:10 vhost2 kernel: [ 213.258004] md/raid1:mdX: active with 2 out of 2 mirrors Aug 7 08:15:10 vhost2 kernel: [ 213.258194] created bitmap (25 pages) for device mdX Aug 7 08:15:11 vhost2 kernel: [ 213.454238] mdX: bitmap initialized from disk: read 4/2 pages, set 0 of 51200 bits Aug 7 08:17:01 vhost2 /USR/SBIN/CRON[4372]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 7 08:17:37 vhost2 kernel: [ 360.656677] INFO: task kvm:3783 blocked for more than 120 seconds. Aug 7 08:17:37 vhost2 kernel: [ 360.656749] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 7 08:17:37 vhost2 kernel: [ 360.656813] kvm D ffff880106c33780 0 3783 1 0x00000000 Aug 7 08:17:37 vhost2 kernel: [ 360.656817] ffff8801010730e0 0000000000000086 0000000000000008 ffff880102ecd650 Aug 7 08:17:37 vhost2 kernel: [ 360.656821] 0000000000013780 ffff8800e8c1dfd8 ffff8800e8c1dfd8 ffff8801010730e0 Aug 7 08:17:37 vhost2 kernel: [ 360.656825] ffffffff8101360a ffffffff810660a1 ffff880105c3e0c0 ffff880106c33fd0 Aug 7 08:17:37 vhost2 kernel: [ 360.656829] Call Trace: Aug 7 08:17:37 vhost2 kernel: [ 360.656836] [<ffffffff8101360a>] ? read_tsc+0x5/0x14 Aug 7 08:17:37 vhost2 kernel: [ 360.656841] [<ffffffff810660a1>] ? timekeeping_get_ns+0xd/0x2a Aug 7 08:17:37 vhost2 kernel: [ 360.656845] [<ffffffff8134da71>] ? io_schedule+0x59/0x71 Aug 7 08:17:37 vhost2 kernel: [ 360.656848] [<ffffffff81123e30>] ? __blockdev_direct_IO+0x99e/0xa67 Aug 7 08:17:37 vhost2 kernel: [ 360.656853] [<ffffffff81122071>] ? blkdev_max_block+0x2e/0x2e Aug 7 08:17:37 vhost2 kernel: [ 360.656857] [<ffffffff81121b95>] ? blkdev_direct_IO+0x4e/0x53 Aug 7 08:17:37 vhost2 kernel: [ 360.656860] [<ffffffff81122071>] ? blkdev_max_block+0x2e/0x2e Aug 7 08:17:37 vhost2 kernel: [ 360.656864] [<ffffffff810b57c8>] ? generic_file_direct_write+0xdc/0x14c Aug 7 08:17:37 vhost2 kernel: [ 360.656868] [<ffffffff810b59cc>] ? __generic_file_aio_write+0x194/0x278 Aug 7 08:17:37 vhost2 kernel: [ 360.656871] [<ffffffff81062599>] ? hrtimer_cancel+0xc/0x16 Aug 7 08:17:37 vhost2 kernel: [ 360.656875] [<ffffffff8106def8>] ? futex_wait+0x1fe/0x236 Aug 7 08:17:37 vhost2 kernel: [ 360.656878] [<ffffffff81121e8d>] ? bd_may_claim+0x2e/0x2e Aug 7 08:17:37 vhost2 kernel: [ 360.656881] [<ffffffff81121eac>] ? blkdev_aio_write+0x1f/0x61 Aug 7 08:17:37 vhost2 kernel: [ 360.656885] [<ffffffff81121e8d>] ? bd_may_claim+0x2e/0x2e Aug 7 08:17:37 vhost2 kernel: [ 360.656888] [<ffffffff810fa6df>] ? do_sync_readv_writev+0xa3/0xe0 Aug 7 08:17:37 vhost2 kernel: [ 360.656892] [<ffffffff810364e8>] ? should_resched+0x5/0x23 Aug 7 08:17:37 vhost2 kernel: [ 360.656895] [<ffffffff81164201>] ? security_file_permission+0x16/0x2d Aug 7 08:17:37 vhost2 kernel: [ 360.656898] [<ffffffff810fa943>] ? do_readv_writev+0xaf/0x11c Aug 7 08:17:37 vhost2 kernel: [ 360.656900] [<ffffffff810364e8>] ? should_resched+0x5/0x23 Aug 7 08:17:37 vhost2 kernel: [ 360.656904] [<ffffffff8106f987>] ? sys_futex+0x120/0x151 Aug 7 08:17:37 vhost2 kernel: [ 360.656907] [<ffffffff810fac4f>] ? sys_pwritev+0x55/0x97 Aug 7 08:17:37 vhost2 kernel: [ 360.656910] [<ffffffff81353b52>] ? system_call_fastpath+0x16/0x1b Aug 7 08:17:37 vhost2 kernel: [ 360.656915] INFO: task lvremove:4329 blocked for more than 120 seconds. Aug 7 08:17:37 vhost2 kernel: [ 360.656976] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 7 08:17:37 vhost2 kernel: [ 360.657039] lvremove D ffff880106c13780 0 4329 4328 0x00000000 Aug 7 08:17:37 vhost2 kernel: [ 360.657043] ffff880102a223c0 0000000000000082 0000000000000008 ffff880106688040 Aug 7 08:17:37 vhost2 kernel: [ 360.657046] 0000000000013780 ffff8800cf303fd8 ffff8800cf303fd8 ffff880102a223c0 Aug 7 08:17:37 vhost2 kernel: [ 360.657050] ffff8800cf303a78 ffff8800cf303a78 ffff880102a48670 ffff880106c13fd0 Aug 7 08:17:37 vhost2 kernel: [ 360.657053] Call Trace: Aug 7 08:17:37 vhost2 kernel: [ 360.657055] [<ffffffff8134da71>] ? io_schedule+0x59/0x71 Aug 7 08:17:37 vhost2 kernel: [ 360.657058] [<ffffffff81123e30>] ? __blockdev_direct_IO+0x99e/0xa67 Aug 7 08:17:37 vhost2 kernel: [ 360.657062] [<ffffffff811ab8f9>] ? kobject_get+0x12/0x17 Aug 7 08:17:37 vhost2 kernel: [ 360.657066] [<ffffffff81122071>] ? blkdev_max_block+0x2e/0x2e Aug 7 08:17:37 vhost2 kernel: [ 360.657069] [<ffffffff81121b95>] ? blkdev_direct_IO+0x4e/0x53 Aug 7 08:17:37 vhost2 kernel: [ 360.657072] [<ffffffff81122071>] ? blkdev_max_block+0x2e/0x2e Aug 7 08:17:37 vhost2 kernel: [ 360.657076] [<ffffffff810b5c52>] ? generic_file_aio_read+0xed/0x5cf Aug 7 08:17:37 vhost2 kernel: [ 360.657078] [<ffffffff81122a11>] ? blkdev_get+0x2a7/0x2a7 Aug 7 08:17:37 vhost2 kernel: [ 360.657081] [<ffffffff810f8abe>] ? __dentry_open+0x1cd/0x2c2 Aug 7 08:17:37 vhost2 kernel: [ 360.657084] [<ffffffff81101fa0>] ? dget+0x12/0x1e Aug 7 08:17:37 vhost2 kernel: [ 360.657087] [<ffffffff8110a1d7>] ? dput+0x27/0xee Aug 7 08:17:37 vhost2 kernel: [ 360.657090] [<ffffffff81110037>] ? mntput_no_expire+0x1e/0xc9 Aug 7 08:17:37 vhost2 kernel: [ 360.657092] [<ffffffff8110a1d7>] ? dput+0x27/0xee Aug 7 08:17:37 vhost2 kernel: [ 360.657094] [<ffffffff81110037>] ? mntput_no_expire+0x1e/0xc9 Aug 7 08:17:37 vhost2 kernel: [ 360.657097] [<ffffffff810f9d58>] ? do_sync_read+0xb4/0xec Aug 7 08:17:37 vhost2 kernel: [ 360.657100] [<ffffffff810fa443>] ? vfs_read+0x9f/0xe6 Aug 7 08:17:37 vhost2 kernel: [ 360.657103] [<ffffffff810fa4cf>] ? sys_read+0x45/0x6b Aug 7 08:17:37 vhost2 kernel: [ 360.657105] [<ffffffff81353b52>] ? system_call_fastpath+0x16/0x1b I was able to restore normal operation issuing 'dmsetup resume /dev/vguestpool/*' But another attempt to create a snapshot resulted in general protection fault. Symptoms are analogus to RH bug report: https://bugzilla.redhat.com/show_bug.cgi?id=254185 I can not tell for sure, but the problem may have begun after upgrade of linux-image-3.2.0-4-amd64 from 3.2.39-2 to 3.2.46-1 I was able to create snapshots successfully some time before upgrade. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (900, 'stable'), (400, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qemu-kvm depends on: ii adduser 3.113+nmu3 ii ipxe-qemu 1.0.0+git-20120202.f6840ba-3 ii libaio1 0.3.109-3 ii libasound2 1.0.25-4 ii libbluetooth3 4.99-2 ii libbrlapi0.5 4.4-10+deb7u1 ii libc6 2.13-38 ii libcurl3-gnutls 7.26.0-1+wheezy3 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgnutls26 2.12.20-7 ii libiscsi1 1.4.0-3 ii libjpeg8 8d-1 ii libncurses5 5.9-10 ii libpng12-0 1.2.49-1 ii libpulse0 2.0-6.1 ii libsasl2-2 2.1.25.dfsg1-6+deb7u1 ii libsdl1.2debian 1.2.15-5 ii libspice-server1 0.11.0-1 ii libtinfo5 5.9-10 ii libusbredirparser0 0.4.3-2 ii libuuid1 2.20.1-5.3 ii libvdeplug2 2.3.2-4 ii libx11-6 2:1.5.0-1+deb7u1 ii python 2.7.3-4 ii qemu-keymaps 1.1.2+dfsg-6a ii qemu-utils 1.1.2+dfsg-6a ii seabios 1.7.0-1 ii vgabios 0.7a-3 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages qemu-kvm recommends: ii bridge-utils 1.5-6 ii iproute 20120521-3+b3 Versions of packages qemu-kvm suggests: pn debootstrap <none> pn samba <none> pn vde2 <none> -- no debconf information
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
