-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.5
-
guestfs-tools-1.51.6-4.el9
-
None
-
Moderate
-
rhel-sst-virtualization
-
ssg_virtualization
-
3
-
False
-
-
None
-
None
-
Pass
-
Automated
-
-
x86_64
-
None
Windows 2022 Server vms (and possibly others, I have only tested with Windows Server 2022), do not have the "blnsvr.exe" service installed as part of the migration process. This service is required to make memory usage statistics available for Windows VMs in the OpenShift UI.
Specifically the "kubevirt_vmi_memory_used_bytes" (along with other kubevirt_vmi_memory" stats) are not available/populated unless the blnsvr.exe service is installed and running.
This can be tested by doing the following:
- migrate a windows server 2022 vm
- ensure that the qemu-gest-agent is installed
- Check the OpenShift Virtual Machine "metrics" tab, you will see that "Memory" shows "No data available"
- query the "kubevirt_vmi_memory_used_bytes" from Prometheus to see that there is no data gathered for the windows virutal machine
- Install the "blnsvr.exe" service by locating the file on the virtio.iso and run `blnsvr.exe -i` to install the service (i used https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.240-1/virtio-win.iso but I believe the openshift built in one also has this file ... or it should)
- Reboot the Windows machine
- You will now notice that "memory" information is now available including both in the UI as well as querying directly from prometheus with the "kubevirt_vmi_memory_used_bytes" query.
Note the balloon driver is installed as part of the migration, but the service that makes it usable is NOT installed.
- clones
-
RHEL-36591 Migrated Windows VMs require the BLNSVR.exe service to be installed for accurate memory reporting
- Closed
- is cloned by
-
RHEL-56330 Implement virt-customize --inject-blnsvr [RHEL 10.0 beta]
- Release Pending
- links to
-
RHBA-2024:137879 guestfs-tools bug fix and enhancement update