qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 1/1] RFC: net/slirp: link with libslirp


From: Marc-André Lureau
Subject: Re: [Qemu-devel] [PATCH 1/1] RFC: net/slirp: link with libslirp
Date: Mon, 11 Feb 2019 11:49:09 +0100

Hi

On Sun, Feb 10, 2019 at 10:37 PM Peter Maydell <address@hidden> wrote:
>
> On Fri, 8 Feb 2019 at 20:44, Marc-André Lureau
> <address@hidden> wrote:
> >
> > Once libslirp has received its first release, we can link with the
> > external libslirp library.
> >
> > The migration data should be compatible with current and older qemu
> > versions (same compatibility as today). See "slirp: add state
> > saving/loading" patch. However, the content should be treated as a
> > blob, as the format may change eventually in the future.
>
> Could you elaborate a bit on what you mean by "the format
> might change" ? It's not clear to me what libslirp's API/ABI
> guarantees are here to ensure that QEMU can retain cross-QEMU-version
> migration compatibility and that QEMU version X with libslirp
> version Y can migrate both to and from QEMU version X with
> libslirp version Z.

So far, the migration code should be 1:1 with existing qemu code. It's
tricky to tell the compatibility on existing code, but the saved
bitstream version_id is 4, and it can load some older versions (I am
not sure all the way down to original migration code).

QEMU bitstream version shouldn't be relevant here, as qemu will get
and provide a binary blob.

libslirp should aim at keeping compatibility with its own older
bitstreams. A newer version will fail to be read with a library that
doesn't support it.

Does that sound correct?

thanks



reply via email to

[Prev in Thread] Current Thread [Next in Thread]