all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Yao Xu <xy2462381442@gmail.com>
To: pve-devel@lists.proxmox.com
Cc: Yao Xu <Xy2462381442@gmail.com>
Subject: [PATCH pve-docs 2/2] qm: pci passthrough: name the function in the GPU example
Date: Mon, 24 Aug 2026 19:08:28 +0200	[thread overview]
Message-ID: <20260824170828.42821-3-Xy2462381442@gmail.com> (raw)
In-Reply-To: <20260824170828.42821-1-Xy2462381442@gmail.com>

The example pairs a PCIe port with the shortened all-functions form,
which is the case the note above warns about: QEMU adds AtomicOp
completer support to the virtual root port only for a single-function
device, so a guest driver that asks for AtomicOps finds none. A GPU is
the most likely device to ask.

What the example demonstrates is x-vga and pcie, not the shortened
syntax, so naming the function changes nothing else about it.

Signed-off-by: Yao Xu <Xy2462381442@gmail.com>
---
 qm-pci-passthrough.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc
index 850ba40..b95de06 100644
--- a/qm-pci-passthrough.adoc
+++ b/qm-pci-passthrough.adoc
@@ -374,7 +374,7 @@ This is a relative path under */usr/share/kvm/*.
 An example of PCIe passthrough with a GPU set to primary:
 
 ----
-# qm set VMID -hostpci0 02:00,pcie=on,x-vga=on
+# qm set VMID -hostpci0 02:00.0,pcie=on,x-vga=on
 ----
 
 .PCI ID overrides
-- 
2.50.1 (Apple Git-155)




  parent reply	other threads:[~2026-08-25  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 17:08 [PATCH pve-docs 0/2] qm: pci passthrough: the AtomicOps caveat of the all-functions form Yao Xu
2026-08-24 17:08 ` [PATCH pve-docs 1/2] qm: pci passthrough: note the AtomicOps caveat of " Yao Xu
2026-08-24 17:08 ` Yao Xu [this message]
2026-08-25 13:16 ` [PATCH pve-docs 0/2] qm: pci passthrough: the AtomicOps caveat of the " Dominik Csapak
     [not found]   ` <CANzZxgda3RsuakrK2wmDH3ez-hbby3qNte+qkfixipSrWoBzaQ@mail.gmail.com>
2026-08-25 14:09     ` Dominik Csapak

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=20260824170828.42821-3-Xy2462381442@gmail.com \
    --to=xy2462381442@gmail.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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal