@olivierlambert is spot on. Manage expectations. The best thing we can do is contribute helpful information.

Here is what I was able to deduce when this issue came up.

When creating a Windows VM in uefi mode and using the floppy_file option in packer:

1. There is a disk added as "fda"
2. However the fda device is not available as the a: drive or any other drive letter. When booted using bios mode, you can find the fda device by settting drive letter to "a:".

This is likely because uefi typically does not support floppy disks. I believe in VMWare when the floppy_file option was used in UEFI mode, it added the ISO as a DVD drive instead of an FDA.

Not sure if this is best solved at the Packer level or if it should be intercepted and corrected XCP-ng level?

@fatek

I noted that in the packer file. I was not able to get packers floppy_files working in uefi mode.

@ddelnano might have some insight?

@fatek

After posting this I ended up building out a sample project and shared on github.
https://github.com/mtcoffee/xcp-ng-packer-examples

@olivierlambert

It turns out this had nothing to do with the VM or Hypervisor, but was guest specific. Here is the scoop for anyone that may come across this Ansible AWX install error.

Ansible AWX now prefers Kubernetes over Docker to run on and in this case I used K3s on Rocky Linux. After K3s is installed if you run "kubectl get apiservice" you will see:
"kube-system/metrics-server false (missingendpoints)"

This is what causes the Ansible AWX install to fail with "Unable to determine if virtual resource"

The solution:
Installing K3s on Rocky Linux requires the extra step of disabling SELinux and firewalld

sudo setenforce 0
sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/' /etc/selinux/config
sudo systemctl disable firewalld --now

@olivierlambert

Thanks for the insight. I will follow up and post back.

While installing Ansible on RockyLinux on an XCP-ng host I'm getting the error "Unable to determine if virtual resource". Same error described here:
https://chr00t.com/installing-awx-on-almalinux-9/

In the case of Proxmox the post describes:
Changing the CPU type from “Default (kvm64)” to Host. This sets the VM to match the CPU of the host.

Is their a similar setting in XCP-ng?

@olivierlambert Sure, happy to do so.

I am now a VMware -> XCP-ng convert and wish I had known sooner. This post helped me get to the point of fully automated template and server builds with Packer/Terraform.

Here are my code samples. Hope it helps someone else!

Packer/XCP-ng Templates
https://github.com/mtcoffee/xcp-ng-packer-examples

Terraform/XCP-ng Templates
https://github.com/mtcoffee/xcp-ng-terraform-examples

I had never heard of Cloudbase-init for Windows until reading this post. I was inspired and found away to get it working with XCP-ng. Hope it helps someone.

Packer/XCP-ng Template for Windows that loads Cloudbase-init
https://github.com/mtcoffee/xcp-ng-packer-examples

Terraform/XCP-ng Template for Windows that leverages Cloudbase-init template
https://github.com/mtcoffee/xcp-ng-terraform-examples

@dan89

Do you have a pkr.hcl for windows that you can share?

I am curious how your handling winrm and autounattend.xml?

This post saved me a lot of time. Thank you for sharing