From: Rob Gardner <rob.gardner@hp.com>
To: Ted Kaczmarek <tedkaz@optonline.net>
Cc: Ryan Grimm <grimm@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: More on domU not starting -- HELP
Date: Wed, 12 Oct 2005 15:48:06 -0600 [thread overview]
Message-ID: <434D8496.5060805@hp.com> (raw)
In-Reply-To: <1129151915.16017.188.camel@pluto.linsolutions.com>
Ted Kaczmarek wrote:
>
>Do not or use any existing designations or reuse any for domU's.
>In your case I am assuming you have a /dev/hda.
>
>edit the domU fstab to /dev/sda1 for / and dev/sda2 for swap and the
>domu config accordingly.
>
>Do not use sda1 or sda2 for any additional domU's.
>
>I will open up a bug on this shortly, this was bugging me for a while,
>but with this workaround my domu's now come up 100% of the time every
>time.
>
>
What was the exact failure mode you observed? It doesn't seem like it's
the same problem I'm seeing...
My domU doesn't get booted to anywhere near the point where fstab would
make a difference. After the message:
xen_blk: Initialising virtual block device driver
There is no message like:
Registering block device major xxx
Which looks to me like the kernel is simply not finding any block device
at all. Presumably this is because xen didn't provide one for it. Why it
does that, I don't know. But it used to work just fine a few weeks ago.
Rob
next prev parent reply other threads:[~2005-10-12 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 21:25 More on domU not starting Rob Gardner
2005-10-11 22:48 ` Ryan Grimm
2005-10-11 23:12 ` Rob Gardner
2005-10-12 16:01 ` Ryan Grimm
2005-10-12 20:57 ` More on domU not starting -- HELP Rob Gardner
2005-10-12 21:18 ` Ted Kaczmarek
2005-10-12 21:48 ` Rob Gardner [this message]
2005-10-12 22:13 ` Ted Kaczmarek
2005-10-12 22:53 ` Rob Gardner
-- strict thread matches above, loose matches on Subject: below --
2005-10-13 0:39 Deuskar, Prafulla
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=434D8496.5060805@hp.com \
--to=rob.gardner@hp.com \
--cc=grimm@us.ibm.com \
--cc=tedkaz@optonline.net \
--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.