From: Peter Xu <peterx@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Fam Zheng" <famz@redhat.com>, "Kevin Wolf" <kwolf@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Eric Auger" <eric.auger@redhat.com>,
"Eric Blake" <eblake@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [RFC] monitor: turn on Out-Of-Band by default again
Date: Mon, 21 May 2018 18:41:47 +0800 [thread overview]
Message-ID: <20180521104147.GA17282@xz-mi> (raw)
In-Reply-To: <20180521085907.GE23090@redhat.com>
On Mon, May 21, 2018 at 09:59:07AM +0100, Daniel P. Berrangé wrote:
> On Mon, May 21, 2018 at 04:42:49PM +0800, Peter Xu wrote:
> > We turned Out-Of-Band feature of monitors off for 2.12 release. Now we
> > try to turn that on again.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > --
> > Now OOB should be okay with all known tests (except iotest qcow2, since
> > it is still broken on master), and AFAIK now we should also be okay with
> > ARM+Libvirt (not testsed, but Eric Auger helped to verify that before
> > the release). So I think it's now safe to turn OOB on again. Please
> > feel free to test this against any of existing testsuites to see whether
> > it'll still break any stuff. Thanks,
>
> Can you remind us what the problem was with ARM+Libvirt that this
> caused ?
Sure. The regression reported by Eric Auger is:
http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06231.html
The fix is:
https://patchwork.kernel.org/patch/10332289/
And the fix is in master already.
Regards,
--
Peter Xu
next prev parent reply other threads:[~2018-05-21 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 8:42 [Qemu-devel] [RFC] monitor: turn on Out-Of-Band by default again Peter Xu
2018-05-21 8:59 ` Daniel P. Berrangé
2018-05-21 10:41 ` Peter Xu [this message]
2018-05-21 14:13 ` Eric Blake
2018-05-22 3:39 ` Peter Xu
2018-05-24 7:08 ` Markus Armbruster
2018-05-24 7:34 ` Peter Xu
2018-05-29 19:00 ` Dr. David Alan Gilbert
2018-06-01 12:39 ` Stefan Hajnoczi
2018-05-22 18:40 ` John Snow
2018-05-30 8:04 ` Peter Xu
2018-05-30 12:10 ` Peter Xu
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=20180521104147.GA17282@xz-mi \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=eblake@redhat.com \
--cc=eric.auger@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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 NNTP newsgroup(s).