Re: [Xen-devel] [PATCH] Guest boot loader support [1/2]

[Mark Williamson <mark.williamson@xxxxxxxxxxxx>]

> As a slight but related digression, has any thought been given to
> using something other than /dev/[hs]d* names for specifying block
> devices? The name /dev/sdb only has meaning for the current
> state of the running dom0 OS. It may not mean the same device
> on a different dom0. This can lead to problems in say migration.
> In fact, it may not be the same when the domain is restored locally.

You could work round this currently using the block config scripts.  I.e. 
similar to the file: syntax now, you could easily hack up nbd:, iscsi:, etc.  
Then network block devices can be connected up at create / migrate / restore 
time, without relying on a particular device node.

This can be done by writing a shell script to bind the device to a node and 
adding a config parameter to Xend.

I'd imagine we can rely on actual physical device numbers generally staying 
the same but this could be fixed by a similar mechanism.

Cheers,
Mark

> Having to configure all the possible migration targets to see all
> the same devices in the same order at all times is not realistic.
> In a dynamic environment it would be ideal to make a device visible
> to the target dom0 only as it was needed to migrate a given VM to
> that dom0. Naming it /dev/sdb may not be a possiblity in this case.
>
>
> Cheers,
>
> Phil
>
> > Cheers,
> > Ian
> >
> > _______________________________________________
> > 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