From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Michael <jan.michael@cern.ch>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Xen Mailing List <xen-devel@lists.xensource.com>
Subject: Re: Re: [ANNOUNCE] virtbench now has xen support
Date: Mon, 21 May 2007 14:13:34 +0100 [thread overview]
Message-ID: <46519AFE.4050501@goop.org> (raw)
In-Reply-To: <DB1C98A8-CBEE-44E3-99D5-BD74A413BB04@cern.ch>
Jan Michael wrote:
> Salut Rusty,
>
> On 21.05.2007, at 08:16, Rusty Russell wrote:
>> On Fri, 2007-05-18 at 19:56 +0200, Jan Michael wrote:
>>> Hi Rusty,
>>
>> Hi JaN!
>>
>>> Now I'm one step further. The domUs will be created, but they are
>>> destroyed after seconds. I started one of them manually with console
>>> so that I could see the error message:
>>>
>>> <boot error>
>>> md: autorun ...
>>> md: ... autorun DONE.
>>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
>>> block(1,0)
>>> </boot error>
>>>
>>> That must have been something to do with the kernel I'm using. I have
>>> to investigate (google) this. But if you can also help me in this
>>> case - you're welcome!
>>
>> Hmm, perhaps your kernel doesn't have INITRD support? The default Xen
>> kernel works (at least, for me on i386 it does)...
>
> Hm. No. Unfortunately the kernel I'm using has INITRD support, because
> we need it also for self-installation of our domUs in productive
> environment. I attached the whole startup log. The RAM disk driver is
> loaded in line 50.
> Do you have any other suggestions?
66 XENBUS: Device with no driver: device/vbd/51713
67 XENBUS: Device with no driver: device/vif/0
looks worrysome. Do you have netfront and blkfront compiled into (your
kernel, either built-in or as modules in your initrd)?
Though it seems you have a more basic problem with mounting the initrd.
J
next prev parent reply other threads:[~2007-05-21 13:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 2:38 [ANNOUNCE] virtbench now has xen support Rusty Russell
2007-05-15 7:44 ` Jan Michael
2007-05-15 19:50 ` Anthony Liguori
2007-05-18 10:14 ` Jan Michael
2007-05-18 11:51 ` Rusty Russell
2007-05-18 17:56 ` Jan Michael
2007-05-21 6:16 ` Rusty Russell
2007-05-21 8:13 ` Jan Michael
2007-05-21 13:13 ` Jeremy Fitzhardinge [this message]
2007-05-21 23:45 ` Rusty Russell
2007-05-22 7:33 ` Jan Michael
2007-05-22 9:33 ` Jeremy Fitzhardinge
2007-05-23 18:05 ` Jan Michael
[not found] ` <157A1A05-C74F-4055-A71B-3068BFECB61E@cern.ch>
2007-05-24 16:11 ` Petersson, Mats
2007-06-09 3:19 ` Rusty Russell
[not found] ` <7C99B109-A4B0-4957-8583-E3C3651BCE1D@cern.ch>
2007-06-09 3:57 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46519AFE.4050501@goop.org \
--to=jeremy@goop.org \
--cc=aliguori@us.ibm.com \
--cc=jan.michael@cern.ch \
--cc=rusty@rustcorp.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.