From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Gardner Subject: Re: More on domU not starting -- HELP Date: Wed, 12 Oct 2005 15:48:06 -0600 Message-ID: <434D8496.5060805@hp.com> References: <434C2DC0.10701@hp.com> <434C46D8.9020204@hp.com> <434D78A9.4060904@hp.com> <1129151915.16017.188.camel@pluto.linsolutions.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1129151915.16017.188.camel@pluto.linsolutions.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ted Kaczmarek Cc: Ryan Grimm , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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