4 posts • joined Saturday 9th May 2009 06:50 GMT
Intel and virtualization
"Virtualization is a standard feature in Intel's chips"
You're kidding right? Finding out which intel chips support virtualization is a frakkin' nightmare.
KVM is the only credible way to go
Xen does suffer from that tiny problem that it is not linux. They managed to keep it quite for a long time but now that there is an alternative I'd say the game is up.
KVM is rapidly reaching the point where xen is no longer relevant on a linux distro. So Novell have to provide full support for it, otherwise users and customers will abandon (open)SUSE.
RedHat, of course, have two strategies - developing KVM while simultaneously enhancing libvirt to work with all known hypervisors. And suse are starting to suffer, afaict, because they do not _seem_ to involved in the development of either. Which makes it an unnecessary hassle for anyone who wants to use the latest libvirt code on a suse distro.
Intel are more to blame here than MS
I think the article and a lot of the comments miss the point. Intel have basically disabled VT on a lot of chips that otherwise are capable of it. The policy is not at all transparent and seems to exist for no other reason than to make punters who need the feature part with more money.
I've been a happy AMD customer for years and they are much more straightforward about this. The rule there is that VT is enabled on pretty much all chips, except maybe single core semprons.
I've been stung by this Intel policy once and it will be a long time before I buy another Intel processor.