From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Running QEMU on FreeBSD
Date: Sat, 29 May 2004 23:09:27 +0100 [thread overview]
Message-ID: <1085868567.93476.13.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <40B90776.60406@fabianowski.de>
On Sat, 2004-05-29 at 22:58, Bartosz Fabianowski wrote:
> > I even put in code to use the if_tap interface, but so far it's
> > untested.
>
> It's all in CVS already ;). There was a set of patches posted in March
> and then updated in April I think that got committed recently. It was in
> the list's archive, but for some reason the archive vanished this morning.
>
> > Does the version in CVS offer much more than the 0.5.5 I downloaded
> > and built from?
>
> It has most FreeBSD patches built in. It has some bug fixes. It allows
> you to install FreeBSD inside QEMU. Quite cool.
I'll have to check it out then :)
> > And one of the things I am interested in doing is having a working
> > OS/2 on my P4 laptop (OS/2 doesn't install on it) and maybe booting
> > the XP partition from FreeBSD.
>
> XP works inside QEMU, I can confirm that. But some of the Windows
> updates didn't want to install. No clue why. Another problem is that
> because there is no long double type in FreeBSD yet, the FPU emulation
> is a bit hackish and you get stuff like this:
>
> http://www.fabianowski.de/long_double.png
Hmm... gcc 3.3 does support long doubles...
I pulled in some code from Linux for the missing long double
functions... So in theory, the binary I have does have long double
support ;)
> Best regards,
> - Bartosz Fabianowski
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> FLAGS (\Recent \Seen))
--
next prev parent reply other threads:[~2004-05-29 22:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 21:25 [Qemu-devel] Running QEMU on FreeBSD Antony T Curtis
2004-05-29 21:39 ` Bartosz Fabianowski
2004-05-29 21:50 ` Antony T Curtis
2004-05-29 21:58 ` Bartosz Fabianowski
2004-05-29 22:09 ` Antony T Curtis [this message]
2004-05-29 22:24 ` Bartosz Fabianowski
2004-05-29 23:09 ` Antony T Curtis
2004-05-30 3:53 ` Antony T Curtis
2004-05-30 7:25 ` Markus Niemistö
2004-05-30 9:50 ` Antony T Curtis
2004-05-30 14:41 ` Bartosz Fabianowski
2004-05-30 17:27 ` Antony T Curtis
2004-05-30 18:57 ` Bartosz Fabianowski
2004-05-30 20:09 ` Antony T Curtis
2004-05-31 0:36 ` Bartosz Fabianowski
2004-05-31 1:24 ` Antony T Curtis
2004-05-31 1:42 ` Bartosz Fabianowski
2004-05-31 1:59 ` Kyle Hayes
2004-05-31 12:15 ` Bartosz Fabianowski
2004-05-31 13:22 ` Antony T Curtis
2004-05-31 9:38 ` Antony T Curtis
2004-05-31 20:36 ` Bartosz Fabianowski
2004-05-31 13:54 ` Antony T Curtis
2004-05-31 20:31 ` Bartosz Fabianowski
2004-05-31 22:15 ` Antony T Curtis
2004-05-31 22:56 ` Brion Vibber
2004-05-31 23:01 ` Bartosz Fabianowski
2004-06-02 23:18 ` qemu port (was: Re: [Qemu-devel] Running QEMU on FreeBSD) Juergen Lock
2004-06-02 23:54 ` [Qemu-devel] Re: qemu port Bartosz Fabianowski
2004-06-03 17:10 ` Gianni Tedesco
2004-06-04 18:44 ` Juergen Lock
2004-06-05 21:04 ` [Qemu-devel] FreeSBIE timer (was: Re: qemu port) Juergen Lock
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=1085868567.93476.13.camel@pcgem.rdg.cyberkinetica.com \
--to=antony.t.curtis@ntlworld.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).