Page MenuHomeFreeBSD

bhyve/virtio: add config option to change the subvendor
AbandonedPublic

Authored by corvink on Sep 5 2022, 8:25 AM.
Tags
Referenced Files
Unknown Object (File)
Dec 20 2023, 6:16 AM
Unknown Object (File)
Dec 10 2023, 8:03 PM
Unknown Object (File)
Nov 8 2023, 8:49 AM
Unknown Object (File)
Nov 6 2023, 8:47 AM
Unknown Object (File)
Oct 10 2023, 5:37 PM
Unknown Object (File)
Oct 5 2023, 7:47 AM
Unknown Object (File)
Sep 6 2023, 6:14 AM
Unknown Object (File)
Aug 14 2023, 9:34 PM

Details

Reviewers
jhb
markj
Group Reviewers
bhyve
Summary

A Windows VM with secure boot only accepts Windows signed driver. So, it
doesn't accept the widely used VirtIO driver from Red Hat. The VM only
accepts the VritIO driver from Oracle. Instead of setting the subvendor
id of each VirtIO device separately, create a single config option to
change it.

The use case for secure boot is Windows 11. It requires secure boot.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Can we have a universal PCI vendor/subvendor setting for all PCI devices instead of for particular PCI devices? other pci devices may want to change the ID/subID too. For example, if I want to fake the NVMe controller as an Intel one.

Thought of this approach too but it's harder for the user to patch all virtio device properly than setting a single flag.

Maybe some bhyve maintainer could give some feedback.

The VM only accepts the VritIO driver from Oracle

official virtio-win-0.1.221-1 not work?

The VM only accepts the VritIO driver from Oracle

official virtio-win-0.1.221-1 not work?

I've tested virtio-win-0.1.185-2 which doesn't work but virtio-win-0.1.221-1 works. Thanks for the hint.