-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.5
-
None
-
Server 2025 need to be certified with VBS enabled and IOMMU (DeviceGuard)
-
-
rhel-sst-virtualization-hwe
-
ssg_virtualization
-
False
-
Description
In order to pass SVVP certification of Server 2025 we need to make the system to be functional with VBS enabled and IOMMU enabled (DeviceGuard compatibility)
[VBS - virtualization based security]
Unfortunately on several tried hosts the Server 2025 is not able to boot when VBS is enabled on the guest and IOMMU is enabled
This issue is just common point to the entire problem, please open separate issue for each new CPU model when needed and place a link here. In the CPU-specific issues please attach /proc/cpuinfo, exact command line, machine name (for further investigation)
For CPU(s) where VBS with IOMMU works please make a comment with reference exact command, /proc/cpuinfo and machine name.
What SSTs and Layered Product teams should review this?
- blocks
-
RHEL-30840 Windows 11 VM with VBS enabled crashes on different CPUs
- Planning
-
RHEL-56835 Support Windows Server 2025
- Closed
- is depended on by
-
RHEL-17930 [virtio-win] Ensure that the drivers are operating correctly with DMAGuardCompatible requirement
- In Progress
- is duplicated by
-
RHEL-50779 can't enable VBS on AMD EPYC 7301 and AMD EPYC 7413
- Closed
- relates to
-
RHEL-26340 [RFE] Windows VBS can not be enabled properly on Win11
- New
-
RHEL-17930 [virtio-win] Ensure that the drivers are operating correctly with DMAGuardCompatible requirement
- In Progress
-
RHEL-50779 can't enable VBS on AMD EPYC 7301 and AMD EPYC 7413
- Closed