@Pix Ok i'm self replying here: just connect one XO to both pools, and then migrate.

@Pix

Looks like the different HW or Pool is an issue, i'll make more tests and report here if it's ok

@olivierlambert Hm well maybe i talked to quickly, task started 18mn ago, 0%, VM is very small..
I'll wait

and my first post still stands: an xva exported in 8.3 could not be reimported on 8.3 ( host cpu on source HV is smaller that the one on destination HV, both Xeon v3 Intels)

@Pix Ok i'm self replying here: just connect one XO to both pools, and then migrate.

@olivierlambert Stupid question, how do i warm migrate between two different pools using the same NFS SR ? when it's done, i move the vhd file from one uuid-pool directory to the other ?

@Danp Nope, Staging pool have 3 hosts running same 8.3 up to date, and production pool runs 1 host running also 8.3 up to date

Gonna try warm migration between two CE XOs ( i don't think my yet-to-be-licensed actual XOs will allow it)

Hi, i'm basically trying to migrate a windows VM ( but i'm not sure it's relevant) between two different Pools.

After trying unsuccessfully using both their XO, i went down in the stack and tried directly from 2 HVs.

Both HVs are on different Pools, both have a NFS share mounted ( for the transfer ), both up to date ( yum update/upgrade )

And here what happens:

[13:53 XenStaging1 ~]# xe vm-export uuid=3a177607-d851-0f5b-901d-1660c7bdd8d4 filename=/mnt/transfer/staging/mcaffee.xva compress=zstd
Export succeeded
[14:18 XenStaging1 ~]#

[14:26 xenprodpp ~]# xe vm-import filename=/mnt/transfer/staging/mcaffee.xva preserve=true
The import failed because this export has been created by a different (incompatible) product version
[14:26 xenprodpp ~]# xe vm-import filename=/mnt/transfer/staging/mcaffee.xva
The import failed because this export has been created by a different (incompatible) product version
[14:26 xenprodpp ~]#

Did i miss an obvious step ?

Hi,
I've got a bond0 connected to a switch which exposes a LOTs of VLANs in trunk mode, so i need to create the associated networks/vlan in XO to connect my VMs directly to the VLANs.
Unfortunately i'm stuck and i can't find the correct parameters to give to network.create:

The pif i'm giving as a parameter is the bond0 listed in the network part of XO, obviously i'm doing it wrong, but what ? :))

xo@xo-ce:~$ xo-cli network.create pool=5ecb81a5-8ea7-d88a-3d8d-76bec7a83a03 name="VLAN20 - Builders" pif=85fcc01b-f13d-a6f9-2ad4-d3ee99ce12ef vlan=json:20
✖ JsonRpcError: no such PIF 85fcc01b-f13d-a6f9-2ad4-d3ee99ce12ef
    at Peer._callee$ (/opt/xo/xo-builds/xen-orchestra-202407081745/node_modules/json-rpc-peer/dist/index.js:139:44)
    at tryCatch (/opt/xo/xo-builds/xen-orchestra-202407081745/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:45:16)
    at Generator.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202407081745/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:133:17)
    at Generator.next (/opt/xo/xo-builds/xen-orchestra-202407081745/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:74:21)
    at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202407081745/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
    at _next (/opt/xo/xo-builds/xen-orchestra-202407081745/node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
    at /opt/xo/xo-builds/xen-orchestra-202407081745/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
    at new Promise (<anonymous>)
    at Peer.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202407081745/node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
    at Peer.exec (/opt/xo/xo-builds/xen-orchestra-202407081745/node_modules/json-rpc-peer/dist/index.js:182:20) {
  code: 1,
  data: { id: '85fcc01b-f13d-a6f9-2ad4-d3ee99ce12ef', type: 'PIF' }
}
xo@xo-ce:~$