From: Tim <tim-qemu@sentinelchicken.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] NE2K PCI and Windows 98SE & Cirrus Logic
Date: Sun, 6 Jun 2004 22:24:24 -0700 [thread overview]
Message-ID: <20040607052424.GD3296@sentinelchicken.org> (raw)
In-Reply-To: <1086584098.887.18.camel@shawn.local>
> I don't unfortunately have any work-around for the network problems.
> I've also tried a manual network setup using the tun/tap device, but it
> doesn't work any better.
For the most part, network has been working fine for me. I have used
the linux bridging module, across a real ethernet device and tun0, and
it worked ok. I am now routing across my host OS (which I have done
before), and it is also working ok. However, I have noticed that from
time to time my pings time out. Typically the first one or two pings
when I ping a given host. After that, it usually works fine for
subsequent pings, though sometimes re-surfaces. Could it be a timing
issue with the virtual device? Probably not the problems you are
experiencing Hetz, though worth mentioning.
I am using the most recent CVS (at least, as of this afternoon), and the
following command line:
qemu -pci -m 256 -cdrom win2k-install-cd.img -hda win2k-cow.img -boot c -n "$TUN_SCRIPT"
with the contents of $TUN_SCRIPT being:
sudo ifconfig tun0 192.168.19.1 netmask 255.255.255.0 broadcast 192.168.19.255
sudo sh -c 'echo 1 > /proc/sys/net/ipv4/ip_forward'
I am quite impressed with the momentum this project has had thus far. I
tell all of my friends about it. Keep up the good work!
tim
next prev parent reply other threads:[~2004-06-07 5:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 22:49 [Qemu-devel] NE2K PCI and Windows 98SE & Cirrus Logic Hetz Ben Hamo
2004-06-07 4:54 ` Leigh Dyer
2004-06-07 5:24 ` Tim [this message]
2004-06-07 5:27 ` Tim
2004-06-07 5:37 ` Leigh Dyer
2004-06-07 6:28 ` Tim
2004-06-07 6:34 ` Leigh Dyer
2004-06-07 10:14 ` Antony T Curtis
2004-06-07 20:12 ` [Qemu-devel] " Fabrice Bellard
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=20040607052424.GD3296@sentinelchicken.org \
--to=tim-qemu@sentinelchicken.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.