From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Clarification about qemu-fast (was segfaults in fc1)
Date: Wed, 23 Jun 2004 16:12:01 +0100 [thread overview]
Message-ID: <1088003520.651.66.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <s0d9478a.059@GW-FS1.SHANDS.UFL.EDU>
On Wed, 2004-06-23 at 14:03, Thomas Munn wrote:
> I would suggest that the documentation perhaps have large letters so
> people won't have to go through the hell that I did. Basically, the
> "qemu-fast" patch is only for oses inside of the main os (I know it
> says it "guest" in docs), and NOT to be applied to main os! You might
> want to include a warning so other people who aren't developers won't
> try applying this patch to their main kernel. So Perhaps:
>
> Warning: The qemu-fast patch should NOT be applied to the "host" os,
> (e.g. the main os) as it will impair the functionality of qemu by
> causing segfaults and all kinds of other nasty stuff. Only apply this
> when using linux inside of qemu-fast.
>
> You also might want to further clarify the purposes of qemu-fast and
> its ilk, when not to use etc.
I have patched it to compile under FreeBSD... but I do not know how I
should test/debug it ...
--
Antony T Curtis <antony.t.curtis@ntlworld.com>
prev parent reply other threads:[~2004-06-23 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 13:03 [Qemu-devel] Clarification about qemu-fast (was segfaults in fc1) Thomas Munn
2004-06-23 12:05 ` David
2004-06-23 16:50 ` Jim C. Brown
2004-06-23 19:22 ` John R. Hogerhuis
2004-06-24 6:36 ` Jean-Michel POURE
2004-06-24 9:08 ` Christof Petig
2004-06-24 21:48 ` John R. Hogerhuis
2004-06-23 15:12 ` Antony T Curtis [this message]
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=1088003520.651.66.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).