Recent update of Xen packages causes kernel panic with HVM domU
Recently I lost power (along with much of New England) for eight days.
When the juice started flowing again, I restarted my Xen server (Debian
Squeeze, dual Xeon (8 cores), 16GB RAM), which came up fine but had a
pile of package updates pending...
===============================================================================
[UPGRADE] libavcodec52 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libavformat52 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libavutil49 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libnss3-1d 3.12.8-1+squeeze3 -> 3.12.8-1+squeeze4
[UPGRADE] libpostproc51 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libpq5 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1
[UPGRADE] libswscale0 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libxenstore3.0 4.0.1-2 -> 4.0.1-4
[UPGRADE] postgresql 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] postgresql-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1
[UPGRADE] postgresql-client 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] postgresql-client-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1
[UPGRADE] postgresql-contrib 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] postgresql-contrib-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1
[UPGRADE] postgresql-doc 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] postgresql-doc-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] tzdata 2011m-0squeeze1 -> 2011n-0squeeze1
[UPGRADE] tzdata-java 2011m-0squeeze1 -> 2011n-0squeeze1
[UPGRADE] xen-hypervisor-4.0-amd64 4.0.1-2 -> 4.0.1-4
[UPGRADE] xen-utils-4.0 4.0.1-2 -> 4.0.1-4
[UPGRADE] xenstore-utils 4.0.1-2 -> 4.0.1-4
===============================================================================
I did an "aptitude safe-upgrade" without even really looking at it. At
the time, I had an HVM domU running. The upgrade crashed the system.
I'm pretty sure it crashed while configuring the
xen-hypervisor-4.0-amd64 package. When I brought it back up, I ran a
"dpkg --configure -a" to finish the job.
However, now, when I try to use my Windows HVM, I always get a kernel
panic dealing with the vbd. For example...
========8<=================
kernel:[ 1919.981706] general protection fault: 0000 [#1] SMP
kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent
kernel:[ 1919.981870] Stack:
kernel:[ 1919.981893] Call Trace:
kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00
00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db
74 0c 8b 42 14 <48> 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44
89 ee 83
kernel:[ 1920.014542] general protection fault: 0000 [#2] SMP
kernel:[ 1920.014550] last sysfs file: /sys/devices/vbd-3-832/uevent
kernel:[ 1920.014729] Stack:
kernel:[ 1920.014752] Call Trace:
kernel:[ 1920.014836] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00
00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db
74 0c 8b 42 14 <48> 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44
89 ee 83
========8<=================
Then the system destabilizes.
I have a pretty common setup. I can't be the only one!
What the heck happened with those updates?!? Please help me out!
thanks,
-d
Reply to: