Jump to content
Welcome to our new Citrix community!
  • 0

VM-Migrate form XS 7.1 CU2 to XS 8.0 not possible


Marc Wilhelmi

Question

Hi,

 

we setup a new pool with XenServer 8.0 / Citrix Hypervisor and it´s not possible to migrate VM from our 7.1 LTSR CU2 pools to the new pool.

We can choose the new pool during the wizard, but after choosing pool and destination server, the "next" button keeps grey.

No error, no message.

 

Are there limitations from wich version a live migration is possible?

Link to comment

11 answers to this question

Recommended Posts

  • 0
On 6.8.2019 at 0:08 AM, Alan Lantz said:

I agree, try command live over XenCenter, maybe XenCenter has some sort of bug. I guess one could always export\import

if the size is reasonably small and you can handle the downtime. Maybe check on XenOrchestra and see what they support.

 

--Alan--

 

 

Ok, XenOrchestra was a good idea. Migration through XOA worked like a charm.

 

And after adding a shared SR migration with the wizard in XenCenter works as well.

looks like the wizard needs a shared SR set as deflaut in the destination pool to work

  • Like 1
Link to comment
  • 0
1 hour ago, Tobias Kreidl said:

OK, that's all good then regarding licensing. Next, I would try this from the CLI because it will give you more of a detailed error message it it fails. Look at things like compatible network routes, adequate space available on both servers, and if a smaller VM can be made first to succeed or not. See also: https://discussions.citrix.com/topic/397729-vm-migration-command/

 

-=Tobias

 

Performing a Storage XenMotion migration. Your VM's VDIs will be migrated with the VM.
Selecting remote pool's default SR for migrating VDIs
Will migrate to remote host: ii-rxp10-xen1, using remote network: Management. Here is the VDI mapping:
You gave an invalid object reference.  The object may have recently been deleted.  The class parameter gives the type of reference given, and the handle parameter echoes the bad value given.
class: SR
handle: OpaqueRef:NULL

 

That´s the error when migrating via CLI

Link to comment
  • 0
5 minutes ago, Tobias Kreidl said:

Do you perhaps not have an SR designated as the default storage SR on the destination pool? Otherwise, you need the extra parameter for the destination SR.

You should get a message indicating something like "selecting remote pool's default SR for migrating".

 

-=Tobias

 

Ok, I don´t have a default SR and can´t set a local SR as default

 

If adding a destination SR Iget this error:

 

Performing a Storage XenMotion migration. Your VM's VDIs will be migrated with the VM.
Selecting remote pool's default SR for migrating VDIs
Error: Unknown field 'destination-sr-uuid'
 

Link to comment
  • 0

Something is amiss if you cannot even set your local SR as the default SR. Does any SR show up in XenCenter with a clack checkmark?  I may not have given you quite the right syntax -- it's not destination-sr=uuid -- instead it's 'vdi:<source vdi uuid>=<dest sr uuid>'.   The syntax changed after XS 6.X. Also, if the VM is running, you'll need "live=true" included in the command line.

Could you post (with any private information redacted) of the full command line?  You have to be sure to supply all the tokens that are needed as in some cases, there is no default:

 

# xe help vm-migrate
command name            : vm-migrate
        reqd params     :
        optional params : live, host, host-uuid, remote-master, remote-username, remote-password, remote-network, force, copy, vif:, vdi:, <vm-selectors>
        description     : Migrate the selected VM(s). The parameter '--live' will migrate the VM without shutting it down. The 'host' parameter matches can be either the name or the uuid of the host. If you are migrating a VM to a remote pool, you will need to specify the remote-master, remote-username, and remote-password parameters. remote-master is the network address of the master host. To migrate to a particular host within a remote pool, you may additionally specify the host or host-uuid parameters. Also for cross-pool migration, setting 'copy=true' will enable the copy mode so that a stopped vm can be copied, instead of migrating, to the destination pool. The vif and vdi mapping parameters take the form 'vif:<source vif uuid>=<dest network uuid>' and 'vdi:<source vdi uuid>=<dest sr uuid>'. Unfortunately, destination uuids cannot be tab-completed. The simplest way to select the VM on which the operation is to be performed is by supplying the argument 'vm=<name or uuid>'. VMs can also be specified by filtering the full list of VMs on the values of fields. For example, specifying 'power-state=halted' will select all VMs whose power-state field is equal to 'halted'. Where multiple VMs are matching, the option '--multiple' must be specified to perform the operation. The full list of fields that can be matched can be obtained by the command 'xe vm-list params=all'. If no parameters to select VMs are given, the operation will be performed on all VMs.

Link to comment
  • 0
On 5.8.2019 at 11:25 PM, Tobias Kreidl said:

Something is amiss if you cannot even set your local SR as the default SR. Does any SR show up in XenCenter with a clack checkmark?  I may not have given you quite the right syntax -- it's not destination-sr=uuid -- instead it's 'vdi:<source vdi uuid>=<dest sr uuid>'.   The syntax changed after XS 6.X. Also, if the VM is running, you'll need "live=true" included in the command line.

Could you post (with any private information redacted) of the full command line?  You have to be sure to supply all the tokens that are needed as in some cases, there is no default:

 

# xe help vm-migrate
command name            : vm-migrate
        reqd params     :
        optional params : live, host, host-uuid, remote-master, remote-username, remote-password, remote-network, force, copy, vif:, vdi:, <vm-selectors>
        description     : Migrate the selected VM(s). The parameter '--live' will migrate the VM without shutting it down. The 'host' parameter matches can be either the name or the uuid of the host. If you are migrating a VM to a remote pool, you will need to specify the remote-master, remote-username, and remote-password parameters. remote-master is the network address of the master host. To migrate to a particular host within a remote pool, you may additionally specify the host or host-uuid parameters. Also for cross-pool migration, setting 'copy=true' will enable the copy mode so that a stopped vm can be copied, instead of migrating, to the destination pool. The vif and vdi mapping parameters take the form 'vif:<source vif uuid>=<dest network uuid>' and 'vdi:<source vdi uuid>=<dest sr uuid>'. Unfortunately, destination uuids cannot be tab-completed. The simplest way to select the VM on which the operation is to be performed is by supplying the argument 'vm=<name or uuid>'. VMs can also be specified by filtering the full list of VMs on the values of fields. For example, specifying 'power-state=halted' will select all VMs whose power-state field is equal to 'halted'. Where multiple VMs are matching, the option '--multiple' must be specified to perform the operation. The full list of fields that can be matched can be obtained by the command 'xe vm-list params=all'. If no parameters to select VMs are given, the operation will be performed on all VMs.

 

That´s the command I used:

 

xe vm-migrate remote-master=10.10.101.121 remote-username=root remote-password=XXX vm=ii-Jasper-WS live=true force=true destination-sr-uuid=6db80747-119c-4169-dd27-daeb2df855cd

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...