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] [PATCH 0/3] domUloader

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH 0/3] domUloader
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Thu, 26 Jan 2006 13:06:13 +0000
Cc: "Edwards, Nigel \(Nigel Edwards\)" <nigel.edwards@xxxxxx>, Jeremy Katz <katzj@xxxxxxxxxx>, "Philip R. Auld" <pauld@xxxxxxxxxxx>, Kurt Garloff <garloff@xxxxxxx>
Delivery-date: Thu, 26 Jan 2006 13:16:29 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <DF5E364A470421429AE6DC96979A4F6F56D9DC@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <DF5E364A470421429AE6DC96979A4F6F56D9DC@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.1
> There are good arguments for isolating storage management in Dom0.
> However, I have been looking at migration of domains with iSCSI
> and have found it a pain to fix up so that the iSCSI disk
> appears on the same /dev/sdx point in both source and destination
> Dom0s.

If you wrote a setup script for iSCSI devices (as we have for NBD, etc) you 
could do some sort of lookup to identify the correct device node when the 
domain arrives at a new host - then you wouldn't need for the device node to 
be the same everywhere.

Don't know terribly much about iSCSI, but you'd just need a device-node 
independent way of specifying the LUN as the block device in the config file.


> That is why I have started looking at direct iSCSI attachment in DomU
> via initrd. Then storage is fixed up automatically via migration of
> network connections. The disadvantage of this, as Kurt points out,
> is that it exposes your iSCSI infrastructure into DomU.
> Cheers,
> Nigel.
> > -----Original Message-----
> > From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> > Kurt Garloff
> > Sent: 23 January 2006 14:20
> > To: Philip R. Auld
> > Cc: Xen development list; Jeremy Katz
> > Subject: Re: [Xen-devel] [PATCH 0/3] domUloader
> >
> >
> > Hi,
> >
> > On Fri, Jan 20, 2006 at 06:08:26PM -0500, Philip R. Auld wrote:
> > > Of course, that would mean support for root on iSCSI in the
> >
> > installer
> >
> > > and mkinitrd code.
> >
> > I would really handle iSCSI in dom0 and export sdX/hdX to domU.
> > Solves the nasty OOM problem as well and makes your domains know
> > less about the underlaying storage. Which is good in my vision
> > of virtualization.
> >
> > Best,
> > --
> > Kurt Garloff, Head Architect, Director SUSE Labs (act.), Novell Inc.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

Xen-devel mailing list