@stormi Tested the new edk package at looks good to me. was able to reboot linux and freebsd VMs without a hitch with UEFI boot mode.
Best posts made by bufanda
-
RE: XCP-ng 8.3 betas and RCs feedback 🚀
-
RE: XCP-ng 8.3 updates announcements and testing
Updated my Lab pool consisting of 2 Nodes this morning
Rebooted master first, then slave. No issues VMs migrated between reboots.
Couldn't see any issue til now. -
RE: XCP-ng 8.3 updates announcements and testing
@dthenot Only have 2 Test VMs currently not running with qcow2. Nothing production and nothing crucial. It's a lab pool. As I said just to understand the behavior when I test the new updates. But thanks for the details. Really appreciated
-
RE: XCP-ng 8.3 updates announcements and testing
Installed on my Test pool with 2 HP EliteDesk 800 G3 mini. Except the no stats in XenOrchestra. Did some VM migragration between hosts, reboot testes (only Linux VMs though) and so far no issues.
-
RE: XCP-ng 8.3 updates announcements and testing
Upgraded my dev Pool
2 HP EliteDesk 800 G3 Mini
One with i5 6500T and one i7 6700T
Both 32GB RAM, SATA and NVMe Storage
1x Intel NIC
1x RTL8139 NICUpdated Master first and then the second node. No issues so far.
-
RE: Hosts compatibility
@wtdrisco There should be no Problem if the core counts don't match. you just can't place a VM that has 32vCPUs on the 24 core host.
But one thing you should have equal over all hosts is the amount of network interfaces and also have them configured equally (which should be done by XOA/XO form sources). Otherwise a VM might not migrate because a network Interface is missing on the target host.
Also passed through hardware might prevent migrating to another host.
I run a pool with two diffrent hosts, one has 8 Cores and one only 4 cores, also one has 64 GB RAM and the other one has only 32GB and in this limitations I can easily migrate VMs back and forth between hosts.
-
RE: Automating VM builds on XO with Redhat AAP (Ansible)
@Murf There is a blog post about using XenOrchestra for a dynamic inventory.
https://xen-orchestra.com/blog/virtops3-ansible-with-xen-orchestra/Creating VMs is usually a job done by terraform and not ansible. I know there is an ansible collection for VMWare which can do that but as far as I know there is no collection that is able to manage VMs and sadly Satellite's virt-who doesn't seem to have XenOrchestra support at the moment and since RedHat is pushing OpenShift I don't think it will ever come.
But there was a wish for a colletion on the DevOps Megathread
https://xcp-ng.org/forum/post/88993 -
RE: DevOps Megathread: what you need and how we can help!
Backup management with the Terraform provider would be a great feature. Maybe also for an upcoming ansible module. I always struggle to find the right backup for a VM since I grouped them in logical groups. So one Backup may handle multiple VMs and Sometimes it would be just easier to edit some IaC then the GUI, especially when I destroy a VM, I always forget to check if Backups exists.
-
RE: XCP-ng 8.3 updates announcements and testing
@stormi Oh Damn, bad timing I shouldn't have updated my 8.2 pool last sunday
-
RE: XCP-ng 8.3 updates announcements and testing
Installed the patches on my lab pool and both hosts are up and running and no issues so far.
Latest posts made by bufanda
-
RE: XCP-ng 8.3 updates announcements and testing
@dthenot Only have 2 Test VMs currently not running with qcow2. Nothing production and nothing crucial. It's a lab pool. As I said just to understand the behavior when I test the new updates. But thanks for the details. Really appreciated
-
RE: XCP-ng 8.3 updates announcements and testing
@dthenot No worries, just wanted to make sure I understand the expected behavior when I had the qcow2 patches installed.
-
RE: XCP-ng 8.3 updates announcements and testing
Did install on my lab pool
2 HP EliteDesk 800 G3 mini
One with i7 6700T, one with i5 6500T
Both 32GB RAM
iSCSI SR, NFS SR and local NVMe SR. VMs from all SR run. Migration during update worked. Migration of VMs after update worked. Backups (exporting VMs) is working
Didn't see any issue so far.One thing the pool had the qcow2 patches installed since XAPI and sm packages gto updated I guess it won't support qcow2 at the moment right?
-
RE: XO Community edition backups dont work as of build 6b263
Hi,
I tested build 48bf9c9 and backups whether they using NBD or not seem not to start transfers at all.
This is the log output without NBD:
2025-07-01T05:09:04.436Z xo:backups:worker INFO starting backup 2025-07-01T05:09:06.481Z xo:backups:MixinBackupWriter INFO deleting temporary VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/38289b78-efb3-439e-90e9-41bbe5f365c2/.20250701T050331Z.vhd' } 2025-07-01T05:09:06.490Z xo:backups:MixinBackupWriter INFO deleting temporary VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/91528678-9ae0-4d85-864f-69c327f0bcba/.20250701T050331Z.vhd' } 2025-07-01T05:09:08.028Z xo:backups:MixinBackupWriter INFO deleting unused VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/01c64faa-ed71-4190-a11b-bce454d2a5d4/20250701T050331Z.vhd' } 2025-07-01T05:09:08.028Z xo:backups:MixinBackupWriter INFO deleting unused VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/38289b78-efb3-439e-90e9-41bbe5f365c2/.20250701T050331Z.vhd' } 2025-07-01T05:09:08.029Z xo:backups:MixinBackupWriter INFO deleting unused VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/91528678-9ae0-4d85-864f-69c327f0bcba/.20250701T050331Z.vhd' } 2025-07-01T05:09:52.631Z xo:backups:worker WARN possibly unhandled rejection { error: TypeError: this.source.readBlock is not a function at XapiDiskSource.readBlock (file:///home/node/xen-orchestra/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:70:28) at XapiDiskSource.buildDiskBlockGenerator (file:///home/node/xen-orchestra/@xen-orchestra/disk-transform/dist/Disk.mjs:69:28) at buildDiskBlockGenerator.next (<anonymous>) at XapiDiskSource.diskBlocks (file:///home/node/xen-orchestra/@xen-orchestra/disk-transform/dist/Disk.mjs:27:39) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.all (index 0) } 2025-07-01T05:09:52.633Z xo:backups:worker WARN possibly unhandled rejection { error: TypeError: this.source.readBlock is not a function at XapiDiskSource.readBlock (file:///home/node/xen-orchestra/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:70:28) at XapiDiskSource.buildDiskBlockGenerator (file:///home/node/xen-orchestra/@xen-orchestra/disk-transform/dist/Disk.mjs:69:28) at buildDiskBlockGenerator.next (<anonymous>) at XapiDiskSource.diskBlocks (file:///home/node/xen-orchestra/@xen-orchestra/disk-transform/dist/Disk.mjs:27:39) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.all (index 0) } 2025-07-01T05:09:52.634Z xo:backups:worker WARN possibly unhandled rejection { error: TypeError: this.source.readBlock is not a function at XapiDiskSource.readBlock (file:///home/node/xen-orchestra/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:70:28) at XapiDiskSource.buildDiskBlockGenerator (file:///home/node/xen-orchestra/@xen-orchestra/disk-transform/dist/Disk.mjs:69:28) at buildDiskBlockGenerator.next (<anonymous>) at XapiDiskSource.diskBlocks (file:///home/node/xen-orchestra/@xen-orchestra/disk-transform/dist/Disk.mjs:27:39) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.all (index 0) }
And smae VM when trying to use NBD
2025-07-01T05:02:49.119Z xo:backups:worker INFO starting backup 2025-07-01T05:02:51.256Z xo:backups:MixinBackupWriter INFO deleting temporary VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/01c64faa-ed71-4190-a11b-bce454d2a5d4/.20250629T003525Z.vhd' } 2025-07-01T05:02:51.268Z xo:backups:MixinBackupWriter INFO deleting temporary VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/38289b78-efb3-439e-90e9-41bbe5f365c2/.20250629T003525Z.vhd' } 2025-07-01T05:02:51.270Z xo:backups:MixinBackupWriter INFO deleting temporary VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/91528678-9ae0-4d85-864f-69c327f0bcba/.20250629T003525Z.vhd' } 2025-07-01T05:02:51.627Z xo:backups:MixinBackupWriter INFO deleting unused VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/01c64faa-ed71-4190-a11b-bce454d2a5d4/.20250629T003525Z.vhd' } 2025-07-01T05:02:51.628Z xo:backups:MixinBackupWriter INFO deleting unused VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/38289b78-efb3-439e-90e9-41bbe5f365c2/.20250629T003525Z.vhd' } 2025-07-01T05:02:51.628Z xo:backups:MixinBackupWriter INFO deleting unused VHD { path: '/xo-vm-backups/e707a6aa-c26b-766c-a2da-051ebdfec000/vdis/a9df501c-2126-4db2-8e30-77ecc7010e35/91528678-9ae0-4d85-864f-69c327f0bcba/.20250629T003525Z.vhd' } 2025-07-01T05:06:04.924Z xo:backups:worker INFO starting backup 2025-07-01T05:06:09.185Z xo:backups:MixinBackupWriter INFO deleting temporary VHD { path: '/xo-vm-backups/3df8fe91-2c2c-c264-4f21-a07e831d3bb7/vdis/49431dbf-9b1a-4a01-a378-d096edda8ff3/8c1a888f-b3a1-4a8d-bddf-c899c7c9b181/.20250629T010511Z.vhd' } 2025-07-01T05:06:09.852Z xo:backups:MixinBackupWriter INFO deleting unused VHD { path: '/xo-vm-backups/3df8fe91-2c2c-c264-4f21-a07e831d3bb7/vdis/49431dbf-9b1a-4a01-a378-d096edda8ff3/8c1a888f-b3a1-4a8d-bddf-c899c7c9b181/.20250629T010511Z.vhd' } 2025-07-01T05:06:18.711Z xo:xapi:vdi WARN invalid HTTP header in response body { body: 'HTTP/1.1 500 Internal Error\r\n' + 'content-length: 346\r\n' + 'content-type: text/html\r\n' + 'connection: close\r\n' + 'cache-control: no-cache, no-store\r\n' + '\r\n' + '<html><body><h1>HTTP 500 internal server error</h1>An unexpected error occurred; please wait a while and try again. If the problem persists, please contact your support representative.<h1> Additional information </h1>Db_exn.Read_missing_uuid("VDI", "", "OpaqueRef:9805714f-7a36-6c2c-c194-9f08baf519df")</body></html>' }
-
RE: XCP-ng 8.3 updates announcements and testing
@stormi Oh Damn, bad timing I shouldn't have updated my 8.2 pool last sunday
-
RE: XCP-ng 8.3 updates announcements and testing
Updated my Lab pool consisting of 2 Nodes this morning
Rebooted master first, then slave. No issues VMs migrated between reboots.
Couldn't see any issue til now. -
RE: XCP-ng 8.3 updates announcements and testing
Installed the patches on my lab pool and both hosts are up and running and no issues so far.
-
RE: XCP-ng 8.3 updates announcements and testing
@andriy.sultanov
I ran it for a minute. -
RE: XCP-ng 8.3 updates announcements and testing
@andriy.sultanov
Same issue after another reboot. The stats on host just flatline. No CPU usage or anything.
See screenshot
I attached log files
daemon.log.txt xcp-rrdd-plugins.log.txt xensource.log.txt -
RE: XCP-ng 8.3 updates announcements and testing
Installed on my Test pool with 2 HP EliteDesk 800 G3 mini. Except the no stats in XenOrchestra. Did some VM migragration between hosts, reboot testes (only Linux VMs though) and so far no issues.