Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
Package: linux-2.6
Version: 2.6.32-27
Severity: important
If the kernel is used for paravirtual DomU, then the DomU is normally started orshutdown. Ifthe xm save and xm restore
is invoked explicitely,then the DomU also restores normally. Only in the case the DomU is
restored automatically via xendomains script facility on Dom0 start it is restored, so visible in the list
(xm list), but also after a lot of time it does not consume any processor time (shows always 0.0 as consumed processor time) and
after switch to the instance (xm console) the console is not responding to any key.
The same problem was (at least) also in the package version 2.6.32-25 and 2.6.32-23.
If starting the same DomU with kernel from package version 2.6.32-21, then it works correctly
-- Package-specific info:
** Version:
Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-27) (maks@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 17:04:10 UTC 2010
** Kernel log:
[ 78.883733] vif8.1: no IPv6 routers present
[ 79.151732] vif8.2: no IPv6 routers present
[ 80.575300] device vif10.0 entered promiscuous mode
[ 80.579516] perbr: port 5(vif10.0) entering learning state
[ 83.099729] locbr: port 1(vif8.1) entering forwarding state
[ 83.435229] tap8.1: no IPv6 routers present
[ 83.487745] perbr: port 1(vif8.2) entering forwarding state
[ 83.655218] tap8.2: no IPv6 routers present
[ 83.791158] alloc irq_desc for 1210 on node 0
[ 83.791162] alloc kstat_irqs on node 0
[ 84.043221] tap8.0: no IPv6 routers present
[ 84.131388] device tap10.0 entered promiscuous mode
[ 84.132646] perbr: port 6(tap10.0) entering learning state
[ 84.181362] alloc irq_desc for 1209 on node 0
[ 84.181365] alloc kstat_irqs on node 0
[ 84.607717] vif9.0: no IPv6 routers present
[ 84.699718] vif9.2: no IPv6 routers present
[ 84.905506] vif9.1: no IPv6 routers present
[ 85.075718] vif9.3: no IPv6 routers present
[ 86.209157] vif9.6: no IPv6 routers present
[ 86.212755] vif9.4: no IPv6 routers present
[ 86.239161] vif9.5: no IPv6 routers present
[ 88.245200] locbr: port 2(tap8.1) entering forwarding state
[ 88.259224] perbr: port 2(tap8.2) entering forwarding state
[ 88.647215] tap9.2: no IPv6 routers present
[ 88.983212] tap9.1: no IPv6 routers present
[ 89.264206] tap9.6: no IPv6 routers present
[ 89.275208] tap9.3: no IPv6 routers present
[ 89.339202] tap9.0: no IPv6 routers present
[ 89.451215] perbr: port 3(vif9.0) entering forwarding state
[ 89.519208] devhazbr: port 1(vif9.1) entering forwarding state
[ 89.555234] tap9.5: no IPv6 routers present
[ 89.560204] tap9.4: no IPv6 routers present
[ 89.599212] devsafebr: port 3(vif9.2) entering forwarding state
[ 89.967706] tsthazbr: port 1(vif9.3) entering forwarding state
[ 90.147225] tstsafebr: port 1(vif9.4) entering forwarding state
[ 90.303212] prodhazbr: port 1(vif9.5) entering forwarding state
[ 90.513625] prodsafebr: port 6(vif9.6) entering forwarding state
[ 91.207274] vif10.0: no IPv6 routers present
[ 93.451213] perbr: port 4(tap9.0) entering forwarding state
[ 93.463200] devhazbr: port 2(tap9.1) entering forwarding state
[ 93.475204] devsafebr: port 4(tap9.2) entering forwarding state
[ 93.488702] tsthazbr: port 2(tap9.3) entering forwarding state
[ 93.665415] tstsafebr: port 2(tap9.4) entering forwarding state
[ 93.675194] prodhazbr: port 2(tap9.5) entering forwarding state
[ 93.675199] prodsafebr: port 7(tap9.6) entering forwarding state
[ 94.351238] tap10.0: no IPv6 routers present
[ 95.580705] perbr: port 5(vif10.0) entering forwarding state
[ 99.127185] perbr: port 6(tap10.0) entering forwarding state
[ 188.551522] prodsafebr: port 2(vif4.0) entering disabled state
[ 188.567361] prodsafebr: port 2(vif4.0) entering disabled state
[ 191.152151] device vif11.0 entered promiscuous mode
[ 191.156126] prodsafebr: port 2(vif11.0) entering learning state
[ 192.262854] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 192.329113] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 201.855967] vif11.0: no IPv6 routers present
[ 206.154960] prodsafebr: port 2(vif11.0) entering forwarding state
[ 758.603354] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
[ 760.095479] psmouse.c: resync failed, issuing reconnect request
[ 1038.325725] prodsafebr: port 2(vif11.0) entering disabled state
[ 1038.337513] prodsafebr: port 2(vif11.0) entering disabled state
[ 1040.199589] device vif12.0 entered promiscuous mode
[ 1040.203589] prodsafebr: port 2(vif12.0) entering learning state
[ 1041.523037] blkback: ring-ref 770, event-channel 9, protocol 1 (x86_64-abi)
[ 1041.594397] blkback: ring-ref 771, event-channel 10, protocol 1 (x86_64-abi)
[ 1050.517183] vif12.0: no IPv6 routers present
[ 1055.201170] prodsafebr: port 2(vif12.0) entering forwarding state
[ 1921.350497] prodsafebr: port 2(vif12.0) entering disabled state
[ 1921.362225] prodsafebr: port 2(vif12.0) entering disabled state
[ 1924.161006] device vif13.0 entered promiscuous mode
[ 1924.164900] prodsafebr: port 2(vif13.0) entering learning state
[ 1924.848952] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 1924.911654] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 1934.542445] vif13.0: no IPv6 routers present
[ 1939.162447] prodsafebr: port 2(vif13.0) entering forwarding state
[ 2441.036988] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
[ 3522.095864] prodsafebr: port 2(vif13.0) entering disabled state
[ 3522.117854] prodsafebr: port 2(vif13.0) entering disabled state
[ 3526.169073] device vif14.0 entered promiscuous mode
[ 3526.176916] prodsafebr: port 2(vif14.0) entering learning state
[ 3527.970429] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 3528.003303] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 3536.756647] vif14.0: no IPv6 routers present
[ 3541.172643] prodsafebr: port 2(vif14.0) entering forwarding state
[ 4272.117683] prodsafebr: port 2(vif14.0) entering disabled state
[ 4272.133477] prodsafebr: port 2(vif14.0) entering disabled state
[ 4274.282190] device vif15.0 entered promiscuous mode
[ 4274.285999] prodsafebr: port 2(vif15.0) entering learning state
[ 4274.998943] blkback: ring-ref 770, event-channel 9, protocol 1 (x86_64-abi)
[ 4275.051862] blkback: ring-ref 771, event-channel 10, protocol 1 (x86_64-abi)
[ 4285.108130] vif15.0: no IPv6 routers present
[ 4289.284121] prodsafebr: port 2(vif15.0) entering forwarding state
[ 4421.632525] prodsafebr: port 2(vif15.0) entering disabled state
[ 4421.644260] prodsafebr: port 2(vif15.0) entering disabled state
[ 4423.455405] device vif16.0 entered promiscuous mode
[ 4423.459100] prodsafebr: port 2(vif16.0) entering learning state
[ 4424.771009] blkback: ring-ref 8, event-channel 8, protocol 1 (x86_64-abi)
[ 4424.835549] blkback: ring-ref 9, event-channel 9, protocol 1 (x86_64-abi)
[ 4433.531967] vif16.0: no IPv6 routers present
[ 4438.461454] prodsafebr: port 2(vif16.0) entering forwarding state
** Model information
sys_vendor: HP
product_name: ProLiant DL320 G6
product_version:
chassis_vendor: HP
chassis_version:
bios_vendor: HP
bios_version: W07
Kernel: Linux 2.6.32-5-xen-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 linux-image-2.6.32-5-xen-amd64 depends on:
ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy
ii initramfs-tools 0.98.5 tools for generating an initramfs
ii linux-base 2.6.32-27 Linux image base package
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-5-xen-amd64 recommends:
ii firmware-linux-free 2.6.32-27 Binary firmware for various driver
Versions of packages linux-image-2.6.32-5-xen-amd64 suggests:
ii grub-legacy [grub] 0.97-63 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.32 <none> (no description available)
Versions of packages linux-image-2.6.32-5-xen-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
pn firmware-linux <none> (no description available)
pn firmware-linux-nonfree <none> (no description available)
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
ii xen-hypervisor-4.0-amd64 [xen 4.0.1-1 The Xen Hypervisor on AMD64
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20101117124532.9808.86594.reportbug@alg-puv-xen-1">http://lists.debian.org/20101117124532.9808.86594.reportbug@alg-puv-xen-1
11-17-2010, 12:11 PM
Timo Juhani Lindfors
Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
Artur Linhart <al.linux@bcpraha.com> writes:
> If the kernel is used for paravirtual DomU, then the DomU is
> normally started orshutdown. Ifthe xm save and xm restore is invoked
> explicitely,then the DomU also restores normally. Only in the case
> the DomU is restored automatically via xendomains script facility on
> Dom0 start it is restored, so visible in the list
Can you please test the patch that is included in that bug report?
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 84lj4sp01s.fsf@sauna.l.org">http://lists.debian.org/84lj4sp01s.fsf@sauna.l.org
11-17-2010, 05:41 PM
"Artur Linhart"
Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
Yes, it seems to be the same bug. I have figured out, I made a mistake, the statement "xm unpause" does not help. But I have a
little bit other behavior - I have more DomUs and some from them were restored and started correctly, some not. I cannot recognize
any general difference between them...
Unfortunately, I will not have the chance to test the patch directly, I use vanilla kernel from the package only...
-----Original Message-----
From: Timo Juhani Lindfors [mailto:timo.lindfors@iki.fi]
Sent: Wednesday, November 17, 2010 2:11 PM
To: Artur Linhart
Cc: 603802@bugs.debian.org
Subject: Re: Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
Artur Linhart <al.linux@bcpraha.com> writes:
> If the kernel is used for paravirtual DomU, then the DomU is
> normally started orshutdown. Ifthe xm save and xm restore is invoked
> explicitely,then the DomU also restores normally. Only in the case
> the DomU is restored automatically via xendomains script facility on
> Dom0 start it is restored, so visible in the list
Can you please test the patch that is included in that bug report?
__________ Informace od NOD32 5626 (20101117) __________
Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: D8023FF3BDE644B4A700AE12BBCB0E5F@private.praha.bcp raha.com">http://lists.debian.org/D8023FF3BDE644B4A700AE12BBCB0E5F@private.praha.bcp raha.com
11-18-2010, 06:35 AM
"Artur Linhart"
Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
One more correctlion to my last message - I have figured out, some instances have had still the kernel from version 2.6.32-21 what
was the reason why they started correctly... So it seems the effect can be seen on all DomUs with the kernel from package version
2.6.32-27
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 6D22EEE43B8840E8A700835178099DAE@private.praha.bcp raha.com">http://lists.debian.org/6D22EEE43B8840E8A700835178099DAE@private.praha.bcp raha.com