@stormi Thanks @stormi. I have to get used to XO. I always use XCP-ng Admin on Windows because old habits die hard, and there I cannot even select UEFI with all the Linux templates. The magic that XO does is that it allows to use the templates, but with UEFI. I have a VM that I've deployed with the "Other install media" option, so I just dettached the disk and reimported on the new one created by XO, with the correct template. Everything seems fine. So my question about inheriting the template is not relevant if we use XO. Hope my understand is correct. Thanks.

@KPS Because you changed the virtual hardware when disabling the option.Windows now see xcp-ng pci devices instead of Citrix pci devices, and you dont have the xcp-ng drivers installed - i.e. blue screen during boot because Windows cannot access the virtual harddisk.

@AtaxyaNetwork thank you

Sorry but it's still very blurry to me. Which panel are you talking about? Are you using XO from the sources and if yes, how did you install it?

While not critical...It would be nice to have the same dialog for system disks as we do for system names in the multiple VM's section under "advanced." Seems like a really easy thing to add that would prevent someone from having to go back and rename disks later. The system is already creating a name, it's already giving us the ability to name the disks for singles, why not be able to name the disks like the systems for multiples?

Welcome @martinpedros Happy to know it works for you now!

@jimmymiller Thank you! I destroyed the old VM and created a new one and then installed the guest tools using your instructions. XO detects the guest tools as version 8.2.x: [image: 1717620543944-83a24b19-060b-4e2d-8c90-675f3ffc0200-image.png] Thank you again! SW

I won't repeat everything from my response to your ticket, but for the benefit of anyone reading this -- xo-cli ldap.synchronizeGroups

@lawrencesystems configuration is as follows one server, basically a dell t30 that i use to run debian with appliance dell server with 4 3tb drives in raid 5 on hardware controller 24cpus 96gb now beforehand i added this storage to the host it was on, however because i couldnt add the host to the pool with this shared storage, i forgot the storage. lol funny thing is, the storage doesnt appear to be forgotten even after reimaging the server and and reinitializing the storage. heres the log sr.createHba { "host": "5cc10b03-118e-419a-b6fb-c32c4ff50e58", "nameLabel": "s0001", "nameDescription": "vm-storage", "scsiId": "36782bcb035b530002da9ce12118697c1" } { "code": "SR_BACKEND_FAILURE_19", "params": [ "", "No such device [opterr=Device /dev/disk/by-id/scsi-36782bcb035b530002da9ce12118697c1 does not exist]", "" ], "call": { "method": "SR.create", "params": [ "OpaqueRef:0662cf5f-0e81-73b3-ffbe-b7a3020692b5", { "SCSIid": "36782bcb035b530002da9ce12118697c1" }, 0, "s0001", "vm-storage", "lvmohba", "user", true, {} ] }, "message": "SR_BACKEND_FAILURE_19(, No such device [opterr=Device /dev/disk/by-id/scsi-36782bcb035b530002da9ce12118697c1 does not exist], )", "name": "XapiError", "stack": "XapiError: SR_BACKEND_FAILURE_19(, No such device [opterr=Device /dev/disk/by-id/scsi-36782bcb035b530002da9ce12118697c1 does not exist], ) at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202404251617/packages/xen-api/_XapiError.mjs:16:12) at file:///opt/xo/xo-builds/xen-orchestra-202404251617/packages/xen-api/transports/json-rpc.mjs:38:21" }

@Danp I had issue with DNS. After I fixed it I could update xoa to newer version and debian also. wget was included in the update package of Debian. After wget installation I could install zabbix agent also. Not it is up and running and is connected to zabbix server. Please close the topic. Thank you.

Documented at https://xen-orchestra.com/docs/xoa.html#other-interfaces

Although I didn't encounter your problem, I followed the steps in an article ( sorry fail to post the link) and successfully migrated the virtual machine from VMware to XCP-ng, which was very convenient.

@vahric-0 Then I am out of suggestions, sorry.