Re: [tlug] Xen advice, please: Wine is not Virtualization

[<burlingk@example.com>]

> ------------------------------
> 
> Message: 15
> Date: Tue, 9 Jan 2007 12:26:47 -0500
> From: Jim <jep200404@example.com>
> Subject: Re: [tlug] Xen advice, please: Wine is not Virtualization
> To: Tokyo Linux Users Group <tlug@example.com>
> Message-ID: <20070109122647.4c9dfc45.jep200404@example.com>
> Content-Type: text/plain; charset=US-ASCII
> 
> Keith R Mannisto wrote:
> 
> > In this thread, WINE seems to be missing.
> > Is there any reason to exclude WINE as an option?
> 
> Wine and Xen are different _kinds_ of things. 
> 
> Wine is a (big!) shim that allows one to run Windows programs under 
> Linux(/Unix?). It does not allow one to run the whole 
> (Windows) operating system, nor does it offer the strong 
> sandbox that virtualization offers. 
> 
> Often Linux folks will use virtualization to run multiple 
> instances of Linux (not Windows). This can be for security, 
> for running (perhaps old) applications under the 
> specific version of Linux that they require, 
> or for developinng and testing Linux applications under a 
> variety of distributions. 

Another really big issue on the virtualization Vs WINE front.
Win is not a virtualization tool.  Wine will ONLY run on x86 compatible
processors.

While this may seem like a small issue (especially with Mac switching to
intel), it still means that it can only be used on a limited range of
machines.  No alpha, no sparc, etc...

Xen, VMware, are virtual machines.  They emulate everything from the
ground up.  They do something totally different from WINE.  Basically
"WINE Is Not an Emulator", a virtual machine is. ^_^