@pdonias said in Unable to deploy XOA on 8.3.0: We're aware of this and we're going to add a way to deploy another XOA when one is already deployed and also a way to choose which XOA the button redirects to when there are multiple ones deployed. Perfect thank you

Thank you so much for the replies! I appreciate the responses and will take the appropriate actions and then follow back up with a reply. Thanks again! Follow up shortly! 12/18/24 OK, I have no idea what I did to fix it but the VM in question has now recognized the original host. I suspended all VMs and reboot all servers and that didn't seem to help. Then I changed the network "adapter?" in the VM, and started the VM again and it works! I obviously don't understand the networking of Pools, Hosts or VMs well enough to just fix it in the first place, but all I know is that it is working! I would back up the VM in question, but unfortunately I originally made the storage "thick" and also it's around 6 TB big (all storage combined), so I don't have a remote storage big enough to store it. I appreciate all the responses and help!

@buldamoosh Oh yeah, you can't disable CBT on a snapshot. It is inherited from the VDI it is the snapshot of. You can vdi-destroy the snapshot instead of forgetting them But yeah, it is "normal" that the snapshot are not removed by the migration. CBT will be enabled by XO if you have the NBD+CBT enabled on your backup job.

@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