All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Fabiano Rosas" <farosas@suse.de>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Cédric Le Goater" <clg@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Mauro Matteo Cascella" <mcascell@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>
Subject: Re: [PATCH] docs: outline some guidelines for security classification
Date: Mon, 20 Jul 2026 12:53:11 -0400	[thread overview]
Message-ID: <al5Sd4dqho4baw8h@x1.local> (raw)
In-Reply-To: <al5MVNaPRM6GUtLc@redhat.com>

On Mon, Jul 20, 2026 at 05:27:00PM +0100, Daniel P. Berrangé wrote:
> We should likely distinguish live migration from snapshots
> a little.
> 
> In live migration if loading aborts, we still have the source
> VM running fine.
> 
> With snapshots if you launch a new QEMU and restore from snapshot
> there was no source VM that's relevant.
> 
> With snapshots if you have a running QEMU and rollback to a
> snapshot (with loadvm), and QEMU crashes, you've lost your
> currently running QEMU.

Yes, it's a different case, but IMHO not different from triaging security
issues.

loadvm on top of live QEMU is almost saying, "quit this qemu, and start
that snapshot VM instead, without bothering re-starting another process,
because they have the same hardware layout".

So it's not the loadvm process that destroyed the "source QEMU", it's the
user decision.  That's the case with/without loadvm being successful.

Thanks,

-- 
Peter Xu



  reply	other threads:[~2026-07-20 16:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 10:59 [PATCH] docs: outline some guidelines for security classification Daniel P. Berrangé
2026-07-07 12:16 ` Thomas Huth
2026-07-07 12:20 ` Cédric Le Goater
2026-07-07 12:35 ` John Levon
2026-07-07 17:11   ` Daniel P. Berrangé
2026-07-07 12:43 ` Marc-André Lureau
2026-07-07 13:43   ` Michael S. Tsirkin
2026-07-07 16:35   ` Daniel P. Berrangé
2026-07-16 14:08     ` Fabiano Rosas
2026-07-16 15:27       ` Daniel P. Berrangé
2026-07-16 18:34         ` Fabiano Rosas
2026-07-17 15:19           ` Daniel P. Berrangé
2026-07-20 15:23             ` Fabiano Rosas
2026-07-20 15:38               ` Daniel P. Berrangé
2026-07-16 15:40       ` Peter Xu
2026-07-16 18:51         ` Fabiano Rosas
2026-07-16 19:56           ` Peter Xu
2026-07-17  0:21             ` Fabiano Rosas
2026-07-17 15:01               ` Peter Xu
2026-07-20 15:10       ` Daniel P. Berrangé
2026-07-20 16:14         ` Fabiano Rosas
2026-07-20 16:27           ` Daniel P. Berrangé
2026-07-20 16:53             ` Peter Xu [this message]
2026-07-07 16:28 ` Mauro Matteo Cascella
2026-07-07 16:29   ` Daniel P. Berrangé
2026-07-16 20:47 ` Michael S. Tsirkin

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=al5Sd4dqho4baw8h@x1.local \
    --to=peterx@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=clg@redhat.com \
    --cc=farosas@suse.de \
    --cc=marcandre.lureau@redhat.com \
    --cc=mcascell@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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.