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."
Language evolves, like hardware requirements...
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.
Is how we Linux hippies can somehow twist this story in a way that allows us to bash Microsoft. It doesn't matter how delusional the idea, how disconnected from reality, how devoid of fact or reason, WE MUST BASH MICROSOFT.
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.
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
Maybe at the start they asked the Windows Virtual PC team what their minimum requirements were, and made those the minimum requirements for XP Mode.
Then after a big media dustup, they discover that some of those requirements probably only apply to guest OSes newer than XP. So they spend a lot of time verifying this, and then when they're confident enough that this is true, they make a patch that removes this requirement. But they are clear to point out that this change is only supported when XP is your guest OS. But the minimum requirements for Windows Virtual PC didn't change for other guest OSes.
Naw, couldn't be it. Gotta be some sort of i915 payola connection in there somewhere.
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
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?)
"really stood out in my mind"
You lie. AC doesn't have a mind for anything to stand out in. Stand - out - in - Wow that makes a lot of sense. Did you listen to yourself as you mouthed those words, before you typed them? Probably not - mouth breathers don't listen to anything, in my experience. Maybe if you have any literate relatives, you should get them to listen to you, before you type stupid shitz on the intartubez.
Oh, BTW - if you're going to gay out on the Taco, maybe you should get a room somewhere. Or, at least take it to the barn.
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.
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.
I have other news for you: Windows 7 works fine with non-fully acpi compailant bios'es! You just have to replace the "broken" bootloader with something that works after the install "fails". Even the install disk's repair mode fixes things ;] My own experiance. Just another M$ bullshit ;]
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.
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
The myriad of processors from Intel was just two much to deal with. I bought AMD and never looked back. Until Intel get's it act together on the VT, I'll be recommending AMD.
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.
Does any of that mean that MS didn't force HAV on endusers in order to boost sales of high-end Intel hardware ?
What a total load of retrospective ass covering crapola ;)
"Is how we Linux hippies can somehow twist this story in a way that allows us to bash Microsoft. It doesn't matter how delusional the idea, how disconnected from reality, how devoid of fact or reason, WE MUST BASH MICROSOFT"
;)
What's delusional about MS lying about the specs. The last time they lied to Intel regarding the Vista Capable campaign. I figure the 'Linux hippies' you refer to consists of no one but yourself. Now back to the sixties, dude
"well, it's in all new hardware, it probably isn't worth the time and cost of implementing a software solution"
;)
I think we're all now fully on msg
Microsoft has tens of thousands of employees. It the company really so limited that it must think about every feature that way? I don't think so.
I think the original decision was part of an attempt to force people away from using Windows XP. I'm guessing that some big commercial customers voiced extreme annoyance about that.
So, maybe this is just a normal Microsoft story. The company was, as usual, against the common good. Some external force prevented Microsoft from doing as much evil as it would have liked.
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.
So I heard you liked virtualization...
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.
"Which begs the question: Why the bizarro requirement in the first place?"
No, it doesn't. We need to rid ourselves of the idiotic misuse of this logical technical term. Educate oneself: begthequestion.info
"Your premise is moronic."
You didn't think carefully. Microsoft was forced to make an XP compatibility mode. Otherwise that would require corporate users to re-write some of their software before migrating to Windows XP.
But, possibly the intent of not making the XP compatibility mode work with most older computers was to try to force a hardware upgrade. Remember, we are not Microsoft's customers. Computer makers are Microsoft's customers. Computer makers want to force as many people as possible to buy new computers. Microsoft wants to force as many people as possible to buy new computer so that they will buy another copy of Windows.
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
You need new hardware to run this software. Make it arbitrary! Then after driving hardware sales (faster hardware makes iffy software look 'faster' even if the software is much slower than the 'old' software). Then after all of the money has been made and the market is saturated, remove the arbitrary requirements to 'backfill' the market. Suddenly, no new hardware is required. Software sales without hardware sales. If you are running a near monopoly, you can screw people left and right, and since most customers are too scared or stupid to even think about changing, the monopoly continues. When people ask about changing, they ask one vendor for advice ....one they are contemplating leaving.... and they always (surprise) get the message from that one vendor that the other guys are bad bad bad, complete with words like 'you better not' and 'unavailable' and other nonsense. Imagine that!
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