[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC v1 0/2] VM fork detection for RNG
|
From: |
Jason A. Donenfeld |
|
Subject: |
Re: [PATCH RFC v1 0/2] VM fork detection for RNG |
|
Date: |
Thu, 24 Feb 2022 11:57:34 +0100 |
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
- Re: [PATCH RFC v1 1/2] random: add mechanism for VM forks to reinitialize crng, (continued)
[PATCH RFC v1 2/2] drivers/virt: add vmgenid driver for reinitializing RNG, Jason A. Donenfeld, 2022/02/23
Re: [PATCH RFC v1 0/2] VM fork detection for RNG, Jason A. Donenfeld, 2022/02/23
Re: [PATCH RFC v1 0/2] VM fork detection for RNG, Alexander Graf, 2022/02/24