Bug 1731367

Summary: [RFE] SVVP Certification for Windows 10 IoT Enterprise (2016 LTSB)
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: Daniel Schaefer <dschaefe>
Component: qemu-kvmAssignee: Martin Jenner <mjenner>
qemu-kvm sub component: Testing QA Contact: Virtualization Bugs <virt-bugs>
Status: CLOSED WONTFIX Docs Contact:
Severity: medium    
Priority: medium CC: ailan, dschaefe, jjarvis, juzhang, lijin, virt-maint
Version: 8.0Keywords: FutureFeature
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-15 07:37:41 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Daniel Schaefer 2019-07-19 09:25:21 UTC
This is a request for enhancement to submit the SVVP results also for Windows 10 IoT Enterprise (2016 LTSB).

This OS version is heavily used in ATMs (cash machines) which will be used in the solution build by KAL on top of RHEL 8.

Comment 4 Daniel Schaefer 2019-08-06 09:30:52 UTC
Hi, what other info can I provide to help?

The formal certification is required because the solution build by KAL has to be PCI-DSS compliant (which requires formal supported configurations for all components).

Total addressable market is ~4mio ATM devices globally to sell RHEL to.

Comment 6 Daniel Schaefer 2019-10-23 07:48:57 UTC
Hi, what other info can I provide to progress this please?

Comment 7 Amnon Ilan 2019-11-15 13:06:59 UTC
(In reply to Daniel Schaefer from comment #6)
> Hi, what other info can I provide to progress this please?

It is not about other info. SVVP is for Windows Server versions, not for Windows Desktop versions and such
Hence this request is not applicable

Comment 8 Ademar Reis 2020-02-05 23:01:06 UTC
QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks

Comment 11 RHEL Program Management 2021-03-15 07:37:41 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.