Microsoft Lifts XP Mode Hardware Requirement
An anonymous reader writes "This week, Microsoft published a patch that allows Windows XP Mode to run on PCs without hardware-assisted virtualization. Which begs the question: Why the bizarro requirement in the first place? Was it an honest attempt to deliver an 'optimal' user experience? Or simply a concession to the company's jilted lover, Intel Corporation — 'a kind of apology for royally screwing up with the whole Windows Vista “too fat to fit” debacle,' as the blog post puts it."
The "weird" hardware requirements are probably due to the fact that they expected AMD and Intel only to produce CPUs with hardware support for virtualization enabled. The fact that one of the major CPU manufacturers didn't, is most likely what bit Microsoft in the ass. Still, some OEMs also are at fault, I think: Just recently I got to look after a defective laptop (RAM module was broken...) and I looked in the BIOS. The CPU could do hardware virtualization, but by default it was disabled in the BIOS. Why? I have no idea...
Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
This doesn't mean what you think it means. Why do some people (mostly nerds) insist on using this term, when it is obvious they don't know what it means or how to use it?
This must end.
Not only does this not 'beg the question' it's by our good friend Randal C. Kennedy of Devil Mountain Software fame. Come on guys, this is in the frigging Ars Technica.
The problem with Slashdot these days is that has no taste, absolutely no taste.
Faster! Faster! Faster would be better!
On one hand, XP Mode in 7 actually uses Virtual PC, which has been around for a long time - but didn't require hardware virtualization support until the most recent version.
On the other hand, while I can't find that link now, I do recall seeing one of VPC guys explaining that they went hardware-only for the new release simply because it allowed them to cut out a lot of code, which then no longer needs to be supported. In which case it may be that they have realized that it's a bad idea from business perspective, and put that code back in (and brought it up to date) with that patch.
The bigger announcement was that they were dropping the stupid VDI licensing thing. Paying an extra $23/year on top of the outrageous fees we already pay for Select and Open licenses just for the privileged of using the desktop OS licenses in a virtual environment was just stupid and I'm very glad it was dropped, might make it a bit easier to find a positive ROI on a VDI project now.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
That was my initial thought as well. Yes, well-written software-only virtualization can perform at a similar level, but if they can get it out the door faster with hardware supported virtualization, they may have decided the software-only approach wasn't worth the resources at the time. It's called prioritization; if they put the resources into software-only virtualization, they neglect something else.
$_ = "wftedskaebjgdpjgidbsmnjgcdwatb"; tr/a-z/oh, turtleneck Phrase Jar!/; print
Clearly it isn't Intel over AMD, it could support both Intel VT and AMD-V. Don't throw out the hate without justification!
ars technica
Thanks for pointing that out ColdWetDog.
~Mekkah
http://news.slashdot.org/article.pl?sid=10/02/21/2329249 Windows 7 Memory Usage Critic Outed As Fraud, Subsequently Given Front Page Story on Slashdot for Some Reason
Why all the begging?
i've run the desktop version of VMWare on my laptop and it's very slow compared to the VT version of Windows XP Mode on the same laptop.
it's the same old complaints. people want a feature but if it's not supported in hardware and runs extremely slow they will scream on the internets how stupid microsoft is for making it so slow on 6 year old hardware that otherwise runs Windows 7 very well
There are many, many other possibilities than the two derogative possibilities offered. The one which seems most likely to me is that Microsoft thought "well, it's in all new hardware, it probably isn't worth the time and cost of implementing a software solution," only to find out that market demand existed.
Another possibility is that it took them time to produce an implementation of sufficient quality.
StoneCypher is Full of BS
Is it bashing Apple to point out that they do they same thing to OSX?
If you don't know where you are going, you will wind up somewhere else.
WTF. Seriously? Slashdot is sourcing these jokers? This article is written by the same guy who was pretending to be the CTO of Devil Mountain Software and then got fired by InfoWorld after he was outed. What a tragedy....
It's to prevent hypervisor based rootkit attacks
https://www.microsoft.com/taiwan/whdc/system/platform/virtual/CPUVirtExt.mspx
For systems that are destined for a server role (and for only these systems), enable the virtualization extensions. The threat of running malicious code as an administrator on servers is reduced through Windows Server policies and organizational best practices.
For systems that are destined for a client role, disable (and lock off) the virtualization extensions.
For systems that might be deployed in either a server or client role (such as high-end workstations), it would be prudent to disable the extensions by default.
Explanation of this decision from Virtual PC blog:
Why is Microsoft making this change to Virtual PC now?
Because of you :-) We have heard loud and clear from customers that they need to be able to run Windows Virtual PC and Windows XP Mode on systems that do not have hardware virtualization support. So we are going to enable this.
Why did Microsoft release Windows Virtual PC without this in the first place?
There are two main reasons here.
The first is that we believe that customers will get the best virtualization experience on computers with hardware virtualization support. This has not changed – and even though we are releasing this update I would strongly encourage anyone who is looking at buying a new computer, and intends to use virtualization, to make sure that they get a system that is capable of supporting hardware virtualization.
The second is that we had hoped that by the time Windows Virtual PC released – hardware virtualization support would be prevalent enough that this would not be an issue. We were wrong on that. Bummer.
Also, it's not like hardware virtualization is exceedingly rare, either. On current AMD processors, for example, only the Sempron line doesn't support it. You also don't need to turn it on in the BIOS on AMD processors either: It either has it or it doesn't. It was actually a safe bet. I'm deliberately pointing out AMD's processors here, too, to show that it really couldn't have been a concession to Intel.
My blog
I believe I've found the source of the taste drain.
"Sacrifice for the good of The State" - The State
With actual links so you can download the patch to enable XP mode on previously unsupported processors, for instance:
http://arstechnica.com/microsoft/news/2010/03/microsoft-removes-vm-hardware-requirements-from-xp-mode.ars
Why the hell is this Exo-Blog post being cited? The author of TFA doesn't cite a goddamn thing.
But this mistake is so common, so many people are using it this way, it is high time we start de linking "begs the question" from "petitio principii".
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
In common English, as practiced by most people "begs the question" no longer means "petitio principii". It now means "this information begs that a question be asked, that wasn't".
Of course, we are in a transition. "Begs the question" in taken as logical fallacy by some, and as colloquial expression by others.
There is a perfectly reasonable expression used to replace "Begs the question" -- circular reasoning.
Just another "Cubible(sic) Joe" 2 17 3061