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.
Bug 1854218 - [VBS] Poor performance of Windows 10 OS when VBS with HVCI is enabled
Summary: [VBS] Poor performance of Windows 10 OS when VBS with HVCI is enabled
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virtio-win
Version: ---
Hardware: Unspecified
OS: Windows
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Marek Kedzierski
QA Contact: lijin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-06 19:16 UTC by Marek Kedzierski
Modified: 2020-09-23 00:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-06 15:51:52 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marek Kedzierski 2020-07-06 19:16:00 UTC 
Description of problem:

After enabling HVCI on Windows 10 OS (2004), the performance degradation can be observed.




Steps to Reproduce:

Enable HVCI according to requirements - https://docs.microsoft.com/en-us/windows/security/threat-protection/device-guard/enable-virtualization-based-protection-of-code-integrity

Actual results:

The system is running slowly

Expected results:

There should not be huge performance degradation.

Additional info:

Information from HVCI documentation:

"Because it makes use of Mode Based Execution Control, HVCI works better with Intel Kaby Lake or AMD Zen 2 CPUs and newer. Processors without MBEC will rely on an emulation of this feature, called Restricted User Mode, which has a bigger impact on performance."
Comment 3 lijin 2020-07-31 03:13:22 UTC 
Hi Merek,

How slow is the win10 vm?
I did not feel the poor performance after I enable HVCI on win10-64(2004).

btw, the poor performance is caused by virtio drivers? which driver cause it?(I load vioscsi and netkvm drivers)
Comment 4 Marek Kedzierski 2020-07-31 11:44:38 UTC 
(In reply to lijin from comment #3)
> Hi Merek,
> 
> How slow is the win10 vm?
> I did not feel the poor performance after I enable HVCI on win10-64(2004).

If you don't see that it's poor it is very good. I got another notfication
that's is not so bad. I need to check my setup then -- on my system serious 
lags can be observed.

> 
> btw, the poor performance is caused by virtio drivers? which driver cause
> it?(I load vioscsi and netkvm drivers)

This is not caused by virtio drivers. It is caused by nesting and by lack of
hardware suppport for MBEC. Microsoft mentions that:

'Because it (HVCI) makes use of Mode Based Execution Control, HVCI works better with 
Intel Kaby Lake or AMD Zen 2 CPUs and newer. Processors without MBEC will rely on an 
emulation of this feature, called Restricted User Mode, which has a bigger impact on 
performance.'

However the scale of the impact not shown in the figures.
Comment 5 lijin 2020-08-03 01:32:55 UTC 
(In reply to Marek Kedzierski from comment #4)
> (In reply to lijin from comment #3)
> > Hi Merek,
> > 
> > How slow is the win10 vm?
> > I did not feel the poor performance after I enable HVCI on win10-64(2004).
> 
> If you don't see that it's poor it is very good. I got another notfication
> that's is not so bad. I need to check my setup then -- on my system serious 
> lags can be observed.
> 
> > 
> > btw, the poor performance is caused by virtio drivers? which driver cause
> > it?(I load vioscsi and netkvm drivers)
> 
> This is not caused by virtio drivers. It is caused by nesting and by lack of
> hardware suppport for MBEC. Microsoft mentions that:


Could you help to move this bug to correct component if it's not caused by virtio drivers?

Thanks
Comment 6 Marek Kedzierski 2020-08-06 15:51:52 UTC 
The mentioned 'huge performance degradation' happens only on my system. 
On two other tested systems the performance was OK.

Microsoft oficially mentions that enabling HVCI may have an impact on performance of
the systems that don't have hardware support for MBEC. So the only thing we can do 
is to add note to our customers (with link to MS documentation) that enabling HVCI may have an impact on performance.
Note You need to log in before you can comment on or make changes to this bug.