qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: qemu-devel@nongnu.org, freebsd-emulation@freebsd.org
Subject: Re: [Qemu-devel] qemu-cvs FreeBSD guests, cirrus, vmwarevga emulation - experimental qemu-devel FreeBSD port update available for testing
Date: Sun, 6 Jan 2008 18:03:24 -0600	[thread overview]
Message-ID: <20080107000324.GB21491@tapir> (raw)
In-Reply-To: <20080106224450.GA76738@saturn.kn-bremen.de>

On Sun, Jan 06, 2008 at 11:44:50PM +0100, Juergen Lock wrote:
> Also, still slirp causes qemu to crash on amd64 hosts when just
> trying to access a webpage from inside a guest.

I never though slirp will ever work in an amd64 (judging by all the pointer
<-> integer size mismatches) or any other LP64 architecture, regardless of
the guest OS being used, which is why I never even bother to test.

>  So, can anyone reproduce any of these problems on e.g. a Linux host?

does anyone have a woking setup for slirp for linux 64bit hosts?

Carlo

  reply	other threads:[~2008-01-06 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06 22:44 [Qemu-devel] qemu-cvs FreeBSD guests, cirrus, vmwarevga emulation - experimental qemu-devel FreeBSD port update available for testing Juergen Lock
2008-01-07  0:03 ` Carlo Marcelo Arenas Belon [this message]
2008-01-07 22:34 ` [Qemu-devel] " Juergen Lock
2008-01-08 19:43 ` [Qemu-devel] scsi emulation throughput (was: Re: qemu-cvs FreeBSD guests, cirrus, vmwarevga emulation - experimental qemu-devel FreeBSD port update available for testing) Juergen Lock
2008-01-09  9:37 ` [Qemu-devel] qemu-cvs FreeBSD guests, cirrus, vmwarevga emulation - experimental qemu-devel FreeBSD port update available for testing Laurent Vivier

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=20080107000324.GB21491@tapir \
    --to=carenas@sajinet.com.pe \
    --cc=freebsd-emulation@freebsd.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).