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

Re: [Publicity] Blog Czar update, week of August 12

On Wed, 2013-08-21 at 11:24 +0100, George Dunlap wrote:
> On 21/08/13 04:08, Russell Pavlicek wrote:
> > Okay, so here is my post, available for comment:
> >
> > http://blog.xen.org/index.php/2013/08/21/why-a-cloud-independent-hypervisor-is-essential/?preview=true
> >
> > This piece is a thought leadership post.  It is meant to appeal to a
> wider Cloud-interested audience.  It doesn't even mention Xen until
> the conclusion.
> Isn't it the case that it's relatively difficult to port from *any* 
> hypervisor to another -- KVM to Xen, Xen to VirtualBox, VB to Hyper-V, 
> Hyper-V to VMWare?  I guess that's probably only for Windows, really... 
> Can you give me an example of some features from VMWare's HV that might 
> promote vendor lock-in, over and above the simple fact that the emulated 
> HW in different?

We should be careful here. I think porting guests among "HVM" type
hypervisors is likely to be relatively easy compared with moving a PV
Xen guest to another hypervisor (which would require switching it to
HVM). People in glass houses etc...

I'm not sure this is the sort of "lockin" Russ was referring too though.

> Obviously vendor lock-in is something people should be aware of; it's 
> likely that VMWare will try it, but probably likely that Amazon and 
> Rackspace will try it as well - just not with the hypervisor.
>   -George

Publicity mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.