From: Lindsay Mathieson <lindsay@softlog.com.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Attitute and Predisposition of the List & newbie documets
Date: Thu, 02 Sep 2004 09:09:19 +1000 [thread overview]
Message-ID: <4136569F.1030707@softlog.com.au> (raw)
In-Reply-To: <s135e6b3.062@GW-FS1.SHANDS.UFL.EDU>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
Thomas Munn wrote:
> While I am not among those who are enlightened enought to talk about
> opcodes and their proper optimization, I do have a few observations to
> make, having watched this list for 2 months.
>
> 1. People really don't like newcomers on this list.
As a newbie from a few weeks ago, that is *not* my experience, people
have been quite helpful.
> 3. QEMU is rather DIFFICULT to use. I have been a UNIX admin for 10
> years.
Well I haven't, and I managed fine. I would venture to say that qemu is
*not* for casual users at the moment, its in heavy dev and prone to
breaking :(
> 4. I am compiling a list of my difficulties, and will be writing
> documentation to help people setting qemu for the first time. The
> existing documentation simply does not cover in high detail how to get
> qemu working. For example, I found it very confusing on what
> qemu-fast is for. A simple "QEMU-FAST ONLY works with linux at this
> time. You must install a working GUEST image, apply the appropriate
> patch to the GUEST kernel, and then run qemu-fast. DO NOT TRY to use
> QEMU-FAST otherwise. It will simply segfault!
Thats great - thanks, gotta admit I spent a long time trying to get
qemu-fast working before I realised it was the guest that was patched,
not the host :)
[-- Attachment #2: Type: text/html, Size: 2033 bytes --]
next prev parent reply other threads:[~2004-09-01 23:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 19:11 [Qemu-devel] Attitute and Predisposition of the List & newbie documets Thomas Munn
2004-09-01 19:22 ` Kai Cherry
2004-09-02 21:29 ` Jim C. Brown
2004-09-01 19:40 ` Johannes Martin
2004-09-01 19:41 ` Lionel Ulmer
2004-09-01 20:38 ` Magnus Damm
2004-09-01 20:36 ` Kai Cherry
2004-09-01 20:57 ` Derek Fawcus
2004-09-02 6:46 ` Johannes Martin
2004-09-01 23:09 ` Lindsay Mathieson [this message]
2004-09-02 0:54 ` Bochnig, Martin
2004-09-02 21:22 ` Jim C. Brown
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=4136569F.1030707@softlog.com.au \
--to=lindsay@softlog.com.au \
--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.