Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] choice of hypervisor (was gracefully shutdown guests)

Matthew Gillen wrote:
> The history is a little more convoluted.  Redhat got on board with Xen
> because at the time it was the more advanced solution.  With RH's

Minor nit: at the time it was the ONLY solution. Xen predates KVM by
almost 10 years.

> Linus much preferred the QEMU/KVM approach, and basically said he'd
> never bring Xen into the mainline.  Since RH has a policy (a wise one

I don't. KVM isn't a bare metal hypervisor like Xen. Every KVM guest is
a process running on the Linux host. That's fine as a substitute for
VMware Workstation but it's not so good for enterprise class virtual
server racks. It's also not so good for workstation virtualization since
you can only run KVM guests on Linux hosts thus negating the easy
portability that makes workstation virtualization so useful.	

> So basically at this point everyone has thrown their lot in with
> QEMU/KVM and Xen is pretty much abandoned except for some researchers.

Xen abandoned? Only used by researchers? Perhaps you've never heard of
Amazon EC2 or Rackspace or Linode. They're only some of the largest VPS
platforms in the world and they all run on Xen.

Rich P.

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /