Unable to retrieve UUID of windows VM using `wmic` command

[Pearl1594]

Unable to get the UUID information from a Windows VM deployed on hosts with AMD processors using the:
wmic path win32_computersystemproduct get uuid command, which works on hosts with Intel processors.

[DaanHoogland]

@Pearl1594 , this is a regression on 4.20, right? or is it new/on 4.19?

[nvazquez]

@DaanHoogland we have been doing some tests with different KVM host OS against 4.19 and 4.20 and found out that is not a CloudStack regression but a problem with the latest libvirt and qemu versions. Tests performed at the moment:

KVM Host Operating System / CloudStack Version	Oracle Linux 8 - libvirtd 8.0.0 0, QEMU emulator version 6.2.0 (qemu-kvm-6.2.0-53.module+el8.10.0+90638+6d8ade84.4)	Ubuntu 22 - libvirtd (libvirt) 8.0.0, QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.26)	Oracle Linux 9 - libvirtd 9.0.0, qemu-kvm-7.2.0-14.el9_2.5	Ubuntu 24 - libvirt 10.0.0, QEMU emulator version 8.2.2
4.19.3.0	Works	Works	Works	Doesn’t Work(on both Intel and AMD)
4.20.1.0	Works	Works	Works	Doesn’t Work

[nvazquez]

We have completed the test matrix with different KVM OS against 4.19.3 and 4.20.1, it seems to be a regression from libvirt version 10 + qemu version 8 (included on Ubuntu 24) - the rest of the OSes with previous libvirt and qemu versions work fine on both CloudStack versions

[rohitpals]

@nvazquez Could you please let us know if there is any Workaround to resolve this issue.
We can't downgrade the OS from Ubuntu 24 to ubuntu 22.

[DaanHoogland]

@rohitpals , maybe you can downgrade qemu and libvirt?

[rohitpals]

While Doing that I saw CloudStack-Agent also getting removed as Qemu was being used by Agent.
Have you checked with Libvirt 10 and Qemu 7.2x or 6.2x - Does this combination works?

[rohitpals]

@weizhouapache I see the label as "not-a-bug"
Could you please confirm if this is not a BUG ANY MORE?

[rohitpals]

@nvazquez @DaanHoogland @weizhouapache @Pearl1594

Please confirm whether this a bug or not?

[DaanHoogland]

@rohitpals this is a failing interaction with libvirt/qemu due to changed behaviour in those programs. This is not a regression in CloudStack. We do not know the reason the integration API has changed in behaviour and where it should be fixed.

[nvazquez]

@rohitpals we have also raised the issues on the libvirt and QEMU projects. Please find the following links: https://gitlab.com/libvirt/libvirt/-/issues/807 and https://gitlab.com/qemu-project/qemu/-/issues/3098

[nvazquez]

As a workaround, you can still obtain the VM UUID through the VR user data by the URL:

http://<VR_IP>:80/latest/meta-data/instance-id