WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] 2.6.31.6 pv_ops can't boot pv_ops DomU kernel

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] 2.6.31.6 pv_ops can't boot pv_ops DomU kernel
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Thu, 28 Jan 2010 23:13:35 +0200
Delivery-date: Thu, 28 Jan 2010 13:14:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B61FA33.3000706@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4B61E7BF.5020208@xxxxxxxxxxxxx> <20100128195820.GZ2861@xxxxxxxxxxx> <4B61FA33.3000706@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Thu, Jan 28, 2010 at 09:57:23PM +0100, Stefan Kuhne wrote:
> Am 28.01.2010 20:58, schrieb Pasi Kärkkäinen:
> > On Thu, Jan 28, 2010 at 08:38:39PM +0100, Stefan Kuhne wrote:
> >> Hello,
> >>
> >> i've a xen-4.0.0-rc1 with 2.6.31.6 pv_ops.
> >> Dom0 seams to work fine.
> >> But i can only boot "old" domU kernel.
> >> A pv_ops Kernel hangs after initrd.
> >>
> > 
> > Please post the "xm create -f /etc/xen/<guest> -c" full output.
> > 
> Here is it:
> 
> maxdata # xm del Test-Eis2
> maxdata # xm create -f /etc/xen/xm/xmTest-Eis2 -c
> Using config file "/etc/xen/xm/xmTest-Eis2".
> Started domain Test-Eis2 (id=1)
>                                [    0.024965] xenbus_probe wake_waiting
> [    0.024986] xenbus_probe_init ok
> [    0.053377] xenbus_probe_backend_init bus registered ok
> [    0.053377] xenbus_probe_devices backend
> [    0.056058] xenbus_probe_devices failed xenbus_directory
> [    0.056058] backend_probe_and_watch devices probed ok
> [    0.056062] backend_probe_and_watch watch add ok ok
> [    0.056062] backend_probe_and_watch all done
> [    0.057093] xenbus_probe_frontend_init bus registered ok
> [    0.057110] xenbus_probe_devices device
> [    0.057132] xenbus_probe_devices 1/3 vbd
> [    0.057132] xenbus_probe_device_type type vbd
> [    0.057132] xenbus_probe_device_type 1/2 769
> [    0.057172] xenbus_probe_device_type 2/2 770
> [    0.058184] xenbus_probe_devices 2/3 vif
> [    0.058198] xenbus_probe_device_type type vif
> [    0.058222] xenbus_probe_device_type 1/1 0
> [    0.058222] xenbus_probe_devices 3/3 console
> [    0.058222] xenbus_probe_device_type type console
> [    0.058222] xenbus_probe_device_type 1/1 0
> [    0.059188] frontend_probe_and_watch devices probed ok
> [    0.059214] frontend_probe_and_watch watch add ok ok
> [    0.059214] frontend_probe_and_watch all done
> [    0.095263] microcode: no support for this CPU vendor
> [    0.134850] registering netback
> [    0.203010] i8042.c: No controller found.
> 

Do you have "console=hvc0 earlyprintk=xen" passed to the domU kernel cmdline? 
You should get more output then..

-- Pasi


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