@stormi It was a fresh install of 8.2.1. No updates had been applied.
Posts made by Denson
-
RE: Installation of XCP Guest tool frivers on RHEL9
-
RE: Installation of XCP Guest tool frivers on RHEL9
@ThasianXi This worked well, thank you for the feedback!
-
Installation of XCP Guest tool frivers on RHEL9
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
-
RE: XCP-NG Host stuck in read-only mode
@olivierlambert Those were the only messages on the log, nothing else captured on any other log file like the crit.log file or dmesg
-
RE: XCP 8.2 ssd error
@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
-
RE: XCP-NG Host stuck in read-only mode
@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 -
RE: Migrating VMs from Xenserver 6.5 to XCP-ng 8.2.1
@olivierlambert This was resolved by editing the disk position. The disk position on XenServer was xvda and changing it to 0 resolved this.
-
RE: Migrating VMs from Xenserver 6.5 to XCP-ng 8.2.1
@olivierlambert Yes,they are in HVM mode and currently running.
-
Migrating VMs from Xenserver 6.5 to XCP-ng 8.2.1
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 -
RE: XCP-NG Host stuck in read-only mode
Issue still persisted after rebooting and running fsck. Host went into read-only mode not long after it came up.
-
RE: XCP-NG Host stuck in read-only mode
I will restart and use a systemrescuecd to run fsck -
RE: XCP-NG Host stuck in read-only mode
It's a recently installed host.Root is only at 10% utilization. Does XCP-ng have any compatibility issues with Supermicro servers?
-
XCP-NG Host stuck in read-only mode
Hello all,
Recently experienced an issue of host upgraded from XenServer 6.5 to XCP-ng going into read-only mode. Once in this state, VMs can't be migrated to other hosts nor can VMs be started on the host. When restarted the issue is resolved for a short time but then re-occurs.
Did a fsck check and repair but this did not resolve the issue. Posts on similar issue pointed to a boot disk failure and so we replaced the disk and re-installed XCP-ng Ver 8.0 but once added back to the pool the issue re-occurred. Trying to start a VM on the host shows the error below:
Does anyone have any experience with this and how to resolve.