@stormi It was a fresh install of 8.2.1. No updates had been applied.

@ThasianXi This worked well, thank you for the feedback!

Hello,
Are the XCP Guest tool drivers supported on RHEL 9? I am having a challenge getting them installed. Installation of the guest tools provided by XCP-ng completes but the drivers are still shown as not configured. I have tried on several vms running RHEL9 and all behave the same. Hypervisor version is XCP-ng 8.2.1

@olivierlambert Those were the only messages on the log, nothing else captured on any other log file like the crit.log file or dmesg

@olivierlambert Had the same issue with a similar server. Replaced both RAM and disk but the host kept going into read-only mode. The host would run just fine when installing any other OS/hypervisor. The server model is Supermicro SYS-6028TP-HC0R

@dmjorge This was never resolved. Replaced RAM and SSD, disabled SAS controller and same issue. Tried installing XCP on a different server but the same model and the issue re-occured.

Installed Proxmox and it has been running without any issue. I believe there is a compatibility issue of XCP-ng and Supermicro SYS-6028TP-HC0R

@olivierlambert This was resolved by editing the disk position. The disk position on XenServer was xvda and changing it to 0 resolved this.

Reference
https://support.citrix.com/article/CTX216911/error-no-bootable-device-found-while-booting-xenserver-vm

@olivierlambert Yes,they are in HVM mode and currently running.

Hello all, looking for feedback as to a challenge I'm experiencing when migrating VMs from Xenserver 6.5 to XCP-ng 8.2.1. The exported vms fail to start and have the error "Boot device:Hard Disk - failure: could not read boot disk".The methods I have used to migrate are taking a snapshot of the VM,create a template from that snapshot, export that template to XCP then create a VM from it. The newly created VM will not start for some VMs. The only common trait that the VMs have is that they are Linux but they are diffrerent distros. I have tried removing xentools then trying the same but the issue still remains.

Any insight or alternatives on how to move these VMs will be appreciated

Issue still persisted after rebooting and running fsck. Host went into read-only mode not long after it came up.