This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: Virtual block devices (vbd) still not working... :-(

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Virtual block devices (vbd) still not working... :-(
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 11 Oct 2003 08:23:58 +0100
Cc: sven.kretzschmar@xxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 11 Oct 2003 08:24:23 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Sat, 11 Oct 2003 08:11:56 BST." <E1A8Duv-0001PU-00@xxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > Then I tried fdisk /dev/xvda  and it complained about not having
> > any partition label on it and that I have to set the number of
> > cylinders.
> > Entering the 'p' option in fdisk showed an empty partition table
> > and 255 heads, 63 sectors, 0 cylinders ??
> There wouldn't have been a valid partition table on the virtual
> disk, so fdisk would have just read rubbish and got confused. You
> could just delete all the bogus partitions, but using "dd
> if=/dev/zero of=/dev/vbda count=5" is probably safest.

This doesn't work for me. The problem is that vbd's are registered
with the Linux blkdev layer at boot time, but we have no mechanism to
properly attach new vbd's that are created after the domain has
already booted.

I really can't see how it could possibly have worked for you --- DOM0
would have booted with no vbd's and there's no way to register them

> That really is odd. Write access seems to work for me with the
> "-w" flag. I don't believe there is a "-rw" flag as read access
> is the default.

Something here is broke. 'vbd show' will show that the vbd is ro if
you specify -w, but rw if you specify -rw. I'll have a look... 

 -- Keir

This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
Xen-devel mailing list