There's no difference in that procedure between LVM and a file backed
vbd other than the commands issued to create it.
You'd want to have the 'receiving' loop ready and formatted, and a
separate swap file made for it ready and waiting (just so you aren't
burdened with it during the actual "cloning" process).
I wouldn't do this with dom-u's running any kind of SQL server if you
intend to revert if something went wrong. You'd also find problems with
sessions if you had to revert for some reason.
If, per chance you kept an eye on slabs on the target dom-u (dentry /
inodes and dirty cache) and timed this so you did it when they were low,
I think you'd enjoy more repeatable success.
Good luck with this :) Please let me know how it goes.
HTH
Tim
On Tue, 2006年06月27日 at 17:47 +0200, Emiliano Gabrielli (aka AlberT)
wrote:
> On Tuesday 27 June 2006 17:10, Javier Guerra wrote:
> > 0) use LVM backed domUs
> > 1) on dom0, create a LVM read-only snapshot of the dumU image
> > 2) do a block copy (dd) to a new LVM partition
> > 3) release the snapshot. the old domU keeps running
>
> yes .. running but freezed .. LVN snapshots are very very unstable in my
> experience .. if anyone has better experiences plz report here
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users