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

Re: [Xen-users] Debian Etch 4.0 domU will not boot

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Andrew W." <andrewinet@xxxxxxxxx>
  • Date: Fri, 6 Jul 2007 07:25:42 -0400
  • Delivery-date: Fri, 06 Jul 2007 04:23:38 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RkQV48ewKswl/ESs3eHNxfrT2zunMURnHQ/ZJ10iu+Yv585D0nA5IStuUu7FMtxgun36fXlAbfdIFS7tSA9l7FoetonO1eACV5gIwcFv+Q/plMnQrZZkfT0ON5AVMB1X93XRZrtGYyVwCTERGiQxgMUvdkTs37IwSqinhe7XsAA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I hate to keep bumping this topic, but it's worth pointing out that
Ubuntu 7.04 Feisty Fawn exhibits the same behavior.  As soon as init
starts, CPU utilization goes to 100%.  It gets all the way through the
boot process but will not spawn a login prompt.


On 7/6/07, Andrew W. <andrewinet@xxxxxxxxx> wrote:
One other thing I can add, which will hopefully shed quite a bit of
light on what's happening.  Once I see "INIT: version 2.86 booting", a
quick flip over to 'xm top' in another console reveals that the domU
starts using 100% of its available CPU at that point, and does not
stop from henceforth until it's destroyed.


Andrew Wang

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.