Error installing Ubuntu 24.04 on new xcp-ng host.
-
What more information is needed?
Fresh install of xcp-ng 8.3 on host. Join host to existing xo-ce as 2nd pool (single host).
Connected nfs SR for vms and connected same ISO SR from pool 1.
did secureboot-certs install on host.
Created new vm for windows 11 and installed successfully.
Create new vm for Ubuntu error doring install.
-
And what about other Ubuntu version or Debian? Same issue?
-
I at first i didnt try any other Linux distros as I primarily use Ubuntu. However i just tried 25.10 and that worked.
Will try again with 24.04.03 iso again or redownload the iso.... Had no problems with the iso before.
-
Ok keep us posted
-
Ubuntu 24.04.2 installer failed as well...
Fresh download of 24.04.3 iso and same error. Also getting same error on my existing host also.
-
@acebmxer Could you fetch and send the error report somewhere?
-
Could you tell me where and how to fetch error report?
The only other cavoite i can state but i dont think should have caused this, but just to be 100% transparent.
When i tried connecting the new host to xo-ce i did try to add the new (Intel) host to a pool that consited of AMD cpus. I also tried using the same SR for VM storage as the other pool but it would not add the SR to the new pool but only to the host.
I have since created a new SR for the vm storage but i was able to mount the ISO SR from the other pool to the new pool. That ISO SR can been see by both pools and see the contents of the SR.
As stated before i was able to success fully install Windows 11 and Ubuntu Server 25.10 with no issues. Only Ubuntu 24.xx.xx fail to install.
-
Just tried Ubuntu 24.04.3 on my work servers and the install failed their as well I will open a support ticket as i have support on these servers.
Edit - Opened support ticket - Ticket#7746678
-
Smells a kernel bug in this specific version
-
Yeah not sure. Trying to remember when i was last successful in creating new vm with ubuntu 24.04.3. The best i can come up with is on 10/22/25 as i created a new vm within a day or two from that date.
But that fact that two separate systems showing the same problem....
