Migrate failed
-
And you have the exact same issue? Are you sure you are modifying the right object?
-
@olivierlambert said in Migrate failed:
act same issue? Are you sure you are modifying the right object?
yes. "code": "LICENCE_RESTRICTION"
Absolutely sure. copied uuid from VM xen-center interface. -
Please display here the result of the VM record (
xe vm-param-list uuid=<VM UUID>) -
-
Please display a
xe vm-param-list uuid=<VM UUID>
-
[root@xen8 ~]# xe vm-param-list uuid=73820231-5269-9571-2986-46876a633d66 uuid ( RO) : 73820231-5269-9571-2986-46876a633d66 name-label ( RW): CentOS8 name-description ( RW): user-version ( RW): 3 is-a-template ( RW): false is-default-template ( RW): false is-a-snapshot ( RO): false snapshot-of ( RO): <not in database> snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): <not in database> children ( RO): is-control-domain ( RO): false power-state ( RO): halted memory-actual ( RO): 0 memory-target ( RO): 0 memory-overhead ( RO): 11534336 memory-static-max ( RW): 1073741824 memory-dynamic-max ( RW): 1073741824 memory-dynamic-min ( RW): 1073741824 memory-static-min ( RW): 134217728 suspend-VDI-uuid ( RW): <not in database> suspend-SR-uuid ( RW): bf978200-ccf3-5987-c2d0-5a91876e17df VCPUs-params (MRW): weight: 256 VCPUs-max ( RW): 1 VCPUs-at-startup ( RW): 1 actions-after-shutdown ( RW): Destroy actions-after-reboot ( RW): Restart actions-after-crash ( RW): Restart console-uuids (SRO): hvm ( RO): false platform (MRW): timeoffset: -1; hpet: true; nx: true; device-model: qemu-upstream-compat; pae: true; apic: true; viridian: true; acpi: 1; cores-per-socket: 1 allowed-operations (SRO): changing_dynamic_range; changing_shadow_memory; changing_static_range; make_into_template; migrate_send; destroy; export; start_on; start; clone; copy; snapshot current-operations (SRO): blocked-operations (MRW): allowed-VBD-devices (SRO): 1; 2; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15; 16; 17; 18; 19; 20; 21; 22; 23; 24; 25; 26; 27; 28; 29; 30; 31; 32; 33; 34; 35; 36; 37; 38; 39; 40; 41; 42; 43; 44; 45; 46; 47; 48; 49; 50; 51; 52; 53; 54; 55; 56; 57; 58; 59; 60; 61; 62; 63; 64; 65; 66; 67; 68; 69; 70; 71; 72; 73; 74; 75; 76; 77; 78; 79; 80; 81; 82; 83; 84; 85; 86; 87; 88; 89; 90; 91; 92; 93; 94; 95; 96; 97; 98; 99; 100; 101; 102; 103; 104; 105; 106; 107; 108; 109; 110; 111; 112; 113; 114; 115; 116; 117; 118; 119; 120; 121; 122; 123; 124; 125; 126; 127; 128; 129; 130; 131; 132; 133; 134; 135; 136; 137; 138; 139; 140; 141; 142; 143; 144; 145; 146; 147; 148; 149; 150; 151; 152; 153; 154; 155; 156; 157; 158; 159; 160; 161; 162; 163; 164; 165; 166; 167; 168; 169; 170; 171; 172; 173; 174; 175; 176; 177; 178; 179; 180; 181; 182; 183; 184; 185; 186; 187; 188; 189; 190; 191; 192; 193; 194; 195; 196; 197; 198; 199; 200; 201; 202; 203; 204; 205; 206; 207; 208; 209; 210; 211; 212; 213; 214; 215; 216; 217; 218; 219; 220; 221; 222; 223; 224; 225; 226; 227; 228; 229; 230; 231; 232; 233; 234; 235; 236; 237; 238; 239; 240; 241; 242; 243; 244; 245; 246; 247; 248; 249; 250; 251; 252; 253; 254 allowed-VIF-devices (SRO): 4; 5; 6 possible-hosts ( RO): 5d99acae-c029-4ae4-a8db-eadd21abf67e domain-type ( RW): hvm current-domain-type ( RO): unspecified HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): order: cd HVM-shadow-multiplier ( RW): 1.000 PV-kernel ( RW): PV-ramdisk ( RW): PV-args ( RW): PV-legacy-args ( RW): PV-bootloader ( RW): PV-bootloader-args ( RW): last-boot-CPU-flags ( RO): vendor: GenuineIntel; features: 17cbfbff-f7fa3223-2d93fbff-00000123-0000000f-009c4fbb-00000000-00000000-00001000-9c000000 last-boot-record ( RO): '' resident-on ( RO): <not in database> affinity ( RW): 5d99acae-c029-4ae4-a8db-eadd21abf67e other-config (MRW): base_template_name: Other install media; import_task: OpaqueRef:0f73a93b-f847-4773-8b13-111bb7baf803; mac_seed: ffa13779-f32f-8256-05cd-872652f775dc; install-methods: cdrom dom-id ( RO): -1 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="137438953472"/><restriction field="vcpus-max" max="32"/><restriction field="has-vendor-device" value="false"/><restriction max="255" property="number-of-vbds"/><restriction max="7" property="number-of-vifs"/></restrictions> xenstore-data (MRW): vm-data: ; vm-data/mmio-hole-size: 268435456 ha-always-run ( RW) [DEPRECATED]: false ha-restart-priority ( RW): blobs ( RO): start-time ( RO): 19700101T00:00:00Z install-time ( RO): 20201011T07:12:25Z VCPUs-number ( RO): 0 VCPUs-utilisation (MRO): os-version (MRO): PV-drivers-version (MRO): micro: -1 PV-drivers-up-to-date ( RO) [DEPRECATED]: true memory (MRO): disks (MRO): VBDs (SRO): 0aec3c0d-5ba3-6833-2e3e-e039a870a4e5; 5ac9f293-eff0-75d9-7211-34ce90820392 networks (MRO): PV-drivers-detected ( RO): true other (MRO): platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0; feature-suspend: 1; feature-poweroff: 1; feature-reboot: 1; feature-vcpu-hotplug: 1 live ( RO): true guest-metrics-last-updated ( RO): 20201011T07:29:49Z can-use-hotplug-vbd ( RO): unspecified can-use-hotplug-vif ( RO): unspecified cooperative ( RO) [DEPRECATED]: true tags (SRW): appliance ( RW): <not in database> snapshot-schedule ( RW): <not in database> is-vmss-snapshot ( RO): false start-delay ( RW): 0 shutdown-delay ( RW): 0 order ( RW): 0 version ( RO): 0 generation-id ( RO): hardware-platform-version ( RO): 0 has-vendor-device ( RW): false requires-reboot ( RO): false reference-label ( RO): other-install-media bios-strings (MRO): bios-vendor: Xen; bios-version: ; system-manufacturer: Xen; system-product-name: HVM domU; system-version: ; system-serial-number: ; enclosure-asset-tag: ; hp-rombios: ; oem-1: Xen; oem-2: MS_VM_CERT/SHA1/bdbeb6e0a816d43fa6d3fe8aaef04c2bad9d3e3d -
How do you try to migrate? Is the VM offline?
-
@olivierlambert yes. VM is offline.
-
Can you try to boot it, and then migrate?
Or just boot it once, then shutdown, then migrate?
-
@olivierlambert said in Migrate failed:
r just boot it once, then shutdown, then migrate?
tried both options, result is the same(
-
Hmm that's weird
Can you check detailed logs on the source host?
-
@olivierlambert said in Migrate failed:
Can you check detailed logs on the source host?
yes. which of log file are you recomend to check?
-
/var/log/xensource.log -
-
So I took some time to read the error in details.
It's a problem/bug in your current XenServer 7.2.
Indeed, in 7.2, they locked Xen Storage Motion feature as a paid feature. So you can't migrate a VMs with its storage to another SR/pool, unless you pay for it. The message is pretty clear:
Raised Server_error(LICENCE_RESTRICTION, [ Storage_motion ])There's is multiple workarounds, but as you can see, it's a very dick move from someone at Citrix who decided that
-
@olivierlambert
thank you for your help. Upgrade from 7.6 to 8.2(is it safely?) help to take off this containts. -
You can indeed upgrade your host "locally" from XS to XCP-ng. Just read carefully our official doc on this
-
@olivierlambert
@olivierlambert said in Migrate failed:You can indeed upgrade your host "locally" from XS to XCP-ng. Just read carefully our official doc on this
okay. we'll read that carefully and try to do at the not critical servers. but before start of upgrading procedure we'd like to make sure that migration between xcp-ng(8.2) server is working.
I've tried to migrate VM(from xcp-ng 8.2 to 8.2) and caught another error:vm.migrate { "vm": "2c837cb0-fcf3-6a09-ac47-b939e90869aa", "mapVifsNetworks": {}, "migrationNetwork": "8ad97115-d285-1be6-7738-acd1e7554b3e", "sr": "d4f35636-0125-5318-b915-479bef1ba8c7", "targetHost": "07e1d99b-5dcc-4e78-be88-69e04d625f2b" } { "code": 21, "data": { "objectId": "2c837cb0-fcf3-6a09-ac47-b939e90869aa", "code": "INTERNAL_ERROR" }, "message": "operation failed", "name": "XoError", "stack": "XoError: operation failed at factory (/usr/local/lib/node_modules/xo-server/node_modules/xo-common/src/api-errors.js:21:32) at /usr/local/lib/node_modules/xo-server/src/api/vm.js:487:15 at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:93:5) at runNextTicks (internal/process/task_queues.js:62:3) at processImmediate (internal/timers.js:434:9) at Object.migrate (/usr/local/lib/node_modules/xo-server/src/api/vm.js:474:3) at Api.callApiMethod (/usr/local/lib/node_modules/xo-server/src/xo-mixins/api.js:304:20)" } -
Errors in CAPS means an error from the host.
Check host logs, also check dynamic min memory == dynamic max
