Created attachment 1510849 [details] win2019 Description of problem: [RFE]Add "windows 2019 x64"to operating system option on rhv4.2 Version-Release number of selected component (if applicable): rhv:4.2.7.5-0.1.el7ev How reproducible: 100% Background: 1.Use virt-v2v convert a win2019 guest to rhv4.2 but its operating system shows Windows 2016 x64，pls refer to screenshot"win2019" Actual results: As above description Expected results: Should add "windows 2019 x64" to operating system option on rhv4.2 Additional info:
In general, we adjust the os types when there's a difference in the virtual hardware configuration. Windows 2019 is more or less identical to Windows 2018 in this sense. We can add it to the list of ostypes, but there is basically no chance that such a change will make 4.2
Need to add support in windows guest tools / drivers first, only then it can be supported in RHV. Also do not forget new icon and sysprep xml
also, guest agent reporting. I suspect it's not working in current qemu-ga either.
(In reply to Michal Skrivanek from comment #4) > also, guest agent reporting. I suspect it's not working in current qemu-ga > either. so please also pull in fixed qemu-ga from bug 1659071
(In reply to Michal Skrivanek from comment #5) > (In reply to Michal Skrivanek from comment #4) > > also, guest agent reporting. I suspect it's not working in current qemu-ga > > either. > > so please also pull in fixed qemu-ga from bug 1659071 The fix there is not relevant to us as we don't rely on names reported from qemu-ga. I opened a VDSM bug 1676893
Tested on ovirt-engine-4.3.3.1-0.1.el7.noarch The Win 2019 option is still missing from operating system pick when creating a new VM.
Created attachment 1549464 [details] operating system select in new VM
Verified on ovirt-engine-4.3.4-0.1.el7.noarch
This bugzilla is included in oVirt 4.3.4 release, published on June 11th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.4 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.