RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Current installer do not have windows server 2022 and windows 11 driver support. File this bz to track installer support for them.

Hi Vadim,

Could you please help to set DTM according to your schedule ?  and I will set ITM accordingly , thanks



Thanks
Menghuan

Hi Menghuan.

I'm moving it to 22 for now.
Please let me know if you are not fine with that.

BR,
Vadim.

(In reply to Vadim Rozenfeld from comment #3)
> Hi Menghuan.
> 
> I'm moving it to 22 for now.
> Please let me know if you are not fine with that.
> 
> BR,
> Vadim.

Thanks Vadim， thanks fine for me.

(In reply to menli from comment #4)
> (In reply to Vadim Rozenfeld from comment #3)
> > Hi Menghuan.
> > 
> > I'm moving it to 22 for now.
> > Please let me know if you are not fine with that.
> > 
> > BR,
> > Vadim.
> 
> Thanks Vadim， thanks fine for me.

Thanks Vadim， that's fine for me.

I guess we can move it on ON_QE since the all relevant changes were done already.

Try virtio-win-1.9.24-2.el8_5.iso, current installer have windows server 2022 and windows 11 driver support.
So this issue is fixed, change status to verified.