From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: NE2000 problem found
Date: Thu, 10 Jun 2004 01:17:44 +0200 [thread overview]
Message-ID: <40C79A98.10105@bellard.org> (raw)
In-Reply-To: <000b01c44e6c$dcdef410$0401a8c0@putte2k>
Mike Nordell wrote:
> Fabrice Bellard wrote:
>
>
>>Can you tell me exactly in which case you have problems with NE2000 ?
>
>
> Always? :-)
>
> On Windows 2000, running Windows 2000 sp4, -pci -cirrusvga.
>
> It's also the thing that it seems only about every second time networking
> "works", to the extent the guest actually gets a DHCP address. It seems the
> slirp code is indeed getting the request, and is offering an addr, but the
> response is not reaching the guest OS' IP-stack. Whether this is due to the
> guests driver not even getting the interrupt from the virtual NIC, the
> response frame is malformed or <whatever> I haven't yet been able to
> determine. I'm still in the process of adding better tracing, to be able to
> see what happens when.
>
> After adding the asic writeb I have observed it being written with 0x43
> (just a few times) and 0xff (more times), and only directly after "read
> addr=0x7 val=40". I haven't yet added tracing output of rcnt for writeb, and
> I don't know the significance of this, but I suspect it means something.
Interesting. This problem may really be liked to the WinXP security
problem I mentionned.
Fabrice.
next prev parent reply other threads:[~2004-06-09 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 21:58 [Qemu-devel] Re: NE2000 problem found Mike Nordell
2004-06-09 23:17 ` Fabrice Bellard [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 2:43 Mike Nordell
2004-06-10 5:21 Mike Nordell
2004-06-17 4:50 ` Leigh Dyer
2004-06-26 5:06 ` kazu
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=40C79A98.10105@bellard.org \
--to=fabrice@bellard.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).