Hi jkatz - I am a sales manager for Vates America Corp and I apologize for any confusion but 'complete feature set' is referring to XOA. We list XOSTOR, XOPROXY, and Airgap Support all as 'optional' because they are add-ons and incur additional costs. One of my team members or I will be happy to answer any questions you have and discuss the various costs of our add-on offerings. We can be reached at sales@vates.tech and we'll look forward to hearing from you.

@Kptainflintt said in Cloning Windows 11 with vTPM: No reply to this topic but just seen same thing. And same "workaround" : disabling vTPM at VM creation from template to avoid crashing. I can confirm that XOA want to add a second vTPM, any fix ? Sharing for temporal context: This appears to still be be happening when creating a VM using my custom Windows 11 template (didn't do any cloudbase stuff, just some really basic stuff like updates, then sysprep). Once I click "Open advanced settings" then toggle "Enable vTPM" into the disabled state, my attempt to create the VM succeeds, and the newly cloned VM has a vTPM with a different UUID. This is literally my first attempt at creating and then cloning a windows 11 template, but it seems to be working.

Alright I finally got it to work. I think the trick was to put "Ethernet 2" in quotations. I also perfected the YAML spacing and bracketed the two nameserver addresses. Thanks for the help gentlemen. Final working network config: #network: version: 2 ethernets: "Ethernet 2": dhcp4: false addresses: - 192.168.1.30/24 gateway4: 192.168.1.1 nameservers: addresses: [192.168.1.5, 8.8.8.8]

@Danp Yup, that will do it. Thanks. No longer pulling out my hair.