On Tuesday 27 June 2006 9:47 am, Jürgen Ladstätter wrote:> True, > > so there is no chance that it copies my DomU and resetzs ip, mac and that > stuff? Would need that for testing purposes on running systems.i guess the #IP and mac address problems could be solved by some utilities at the domU, or some kind of switch that disables network devices. but the biggest problem is the block device; live migration doesn''t copy the HD image, it only copies the RAM partition and CPU state (besides kernel and hypervisor info). i think you could do it all like this (untested!!) 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 4) mount on dom0 the new copy of the image 5) modify config scripts, or anything, unmount it. 6) create a new xen config for a new vm using the new copy, with different MAC/IP addresses 7) fire up the new domU -- Javier _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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 runningyes .. running but freezed .. LVN snapshots are very very unstable in my experience .. if anyone has better experiences plz report here -- <?php echo '' Emiliano Gabrielli (aka AlberT) '',"\n", '' socio fondatore e membro del direttivo del GrUSP '',"\n", '' AlberT_at_SuperAlberT_it - www.SuperAlberT.it '',"\n", '' IRC: #php,#AES azzurra.com '',"\n",''ICQ: 158591185''; ?> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com http://lists.xensource.com/xen-users