@cmanos No problem, glad I could helped.
As Olivier also pointed above, it's not an issue anymore when using QCOW2 which is currently in beta, so hopefully it's only a short workaround
I can imagine that a fix could be to send "keepalive" packets in addition to the XCP-ng export-VM-data-stream so that the timeout on XO side does not occur
Yes, they are created either:
on demand for users
when we need in XO 6
Now, XO 6 is becoming the main driver for new endpoint as the UI is providing more and more features.
@carloum70 Disk migration isn't supported by the provider yet. What you can do it's only ignore the changes to the sr_id of a given disk.
For example for the first disk:
lifecycle {
ignore_changes = [
disk[0].sr_id
]
}
You can also manually do the migration in XO and then after edit your HCL to update the sr_id with the new ID. It should do the trick.
@kenkaniff412 said in 404 Error Migration from VMware:
404 Not Found https://10.15.47.11/folder/5ef46e5c-6682-c9cd-48af-e4434b3e0130/vsan://5205fb491e65dc99-62e26f64d9b34c60/60f46e5c-8ca4-eea4-a0ff-e4434b3e0130?dcPath=ha-datacenter&dsName=VxRail-Virtual-SAN-Datastore-5364d40d-1687-4c72-b904-248c54599994
I was talking about this URI @florent Look at the /vsan:// part in the middle
@poltushima As there is no S3 support in Azure Blob Storage, no you can't use XO for direct backup to Azure. There are S3 proxy projects (here's one) that could make it work.
I had to do the following to remove the reboot block:
xe vm-param-remove param-name=blocked-operations param-key=hard_reboot uuid=$UUID
And then:
xe vm-reboot force=true vm=$UUID
I think using a script for an initial test is OK, but if you want to really use it, it's better to follow our documentation and following the per-requisites by the book.
@Danp
Hi everyone.
That "n 18" did it for me. My Xen Orchestra would not hold the connection, with the same "http connection time out".
Thanks a bunch
Regards
Marc
@Mark-C
Wouldn't have made it without your help! Super.
So far everything seems to be working normally, except for my original issue on the other topic, posting there now.
If any more issues come up I'll post them here and reference on this topic. Many thanks!!
In essence, you can write any script you like in your VM that would be executed, test whatever you want in the database, and if it's OK, write a special key in the XenStore. XO will detect it and consider the backup health check done and working
