@AtaxyaNetwork @Pilow @bvitnik Ok, knowing that the p2 partition was likely an old backup was exactly the breadcrumb that I needed. I confirmed via chroot and xsconsole that p2 was xcp-ng v8.2.1, and that p1 was v8.3. Then I was able to check the initrd files there. Namely I needed to see the updated dates and the kernel version. Thankfully, I saw initrd files on the backup that were the correct kernel and hadn't been disturbed. I then just cloned the initrd files from the backup partition to the p1 partition and BOOM. We booted right up. Much appreciated for the assistance, everyone. I'll still need to figure out why my disks are disconnecting, but that will be another post for another day.

Adding @florent and/or @Bastien-Nollet in the loop

@probain The canonical way is to check the product_id instead https://docs.ansible.com/projects/ansible/latest/collections/ansible/windows/win_package_module.html#parameter-product_id The ProductCode changes every time a new version of XCP-ng Windows PV tools is released, and you can get it from each release's MSI: [image: 1764477313181-617a6162-37ca-458d-8f3a-ca4c0102b18e-image.png]

Hi @k11maris, I think the situation you showed in your screenshot where both options are selected but are both greyed out should not happen. We will try to reproduce it on our side and fix it.

@dnordmann the tunnel is closed. By the way the patch will be release tomorrow on latest, by the end of december on stable thank you all for your patience and your help identifying the root cause of this bug

you can uncheck the "Merge backups synchronously" in the advanced view of the backup job to have it run inside the backup job, thus making it visible (we are reworking the internal design for better observability, but there is a lot of job before)

Yes, and then Xen will reduce the RAM if there's not enough available to boot a new VM (reducing down to dynamic min). Static means it can't be changed live, while dynamic can.

@MajorP93 aha, yea. Per disk concurrency is important too.

@acebmxer Great. These are some YAML basics. You should read more about it . Following AI instructions without understanding is not going to take you far.

@olivierlambert Thank you for the reply. There was a thread on here about the iso not being mounted properly and I commented about having power off the vm and back and it will load the iso. This is specifically true with the 0.4.0 for linux. Image pulled from the XO Hub will not mount the ios if the vm is powered on. There is Yellow Explanation mark next to it. Power off vm and power on vm iso is ok. Reboot vm does not let the ios to work.

Commenting for my future self. This works for CentOS Stream 10; # Install Extra Packages for Linux, where xe-guest-utilities-latest lives sudo yum install epel-release # Install sudo yum install xe-guest-utilities-latest # Start the Service on Boot sudo systemctl enable xe-linux-distribution # Start the Service Now sudo systemctl start xe-linux-distribution # Check the Service is Running sudo systemctl status xe-linux-distribution # Check it's installed sudo yum list installed xe-guest-utilities-latest I wasn't particularly committed to Rocky Linux 10, so thought I'd give the usual steps a run on a different similar OS using CentOS Stream 10. Works absolutely fine. As a comparison, when I run the above steps on Rocky Linux 10, it fails on the second step above when trying to install from yum, which appears to be due to this not being included in EPEL. sudo yum search xe-guest-utilities No matches found. Curious to understand if anyone knows why EPEL is different between CentOS Stream 10 VS Rocky Linux 10. Is this just some upstream thing that isn't perfectly aligned?

@dani You mentioned in another thread that you're from Spain. ¿Me ayudas con la traducción al castellano para XCP-ng y XOA? Apúntate a https://translate.vates.tech/projects/xen-orchestra/xen-orchestra-6/es/

@dinhngtu Thanks. We plan to migrate all Windows VMs from the Citrix tools down the road and only have a handful of VMs running these so far so will maybe hold off until the next version. Have been running the Linux rust tools for over a year with zero issues..

Thanks @Bastien-Nollet and @olivierlambert . I'm going to do some tests and write the results. Thank you so much.

@Forza Cancelling a backup run is also on our roadmap ,as soon as we have done reworking the tasks to use xo-task on the full chain, and not an hybrid of various iteration of the tasks objects better tracking of the backup run is also on our roadmap , this is also linked to the task changes plus are some issues with the size on the remote before being able to do this In any case, both are on our backlog

October release fixed it

@andriy.sultanov Thank you very much for working on this! I can test your proposed fix in our lab during next week. Best regards

Hi! I'm not sure who to ping exactly for this question @pdonias or @Bastien-Nollet maybe?