From: Elefterios Stamatogiannakis <estama@dblab.ece.ntua.gr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Status of user-mode networking for win32
Date: Mon, 07 Jun 2004 18:00:28 +0300 [thread overview]
Message-ID: <40C4830C.7070908@dblab.ece.ntua.gr> (raw)
In-Reply-To: <20040607144551.GB10410@cs.unibo.it>
Mmmmmm.
If i understand correctly ne2000 links the guest with the host.
This connection works for me because i can get a dhcp lease from the
qemu-slirp throught ne2000.
I can also ping the dhcp server.
My problem is with the host -> internet connection from what i can
understand.
Qemu doesn't seem to open a "real" socket with the outside world at all.
Also all the above are using win2k as a host with linux as a guest.
teris.
Renzo Davoli wrote:
> On Mon, Jun 07, 2004 at 05:01:35PM +0300, Elefterios Stamatogiannakis wrote:
>
>> The problem is that it doesn't seem to connect to the outside world.
>
> I have seen with a packet sniffer that the packet payload was 16 bits
> misaligned.
>
> I have tried the workaround here included as a patch and
> Win98+vdeqemu pci works.
>
> I am trying to figure out if this is a correct patch or it is the
> writel/readl call parameter to be wrong. (word sized transfers should be
> aligned...)
>
> renzo
> ---------------
> --- hw/ne2000.c.orig 2004-06-07 16:14:28.000000000 +0200
> +++ hw/ne2000.c 2004-06-07 16:27:14.000000000 +0200
> @@ -401,7 +401,8 @@
> static inline void ne2000_mem_writel(NE2000State *s, uint32_t addr,
> uint32_t val)
> {
> - addr &= ~3; /* XXX: check exact behaviour if not even */
> + /*addr &= ~3; XXX: check exact behaviour if not even */
> + addr &= ~1; /* XXX: check exact behaviour if not even */
> if (addr < 32 ||
> (addr >= NE2000_PMEM_START && addr < NE2000_MEM_SIZE)) {
> *(uint32_t *)(s->mem + addr) = cpu_to_le32(val);
> @@ -431,7 +432,8 @@
>
> static inline uint32_t ne2000_mem_readl(NE2000State *s, uint32_t addr)
> {
> - addr &= ~3; /* XXX: check exact behaviour if not even */
> + /*addr &= ~3; XXX: check exact behaviour if not even */
> + addr &= ~1; /* XXX: check exact behaviour if not even */
> if (addr < 32 ||
> (addr >= NE2000_PMEM_START && addr < NE2000_MEM_SIZE)) {
> return le32_to_cpu(*(uint32_t *)(s->mem + addr));
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-06-07 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 13:28 [Qemu-devel] Summary of problems with Mandrake 10 Jean-Michel POURE
2004-06-07 14:01 ` [Qemu-devel] Status of user-mode networking for win32 Elefterios Stamatogiannakis
2004-06-07 14:07 ` [Qemu-devel] Using QEMU-fast Sander Nagtegaal
2004-06-07 15:50 ` Pavel Janík
2004-06-07 14:45 ` [Qemu-devel] Status of user-mode networking for win32 Renzo Davoli
2004-06-07 14:57 ` [Qemu-devel] CVS repository?? Ishwar Rattan
2004-06-07 15:48 ` Pavel Janík
2004-06-07 20:16 ` vaise
2004-06-07 15:00 ` Elefterios Stamatogiannakis [this message]
2004-06-07 17:14 ` [Qemu-devel] Status of user-mode networking for win32 Renzo Davoli
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=40C4830C.7070908@dblab.ece.ntua.gr \
--to=estama@dblab.ece.ntua.gr \
--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).