From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49447) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpJA9-0000Ef-C1 for qemu-devel@nongnu.org; Wed, 28 Sep 2016 14:00:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bpJA3-0002F5-JA for qemu-devel@nongnu.org; Wed, 28 Sep 2016 14:00:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37698) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpJA3-0002Ev-De for qemu-devel@nongnu.org; Wed, 28 Sep 2016 14:00:51 -0400 Date: Wed, 28 Sep 2016 19:00:45 +0100 From: "Dr. David Alan Gilbert" Message-ID: <20160928180044.GK2034@work-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] SLIRP migration? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: samuel.thibault@ens-lyon.org, jan.kiszka@siemens.com Cc: qemu-devel@nongnu.org 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