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] Problems with booting Debian DomU

To: WM RWL <wmrwl@xxxxxxxxxxx>
Subject: Re: [Xen-users] Problems with booting Debian DomU
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Wed, 30 Sep 2009 12:38:38 +0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 29 Sep 2009 22:39:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BAY109-W21328754CBA57EBCCC1D7DBCD50@xxxxxxx>
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: <BAY109-W21328754CBA57EBCCC1D7DBCD50@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Sep 30, 2009 at 6:36 AM, WM RWL <wmrwl@xxxxxxxxxxx> wrote:
> I'm running Xen 3.2 on Debian 5.0 (Lenny) and am having trouble booting up a
> Debian Etch DomU.  It hangs at the end when it says "Starting periodic
> command scheduler: cron."

I think it's fully booted by then. You just don't see the login prompt.

> Here is my config file in /etc/xen:
>
> kernel="/boot/vmlinuz-2.6.26-2-xen-686"
> ramdisk="/boot/initrd.img-2.6.26-2-xen-686"

I don't like putting kernels on dom0. For one thing, you need to sync
dom0's kernel and domU's /lib/modules directory. I prefer pygrub or
pvgrub instead. Not directly related to your problem though.

What I think happens is your domU doesn't know where the console is.
One way to fix that is look at domU boot log, look for "xvc0" or
"hvc0". That's where xen console is. After that, you need to edit
domU's /etc/inittab and /etc/securetty to spawn login console and
allow root login on /dev/xvc0 (or hvc0)

-- 
Fajar

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