Re: [Xen-devel] [PATCH] Blktap: Userspace file-based image support.(RFC)

[Dan Smith <danms@xxxxxxxxxx>]

MW> Well, it doesn't really matter what the destination dom0 is using
MW> as block devices provided the node name doesn't have to stay the
MW> same on the destination machine - and if you use the hotplug
MW> scripts to set up block devices then it doesn;t.

Right, exactly.

MW> I think being able to demand-fault virtual disks across would be
MW> quite cool (with the copy eventually completing in the background,
MW> eliminating the origin as a point of failure.  For smaller, or
MW> more ad-hoc setups this could be quite useful (especially if you
MW> had a daemon trickle updates across the network continuously at
MW> low bandwidth to minimise the diffs during migration)

This is the exact situation I had in mind.  I think it would be
extremely cool to have a peer-to-peer block migration mechanism, which
would allow the convenience of files for migration and the speed of
block devices.  You could even have a method for migrating block
images between machines, independent of a migration.  Imagine
something like:

  lvmcp /dev/vols/foo othermachine:/dev/vols

I think that would be neat.  It's rather straightforward too, I
think.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx

Attachment: pgpzZfGSEJcgW.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel