From: "Leonardo E. Reiter" <lreiter@win4lin.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] user networking - win xp quest, amd64 linux host
Date: Mon, 09 May 2005 10:37:04 -0400 [thread overview]
Message-ID: <427F7590.2030105@win4lin.com> (raw)
In-Reply-To: <427EE18A.6090706@kadu.net>
We have seen problems on the AMD64 with -user-net as well. While we
have not been able to debug further yet, I suspect what is happening is
that some 32-bit values in packet headers that SLIRP is decoding are
actually represented as 64-bit types on 64-bit processors. Again, this
is just a guess, but it's the first place we'll look once we get to it,
since we think it's the most likely cause.
- Leo Reiter
Adrian Smarzewski wrote:
> Adrian Smarzewski wrote:
>
>>bash-2.05b$ uname -a
>>Linux localhost 2.6.11-gentoo-r7 #1 Sun May 8 06:59:56 CEST 2005 x86_64
>>AMD Athlon(tm) 64 Processor 3400+ AuthenticAMD GNU/Linux
--
Leonardo E. Reiter
Vice President of Product Development, CTO
Win4Lin, Inc.
Virtual Computing from Desktop to Data Center
Main: +1 512 339 7979
Fax: +1 512 532 6501
http://www.win4lin.com
next prev parent reply other threads:[~2005-05-09 14:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 1:42 Re: [Qemu-devel] user networking - win xp quest, amd64 linux host Ben Taylor
2005-05-09 3:32 ` Adrian Smarzewski
2005-05-09 4:05 ` Adrian Smarzewski
2005-05-09 14:37 ` Leonardo E. Reiter [this message]
2005-05-09 15:19 ` Adrian Smarzewski
2005-05-09 15:50 ` Leonardo E. Reiter
2005-05-09 16:42 ` Adrian Smarzewski
2005-05-09 15:53 ` Adrian Smarzewski
2005-05-09 17:26 ` Juergen Lock
2005-05-09 17:58 ` Adrian Smarzewski
2005-05-09 18:23 ` Jung-uk Kim
-- strict thread matches above, loose matches on Subject: below --
2005-05-08 23:21 Ben Taylor
2005-05-09 0:06 ` Adrian Smarzewski
2005-05-09 0:22 ` Henrik Nordstrom
2005-05-09 0:49 ` Adrian Smarzewski
2005-05-08 22:22 Adrian Smarzewski
2005-05-15 21:03 ` Adrian Smarzewski
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=427F7590.2030105@win4lin.com \
--to=lreiter@win4lin.com \
--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.