[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



On Sat, Jan 23, 2010 at 06:07:37PM -0800, mail ignored wrote:
> 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,
> 

Did you try 2.6.32-41.1 ?

> [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.
> 
> 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?
> 

Please paste the console log of the guest kernel.. you might see more 
messages there.

Or nothing on the console? 

(You might need to add "console=xvc0" to the guest kernel cmdline options 
to get the output to xen console.

Start with "xm create -f /etc/xen/<guest> -c" to get immediately attached 
to the console.

-- Pasi


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.