Here's the output of xe vm-list params=all uuid ( RO) : f0b2ff27-5a70-2bef-f7bf-cec0f33a4484 name-label ( RW): Win11x64 name-description ( RW): user-version ( RW): 1 is-a-template ( RW): false is-default-template ( RW): false is-a-snapshot ( RO): false snapshot-of ( RO): <not in database> snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): <not in database> children ( RO): is-control-domain ( RO): false power-state ( RO): halted memory-actual ( RO): 8592080896 memory-target ( RO): <expensive field> memory-overhead ( RO): 73400320 memory-static-max ( RW): 8589934592 memory-dynamic-max ( RW): 8589934592 memory-dynamic-min ( RW): 8589934592 memory-static-min ( RW): 4294967296 suspend-VDI-uuid ( RW): <not in database> suspend-SR-uuid ( RW): d0d928ee-1673-dda2-800f-3f027a94e1c5 VCPUs-params (MRW): VCPUs-max ( RW): 4 VCPUs-at-startup ( RW): 4 actions-after-shutdown ( RW): Destroy actions-after-softreboot ( RW): Soft reboot actions-after-reboot ( RW): Restart actions-after-crash ( RW): Restart console-uuids (SRO): hvm ( RO): false platform (MRW): timeoffset: 0; device-model: qemu-upstream-uefi; cores-per-socket: 2; device_id: 0002; viridian: true; viridian_time_ref_count: true; viridian_reference_tsc: true; viridian_apic_assist: true; viridian_crash_ctl: true; viridian_stimer: true; secureboot: false; vga: std; videoram: 8; nx: true; acpi: 1; apic: true; pae: true; hpet: true; acpi_laptop_slate: 1; vtpm: true allowed-operations (SRO): destroy; metadata_export; export; make_into_template; changing_NVRAM; changing_shadow_memory; changing_static_range; changing_dynamic_range; migrate_send; start_on; start; copy; clone; snapshot current-operations (SRO): blocked-operations (MRW): allowed-VBD-devices (SRO): <expensive field> allowed-VIF-devices (SRO): <expensive field> possible-hosts ( RO): <expensive field> domain-type ( RW): hvm current-domain-type ( RO): unspecified HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): firmware: uefi; order: cd HVM-shadow-multiplier ( RW): 1.000 PV-kernel ( RW): PV-ramdisk ( RW): PV-args ( RW): PV-legacy-args ( RW): PV-bootloader ( RW): PV-bootloader-args ( RW): last-boot-CPU-flags ( RO): vendor: GenuineIntel; features: last-boot-record ( RO): <expensive field> resident-on ( RO): <not in database> affinity ( RW): 6d1ccaa7-3e75-4840-9ee6-054a7be36a96 other-config (MRW): base_template_name: Windows 11; import_task: OpaqueRef:58b9d8e8-3578-150b-045d-5e500f94f6b7; mac_seed: 496c087a-d7e4-1a07-cd59-a2e3aa046d04; install-methods: cdrom dom-id ( RO): -1 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="1649267441664"/><restriction field="vcpus-min" min="2"/><restriction field="vcpus-max" max="64"/><restriction field="has-vendor-device" value="true"/><restriction field="supports-bios" value="no"/><restriction field="supports-uefi" value="yes"/><restriction field="supports-secure-boot" value="yes"/><restriction max="255" property="number-of-vbds"/><restriction max="7" property="number-of-vifs"/></restrictions> xenstore-data (MRW): vm-data/mmio-hole-size: 268435456; vm-data: ha-always-run ( RW) [DEPRECATED]: false ha-restart-priority ( RW): blobs ( RO): start-time ( RO): 20260128T17:40:40Z install-time ( RO): 20260128T17:40:36Z VCPUs-number ( RO): 0 VCPUs-utilisation (MRO): <expensive field> os-version (MRO): netbios-name (MRO): PV-drivers-version (MRO): PV-drivers-up-to-date ( RO) [DEPRECATED]: true memory (MRO): disks (MRO): VBDs (SRO): dd13b4f7-4ce6-aa92-977c-d55997ff23b9; a231e90c-f1ff-1715-4335-a842b38e55b8 networks (MRO): services (MRO): PV-drivers-detected ( RO): true other (MRO): platform-feature-xs_reset_watches: 1; platform-feature-multiprocessor-suspend: 1; has-vendor-device: 1 live ( RO): true guest-metrics-last-updated ( RO): 20260128T17:40:44Z can-use-hotplug-vbd ( RO): unspecified can-use-hotplug-vif ( RO): unspecified cooperative ( RO) [DEPRECATED]: <expensive field> tags (SRW): appliance ( RW): <not in database> groups ( RW): snapshot-schedule ( RW): <not in database> is-vmss-snapshot ( RO): false start-delay ( RW): 0 shutdown-delay ( RW): 0 order ( RW): 0 version ( RO): 0 generation-id ( RO): 4909433915876267241:9153903600474305670 hardware-platform-version ( RO): 2 has-vendor-device ( RW): true requires-reboot ( RO): false reference-label ( RO): windows-11 bios-strings (MRO): bios-vendor: Xen; bios-version: ; system-manufacturer: Xen; system-product-name: HVM domU; system-version: ; system-serial-number: ; baseboard-manufacturer: ; baseboard-product-name: ; baseboard-version: ; baseboard-serial-number: ; baseboard-asset-tag: ; baseboard-location-in-chassis: ; enclosure-asset-tag: ; hp-rombios: ; oem-1: Xen; oem-2: MS_VM_CERT/SHA1/bdbeb6e0a816d43fa6d3fe8aaef04c2bad9d3e3d pending-guidances ( RO): vtpms ( RO): 70e89c07-98aa-3716-11a3-f67b370c4a91 pending-guidances-recommended ( RO): pending-guidances-full ( RO):

