OK, found the git where it was added 2 months ago (https://github.com/vatesfr/xen-orchestra/pull/7308), and i haven't updated in 3 months, time to update XO
Latest posts made by anik
-
RE: Load balance plugin interrupting scheduled backups
-
RE: Load balance plugin interrupting scheduled backups
hmm... i do not see such option. I forgot to mention that this is a delta backup job, if that matters.
-
Load balance plugin interrupting scheduled backups
Hi,
i have had this thing happen a few times now, where during scheduled backups, a VM starts migrating due to load balancing during a scheduled backup and then the backup job for that specific VM fails.
Error: cannot backup a VM currently being migrated
Is there a way to prevent this from happening, or at the very least have the backup job finish automatically after migration has finished?
Thanks
-
RE: KVM qcow2 disk converted and and imported to xcp-ng just works?
@AtaxyaNetwork can confirm this works for me as well
I feel like this should be default go-to method mentioned in the documentation and the current documentation mentioned as an alternative.
ps. im not a coder, no idea how to work github to make the changes my self
-
KVM qcow2 disk converted and and imported to xcp-ng just works?
Hi,
I converted couple of .qcow2 images to .vmdk via qemu-img and imported the disks via XO attached the .vmdk to a new VM and the VM just booted and worked perfectly out of the box like that?
Reading the documentation here, the migration process should be much more complex but i didn't have to do any of that, is there some new magic happening that makes this work out of the box like that or should i expect issues later on doing the imports this way??
Also, after importing the .vmdk image to XO, i checked my SR and noticed that the image was automagically converted to .vhd and i cannot find any trace of the original imported .vmdk files, is this normal also?
Here are exact steps i took:
1. Sparify .qcow2 before conversion: virt-sparsify image1.qcow2 sparse_image1.qcow2 --tmp /mnt/vmdata/backups/Server_name/2024-02-05.212740/ 2. Do conversion: qemu-img convert -p -f qcow2 -O vmdk sparse_image1.qcow2 image1.vmdk 3. Copied the .vmdk image to local machine and started disk import 4. Create VM with new disk 5. Remove created disk and attach imported .vmdk image 6. Boot up VM and everything works, Linux boots up done. 7. Checked SR on xcp-node and it is not .vhd file: [13:08 xcp-node01 6b24cd1c-22ad-0994-5b6b-a75389a6ddba]# file 7e5ac555-68fd-406f-8b23-7185b3e30dab.vhd 7e5ac555-68fd-406f-8b23-7185b3e30dab.vhd: Microsoft Disk Image, Virtual Server or Virtual PC
-
RE: Getting errors when migrating 4 out 5 VMGuest
Hi,
i have had the same "VDI_NOT_IN_MAP" error previously on 2 VM's. I have no idea what caused it, but i was able to solve it by doing a warm migration once, after that normal migrations started working normally. -
RE: XCP-ng & XO at Vates
Hmmm, I am interested as to what NVMe adapter card(s) are you using for your Dell R730 TrueNAS servers?
I also have 2 x R730's running Truenas in my XCP-ng setup where i have single NVMe drive for SLOG device, but i have an issue where the server on boot sometimes fails to recognise the NVMe adapter card (pcie link training failure) and i have been looking for a replacement that is more reliable.
So far i have tried couple cheap PCI cards from Akasa and Startech.