@Greg_E thanks for the feedback. I am stuck on this one. is either host or chipset specific and I don't have another e5-2680 v3 to test with. found another post on here around the same time frame that has this same error on boot. hope its not a broader issue. https://xcp-ng.org/forum/topic/10075/imported-vm-starts-but-does-not-initialize-the-display

@gduperrey @business XOA (latest). @home XO from sources (latest build)

@olivierlambert Thanks. I've been doing some digging this morning and what I was thinking of testing isn't going to work. It's interesting reading but not going to help me.

@mauzilla I just read this thread and it might help https://xcp-ng.org/forum/topic/9924/vm-vcpu-allocation I've only ever run my systems with the same processor and configuration in each host, so not sure about your system. The biggest issue with a mixed environment is to keep the processors in the same family/generation, and mixing Intel and AMD in different hosts could cause issues after a migration.

@olivierlambert We have successfully installed using: rpm -Uvh https://repo.zabbix.com/zabbix/7.0/rhel/7/x86_64/zabbix-release-latest.el7.noarch.rpm yum install zabbix-agent2 zabbix-agent2-plugin-* --enablerepo=base,updates

FYI, Xen has a registered OUI: 00:16:3E edit: I didn't read @olivierlambert previous post mentioning the OUI [image: 1732627775032-xen-oui.png] Source: https://www.macvendorlookup.com

@adriangabura This is a production server. This is also the only one we have on the cloud (OVH) for all our others hosts we use a private network behind our firewall and login via OpenVPN. But OVH we are struggling to come to a good design especially since version 8.3 now connect you to the web interface directly. How do we change port or block it?

@CJ the fix has been merged and will be available in the next release.

Oh that's great! Nice catch How did you find the root cause?

Perfect, enjoy XCP-ng and XO!

Hi, This error is telling you that you don't have enough free space on the SR where the VDI currently reside. Regards, Dan

@McHenry Yes, XCP sees and uses all threads (8 core + SMT x2 threads = 16 logical cores). So you can assign all of them to a VM as long as the VM can use them. XO shows 16 "cores" (total threads) and 1 socket. It also shows hyperthreading is enabled. XCP/XO does not differentiate between cores, threads, E-Cores or P-Cores.....a thread is an assignable core resource. You can assign 16 logical vCPU that includes real cores and SMT threads. Some programs do not work well with hyperthreading in a VM environment. So you may wish to disable SMT depending on the workload.

@m-mirzayev said in ISCSI mount - SR_BACKEND_FAILURE_432: @john-c Would you mind to post your custom.conf so i have a reference? @m-mirzayev I don’t use multipath personally however, though managed to get Microsoft Copilot to put what you gave above into a valid structure. I also remember people in the past having trouble with multipath, so Vates employees implemented this /etc/multipath/conf.d/custom.conf to fix these issues. # /etc/multipath/conf.d/custom.conf defaults { user_friendly_names yes } multipaths { multipath { wwid "your_device_wwid_here" alias "truenas_iscsi" path_selector "round-robin 0" path_grouping_policy multibus path_checker tur prio const failback immediate } } devices { device { vendor "TrueNAS" product "iSCSI" path_selector "round-robin 0" path_grouping_policy multibus hardware_handler "0" prio const failback immediate } } Please replace "your_device_wwid_here" with the WWID of the device on your network.