From: John Levon <john.levon@nutanix.com>
To: Jag Raman <jag.raman@oracle.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Elena Ufimtseva <elena.ufimtseva@oracle.com>,
"clg@redhat.com" <clg@redhat.com>
Subject: Re: [PATCH] Mark Multi-Process QEMU as Orphaned
Date: Mon, 11 May 2026 17:25:54 +0100 [thread overview]
Message-ID: <agIDElJbbToE4jWj@lent> (raw)
In-Reply-To: <88BAE7FA-7DAB-4372-8710-C45E98178EBA@oracle.com>
On Mon, May 11, 2026 at 04:15:14PM +0000, Jag Raman wrote:
> > Confused by this comment, as we've discussed before several times that you were
> > going to migrate the testing across to vfio-user instead of the legacy protocol,
> > then remove the legacy protocol altogether.
>
> John, just to double-check, we want the functional test to use the vfio-user client
> and use the x-remote object as the remote server, is that correct?
-machine x-remote,vfio-user=on
I think, which is what uses vfio-user between the two qemu instead of the
MPQEMU_* messages etc, right?
Then we can at some point look at retiring the non-vfio-user implementation.
thanks
john
next prev parent reply other threads:[~2026-05-11 16:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 10:26 [PATCH] Mark Multi-Process QEMU as Orphaned John Levon
2026-05-08 10:31 ` Peter Maydell
2026-05-08 10:35 ` John Levon
2026-05-08 10:43 ` Peter Maydell
2026-05-08 10:48 ` Philippe Mathieu-Daudé
2026-05-08 14:21 ` Jag Raman
2026-05-08 14:28 ` John Levon
2026-05-08 14:33 ` Jag Raman
2026-05-08 14:37 ` John Levon
2026-05-08 15:07 ` Jagannathan Raman
2026-05-08 15:19 ` John Levon
2026-05-08 15:35 ` Jagannathan Raman
2026-05-08 16:07 ` John Levon
2026-05-21 8:24 ` Cédric Le Goater
2026-05-21 14:41 ` Jag Raman
2026-05-11 16:15 ` Jag Raman
2026-05-11 16:25 ` John Levon [this message]
2026-05-11 16:39 ` Jag Raman
2026-05-22 20:48 ` Jag Raman
2026-05-26 9:04 ` John Levon
2026-05-26 15:36 ` Jag Raman
2026-05-08 14:39 ` Peter Maydell
2026-05-08 15:05 ` Daniel P. Berrangé
2026-05-08 18:28 ` Paolo Bonzini
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=agIDElJbbToE4jWj@lent \
--to=john.levon@nutanix.com \
--cc=clg@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.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.