public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: passt-dev@passt.top, Laine Stump <laine@redhat.com>
Subject: Re: [PATCH] qrap: Support JSON syntax for -device
Date: Mon, 24 Oct 2022 14:12:03 +0200	[thread overview]
Message-ID: <20221024141203.501fd33d@elisabeth> (raw)
In-Reply-To: <CABJz62OXASNfQbT4ot0a2SZAsD=EoEZN_Ca-7JjUcSNLZFnp3w@mail.gmail.com>

[Cc: Laine]

On Mon, 24 Oct 2022 03:08:47 -0700
Andrea Bolognani <abologna@redhat.com> wrote:

> On Sat, Oct 22, 2022 at 10:19:43AM +0200, Stefano Brivio wrote:
> > For context, qrap will finally become useless once this patchset by
> > Laurent:
> >   https://patchew.org/QEMU/20221021090922.170074-1-lvivier@redhat.com/
> >
> > lands in qemu -- that should happen soon.
> >
> > However, we'll need to keep it around for a little longer, until an
> > updated version of qemu reaches distributions, and, after that, still
> > give a bit of time to users  
> 
> In addition to QEMU, we also need libvirt to support passt natively.
> 
> I believe there's ongoing work for that as well,

Yes, I'm currently working on this topic with Laine (the patch in
contrib/libvirt is using the qemu interface I implemented in
contrib/qemu, which is not what we'll have in qemu eventually).

> but until that lands (and makes its way to distros) projects like
> KubeVirt are going to be relying on qrap.

Right, it probably makes no sense to force KubeVirt to adopt this in
two steps (passing qemu specific options first, and then switch to the
new configuration model in libvirt), so we'll need to wait for that as
well.

-- 
Stefano


      reply	other threads:[~2022-10-24 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20  9:04 [PATCH] qrap: Support JSON syntax for -device Andrea Bolognani
2022-10-22  8:19 ` Stefano Brivio
2022-10-24 10:08   ` Andrea Bolognani
2022-10-24 12:12     ` Stefano Brivio [this message]

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=20221024141203.501fd33d@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=abologna@redhat.com \
    --cc=laine@redhat.com \
    --cc=passt-dev@passt.top \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).