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

Re: [Xen-users] Debian domU trouble


  • To: Xen-Users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Gabriel Patiño <gepatino@xxxxxxxxx>
  • Date: Tue, 4 Oct 2005 09:56:55 -0300
  • Delivery-date: Tue, 04 Oct 2005 12:54:37 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gkAUopmzbRAh1uA/n7Rz2+cMjOFkLzITXE86pf6eVoB5JPOR81ZIPUIA/IfsQt4yKDRBqQ1p6Op5ay9/Lzzs09ax+OAClnIjUJN2Mll0h782IUdkj7CM97vlqzuidJAN4F4SxwF8o2vwjNRdj3zHE+7tPpb2Rk621/vCWQA2qu4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

2005/10/3, Yann Ramin <atrus@xxxxxxxxxxxxxx>:
>
> I have an Ubuntu dom0 system running the dom0 kernel from the Xen distribution
> (2.0.7).
>
> The kernel on the domU boots successfuly, and init starts. After debian starts
> cron, the system appears to hang. After a few minutes, the domU kernel says
> that PIDs 1-5 are respawning too fast and have been suspended. I'm using a
> file loopback as the main disk.


AFAK, the respawning too fast error is related to the consoles defined
in /etc/inittab.

I've commented out the folowing lines, and it stop appearing:

2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6

This lines are for the alternative consoles (ALT+F2, ALT+F3,etc), so
there is no problem in disabling them.


For the cron problems, maybe its trying to update the system time
before the network is up?

--
Gabriel E. Patiño

_______________________________________________
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®.