On Tue, 12 Sep 2006 12:50:18 +0800, Yu, Ke wrote:
> Hi,
>
> From cset 10921, ioemu: prefix is removed from disk config in
> /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises
> a question: how would HVM domain know if one disk is a qemu-dm disk or a
> VBD disk?
>
> From current implementation, qemu-dm will recognize disk had, hdb, hdc,
> hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) .
Huh. I didn't know we did that.
> So the
> result is: qemu-dm will mount /dev/hda-hdd, and VBD driver will mount the
> rest (/dev/hde,...).
I assume that VBD means the paravirtual driver. If so, we really
shouldn't even give the option of exposing as hdX or sdX but rather only
expose as xvdX (or whatever our assigned prefix it).
Might as well make it a policy for HVM before people start using something
else. Upstream will never allow us to hijack other major/minor numbers so
we should stop doing it as soon as possible.
Of course, using our assigned names also solves your problem so it makes
everyone happy :-)
Regards,
Anthony Liguori
> Actually, VBD will also try to mount /dev/hda..., but
> failed with error message "register_blkdev: cannot get major 3 for ide",
> since the /hda is already mounted as qemu-dm disk.
>
> This looks a litt bit confusing. So I just wonder: is this the expected
> behavor? Do we intend having some explicit mechanism to indentify ioemu
> disk and VBD disk?
>
> Best Regards
> Ke_______________________________________________ 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
|
Home