From: "Mike Nordell" <tamlin@algonet.se>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Status of user-mode networking for win32
Date: Mon, 7 Jun 2004 22:07:56 +0200 [thread overview]
Message-ID: <000401c44ccb$24e25020$0401a8c0@putte2k> (raw)
I wrote:
> I vote to commit the patch for ne2000, aligning on 16-bit, not 32-bit.
>
> It made (among other things) "ipconfig /renew" work in Windows 2000 guest,
> on Windows 2000 host.
Seems I opened my mouth too early. With this patch in place, it seems that
every second time I boot the Windows 2000 guest in QEMU I get a somewhat
working connection between slirp and the guest OS (I've been able to ICMP
ping the host, using it's real IP interface, but ping-ing other hosts on the
net does not work(*)). The other times it just won't talk to it as it should
(even that I do get slirp debug output).
If it works the same or not without the patch I haven't yet tested. Maybe
it's better with it, maybe not - I just wanted to retract my absolute
support of the patch ASAP until I've been able to reasearch the problem
further.
(*) I believe the largest part of the problem is that slirp is so far only
aware of errno. In Win32, since the C runtime library is just that, a
library, while on POSIX I believe it's an integral part of the environment,
no e.g. socket errors propagate to errno - and things go south. As an
example I can mention a recvfrom() (on a UDP socket, obviously) that fails,
and while errno claims 9 (EBADF - "Bad file descriptor"), WSAGetLastError
says WSAECONNRESET - which means the previous send resulted in an ICMP port
unreachable.
/Mike
next reply other threads:[~2004-06-07 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 20:07 Mike Nordell [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-07 20:30 [Qemu-devel] Re: Status of user-mode networking for win32 Mike Nordell
2004-06-07 18:18 Mike Nordell
2004-06-07 19:50 ` Elefterios Stamatogiannakis
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='000401c44ccb$24e25020$0401a8c0@putte2k' \
--to=tamlin@algonet.se \
--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).