From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Virtualization Herd
Date: Tue, 4 Jul 2006 22:00:57 +0200 [thread overview]
Message-ID: <20060704220057.15a8ea5e@c1358217.kevquinn.com> (raw)
In-Reply-To: <1152021552.29593.43.camel@continental.nick125.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
On Tue, 04 Jul 2006 07:59:12 -0600
Nick Devito <nick125@gmail.com> wrote:
> Yeah, to me, having those in the emulation category just
> doesn't...."fit" there, but, that's just me. Maybe we could take xen,
> vmware, qemu, and related packages out of app-emulation, and make a
> new category, app-virtualization. That would seem to fit a bit better
> then emulation.
Waste of time, subjective reasoning, and just causes too much
unnecessary disruption.
> On Tue, 2006-07-04 at 12:11 +0100, Chris Bainbridge wrote:
> > On 03/07/06, Benedikt Böhm <hollow@gentoo.org> wrote:
> > > On Monday 03 July 2006 21:56, Nick Devito wrote:
> > > > Okay, in that case, extend the vserver herd to include a larger
> > > > range of virtualization stuff, including Xen, Bochs, and so on.
> > > > It just seems more fitting to group those packages together.
> > >
> > > not really, bochs, qemu and vmware is emulation, merely used in
> > > virtualization environments
> >
> > Qemu (with the kqemu module) and vmware both directly execute the
> > native bytecode. Bochs is the only real emulator.
For the record, Qemu is much more than virtualisation; indeed
virtualisation is just a small part of what Qemu can do. Emulation is
the main thing that Qemu does, for many targets on many hosts.
--
Kevin F. Quinn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-04 19:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 17:49 [gentoo-dev] Virtualization Herd Nick Devito
2006-07-03 19:48 ` Benedikt Böhm
2006-07-03 19:56 ` Nick Devito
2006-07-03 20:28 ` Benedikt Böhm
2006-07-03 20:38 ` Benedikt Böhm
2006-07-03 21:18 ` Nick Devito
2006-07-04 1:09 ` Daniel Gryniewicz
2006-07-04 2:15 ` Nick Devito
2006-07-04 3:03 ` Daniel Gryniewicz
2006-07-05 12:48 ` Chris Gianelloni
2006-07-05 15:40 ` Benedikt Böhm
2006-07-04 11:11 ` Chris Bainbridge
2006-07-04 13:59 ` Nick Devito
2006-07-04 14:27 ` Ned Ludd
2006-07-04 20:00 ` Kevin F. Quinn [this message]
2006-07-04 20:08 ` Kevin F. Quinn
2006-07-05 12:56 ` Chris Gianelloni
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=20060704220057.15a8ea5e@c1358217.kevquinn.com \
--to=kevquinn@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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