@indyj said in Centos 8 is EOL in 2021, what will xcp-ng do?:
@jefftee I prefer Alpine Linux.
+1
Low resource footprint, no bloatware... They even have a pre-built Xen Hypervisor ISO flavor
@indyj said in Centos 8 is EOL in 2021, what will xcp-ng do?:
@jefftee I prefer Alpine Linux.
+1
Low resource footprint, no bloatware... They even have a pre-built Xen Hypervisor ISO flavor
I liked as well. Easy to find the topics and good layout
@olivierlambert congrats to the team and also to this great community!
@erfant probably not because the nvme driver is loaded and there're no nvme errors in the logs.
@olivierlambert thank you and your team for this great project and community! It's a nice place to share knowledge and learn new stuff. I learn a lot here!
@erfant after seeing your uploaded dmesg
, the steps 2 & 3 boot options can be put aside for while because the error isn't the same as the other topics.
The log is showing MxGPU driver probe/initialization errors. After some digging, could be the case of a GPU firmware being incompatible with UEFI. Do you have any spare server for testing XCP-ng boot in legacy/BIOS with this GPU?
[ 119.418930] gim error:(gim_probe:123) gim_probe(08:00.0)
[ 121.145663] gim error:(wait_cmd_complete:2387) wait_cmd_complete -- time out after 0.003044131 sec
[ 121.145719] gim error:(wait_cmd_complete:2390) Cmd = 0x17, Status = 0x0, cmd_Complete=0
[ 121.145984] gim error:(init_register_init_state:4643) Failed to INIT PF for initial register 'init-state'
Edited for clarification.
@Appollonius said in Strange issue with booting XCP-NG:
Its only when I install the GPU and dont connect it to a monitor that it will not boot properly.
Maybe because, when there's a GPU installed but no monitor attached, the motherboard POST fails at EDID probe? As stated, some boards/BIOS require an explicit configuration in order to boot without a monitor/keyboard/mouse plugged, eg.:
https://www.supermicro.com/support/faqs/faq.cfm?faq=11902
The incorrect clock results mean that Xen isn't in charge of frequency scaling management. Set the CPU Power Management to Performance Per Watt (OS)
and run the previous xenpm
, this time with a watch
for real-time:
# watch 'xenpm start 1 | grep -i "avg freq"'
Start a VM boot storm (or a stress test inside one or more VMs) in order to generate some CPU load.
It could be. For an user point of view, a single host pool wouldn't make any sense, so they created the "implicit/explicit" concept and treated everything as a pool internally.
That's a question for the Citrix dev team
Just FYI guys, XenCenter/XCP-ng Center have the menu option Pool > Make into standalone server. As pointed out by other members, every standalone host is in a pool, but that option reverts to an "implicit" one.
Hope this helps.
@jeff In order to create a virtual NUMA topology and expose it to the guest, the vNUMA feature needs to be implemented at hypervisor level and accessible through XAPI. I'm not sure if that feature is fully supported at the moment. Maybe @olivierlambert can confirm this?
You could try adding the cores-per-socket
attribute following the physical NUMA topology (96 / 4 nodes = 24):
xe vm-param-set platform:cores-per-socket=24 uuid=<VM UUID>
Let me know if it works.
@indyj said in Centos 8 is EOL in 2021, what will xcp-ng do?:
@jefftee I prefer Alpine Linux.
+1
Low resource footprint, no bloatware... They even have a pre-built Xen Hypervisor ISO flavor
This got my attention:
Jan 15 19:17:40 xcp-ng-xen12-lon2 xapi: [error||623653 INET :::80||import] Caught exception in import handler: VDI_IO_ERROR: [ Device I/O errors ]
Jan 15 19:17:40 xcp-ng-xen12-lon2 xapi: [error||623653 INET :::80||backtrace] VDI.import D:378e6880299b failed with exception Unix.Unix_error(Unix.EPIPE, "single_write", "")
Jan 15 19:17:40 xcp-ng-xen12-lon2 xapi: [error||623653 INET :::80||backtrace] Raised Unix.Unix_error(Unix.EPIPE, "single_write", "")
This Unix.EPIPE error on the remote target means that the pipe stream is being closed before VDI.Import receives all the data. The outcome is a VDI I/O error due to a broken, partial sent/received VDI.
Since a remote-over-the-internet link can be more prone to latency/intermittency issues, it might be needed to adjust the remote NFS soft timeout/retries or mounting the target with hard option.
I would also check if the remote target is running out-of-space during the backup process.
Could the fcoe
driver causing the issue?
dmesg:
[ 42.363389] bnx2fc: QLogic FCoE Driver bnx2fc v2.12.5 (November 16, 2018)
[ 42.371336] bnx2fc: FCoE initialized for eth1.
[ 42.371641] bnx2fc: [04]: FCOE_INIT passed
[ 42.387017] bnx2fc: FCoE initialized for eth0.
[ 42.387305] bnx2fc: [04]: FCOE_INIT passed
lsmod:
fcoe 32768 0
libfcoe 77824 2 fcoe,bnx2fc
libfc 147456 3 fcoe,bnx2fc,libfcoe
scsi_transport_fc 69632 3 fcoe,libfc,bnx2fc
@erfant probably not because the nvme driver is loaded and there're no nvme errors in the logs.
@olivierlambert thank you and your team for this great project and community! It's a nice place to share knowledge and learn new stuff. I learn a lot here!
@erfant after seeing your uploaded dmesg
, the steps 2 & 3 boot options can be put aside for while because the error isn't the same as the other topics.
The log is showing MxGPU driver probe/initialization errors. After some digging, could be the case of a GPU firmware being incompatible with UEFI. Do you have any spare server for testing XCP-ng boot in legacy/BIOS with this GPU?
[ 119.418930] gim error:(gim_probe:123) gim_probe(08:00.0)
[ 121.145663] gim error:(wait_cmd_complete:2387) wait_cmd_complete -- time out after 0.003044131 sec
[ 121.145719] gim error:(wait_cmd_complete:2390) Cmd = 0x17, Status = 0x0, cmd_Complete=0
[ 121.145984] gim error:(init_register_init_state:4643) Failed to INIT PF for initial register 'init-state'
Edited for clarification.
@erfant could you upload lspci -k
and dmesg
? Also, have you checked/tried:
vmlinuz
entry, boot with pci=realloc
;vmlinuz
entry, boot with pci=realloc pci=assign-busses