All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "João Vilaça" <machadovilaca@gmail.com>
Cc: Kostiantyn Kostiuk <kkostiuk@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] qga: implement 'guest-get-nvidia-smi' command
Date: Wed, 1 Apr 2026 12:58:36 +0100	[thread overview]
Message-ID: <ac0IbJM3RFRt44Kx@redhat.com> (raw)
In-Reply-To: <CAPM7mp10RGfhV7hpnhDcvm_fj7Ks=ozK=2=MTew-4fKKmxq8pA@mail.gmail.com>

On Tue, Mar 31, 2026 at 02:07:27PM +0100, João Vilaça wrote:
> Monitoring, on the hypervisor side, of GPU workloads running in guests with
> NVIDIA GPU passthrough (VFIO) or vGPU (NVIDIA GRID).
> Operators who want GPU metrics from a fleet of VMs must either SSH into
> each guest or deploy a separate monitoring agent inside the guest itself
> (e.g. DCGM exporter).


IMHO, directly people to deploy an existing monmitoring agent solution
in the guest is likely the right thing todo.

We don't really want the QEMU guest agent expanding arbitrarily such
that it effectively re-invents what's already offered by general
purpose monitoring agents.

If the problem is that those existing monitoring agents need network
support, then IMHO the answer is likely to enhance the agent to use
vsock, rather than add more monitoring commands to QEMU.

With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|



  reply	other threads:[~2026-04-01 11:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 11:01 [PATCH] qga: implement 'guest-get-nvidia-smi' command João Vilaça
2026-03-31 12:57 ` Kostiantyn Kostiuk
2026-03-31 13:07   ` João Vilaça
2026-04-01 11:58     ` Daniel P. Berrangé [this message]
2026-04-01 11:25 ` Markus Armbruster
2026-04-01 11:50   ` Kostiantyn Kostiuk
2026-04-01 12:00     ` João Vilaça
2026-04-01 12:01     ` Daniel P. Berrangé

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=ac0IbJM3RFRt44Kx@redhat.com \
    --to=berrange@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=machadovilaca@gmail.com \
    --cc=qemu-devel@nongnu.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.