From: Nicholas Sherlock <nick@nicksherlock.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] pci-passthrough: add section about ID overrides
Date: Fri, 28 Jan 2022 10:16:42 +0000 [thread overview]
Message-ID: <0100017ea02fea9d-077b36f9-0309-4931-a57c-f10deba1b77f-000000@email.amazonses.com> (raw)
In-Reply-To: <pci-id-override-docs@nicksherlock.com>
From: Nicholas Sherlock <n.sherlock@gmail.com>
Signed-off-by: Nicholas Sherlock <n.sherlock@gmail.com>
---
qm-pci-passthrough.adoc | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc
index edaa01f..fa6ba35 100644
--- a/qm-pci-passthrough.adoc
+++ b/qm-pci-passthrough.adoc
@@ -233,6 +233,24 @@ An example of PCIe passthrough with a GPU set to primary:
# qm set VMID -hostpci0 02:00,pcie=on,x-vga=on
----
+.PCI ID overrides
+
+You can override the PCI vendor ID, device ID, and subsystem IDs that will be
+seen by the guest. This is useful if your device is a variant with an ID that
+your guest's drivers don't recognize, but you want to force those drivers to be
+loaded anyway (e.g. if you know your device shares the same chipset as a
+supported variant).
+
+The available options are `vendor-id`, `device-id`, `sub-vendor-id`, and
+`sub-device-id`. You can set any or all of these to override your device's
+default IDs.
+
+For example:
+
+----
+# qm set VMID -hostpci0 02:00,device-id=0x10f6,sub-vendor-id=0x0000
+----
+
Other considerations
^^^^^^^^^^^^^^^^^^^^
--
2.35.0
next parent reply other threads:[~2022-01-28 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <pci-id-override-docs@nicksherlock.com>
2022-01-28 10:16 ` Nicholas Sherlock [this message]
2022-01-28 13:16 ` [pve-devel] applied: " Thomas Lamprecht
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=0100017ea02fea9d-077b36f9-0309-4931-a57c-f10deba1b77f-000000@email.amazonses.com \
--to=nick@nicksherlock.com \
--cc=pve-devel@lists.proxmox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox