From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: samuel.thibault@ens-lyon.org, jan.kiszka@siemens.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] SLIRP migration?
Date: Wed, 28 Sep 2016 19:00:45 +0100 [thread overview]
Message-ID: <20160928180044.GK2034@work-vm> (raw)
Hi Samuel, Jan,
I'd like to convert SLIRPs migration code to VMState
and avoid all the qemu_put_/qemu_get_'s - but first I'd like to understand
when a lot of the slirp migration code makes sense.
I can see that migrating a VM with slirp makes sense (actually more
commonly saving a VM with slirp to a file); but when that happens
aren't you likely to lose all the network connections anyway?
If that's the case then why bother saving all the TCP state?
Under what circumstances do the network connections survive and
how can I test that?
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next reply other threads:[~2016-09-28 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 18:00 Dr. David Alan Gilbert [this message]
2016-09-28 18:04 ` [Qemu-devel] SLIRP migration? Jan Kiszka
2016-09-28 18:43 ` Dr. David Alan Gilbert
2016-09-28 22:14 ` Samuel Thibault
2016-09-29 9:05 ` Dr. David Alan Gilbert
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=20160928180044.GK2034@work-vm \
--to=dgilbert@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).