What were you trying to do that didn't work?

The customer is moving from vSphere to "Azure Local hypervisors", which is a new offering from Azure

What is the impact of this issue to you?

Assuming this is not supported/tested, there is no way to track the vms and create the host-guest mapping

Ps.: We don't know if this new offering will act as a regular Hyper-V

Please provide the package NVR for which the bug is seen:

How reproducible is this bug?:

Steps to reproduce

1. Setup virt-who to point to the new "Azure Local hypervisors"
2.  
3.  

Expected results

Be able to track the info and create the host-guest mapping

Actual results

We don't have the environment, and we don't know if the new offering will act as a regular Hyper-V hypervisor