From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: [pve-devel] applied: [PATCH qemu-server v2 1/2] automatically add 'uuid' parameter when passing through NVIDIA vGPU
Date: Fri, 12 Aug 2022 14:04:16 +0200 [thread overview]
Message-ID: <20220812120416.ohc77kflckpbxedq@casey.proxmox.com> (raw)
In-Reply-To: <20220812092951.2053040-3-d.csapak@proxmox.com>
applied this one, left out patch 2 after some off-list discussion
On Fri, Aug 12, 2022 at 11:29:49AM +0200, Dominik Csapak wrote:
> When passing through an NVIDIA vGPU via mediated devices, their
> software needs the qemu process to have the 'uuid' parameter set to the
> one of the vGPU. Since it's currently not possible to pass through multiple
> vGPUs to one VM (seems to be an NVIDIA driver limitation at the moment),
> we don't have to take care about that.
>
> Sadly, the place we do this, it does not show up in 'qm showcmd' as we
> don't (want to) query the pci devices in that case, and then we don't
> have a way of knowing if it's an NVIDIA card or not. But since this
> is informational with QEMU anyway, i'd say we can ignore that.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> PVE/QemuServer.pm | 9 ++++++++-
> PVE/QemuServer/PCI.pm | 4 +++-
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index 7d9cf22..c706653 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -5594,12 +5594,19 @@ sub vm_start_nolock {
> PVE::QemuServer::PCI::reserve_pci_usage($pci_id_list, $vmid, $start_timeout);
>
> eval {
> + my $uuid;
> for my $id (sort keys %$pci_devices) {
> my $d = $pci_devices->{$id};
> for my $dev ($d->{pciid}->@*) {
> - PVE::QemuServer::PCI::prepare_pci_device($vmid, $dev->{id}, $id, $d->{mdev});
> + my $info = PVE::QemuServer::PCI::prepare_pci_device($vmid, $dev->{id}, $id, $d->{mdev});
> +
> + # nvidia grid needs the uuid of the mdev as qemu parameter
> + if ($d->{mdev} && !defined($uuid) && $info->{vendor} eq '10de') {
> + $uuid = PVE::QemuServer::PCI::generate_mdev_uuid($vmid, $id);
> + }
> }
> }
> + push @$cmd, '-uuid', $uuid if defined($uuid);
> };
> if (my $err = $@) {
> eval { PVE::QemuServer::PCI::remove_pci_reservation($pci_id_list) };
> diff --git a/PVE/QemuServer/PCI.pm b/PVE/QemuServer/PCI.pm
> index 23fe508..3d0e70e 100644
> --- a/PVE/QemuServer/PCI.pm
> +++ b/PVE/QemuServer/PCI.pm
> @@ -253,7 +253,7 @@ sub get_pci_addr_map {
> return $pci_addr_map;
> }
>
> -my sub generate_mdev_uuid {
> +sub generate_mdev_uuid {
> my ($vmid, $index) = @_;
> return sprintf("%08d-0000-0000-0000-%012d", $index, $vmid);
> }
> @@ -514,6 +514,8 @@ sub prepare_pci_device {
> die "can't reset PCI device '$pciid'\n"
> if $info->{has_fl_reset} && !PVE::SysFSTools::pci_dev_reset($info);
> }
> +
> + return $info;
> }
>
> my $RUNDIR = '/run/qemu-server';
> --
> 2.30.2
next prev parent reply other threads:[~2022-08-12 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 9:29 [pve-devel] [PATCH common/qemu-server/manager v2] improve vGPU (mdev) usage for NVIDIA Dominik Csapak
2022-08-12 9:29 ` [pve-devel] [PATCH common v2 1/1] SysFSTools: get name from mediated device types Dominik Csapak
2022-08-12 12:02 ` [pve-devel] applied: " Wolfgang Bumiller
2022-08-12 9:29 ` [pve-devel] [PATCH qemu-server v2 1/2] automatically add 'uuid' parameter when passing through NVIDIA vGPU Dominik Csapak
2022-08-12 12:04 ` Wolfgang Bumiller [this message]
2022-08-16 22:57 ` [pve-devel] applied: " DERUMIER, Alexandre
2022-08-12 9:29 ` [pve-devel] [PATCH qemu-server v2 2/2] cleanup pci devices in more situations Dominik Csapak
2022-08-12 9:29 ` [pve-devel] [PATCH manager v2 1/1] ui: improve form/MDevSelector Dominik Csapak
2022-08-12 12:07 ` [pve-devel] applied: " Wolfgang Bumiller
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=20220812120416.ohc77kflckpbxedq@casey.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=d.csapak@proxmox.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