[Xen-users] DomU kernel-xen upgade from 2.6.31 - 2.6.32 causes Guest boot to fail. known issue?

[mail ignored <0.bugs.only.0@xxxxxxxxx>]

running @ Dom0,

 rpm -qa | egrep "kernel-xen-2|xen-3"
  xen-3.4.1_19718_05-1.1.x86_64
  kernel-xen-2.6.31.8-0.1.1.x86_64

booting a test guest DomU with kernel-xen-2.6.31.8-0.1.1.x86_64 works
fine, as expected.

if i upgrade @ DomU from

  kernel-xen-2.6.31.8-0.1.1.x86_64

to 2.6.32-41-xen (opensuse KOTD), no problems at the upgrade or with mkinitrd,

   ls -al /boot/{vmlinuz,initrd}-xen
      lrwxrwxrwx 1 root root 20 2010-01-23 17:19 /boot/initrd-xen ->
initrd-2.6.32-41-xen
      lrwxrwxrwx 1 root root 21 2010-01-23 17:19 /boot/vmlinuz-xen ->
vmlinuz-2.6.32-41-xen

but, boot to same DomU with 'new' kernel-xen fails,

...
[2010-01-23 17:40:33 4632] DEBUG (DevController:97) DevController:
writing {'domain': 'test', 'frontend':
'/local/domain/5/device/console/0', 'uuid':
'71f561b2-2239-c14b-4506-74a973e71faa', 'frontend-id': '5', 'state':
'1', 'location': '2', 'online': '1', 'protocol': 'vt100'} to
/local/domain/0/backend/console/5/0.
[2010-01-23 17:40:33 4632] DEBUG (pciif:468)
XendDomainInfo.handleAerStateWatch
[2010-01-23 17:40:33 4632] DEBUG (XendDomainInfo:1733)
XendDomainInfo.handleShutdownWatch
[2010-01-23 17:40:35 4632] DEBUG (DevController:139) Waiting for
devices vif.
[2010-01-23 17:40:35 4632] DEBUG (DevController:144) Waiting for 0.
[2010-01-23 17:40:35 4632] DEBUG (DevController:654)
hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status.
[2010-01-23 17:40:35 4632] DEBUG (DevController:668)
hotplugStatusCallback 1.
[2010-01-23 17:40:35 4632] DEBUG (DevController:144) Waiting for 1.
[2010-01-23 17:40:35 4632] DEBUG (DevController:654)
hotplugStatusCallback /local/domain/0/backend/vif/5/1/hotplug-status.
[2010-01-23 17:40:35 4632] DEBUG (DevController:668)
hotplugStatusCallback 1.
[2010-01-23 17:40:35 4632] DEBUG (DevController:144) Waiting for 2.
[2010-01-23 17:40:35 4632] DEBUG (DevController:654)
hotplugStatusCallback /local/domain/0/backend/vif/5/2/hotplug-status.
[2010-01-23 17:40:35 4632] DEBUG (DevController:668)
hotplugStatusCallback 1.
[2010-01-23 17:40:35 4632] DEBUG (DevController:144) Waiting for 3.
[2010-01-23 17:40:35 4632] DEBUG (DevController:654)
hotplugStatusCallback /local/domain/0/backend/vif/5/3/hotplug-status.
[2010-01-23 17:40:35 4632] DEBUG (DevController:668)
hotplugStatusCallback 1.
[2010-01-23 17:40:35 4632] DEBUG (DevController:139) Waiting for
devices vkbd.
[2010-01-23 17:40:35 4632] DEBUG (DevController:139) Waiting for
devices ioports.
[2010-01-23 17:40:35 4632] DEBUG (DevController:139) Waiting for
devices tap.
[2010-01-23 17:40:35 4632] DEBUG (DevController:139) Waiting for
devices console.
[2010-01-23 17:40:35 4632] DEBUG (DevController:144) Waiting for 0.
[2010-01-23 17:40:35 4632] DEBUG (DevController:139) Waiting for
devices vscsi.
[2010-01-23 17:40:35 4632] DEBUG (DevController:139) Waiting for
devices vbd.
[2010-01-23 17:40:35 4632] DEBUG (DevController:144) Waiting for
51712.
[2010-01-23 17:40:35 4632] DEBUG (DevController:654)
hotplugStatusCallback
/local/domain/0/backend/vbd/5/51712/hotplug-status.
[2010-01-23 17:40:35 4632] DEBUG (DevController:668)
hotplugStatusCallback 1.
[2010-01-23 17:40:35 4632] DEBUG (DevController:144) Waiting for
51728.
[2010-01-23 17:40:35 4632] DEBUG (DevController:654)
hotplugStatusCallback
/local/domain/0/backend/vbd/5/51728/hotplug-status.
[2010-01-23 17:40:35 4632] DEBUG (DevController:668)
hotplugStatusCallback 1.
[2010-01-23 17:40:35 4632] DEBUG (DevController:144) Waiting for
51744.
[2010-01-23 17:40:35 4632] DEBUG (DevController:654)
hotplugStatusCallback
/local/domain/0/backend/vbd/5/51744/hotplug-status.
[2010-01-23 17:40:36 4632] DEBUG (DevController:654)
hotplugStatusCallback
/local/domain/0/backend/vbd/5/51744/hotplug-status.
[2010-01-23 17:40:36 4632] DEBUG (DevController:668)
hotplugStatusCallback 1.
[2010-01-23 17:40:36 4632] DEBUG (DevController:139) Waiting for
devices irq.
[2010-01-23 17:40:36 4632] DEBUG (DevController:139) Waiting for
devices vfb.
[2010-01-23 17:40:36 4632] DEBUG (DevController:139) Waiting for
devices pci.
[2010-01-23 17:40:36 4632] DEBUG (DevController:144) Waiting for 0.
[2010-01-23 17:40:36 4632] DEBUG (DevController:139) Waiting for
devices vtpm.
[2010-01-23 17:40:36 4632] INFO (XendDomain:1181) Domain test (5)
unpaused.
[2010-01-23 17:40:36 4632] WARNING (XendDomainInfo:1902) Domain has
crashed: name=test id=5.
[2010-01-23 17:40:36 4632] DEBUG (XendDomainInfo:2757)
XendDomainInfo.destroy: domid=5
[2010-01-23 17:40:37 4632] DEBUG (XendDomainInfo:2227) Destroying
device model
[2010-01-23 17:40:37 4632] INFO (image:567) test device model
terminated
[2010-01-23 17:40:37 4632] DEBUG (XendDomainInfo:2234) Releasing
devices
[2010-01-23 17:40:37 4632] DEBUG (XendDomainInfo:2247) Removing vif/0
[2010-01-23 17:40:37 4632] DEBUG (XendDomainInfo:1137)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-01-23 17:40:37 4632] DEBUG (XendDomainInfo:2247) Removing vif/1

if i kpartx the guest from Dom0, switch grub back to the 2.6.31.8-0.1
vmlinuz/initrd, it boots without error.

before spending diving into this ... is there a known prob with using
2.6.32x kernel in DomU?

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users