Re: Xen vs VMware

["Kevin L. Kane" <kevin.kane@xxxxxxxxx>]

Possibly offtopic for this thread, but:

Will the approach your taking with DragonFly allow for quickly and
easily migrating the virtualized kernels between machines?

Also, what about the possibility of running your userland kernels
under other operating systems?  One of the advantages that Xen and
VMWare has is that you CAN run multiple operating systems when you are
forced to.

-Kevink

On 10/18/06, Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx> wrote:
> :On 10/18/06, Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx> wrote:
> :
> :>     Generally speaking I prefer the VMWare concept over the Xen concept.
> :>     Xen actually has to run two operating systems, one serving as the
> :>     master and the other as the 'guest' OS, and this compounds the
> :>     number of potential bugs you might run into a lot more then a machine
> :>     emulator does.
> :
> :The master and guest relationship exists inside the VMWare model as
> :well.  I don't see how Xen is any more or less bug prone.  They are
> :just two approaches at acheiving the exact same goal.  And with the
> :new VT hardware, guest operating systems no longer need to be Xen
> :aware or ported.
> :
> :As an aside has anyone tried using DragonFly under Xen with the VT
> :enabled hardware?
> :
> :-Kevink
> :
> :--
> :Kevin L. Kane
> :kevin.kane at gmail.com
>
>     Yes, that's very true.  I suppose the approach I favor the most is the
>     one I am taking with the DragonFly virtualization work... that is,
>     running the virtualized kernel as a standard user process linked against
>     libc, with only very minimal support required from the 'real' kernel
>     to allow the virtual kernel to manage the VM contexts for its own
>     'user' processes.  That way you don't actually have to learn to admin
>     two different operating systems.
>
>                                         -Matt
>                                         Matthew Dillon
>                                         <dillon@xxxxxxxxxxxxx>


--
Kevin L. Kane
kevin.kane at gmail.com