Windows virtual machine losing static IP configuration and secondary disks coming up offline after changing cluster compatibility to 4.6
Environment
- Red Hat Virtualization 4.4.6 and up
- Windows server 2016
- Windows server 2019
Issue
- Post cluster compatibility change from 4.5 to 4.6 after the first reboot all Windows VM's started losing static IP configuration and Secondary disks coming up offline.
Resolution
Possible workarounds:
- After updating the CL, fix the Windows guests manually: reconfigure the static IP and re-enable all secondary disks that got offline; then restart the VM.
- Set custom cluster level on each potentially impacted VM before the cluster-upgrade (also available via API) to avoid the change of the machine type (less recommended).
- Another option is to stay on CL 4.5 and to not change to CL 4.6; there are no plans to deprecate CL 4.5 in RHV as of today, so it will continue being supported with RHV 4.4.
Root Cause
The root cause and potential resolution are being investigated in This content is not included.Bug 1979730:
- When importing Windows 2016/2019 VMs to either cluster level 4.5 or 4.6 the secondary disks are set to offline.
- When changing the emulated machine of the VM from
pc-q35-rhel8.3.0topc-q35-rhel8.4.0, an additional NIC is discovered within the guest and the secondary disks go offline.
This is triggered by This content is not included.BZ 1939546 - virtio-win drivers change instance name when PCI host/bridge UID changes from 1 to 0 .
Diagnostic Steps
- In Windows guest Device Manager tab new Ethernet Adapter #2 created and old Ethernet Adapter showing grayed out.
Device Manager
SBR
Product(s)
Components
Category
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.