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

Re: [Xen-users] Missing device question


  • To: "Jörg Spilker" <js@xxxxxxxxx>
  • From: "Todd Deshane" <deshantm@xxxxxxxxx>
  • Date: Tue, 26 Aug 2008 12:32:53 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 26 Aug 2008 09:33:34 -0700
  • 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=HP7yATD2Af5c5rKdaavXJ0BbD1G1STo/DHKxt1GyLSfRqNGvKq1EMG3hRCJi7bp3lr lLnBBU4I/jJT9r77RB9SDutDOcirhHnxtoZFJg0bc53V+jS69NMCadpAw99LoamGqXQ6 iUsARs7A0rnQHZ/T4+1HHHYPeLHm0DhW71n4k=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Tue, Aug 26, 2008 at 12:26 PM, Jörg Spilker <js@xxxxxxxxx> wrote:
> Todd Deshane schrieb:
>
> Hello Todd,
>
>> This is usually caused by a missing module in the initial ram disk of the
>> guest.
>>
>> when it drops you to busybox, do what it suggest, check the modules,
>> cmdline,
>> and /dev/
>>
>> You may just need to rebuild your initial ram disk.
>
> the domU doesn´t drop into busybox. After complaining about the missing
> device, booting continues and the system comes up. Everything seems to be ok
> then. It´s just this annoying delay during bootup.
>

Interesting, I've never seen it do that. I'm afraid I don't know the
answer. Someone
else should be able to give at least a pointer.

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


 


Rackspace

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