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] Xen domU stalling during boot

To: "Mark Petersen" <mtp@xxxxxxxxxx>
Subject: Re: [Xen-users] Xen domU stalling during boot
From: mrkris@xxxxxxxxxx
Date: Fri, 24 Mar 2006 20:47:01 -0500 (EST)
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 25 Mar 2006 01:48:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <7.0.1.0.2.20060324194040.02695150@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <56386.67.168.169.105.1143248483.squirrel@xxxxxxxxxx> <7.0.1.0.2.20060324194040.02695150@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.4
It turns out that I didn't have the neccessary tty's, and found it like 3
minutes before your email, was just getting ready to send it out. So it
all works well now. Can anyone recommend a good site for bootstrapping a
minimal debian sarge system? I just did a normal bootstrap with
debootstrap but apparently I missed a command or two to generate needed
devices.

mrkris

> At 07:01 PM 3/24/2006, you wrote:
>>on it. The problem I am having is I booted it up and it sits right here:
>>INIT: Id "6" respawning too fast: disabled for 5 minutes
>>INIT: no more processes left in this runlevel
>>
>>And it all started when it ran cron. Anyone run into this? Any idea what
>>it could be?
>
> It looks like your vtty's aren't setup and working
> properly.  Probably something to do with /dev/vtty1 not having been
> created.  It could be that something is botched in etch though.  What
> happens when you run a non-Xen kernel?  Can you gzip a log (you might
> have to get it from serial console) of the boot-up and send it if you
> can't get this resolved?  There's probably a more significant error
> message about /dev somewhere.  In the past this would have cause
> Linux to fork-bomb and you'd have no clue what happend, at least it's
> playing nice.
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>


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