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] 64-bit PV domU (2.6.27) hangs during boot?

To: "Logan, John G." <John.G.Logan@xxxxxxx>
Subject: Re: [Xen-users] 64-bit PV domU (2.6.27) hangs during boot?
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Tue, 2 Sep 2008 14:53:35 -0400
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 02 Sep 2008 11:54:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=STyi/bbwSLX8QiiuqJ5NQdiDvAzoFywNSR4a3x0b2Tg=; b=n9o8kgQtRlrWN2SY7HKF70y88h975QcszADXFthn4IGpA3VTWXkob6VGmINIruewpb wjJecDeW8+QhYDbZFFaI7Tg22V8Ft5Uv2HGs0NlwIRx20J5sAWtV7fSpLlFKMQCc7KgH ro2NLhVcc2y9pxX2PDRZZWmnDB6reKrIzHOQE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=ddoIJcNoBGSw+DQEMldZPW5QyPQNVeaB1qayLX8PMK7giOhG9WnKLCjDRULBUdxCrc bxy6HgcW/zXeXg5u10SNcJ2sBWlyaxlaGXJOiEJ5wlIyL1gPfJeku7FIiIt5IwUbvkGR YJ3vfJ7XdXJRwDO2IPVha49GjaFE4iflsbU6c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CAA0DF84CAB184EB09525A5938E5C748DE8E283@xxxxxxxxxxxxxxxxx>
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: <1e16a9ed0809020936t44b68962q849d7ff058167@xxxxxxxxxxxxxx> <4CAA0DF84CAB184EB09525A5938E5C748DE8E283@xxxxxxxxxxxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [    0.669545] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: 
> dm-devel@xxxxxxxxxx
> Done.
> Begin: Running /scripts/init-premount ...
> Done.
> Begin: Mounting root file system... ...
> Begin: Running /scripts/local-top ...
> Done.
> Begin: Waiting for root file system... ...
> Done.
>  Reading all physical volumes.  This may take a while...
> Begin: Waiting for root file system... ...
> Done.
>  Reading all physical volumes.  This may take a while...
> <<and so on...>>
>

Did you wait for this to finish? or does it hang?
It may take awhile, but it should drop you to a busybox shell.

Then you can double check things like
/proc/cmdline
/proc/modules
/dev/xvd*


> http://wiki.xensource.com/xenwiki/XenParavirtOps says to use xvd devices,

xvd devices are right, and seem right in your gues config

so I'm doing that, as well as using tap:aio.  'xm block-list' on the
domain gives me:

>

> Vdev  BE handle state evt-ch ring-ref BE-path
> 51713  0    0     1      -1     -1    /local/domain/0/backend/tap/30/51713
> 51714  0    0     1      -1     -1    /local/domain/0/backend/tap/30/51714
>
> I wish I understood more about what this output means, but the event channel 
> ID of -1 for these devices doesn't seem like a good sign.
>

It doesn't but they are not connected it seems...

> Could it be that something's missing from the initramfs I'm using?  I had 
> thought that the Ubuntu intrepid stuff was ready to go as a 64-bit domU.
>

This could be your problem, and likely is. I doubt the intrepid stuff
is that ready to go, they are still in alpha.

The stuff from kernel.org has been working well from me,so you should
double check that they built the initramfs
 correctly.

I would check the config in /boot/ for the kernel that you are using
to see how the XEN, PARA, HVC, stuff was built.

Below are those config options in the 2.27-rc4 kernel from kernel.org
that I have been using successfully.

CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=32
CONFIG_XEN_SAVE_RESTORE=y
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_NETXEN_NIC=m
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_XEN_KBDDEV_FRONTEND=y
CONFIG_HVC_XEN=y
CONFIG_XEN_FBDEV_FRONTEND=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y

CONFIG_PARAVIRT_GUEST=y
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_CLOCK=y
CONFIG_PARAVIRT_DEBUG=y

CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y


Hope that helps,
Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

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