From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"KVM list" <kvm@vger.kernel.org>,
linux-s390@vger.kernel.org, adrian@parity.io, "Woodhouse,
David" <dwmw@amazon.co.uk>,
"Catangiu, Adrian Costin" <acatan@amazon.com>,
graf@amazon.com, "Colm MacCarthaigh" <colmmacc@amazon.com>,
"Singh, Balbir" <sblbir@amazon.com>,
"Weiss, Radu" <raduweis@amazon.com>,
"Jann Horn" <jannh@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
"Igor Mammedov" <imammedo@redhat.com>,
ehabkost@redhat.com, ben@skyportsystems.com,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [PATCH RFC v1 0/2] VM fork detection for RNG
Date: Fri, 25 Feb 2022 05:40:21 -0500 [thread overview]
Message-ID: <20220225053937-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHmME9qRrLHwOjD+_xkGC7-BMVdzO95=DzhCo8KvDNa0JXVybA@mail.gmail.com>
On Thu, Feb 24, 2022 at 11:57:34AM +0100, Jason A. Donenfeld wrote:
> On Thu, Feb 24, 2022 at 11:56 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
> > IIRC this part of the QEMU doc was making an implicit assumption
> > about the way QEMU is to be used by mgmt apps doing snapshots.
> >
> > Instead of using the 'loadvm' command on the existing running QEMU
> > process, the doc seems to tacitly expect the management app will
> > throwaway the existing QEMU process and spawn a brand new QEMU
> > process to load the snapshot into, thus getting the new GUID on
> > the QEMU command line.
>
> Right, exactly. The "there are no known use cases" bit I think just
> forgot about one very common use case that perhaps just wasn't in use
> by the original author. So I'm pretty sure this remains a QEMU bug.
>
> Jason
Quite possibly yes.
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-s390@vger.kernel.org,
"Daniel P. Berrangé" <berrange@redhat.com>,
adrian@parity.io, "KVM list" <kvm@vger.kernel.org>,
"Jann Horn" <jannh@google.com>,
"Singh, Balbir" <sblbir@amazon.com>,
ben@skyportsystems.com, "Weiss, Radu" <raduweis@amazon.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Richard W.M. Jones" <rjones@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"Catangiu, Adrian Costin" <acatan@amazon.com>,
graf@amazon.com,
"Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
"Colm MacCarthaigh" <colmmacc@amazon.com>,
"Laszlo Ersek" <lersek@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
ehabkost@redhat.com
Subject: Re: [PATCH RFC v1 0/2] VM fork detection for RNG
Date: Fri, 25 Feb 2022 05:40:21 -0500 [thread overview]
Message-ID: <20220225053937-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHmME9qRrLHwOjD+_xkGC7-BMVdzO95=DzhCo8KvDNa0JXVybA@mail.gmail.com>
On Thu, Feb 24, 2022 at 11:57:34AM +0100, Jason A. Donenfeld wrote:
> On Thu, Feb 24, 2022 at 11:56 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
> > IIRC this part of the QEMU doc was making an implicit assumption
> > about the way QEMU is to be used by mgmt apps doing snapshots.
> >
> > Instead of using the 'loadvm' command on the existing running QEMU
> > process, the doc seems to tacitly expect the management app will
> > throwaway the existing QEMU process and spawn a brand new QEMU
> > process to load the snapshot into, thus getting the new GUID on
> > the QEMU command line.
>
> Right, exactly. The "there are no known use cases" bit I think just
> forgot about one very common use case that perhaps just wasn't in use
> by the original author. So I'm pretty sure this remains a QEMU bug.
>
> Jason
Quite possibly yes.
--
MST
next prev parent reply other threads:[~2022-02-25 10:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 13:12 [PATCH RFC v1 0/2] VM fork detection for RNG Jason A. Donenfeld
2022-02-23 13:12 ` Jason A. Donenfeld
2022-02-23 13:12 ` [PATCH RFC v1 1/2] random: add mechanism for VM forks to reinitialize crng Jason A. Donenfeld
2022-02-23 13:12 ` Jason A. Donenfeld
2022-02-23 23:16 ` Eric Biggers
2022-02-23 23:16 ` Eric Biggers
2022-02-24 0:54 ` Jason A. Donenfeld
2022-02-24 0:54 ` Jason A. Donenfeld
2022-02-24 1:27 ` Eric Biggers
2022-02-24 1:27 ` Eric Biggers
2022-02-24 11:15 ` Jason A. Donenfeld
2022-02-24 11:15 ` Jason A. Donenfeld
2022-02-23 13:12 ` [PATCH RFC v1 2/2] drivers/virt: add vmgenid driver for reinitializing RNG Jason A. Donenfeld
2022-02-23 13:12 ` Jason A. Donenfeld
2022-02-23 16:36 ` Jason A. Donenfeld
2022-02-23 16:36 ` Jason A. Donenfeld
2022-02-23 16:08 ` [PATCH RFC v1 0/2] VM fork detection for RNG Jason A. Donenfeld
2022-02-23 16:08 ` Jason A. Donenfeld
2022-02-23 16:19 ` Jason A. Donenfeld
2022-02-23 16:19 ` Jason A. Donenfeld
2022-02-24 8:22 ` Laszlo Ersek
2022-02-24 10:43 ` Jason A. Donenfeld
2022-02-24 10:43 ` Jason A. Donenfeld
2022-02-24 10:55 ` Daniel P. Berrangé
2022-02-24 10:55 ` Daniel P. Berrangé
2022-02-24 10:57 ` Jason A. Donenfeld
2022-02-24 10:57 ` Jason A. Donenfeld
2022-02-25 10:40 ` Michael S. Tsirkin [this message]
2022-02-25 10:40 ` Michael S. Tsirkin
2022-02-24 8:53 ` Alexander Graf
2022-02-24 10:43 ` Daniel P. Berrangé
2022-02-24 10:43 ` Daniel P. Berrangé
2022-02-24 11:35 ` Alexander Graf
2022-02-24 10:53 ` Jason A. Donenfeld
2022-02-24 10:53 ` Jason A. Donenfeld
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=20220225053937-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Jason@zx2c4.com \
--cc=acatan@amazon.com \
--cc=adrian@parity.io \
--cc=ben@skyportsystems.com \
--cc=berrange@redhat.com \
--cc=colmmacc@amazon.com \
--cc=dwmw@amazon.co.uk \
--cc=ehabkost@redhat.com \
--cc=graf@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=imammedo@redhat.com \
--cc=jannh@google.com \
--cc=kvm@vger.kernel.org \
--cc=lersek@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=raduweis@amazon.com \
--cc=rjones@redhat.com \
--cc=sblbir@amazon.com \
--cc=tytso@mit.edu \
/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.