Bug 2021217

Summary:	[RFE] Windows 2022 support
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Juan Orti <jortialc>
Component:	ovirt-engine	Assignee:	Shmuel Melamud <smelamud>
Status:	CLOSED ERRATA	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.8	CC:	ahadas, nobody, nsimsolo, patrick.lomakin
Target Milestone:	ovirt-4.5.0	Keywords:	FutureFeature, ZStream
Target Release:	4.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.0	Doc Type:	Enhancement
Doc Text:	Add Windows 2022 as a guest operating system	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-26 16:23:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1968312, 2004160, 2036863
Bug Blocks:

Description Juan Orti 2021-11-08 15:29:01 UTC

Windows 2022 is already available but RHV is missing support for it in some areas:

1. Windows 2022 x64 is not available as a guest OS selection for the VMs.

2. ISO image VirtIO win version 1.9.17 does not include directory 2k22 with drivers.

3. Windows 2022 can be installed and runs, but with VirtIO drivers 1.9.17 it does not show IP address in RHV-M and shows a warning about not up to date guest agent.

Comment 5 Nisim Simsolo 2022-04-19 16:07:07 UTC

Verified:
ovirt-engine-4.5.0.2-0.7.el8ev
vdsm-4.50.0.12-1.el8ev.x86_64
qemu-kvm-6.2.0-11.module+el8.6.0+14707+5aa4b42d.x86_64
libvirt-daemon-8.0.0-5.module+el8.6.0+14480+c0a3aa0f.x86_64

Verification scenario:
tested with virtio-win-1.9.25
1. Verify Windows 2022 is listed in edit VM dialog -> operating system
2. install Q35/UEFI windows from scratch using run once without guest-tools checkbox checked (in run once manu).
3. verify vioscsi driver (in attached CD -> virtio-win.iso) for win2022 can be installed during Windows installation, and that Windows VM disk is listed after driver installation
4. From Windows console, attach virtio-win CD and install virtio-win-guest-tools.exe
     Verify all drivers installed 
     Verify guest-agent is functioning
     Verify TPM is listed in Windows device manager and drivers are installed.
5. Verify RHV VM functionality:   
     Migrate VM
     suspend VM -> run VM
     shutdown VM -> run VM
     power off -> run VM
     reboot VM
     make template,
     create VM from template
     VM pool from template
     clone VM
     CPU hotplug 
     Memory hotplug
6. Install windows VM with Q35/SecureBoot using run once with "Attach Windows guest tools CD"  checkbox checked
     After installation is completed, Verify Secure boot is enabled on VM and security keys are enrolled.
     Repeat step 5 test steps    
7. Repeat step 6 this time for Q35/BIOS VM.

Comment 6 Arik 2022-05-08 12:26:19 UTC

This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Comment 7 Arik 2022-05-23 10:34:25 UTC

Oops, component = RHV

Comment 12 errata-xmlrpc 2022-05-26 16:23:22 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: RHV Manager (ovirt-engine) [ovirt-4.5.0] security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:4711