All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 190131] VirtIO Windows Drivers doesn't support SecureBoot.
Date: Thu, 25 Jun 2020 11:38:31 +0000	[thread overview]
Message-ID: <bug-190131-28872-Hcpwgjyvck@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-190131-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=190131

heri16@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |heri16@gmail.com

--- Comment #1 from heri16@gmail.com ---
Any updates on this? I am also seeing the error during boot if SecureBoot via
OVMF is enabled.

According to MS new driver signing policy, Windows 10 1607 and newer versions
require the drivers to be signed via their Dev Portal. Cross-signed drivers,
will not load when Secure Boot is enabled in the BIOS. Fedora's virtio drivers
are cross-signed and therefore were not being loaded.

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/kernel-mode-code-signing-policy--windows-vista-and-later-

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2020-06-25 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12  7:50 [Bug 190131] New: VirtIO Windows Drivers doesn't support SecureBoot bugzilla-daemon
2020-06-25 11:38 ` bugzilla-daemon [this message]
2020-06-26 14:15 ` [Bug 190131] " bugzilla-daemon
2020-06-28 11:04 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-190131-28872-Hcpwgjyvck@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.