From: art yerkes <ayerkes@speakeasy.net>
To: jm@poure.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU 0.5.3 release
Date: Mon, 19 Apr 2004 14:23:11 -0500 [thread overview]
Message-ID: <20040419142311.3a2ccb10.ayerkes@speakeasy.net> (raw)
In-Reply-To: <200404191642.40960.jm@poure.com>
On Mon, 19 Apr 2004 16:42:40 +0200
Jean-Michel POURE <jm@poure.com> wrote:
> Le lundi 19 Avril 2004 15:04, art yerkes a écrit :
> > On my amd64, I can use qemu compiled 32bit, but there seem to be bugs
> > initializing the virtual ethernet, which I need.
>
> Under Win32 guest, you may need Renzo patch sent to the list:
> http://mail.gnu.org/archive/html/qemu-devel/2004-03/msg00202.html
>
> Cheers, Jean-Michel
Actually, the interface name is reported as tun%d to the ifup script, and
qemu seems to freeze on the first packet transmit. Other than that, no
problems so far using 32bit qemu on amd64 (I should add that I'm using it
for running reactos as a guest). When I run my 64bit compiled version, the
tunnel name is reported correctly (tun1), and I suspect that packet transmit
would also work if qemu didn't crash with a segfault trying to execute the
first insruction.
I'd like to help with 64-bit porting.
--
IBM had little or no expertise on Intel processors.
-- paragraph 54, SCO v IBM, second amended complaint
No matter how cynical you become, it's never enough to keep up.
-- Lily Tomlin
next prev parent reply other threads:[~2004-04-19 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 15:41 [Qemu-devel] QEMU 0.5.3 release Fabrice Bellard
2004-04-04 17:45 ` Rudi Lippert
2004-04-04 18:31 ` Herbert Poetzl
2004-04-13 16:00 ` Martin Garton
2004-04-13 19:15 ` Fabrice Bellard
2004-04-18 17:58 ` J. Mayer
2004-04-19 13:04 ` art yerkes
2004-04-19 14:42 ` Jean-Michel POURE
2004-04-19 19:23 ` art yerkes [this message]
2004-04-19 17:43 ` [Qemu-devel] " Andi Kleen
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=20040419142311.3a2ccb10.ayerkes@speakeasy.net \
--to=ayerkes@speakeasy.net \
--cc=jm@poure.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 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).