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!
could it not just be that they wrote the code initially to be reliant on the hardware functions, in order to (i assume) get decent performance relatively quickly and with (again making assumptions) less overheads, and now they have managed to write a software only version at a similar decent level of performance? it seems to be TFA is just assuming that anything microsoft does is cynical and evil, not just a practical decision
Tag the article as randalckennedy. At least we can identify obvious FUD for what it is.
$_ = "wftedskaebjgdpjgidbsmnjgcdwatb"; tr/a-z/oh, turtleneck Phrase Jar!/; print
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.
No twisting required.
It appears Microsoft intentionally restricted this feature in an attempt to make customers purchase hardware they did not need.
Is that bashing Microsoft? No, it's just stating a fact. If the fact bashes Microsoft, that's their fault.
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....
Right now I use VMware player to run an old XP install for some stuff that requires XP, and it works pretty well. Does this patch mean I won't need to do this anymore, or is this patch only available to the windows 7 professional or whatever licenses? Side note: I just recently bought windows 7 home premium and I gotta say, things have improved a lot since XP. I'm a mac user and I think I might actually like windows 7 better (shock, horror). Windows 7 works great on my imac (besides that weird audio stuttering thing that sometimes happens, what is that?)
read: Begging the question
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.
Thanks for posting a link to a reputable site, not some assholes blog.
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.
This has nothing to do with the Guest OS. Hardware virtualization acceleration is dependent on the host OS - specifically, the virtual machine software itself.
Is there a link to it anywhere ?
I actually rtfa and there's no sign of one. I really can't be bothered searching MS site to find one as the CPU on this machine has VT on CPU and enabled in BIOS
One reason I'm glad I don't use Windows is because I don't have to get caught on the short end of the bullshit politics stick. Even if something shitty happens with my favorite distro/browser/app, there's others to choose from.
The answer is probably that hardware virtualization is simply easier to implement. MS wanted to get the feature out of the door and to customers. They probably expect that a large number of Windows 7 users are on newer hardware likely to have VT. Then later updated the software to support software based virtualization in order to allow it to function for more people.
Adding features (in this case software virtualization support) through updates is hardly newsworthy...
Yes, it is the same KB that was leaked back around January, KB977206.
http://support.microsoft.com/?kbid=977206
Really, I'd say if you don't have a chip that supports VT/AMD-V you don't really want to be using XP mode. It is going to be all kinds of slow. This is partially because VT speeds up virtualization but also because it implies an older CPU. After all, ALL Core 2s and up have VT, as do some Pentium Ds. You want a reasonable amount of hardware to run Windows 7 and then run XP on top of it. I don't think that this was an unreasonable requirement.
However, some people seem to think they should be able to do all the latest crap with old computers and bitched, so MS is giving them what they wanted. Now they'll just bitch that it is too slow.
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
What that statement means is that the XP Mode VM must be SP3.
I'm an elbow breather.
I got the udpate from here:
For 32-bit host operating systems: http://www.microsoft.com/downloads/details.aspx?FamilyID=837f12aa-1d37-464e-ae59-20c9ecbebaf6
For 64-bit host operating systems: http://www.microsoft.com/downloads/details.aspx?FamilyID=e70dd043-e262-43c0-a002-446567f1e2b4
(Via: http://blogs.msdn.com/virtual_pc_guy/archive/2010/03/18/windows-virtual-pc-no-hardware-virtualization-update-now-available-for-download.aspx)
"really stood out in my mind" makes perfect sense. Shut up troll.
I would absolutely love to se sources for this claim.
-- Linux user #369862
Intentionally restricted? Not exactly. Rough quote from Raymond Chen: "Every feature starts at -100." That is to say, you need more than just a faint "it would be nice" feeling to write a feature. If every helpful feature were implemented, the product wouldn't ship until the end of time, and the testing and support headaches would multiply exponentially. The features needs to be *very* useful or *very* easy to implement. Since most modern CPUs come with virtualization tech, and few programs require XP mode, the cost/benefit analysis says that easier to implement hardware virtualization is worth the time and effort, while software isn't. Simple as that.
$_ = "wftedskaebjgdpjgidbsmnjgcdwatb"; tr/a-z/oh, turtleneck Phrase Jar!/; print
Except if it takes a longer time to run your task at lower speeds
Only if the task is CPU-bound. For a task that's memory-bound or disk-bound or network-bound or human-bound, Turbo Off could be a win. But you're right that things like the backlight don't scale the same way.
When you can buy a brand new PC with 2 gigabytes and 2 gigahertz, and it only costs $300
Since when does a new laptop with 2 GB RAM and 2 GHz CPU cost 300 USD? I thought Microsoft was still limiting cheap "ULCPC" Windows licenses to smaller CPU and RAM.
Or the update could be patching XP so that it's kernel avoids the troublesome instructions, the way that there patches to linux in the past to allow nearly native speed in qemu. Then it would not need all the essentially an emulator code of the previous vpc versions.
I guess I thought it was just common knowledge that Apple intentionally restricts OSX in an attempt to make consumers purchase Apple-branded x86 computers. Do you disagree?
If you don't know where you are going, you will wind up somewhere else.
Riiight... Creating a feature that works on 90% of modern computers to enable backwards compatibility with an older OS is trying to force people to stop using said older OS. Stop and think for a moment. If those people's computers don't support virtualization, that would be an incentive *not* to upgrade. Your premise is moronic.
$_ = "wftedskaebjgdpjgidbsmnjgcdwatb"; tr/a-z/oh, turtleneck Phrase Jar!/; print
Is it bashing Apple to point out that they do they same thing to OSX?
I constantly see this argument in politics.
Well A did X, so why shouldn't B be able to do X? It doesn't fucking matter, X is still wrong and they should both be criticized.
'Political power grows out of the barrel of a gun.' - Mao Tse-tung
Which, if true, makes it odd that this new method is unsupported for all guest OSes other than XP, doesn't it?
Here, this may answer your questions and get you on the right path.
http://www.microsoft.com/windows/virtual-pc/support/faq.aspx
Don't know something? Look it up. Still don't know? Then ask.
I have a Vaio AR870. One of the reasons I bought it (besides the 1920x1200 screen) was because it had the core 2 duo and the processor supported HAV. Behold the day I intalled windows 7 and tried to get XP Mode working to support all my clients that refuse to move beyond 1999 technology. No HAV enabled. No setting in the bios to change it. Sony's custom bios interface doesn't expose the HAV setting and their stance is that they will only be creating bios updates for selected machines. I created a DOS boot CD and I had to dump the bios, hex edit it, and reflash by hand. A sphincter tightening moment to say the least. It all worked and I didn't brick my laptop. But I was irritated during the original attempt when I found out that if HAV wasn't enabled you couldn't install.
I'm just wondering if there is really widespread use of this feature? Personally I don't run too much older software but I can see that it might have uses for some businesses that have older versions of propriety software that may need this. But really I am just interested to know if anyone has/knows of some software that requires this to be able to run properly. If so some examples would be appreciated. Also IMO I would choose to use VMWare over VirtualPC any day. In my experience with using a variety of Virtualization solutions, I have become a big fan of not only how well VMWare products run, (speed, stability), but also their support is fantastic. My favorite product is ESX server. I recommend this to any business that requires constant uptime. being able to migrate a virtual machine such as an exchange server to another server almost instantly in the case of hardware failure or other issue with the server, with only a couple second interruption in service is fantastic. Every company owes it to themselves to at least evaluate what ESX server may be able to do for them.
I've successfully installed Windows Virtual PC on Windows 7 Home Premium. You have to tell the web site you're using Professional or Ultimate in order to download it, but once you set it up, you can install your own copy of XP and run it just fine. In fact, once you install the Virtual PC integration features in the guest OS, it works just like the "real" XP Mode - floating windows, start menu integration, etc.
Visual IRC: Fast. Powerful. Free.
Every few times I run XP mode, I get a message that my computer cannot run it, that my computer does not have hardware virtualization support. Turning the computer completely OFF (a reboot does not do it) will fix it, but it is a problem. Maybe this is a workaround until they can fix it?
"Sometimes a woman is a kind of religion, she can save your soul & set you free from all your sins" - Bad Examples
Remember "Blue Pill" - the hardware-virtualization-based root kit proof? Turning off HV prevents that type of root kit from being installed. Actually, not a bad idea. Keep it off unless it is needed.
Place nail here >+
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