1 |
On Tue, 04 Jul 2006 07:59:12 -0600 |
2 |
Nick Devito <nick125@×××××.com> wrote: |
3 |
|
4 |
> Yeah, to me, having those in the emulation category just |
5 |
> doesn't...."fit" there, but, that's just me. Maybe we could take xen, |
6 |
> vmware, qemu, and related packages out of app-emulation, and make a |
7 |
> new category, app-virtualization. That would seem to fit a bit better |
8 |
> then emulation. |
9 |
|
10 |
Waste of time, subjective reasoning, and just causes too much |
11 |
unnecessary disruption. |
12 |
|
13 |
> On Tue, 2006-07-04 at 12:11 +0100, Chris Bainbridge wrote: |
14 |
> > On 03/07/06, Benedikt Böhm <hollow@g.o> wrote: |
15 |
> > > On Monday 03 July 2006 21:56, Nick Devito wrote: |
16 |
> > > > Okay, in that case, extend the vserver herd to include a larger |
17 |
> > > > range of virtualization stuff, including Xen, Bochs, and so on. |
18 |
> > > > It just seems more fitting to group those packages together. |
19 |
> > > |
20 |
> > > not really, bochs, qemu and vmware is emulation, merely used in |
21 |
> > > virtualization environments |
22 |
> > |
23 |
> > Qemu (with the kqemu module) and vmware both directly execute the |
24 |
> > native bytecode. Bochs is the only real emulator. |
25 |
|
26 |
For the record, Qemu is much more than virtualisation; indeed |
27 |
virtualisation is just a small part of what Qemu can do. Emulation is |
28 |
the main thing that Qemu does, for many targets on many hosts. |
29 |
|
30 |
-- |
31 |
Kevin F. Quinn |