Bug 2181127

Summary:	Drop WS2012 and WS2012R2 support from qemu-kvm/virtio-win
Product:	Red Hat Enterprise Linux 9	Reporter:	Qianqian Zhu <qizhu>
Component:	qemu-kvm	Assignee:	Vadim Rozenfeld <vrozenfe>
qemu-kvm sub component:	General	QA Contact:	jingzhao <jinzhao>
Status:	CLOSED MIGRATED	Docs Contact:	Jiri Herrmann <jherrman>
Severity:	medium
Priority:	high	CC:	chayang, gveitmic, jinzhao, juzhang, lijin, mdean, mkedzier, mtessun, mzhan, qzhang, rjones, virt-maint, vrozenfe, xuhan, yfu, yvugenfi, zhguo
Version:	9.3	Keywords:	MigratedToJIRA, Tracking, Triaged
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Removed functionality
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-15 15:34:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Qianqian Zhu 2023-03-23 07:49:17 UTC

Description of problem:
This bz is mainly a tracker to update related internal and external docs, including QE's test plan.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 John Ferlan 2023-03-23 10:31:48 UTC

Please don't leave this assigned to virt-maint...

Although I have to wonder wouldn't perhaps using a Jira Epic in the XKVMNINE project be a better way to handle?

Comment 3 RHEL Program Management 2023-08-15 15:25:07 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-08-15 15:34:07 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.