From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Anthony PERARD <anthony.perard@vates.tech>,
Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH] Revert tools/python part of "tools: remove support for running a guest with qemu-traditional"
Date: Tue, 3 Jun 2025 12:46:36 +0200 [thread overview]
Message-ID: <aD7SjAXPrDDPaCAu@mail-itl> (raw)
In-Reply-To: <ae5a5de4-22ce-443b-a88d-16b89b28ac11@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On Mon, Jun 02, 2025 at 12:31:59PM +0100, Andrew Cooper wrote:
> On 02/06/2025 12:27 pm, Marek Marczykowski-Górecki wrote:
> > On Mon, Jun 02, 2025 at 12:22:53PM +0100, Andrew Cooper wrote:
> >> The migration stream is a stable ABI. What this does is break the ability to
> >> inspection and operate on pre-Xen-4.21 streams.
> > Do you mean Xen 4.21 should be able to accept migration of a domU with
> > qemu trad? I don't think it's a desirable feature...
>
> xl is free to reject a qemu-trad stream if it wants.
>
> What's not ok is verify-stream-v2 exploding with "unknown emulator 1"
> when I ask it to tell me what the bytes in this stream mean.
I see, in that case:
Acked-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-06-03 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 11:22 [PATCH] Revert tools/python part of "tools: remove support for running a guest with qemu-traditional" Andrew Cooper
2025-06-02 11:27 ` Marek Marczykowski-Górecki
2025-06-02 11:31 ` Andrew Cooper
2025-06-03 10:46 ` Marek Marczykowski-Górecki [this message]
2025-06-02 12:02 ` Anthony PERARD
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=aD7SjAXPrDDPaCAu@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jgross@suse.com \
--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.