From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nuno Silva Subject: Re: which (pseudo)-device can be used as VBD in xenU ? Date: Mon, 29 Nov 2004 20:11:43 +0000 Message-ID: <41AB827F.1040606@vgertech.com> References: <41AB557D.2070904@enix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <41AB557D.2070904@enix.org> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: =?ISO-8859-1?Q?J=E9r=F4me_Petazzoni?= Cc: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org J=E9r=F4me Petazzoni wrote: > I saw examples of VBD using hdXY and sdXY inside virtual machines, like= =20 > this : disk=3Dphy:hda5,hda1,w >=20 > And I would like to do this : disk=3Dphy:md8,md1,w >=20 > But it failed (the "real" md driver tried to access something that=20 > didn't exist, of course, and rootfs couldn't be mounted). Did I do=20 > something wrong, or is the frontend driver only able to "fake" hdXY and= =20 > sdXY devices ? I guess that you can export _ALL_ the block devices that make your md8=20 and create the md *in* the guest. Exporting a "normal" block device (md8, from the host) is the same as=20 exporting another "normal" block device, like sda2. > FYI, my motivation is to supply mdX devices to ease migration from/to=20 > real servers. IMHO one of the biggest advantages of virtualization is hardware=20 independence. You'll loose (part of) that if you create your md inside=20 the guest... At least it'll be a pain to mantain... Regards, Nuno Silva ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/