From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Lz8t8-00045N-RF
	for qemu-devel@nongnu.org; Wed, 29 Apr 2009 08:27:46 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Lz8t2-00044v-L5
	for qemu-devel@nongnu.org; Wed, 29 Apr 2009 08:27:45 -0400
Received: from [199.232.76.173] (port=47237 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Lz8t2-00044s-Fd
	for qemu-devel@nongnu.org; Wed, 29 Apr 2009 08:27:40 -0400
Received: from www.seclab.tuwien.ac.at ([128.130.60.29]:52117
	helo=mail.seclab.tuwien.ac.at) by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <ck@iseclab.org>) id 1Lz8t2-0007Hc-4g
	for qemu-devel@nongnu.org; Wed, 29 Apr 2009 08:27:40 -0400
Received: from ckol.localnet (ckol.seclab.tuwien.ac.at [128.130.60.24])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.seclab.tuwien.ac.at (Postfix) with ESMTPSA id 107032FC5E
	for <qemu-devel@nongnu.org>; Wed, 29 Apr 2009 14:26:01 +0200 (CEST)
From: Clemens Kolbitsch <ck@iseclab.org>
Date: Wed, 29 Apr 2009 14:25:38 +0200
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200904291425.38631.ck@iseclab.org>
Subject: [Qemu-devel] Tap network reloading
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Hi list,

I am using Qemu (with kqemu and virtual tap device) in a system to analyze 
binaries. In this system, I have to start qemu very often with only very short 
periods (around 10-15 seconds) in between.

Although Qemu itself does not have problems with it, I *very* often (i.e. 9 
out of 10 times) see that the networking inside the guest is not accessible 
from the outside nor the other way around for some time when loading a 
snapshot.

So, when I start qemu, let it run for a few minutes, quit and restart Qemu and 
load a snapshot, I cannot ping the guest network nor can I access the host (or 
anything else for that matter) from inside the guest. After 1-2 minutes, 
suddenly networking starts working. All other (non network-related) things 
work fine right from the start.

I am running Qemu on a (Ubuntu) 2.6.28-11 linux host and a WinXP guest.
Maybe someone has experience with this and can help me, what would greatly be 
appreciated :-)

Clemens