From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Recommended emulators/VMs for P9 install
Date: Sat, 17 Apr 2010 00:10:45 +0100 [thread overview]
Message-ID: <4B118F5B-8C82-4A47-AD79-30E4FEC96D5B@fastmail.fm> (raw)
In-Reply-To: <000201cadd8d$14126ec0$3c374c40$@gmail.com>
On 16 Apr 2010, at 18:48, Patrick Kelly wrote:
>>>
>>> The only emulator you're spending time on is Qemu, the rest are
>>> virtualizers or simulators, and there is a significant difference.
>>> Emulators are much slower, because of what they have to do.
>>
>> Qemu is capable of full emulation, but when host & guest
>> architecture match (or are compatible, e.g. x86_32 guest and x86_64
>> host)
>> it's a virtualizer. Given x86 on x86, there is a world of
>> difference between Bochs's performance and Qemu's.
>
> It's mostly full and not completely accurate.
> I don't use Qemu so this may be wrong, but I was under the
> impression Qemu was an emulator unless you used kqemu, and then it
> lost emulation capability's.
It can virtualise better with kqemu or kvm, but... well, perhaps I
should say what I know rather than try to categorise. Take 3 set-ups.
A: arm guest, x86 host. Full emulation, kqemu cannot be used. B: x86
guest, x86 host without kqemu. C: x86 guest, x86 host with kqemu.
There is a much bigger performance gap between A and B than between B
and C.
>
>> Qemu's display is slow, whatever other factors exist. Drawterm to a
>> qemu cpu server is very much faster. I can't speak for disk IO
>> except to say it seems fast under my light usage.
>>
>> Also, to nit-pick, don't all virtualisers emulate peripheral
>> hardware?
>
> For peripheral hardware, emulators and virtualizers are mostly the
> same, but that isn't the main reason most people use them, it's
> about the execution environment, which involves how the CPU is
> handled. Seeing as you didn't bring up a single full system
> emulator, I doubt you care more about peripherals.
*nods* Not a big point for me right now.
>
>
--
Simplicity does not precede complexity, but follows it. -- Alan Perlis
next prev parent reply other threads:[~2010-04-16 23:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 17:11 Joel C. Salomon
2010-04-15 18:35 ` Gabriel Díaz
2010-04-15 18:44 ` erik quanstrom
2010-04-15 20:43 ` Gabriel Diaz
2010-04-15 18:56 ` Federico G. Benavento
2010-04-15 18:58 ` erik quanstrom
2010-04-16 6:19 ` Rodolfo (kix)
2010-04-16 16:40 ` Patrick Kelly
2010-04-16 17:07 ` Ethan Grammatikidis
2010-04-16 17:48 ` Patrick Kelly
2010-04-16 23:10 ` Ethan Grammatikidis [this message]
2010-04-16 19:00 ` James Chapman
2010-04-16 19:51 ` [9fans] Parallels 5 Lyndon Nerenberg
2010-04-16 19:56 ` Lyndon Nerenberg
2010-04-16 20:25 ` erik quanstrom
2010-04-16 20:25 ` erik quanstrom
2010-04-16 20:50 ` Lyndon Nerenberg
2010-04-16 21:04 ` erik quanstrom
2010-04-16 22:06 ` Francisco J Ballesteros
2010-04-19 15:30 ` erik quanstrom
2010-04-16 23:35 ` erik quanstrom
2010-04-16 14:50 ` [9fans] Recommended emulators/VMs for P9 install Joel C. Salomon
2010-04-16 16:42 ` Patrick Kelly
2010-04-17 15:37 ` Georg Lehner
2010-04-18 17:38 ` Patrick Kelly
2010-04-15 18:56 ` Skip Tavakkolian
2010-04-15 21:59 ` Eric Van Hensbergen
2010-04-15 22:27 ` erik quanstrom
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=4B118F5B-8C82-4A47-AD79-30E4FEC96D5B@fastmail.fm \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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).