Re: [Xen-devel] More on domU not starting

[Ryan Grimm <grimm@xxxxxxxxxx>]

I had a similar problem and was able to rectify it by including the 
following line:
disk = [ 'phy:/dev/sda3,hda1,w' ]

which, as stated in the user doc in section 5.1, will export /dev/sda3 
(the partition where my image is) to the domU as hda1.
then, my disk config is:

disk = [ 'file:/path/to/image,hda1,w' ]

also, the user doc's example in section 5.1 says that disk = [ 
'phy:sda3,hda1,w' ] would work but it did not unless i put /dev/ in front 
of sda3, like above.
ryan

On Tue, 11 Oct 2005, Rob Gardner wrote:

> Xend does seem to start ok, and xm seems to run ok. But domU still can't find 
> its boot disk. In the boot messages I see:
> xen_blk: Initialising virtual block device driver
>
> But following that I see no message like  Registering block device major 3
> which I normally see on a working system.
>
> The non-working system has python 2.3.4 on it. Could this be a problem?
>
> My disk config is:
> disk = [ 'file:/xen/disk-images/dom1.fs,sda1,w']
> The strange thing is if I change the filename to something non-existent, the 
> behavior stays the same. The disk image file does exist and is in good shape.
>
> Rob
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel