@olivierlambert said in Issues migration esxi to do the virtual machine Windows server and SQL in xo:

This message comes from your ESXi host, not XO. I have limited expertise on VMware, but I would check the logs there to understand if there's a problem.

Could it be that the drive where the hard drives are in vmware does not have enough space to take snapshots of them?

Since there are 220 GB between the three hard drives.

@olivierlambert
Hi.
Sorry.

I created a virtual machine in XO/XCP-ng and it created it perfectly.

I migrated a similar virtual machine but with only one hard drive and it also migrated it fine.

@olivierlambert thanks olivier

Yes I can create the job from import---->vmware.
I can access the vmware host as root user and full permissions.

The job starts to perform the migration, stops after 40-45 min.

In xo it creates the vm and the hard drive, but they are corrupted.
I tried to boot the machine created in xo in case I was lucky.

Thanks in advance.

Hello.

I'm having problems migrating a virtual machine from esxi to xo.

This machine has 3 hard drives of 150GB + 20GB + 100GB.

When checking the error logs, I get an error:
"message": "503 Service Unavailable https://xxx.xxx.xxx.xxx/folder/testSql2017/testSql2017_3-000001-delta.vmdk?dcPath=ha-datacenter&dsName=StorageVM_03",

This error appears on each hard drive. I understand that the delta is the snapshot that xo takes before migrating?

Then I have these more errors on the import:

 "task": {
 "uuid": "4ee878dd-53f4-85b0-e5a3-7e19aa9a17e8",
 "name_label": "[XO] Importing content into VDI [ESXI]testSql2017_1-flat.vmdk on SR Nfs_VM02",
 "name_description": "",
 "allowed_operations": [],
 "current_operations": {},
 "created": "20240921T21:34:42Z",
 "finished": "20240921T21:55:00Z",
 "status": "failure",
 "resident_on": "OpaqueRef:621f8618-cbed-40ee-9b57-81c5ed682dac",
"progress": 1,
"type": "<none/>",
"result": "",
"error_info": [
"VDI_IO_ERROR",
"Device I/O errors"

I guess they are related.

Any idea how to fix it??

Thanks.

@olivierlambert Thank you very much for the info.

Better this way, I will create a pool with the 4 equal hosts.

@olivierlambert Ok, understood.

The issue is that the current server which is master is the most different from the other 4 we have.

We have this fifth one for testing and migrations.

The others are all the same.

Can VMs be migrated in different pools?

Could one host be changed from master to another once we have the same ones in the same pool??

Thanks in advance.

@olivierlambert Now it has been added,

But it has also copied the vlan configurations with the network cards....

Is that so?

If on host 1 in eth1 I had vlan 40 for storage
on host 2 do I have to have it the same?

Can't I have it on eth4???

@olivierlambert I'll try it!

@olivierlambert Thank you for your prompt response.

If I understood correctly, the slave host only needs to have the manager network configured.

But I have more vlans that access the shared sr. Do I have to configure these later?

Continuing with the migration of vmware to XCP-ng I am facing the following problem.

I have removed vmware from my second host and I have it ready to add to the existing pool.

I got the following error: POOL_JOINING_HOST_HAS_NON_MANAGEMENT_VLANS()

I checked that both host 1 and host 2 had management.

The peculiarities are that both hosts are on vlan90
the master has 192.168.90.55 and the slave 192.168.90.57

I also thought that the problem was that they did not have the same vlans.
I put both hosts with the same vlans but the problem continues.

Can you help me?

Log error: pool.mergeInto
{
  "sources": [
    "7798f8c1-7cea-3d3f-8c43-75fe48b056cc"
  ],
  "target": "9f1b93a6-eea2-3cd4-da77-ecf5afa1a66d",
  "force": true
}
{
  "code": "POOL_JOINING_HOST_HAS_NON_MANAGEMENT_VLANS",
  "params": [],
  "call": {
    "method": "pool.join_force",
    "params": [
      "192.168.90.55",
      "root",
      "* obfuscated *"
    ]
  },
  "message": "POOL_JOINING_HOST_HAS_NON_MANAGEMENT_VLANS()",
  "name": "XapiError",
  "stack": "XapiError: POOL_JOINING_HOST_HAS_NON_MANAGEMENT_VLANS()
    at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202312051521/packages/xen-api/_XapiError.mjs:16:12)
    at file:///opt/xo/xo-builds/xen-orchestra-202312051521/packages/xen-api/transports/json-rpc.mjs:35:21
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
    at process.callbackTrampoline (node:internal/async_hooks:128:17)"