From: Thomas Huth <thuth@redhat.com>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] slirp: Fix migration from older versions of QEMU to the current one
Date: Fri, 1 Apr 2016 10:00:40 +0200 [thread overview]
Message-ID: <56FE2AA8.6070801@redhat.com> (raw)
In-Reply-To: <20160331222221.GO2749@var.home>
On 01.04.2016 00:22, Samuel Thibault wrote:
> Samuel Thibault, on Fri 01 Apr 2016 00:00:43 +0200, wrote:
>> Just realizing... We'd need to add AF_INET6 cases here too, to be able
>> to save/restore a VM using ipv6 connections.
>
> That seems quite involved however, maybe we should postpone that to
> later?
I think it's ok to do it later. The code there is only invoked when the
user specified the "guestfwd=..." option, so that's likely rather a rare
case, I think, which could be postponed to QEMU 2.7.
Thomas
prev parent reply other threads:[~2016-04-01 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 14:48 [Qemu-devel] [PATCH] slirp: Fix migration from older versions of QEMU to the current one Thomas Huth
2016-03-31 22:00 ` Samuel Thibault
2016-03-31 22:22 ` Samuel Thibault
2016-04-01 8:00 ` Thomas Huth [this message]
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=56FE2AA8.6070801@redhat.com \
--to=thuth@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).