@benapetr yes, i'm about connections and credentials export\portable mode. Got it.

Keep us posted, happy to hear from it!

I made a list of processes with a small bash script that I am attaching here [image: 1769612600385-screenshot-2026-01-28-alle-16.01.53.png]

@florent Yes.

@jkatz So everyone is cleared since I just experience the same issue not allowing me to create a new vm using the template. Before you use the Windows 11 Template and you have it with SYSPREP ready. You need to go down to advanced and make sure you delete the VTPM [image: 1769552292859-5d61aad5-013e-4cff-af7c-adbb4c4ca809-image.png] then create the Template. Once you create the vm again you will not receive the error and a vtpm will be created for the new VM with no issue. Hope this helps.

@drwhite85 I suggest watching some youtube videos about xcp-ng. I guest Lawrence Systems - https://www.youtube.com/watch?v=2wMmSm_ZeZ4 He has other videos that go into more depth

@dinhngtu That's great, thank you. I think I'll wait a bit before switching tools. Everything's working perfectly at the moment. If you need me to test anything, just let me know. I'd be happy to test it when I have time.

@rzr Thank you very much! @michmoor0725 Absolutely! The community is another aspect of why working with XCP-ng is a lot more fun compared to working with VMWare!

@olivierlambert Thanks! Very little time/ learning progress had been made/spent on this VM so I have gone ahead and created a new VM. The VM with the mysterious device still exists. So it would be interesting to know how but not essential.

You can forget them, no issue.

@psafont Freezing/thawing doesn't actually suspend a VM, but it's just a part of the backup process, where I/O operations are quiesced to create a stable view of the on-disk data.

@pdonias https://docs.xen-orchestra.com/users [...] Operator An operator can make everyday operations on assigned objects. For example, on a VM: eject a CD insert a CD (if he can view the ISO storage repository) start, restart, shutdown, suspend/resume it All other operations are forbidden. [...] As I understand it (I may be mistaken), changing the "Rate Limit" is already a configuration change and should not be available to an Operator.

@samuelolavo Yes, I do use NUT, but I don’t want to install any additional packet on XCP-ng. The way I found leverage the SSH authorized keys restrictions, and so you only need to change one file. Thanks for the link anyway

I had the same question but the responses here was amazing and the following blogpost nailed it. I hope it helps someone else too: https://techdirectarchive.com/2026/01/25/a-z-of-xcp-ng-and-xen-orchestra-setup-and-vm-creation/

@LoTus111 Hello, I attempted to reproduce the issue without success. Could you please share the logs with us so we can conduct a deeper investigation? Feel free to send them to me via PM.