Re: Moving VR to another pool
The below steps might help in moving VR to another host and storage.
There'll be downtime.
- Create a new System Service Offering with System VM type "Domain Router"
and appropriate host and storage tags [Tag the host and storage which has
to be used for VR and use them here].
- Create a network offering with the same specs as the old network offering
used for the VR network and update System Offering for Router with the one
- Change the network offering in the network associated with the VR. Stop &
Start VR (or) Destory VR.
On Wed, May 9, 2018 at 8:51 PM, Stephan Seitz <s.seitz@xxxxxxxxxxxxxxxxxxx>
> Hi sven,
> As far.as i can remember from our workflow a few month ago, we've added
> a matching Storage tag to the systemtemplate offering and subsequently
> simply destroyed the running VR waiting for them to spawn on the new
> cluster. If you're running systemvms on local Storage i assume (unverified)
> disabling the old cluster and destroying the VR should work.
> I don''t think that live migration of VR to a diffrent cvluster is
> Von: Swen - swen.io
> Gesendet: Mittwoch, 9. Mai 2018 16:50
> An: users@xxxxxxxxxxxxxxxxxxxxx
> Antwort an: users@xxxxxxxxxxxxxxxxxxxxx
> Betreff: Moving VR to another pool
> we want to delete a XenServer cluster in our CS installation and so moving
> everything of it. Can we also move all VR from on cluster to another
> via live migration and without downtime? It looks like I can only move VR
> inside a cluster and its primary storage. Is there a way to do a storage
> live migration of VR via api with "migrateVirtualMachineWithVolume"? I
> it but failed, maybe because of a syntax error.
> Thanks for help!
> Best regards,