From: Anthony PERARD <anthony.perard@citrix.com>
To: Ian Jackson <iwj@xenproject.org>
Cc: Jan Beulich <jbeulich@suse.com>, Olaf Hering <olaf@aepfle.de>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"George Dunlap" <george.dunlap@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Julien Grall <julien@xen.org>
Subject: Re: QEMU 6.0+ in 4.15 and 4.14 (Re: preparations for 4.15.1 and 4.13.4)
Date: Fri, 27 Aug 2021 13:39:28 +0100 [thread overview]
Message-ID: <YSjdAC98JqOXj5pn@perard> (raw)
In-Reply-To: <24862.34174.101215.640300@mariner.uk.xensource.com>
On Thu, Aug 19, 2021 at 05:23:26PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("Re: preparations for 4.15.1 and 4.13.4"):
> > Can we backport support of QEMU 6.0 to Xen 4.15? I'm pretty sure
> > distributions are going to want to use the latest QEMU and latest Xen,
> > without needed to build two different QEMU binaries.
>
> I think this is appropriate. Xen 4.15 is still now, and there was an
> unfortunate interaction between release dates. Your argument makes
> sense.
>
> > [XEN PATCH v2 0/8] Fix libxl with QEMU 6.0 + remove some more deprecated usages.
> > <20210511092810.13759-1-anthony.perard@citrix.com>
> > Commits: d5f54009db^..fe6630ddc4
> >
> > Some more QEMU 6.0 fixes
> > <20210628100157.5010-1-anthony.perard@citrix.com>
> > Commits: 217eef30f7 3bc3be978f
>
> So I have queued all these.
>
> > Also, Olaf want them to be backported to 4.14, see
> > <20210629095952.7b0b94c1.olaf@aepfle.de>
>
> I'm unsure about this. The diff seems moderately large. Also, are we
> sure that it wouldn't break anything other than very old qemu ? OTOH
> compat problems with newer qemu are indeed a problem especially for
> distros.
I've check all commits, beside two commits they all have a fallback
mechanism so we still are compatible with old qemus.
There is these two commits
libxl: Fix QEMU cmdline for scsi device
libxl: Use -device for cd-rom drives
which replace command line arguments, but it is to use something that
has been available since QEMU 0.15, so before the first version that
libxl as evert supported.
So overall, I don't think we break compatibility with very old qemus. It
would take a couple more QMP command to run some feature as libxl would
try the new command first before falling back to previous ones.
> I'm currently leaning towards "no" but I am very open to being
> convinced this is a good idea.
I don't know if it is a good idea, but at least it doesn't seems to be a
bad one.
--
Anthony PERARD
next prev parent reply other threads:[~2021-08-27 12:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 14:29 [PATCH-4.15] tools/libs/ctrl: fix xc_core_arch_map_p2m() to support linear p2m table Juergen Gross
2021-07-16 6:47 ` Juergen Gross
2021-07-15 7:58 ` preparations for 4.15.1 and 4.13.4 Jan Beulich
2021-07-15 8:02 ` Jan Beulich
2021-07-15 9:02 ` Anthony PERARD
2021-08-19 16:23 ` QEMU 6.0+ in 4.15 and 4.14 (Re: preparations for 4.15.1 and 4.13.4) Ian Jackson
2021-08-23 9:48 ` Olaf Hering
2021-08-27 12:39 ` Anthony PERARD [this message]
2021-07-15 10:58 ` preparations for 4.15.1 and 4.13.4 Andrew Cooper
2021-07-15 11:12 ` Jan Beulich
2021-07-15 14:11 ` Olaf Hering
2021-07-15 14:21 ` Jan Beulich
2021-08-19 16:46 ` Ian Jackson
2021-08-23 8:42 ` Olaf Hering
2021-07-15 17:16 ` Andrew Cooper
2021-07-16 6:16 ` Jan Beulich
2021-08-19 16:43 ` preparations for 4.15.1 and 4.13.4 [and 1 more messages] Ian Jackson
2021-08-19 16:55 ` Ian Jackson
2021-08-19 17:04 ` Ian Jackson
2021-08-19 16:56 ` Andrew Cooper
2021-08-20 6:10 ` Jan Beulich
2021-07-16 7:41 ` preparations for 4.15.1 and 4.13.4 Julien Grall
2021-07-16 20:16 ` Stefano Stabellini
2021-07-19 10:32 ` Jan Beulich
2021-08-19 16:49 ` Ian Jackson
2021-08-19 15:44 ` preparations for 4.15.1 and 4.13.4 support linear p2m table [and 1 more messages] Ian Jackson
2021-08-19 7:45 ` [PATCH-4.15] tools/libs/ctrl: fix xc_core_arch_map_p2m() to support linear p2m table Juergen Gross
2021-08-19 16:11 ` Ian Jackson
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=YSjdAC98JqOXj5pn@perard \
--to=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=olaf@aepfle.de \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.