From: Clemens Kolbitsch <ck@iseclab.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Tap network reloading
Date: Wed, 29 Apr 2009 14:25:38 +0200 [thread overview]
Message-ID: <200904291425.38631.ck@iseclab.org> (raw)
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
reply other threads:[~2009-04-29 12:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200904291425.38631.ck@iseclab.org \
--to=ck@iseclab.org \
--cc=qemu-devel@nongnu.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).