Slashdot Mirror


VMware-Microsoft Battle Looming

An anonymous reader writes "VMWare released a white paper detailing its concerns with license changes on Microsoft software that may limit the ability to move virtual-machine software around data centers to automate the management of computing work. Two choice quotes: '"Microsoft is looking for any way it can to gain the upper hand," said Diane Greene, the president of VMware.' And, '"This seems to be a far more subtle, informed and polished form of competitive aggression than we've seen from Microsoft in the past," said Andrew I. Gavil, a law professor at Howard University. "And Microsoft has no obligation to facilitate a competitor."'"

27 of 258 comments (clear)

  1. uh, news... by cosmocain · · Score: 4, Funny

    ...Microsoft is using dirty strategies to fight a competitor. Films at 11.

  2. Everybody now by myopiate · · Score: 3, Insightful

    (chorus) Switch to GNU/Linux.

    1. Re:Everybody now by ocbwilg · · Score: 5, Insightful

      (chorus) Switch to GNU/Linux.

      You know, I toyed with the idea of modding your post down as overrated, but then I thought that it made more sense to explain why rather than just do it. To put it simply, not everybody can switch to GNU/Linux for their datacenters. In a lot of vertical markets the only products available (or at least the best products available) run on Windows. Even if there may be a reasonable GNU/Linux alternative available there can be a significant barrier to entry in the form of long-term contracts, or an entrenched user base numbering in the thousands. Let's be realistic here, for many companies (especially larger companies, the type that are most likely to use virtualization) it's not simply a matter of swapping out Vista and Office for Ubuntu and OpenOffice, and then tying it together with OpenLDAP on the back end.

      In my case I work for a software company that develops enterprise application software that is used by most banks, insurance companies, and large manufacturers. We actually started as a Unix-only application, but eventually we had to start developing for Windows simply because that's what the market place demanded. Now we develop and support on both platforms. Our in-house datacenter is heavily virtualized, and our servers are split roughly 50% Windows and 50% Linux/UNIX. Phasing out Windows in our case would not only be incredibly stupid, it would literally kill the company.

      Don't get me wrong, OSS is great. We use it a lot, and it has it's place. But it is not some sort of magic bullet, and it definitely is not the answer to every IT-related question.

    2. Re:Everybody now by zero+time+ghost · · Score: 5, Informative

      I manage 100s of VMs with VMWare's Virtual Infrastructure, and I call bullshit on your whole post my good man.

      "Actual state of management software is ... poor. On other side, the people who have developed their own management for cheap (e.g. blade) hosts farms - feel least urge to switch to VMs from real hosts. For well managed environment with redundant hardware it is really waste to burn CPU cycles of emulation. (*)"

      The actual state of the management software is excellent. Have you used Virtual Center 3? Care to elaborate with your details? I can: it's easy to organize a huge farm of VM's, prioritize them based on their CPU and RAM needs, move VMs from one physical host to another on the fly, generate alerts on nearly anything and customize actions based on those alerts, on and on. There is only one thing I don't like so far about VC/VI, and that is how LUNs on the ESX hosts are managed.

      "VMs solve no particular problem, but just propagate problem of poor OS management to another level - hardware/emulated hardware."

      It solves two problems off the top of my head: hardware proliferation, and hardware failure.

      We have a glut of CPU speed and RAM space, but the chasses surrounding those chips are still expensive. Not just expensive in terms of the box itself, but in the cost of powering and cooling the server as well as the spacial cost of having it in the rack. The solution is to have one physical server do more than one job. The way to do that safely and sanely is to virtualize.

      Another major problem VMs solve is hardware failure. Right now, in my own virtual datacenter, I pretty much don't care about anything less than a whole blade going down. If there is a single blip in the hardware, Virtual Infrastructure migrates the VMs off of the faulty hardware automatically, *without interrupting the VMs*. In other words, for 99% of all hardware failures, my VMs keep running and I can swap out the bad physical server without disturbing anything. Zero downtime. I still cluster at the OS level, too, so in reality I am only worried about my whole datacenter being nuked. Similarly, I don't care too much about hardware replacement cycles anymore either. When a warranty expires, I push all the VMs off of the box and unrack it. We unpack the replacement box, rack it & install ESX, and that's it. The Virtual Center will automatically shuffle VMs onto the new hardware.

      "In the end, when box is plain hardware you can always pull the plug. Try to emulate that with compromised/erroneous VM which started hogging all system resources from other VMs - and management interface too."

      Hehe. 'You try to open the door, but *there's too much blood on the knob!*' You are defining an extremely specific problem and treating it like it's a general issue with virtualization, but I will play along.

      Here is what would happen in my environment. First the VC would automatically migrate all of the other VMs away from the crazy VM. Once the crazy VM was isolated, I could pull the plug on the box if I felt like that was my only option. Then I would activate a clone of the VM (I clone every freshly minted server and put the clone on ice--try doing that with nothing but "OS management"), restore data from backup if necessary, and away we go on an fresh, uncompromised server. Meanwhile I can go back and examine the crazy VM at my leisure and have it completely sandboxed.

      The state of the art in virtualization is not a single server running a few linux instances, sir. Check out where VMWare (and probably Microsoft) is heading and you will see that things are rapidly evolving. I'm talking a quantum leap in datacenter management here, the biggest thing since commodity hardware.

  3. Sigh... by djupedal · · Score: 4, Insightful

    "This seems to be a far more subtle, informed and polished form of competitive aggression"

    Just wait a bit - I'm sure that by the time it hits the front page and the dust settles, it will prove to only be another example of the heavy-handed recidivism we've all come to expect out of redmond. MS can't innovate...can't spot new markets...can't ignore a plum in someone else's grasp, without the targeting systems being brought online. '...Microsoft has no obligation to facilitate a competitor'

    As has been said in the past - investing in MS is asking to have your own money used against you in the marketplace.

  4. Quasinominative Determinism by ettlz · · Score: 5, Funny

    Andrew I. Gavil, a law professor

    I wonder if he has judicial ambitions.

  5. Not news by paganizer · · Score: 3, Informative

    It's not as if anyone in charge of a datacenter is going to be foolish enough to run Vista; most places that require things to work have a predominance of Windows 2000 server, with a few win2k3, Win NT4 and OS/2 boxes.
    banks and government won't touch it; heck, the U.S. Military made it a criminal offense to run Windows XP on a secured network, until microsoft bribed them with a few thousand essentially free licenses.

    --
    Why, yes, I AM a Pagan Libertarian.
  6. It's Microsoft being themselves by Vskye · · Score: 4, Insightful

    Same old Microsoft. They can't invent crap anymore, so when a company such as VMware comes out with something that works, is innovative, MS does what they do what they always do best..., restrict the competition. I hate MS just like most /. users, but just once I'd like to see them actually create something original. (yep.. and like that will happen anytime soon)

    --
    Life was hell, then I discovered Linux...
    1. Re:It's Microsoft being themselves by BuR4N · · Score: 4, Funny

      "but just once I'd like to see them actually create something original"

      I think your out of line here...there is allot going on in Redmon that must be a "first"...just check these fine examples, no prior art here (no "post art" either)!

      http://en.wikipedia.org/wiki/Clippy
      http://en.wikipedia.org/wiki/Microsoft_bob

      --
      http://www.intellipool.se/ - Intellipool Network Monitor
  7. Bring it on. by plierhead · · Score: 4, Insightful

    Bring it on Microsoft.

    Pissing off the suits that run large data centers and have drunk the virtualization koolaid might just backfire big time for MS. When those execs realise that linux is free to virtualize they'll have a TCO factor bigger than anyone can hide sitting right in front of them. Microsoft will be shafting themselves if they try preventing virtualization.

    --

    [x] auto-moderate all posts by this user as insightful

  8. restricting windows on VMWare? by apodyopsis · · Score: 5, Interesting

    I'm confused here, maybe some of you poeple who use virtual machines (more than me) can help me out. I've posted a few questions and points I am either interested in, or do not understand..

    =============

    Where is the boundary between a "virtual machine" and a "real one"?

    After all, the BIOS is definately part of the machine/motherboard and thats SW. If there is another layer of SW inbetween your OS and you HW why should that be any different? I would treat a "virtual" machine as essentially the same as a "real" one - surely in the eyes of the law they must be the same, no?

    M$ changing the license restrictions seems as though they are essentialy stepping outside the OS box and determining the physical HW you are and are not allowed to run on. Whats the legal situation here, has this been tried and testing in a court?

    Can they actually prevent any version of Windows from running in a VM if that version of Windows cannot detect it?

    At the end of they day if a court rules a VM and a real PC are legally the same, where would that leave M$?

    1. Re:restricting windows on VMWare? by ocbwilg · · Score: 4, Informative

      Can they actually prevent any version of Windows from running in a VM if that version of Windows cannot detect it?

      If it cannot detect the VM then technically, no. But they can legally, then when it comes time to do a license audit they will discover how the licensed software is being used, and you can get dinged.

      But I wouldn't put too much faith into them being unable to detect whether they're running in a VM. We were trying to install SP2 to SQL Server 2005 last week on a machine that was runnig on VMWare ESX, and the install failed repeatedly. When we checked the logs there were entries that specifically stated that the SP couldn't be installed in a virtualized environment. So it's certainly detectable. There were some recent articles at the ISC about malware that could detect if it was running in a virtual environment, and there are a number of reliable ways of doing so.

    2. Re:restricting windows on VMWare? by ray-auch · · Score: 4, Informative

      If I remove the BIOS chip and hard disk from my computer, and plug it into a different computer with the same components...

      With Vista you will most likely need to reactivate - which is what MS wants.

      If you activate on a virtual set of components then you can move to a new physical set of components at will, without reactivation - which is what MS doesn't want.

      MS has (half) an argument that virtualisation could subvert the activation stuff (and some of the DRM stuff). The flaw is not in that argument but in the fact that the whole activation-tied-to-hardware thing is fundamentally flawed.

  9. actually, MS does many creative things by alizard · · Score: 4, Insightful

    The MS Research organization is first-rate.

    And they do the same great job of getting things to market that Xerox PARC used to do.

    MS really doesn't know what to do with good ideas.

  10. Re:Virtualization in the OS? by lukas84 · · Score: 5, Interesting

    I suggest you to look into IBM's System i product line.

    They've got a fancy Hypervisor in Hardware (called the FSP, flexible service processor). Linux is supported natively.

    The Managment Console is running Linux, too.

  11. Not a lawyer, but... by julesh · · Score: 3, Interesting

    ... I do know a little legal theory, and it occurs to me that:

    a) the passage that denies permission to run Vista Home et al in a VM is rather ambiguous, in that it could just be a clarification that the rule that allows you to run the higher-end versions in a virtual machine *at the same time* as a real machine doesn't apply. I'd really like to here official comment from MS's lawyers about how they intended this to be interpreted, and so far I haven't seen any.

    b) Even if the ambiguity is only small, it still seems to be there to me, and the rule of contra proferentem should mean it is interpreted in the consumer's favour.

    c) It might not make a difference anyway. As I understand it (and I'll admit my understanding of this area is rather fuzzy, because it is a very obscure corner of contract law that I've only heard about once, so I could be completely wrong), for a contract term to be enforceable, one or the other party must derive some legitimate benefit from it. I don't see what legitimate benefit MS derive from restricting the use of their products in this fashion.

  12. Microsoft has no technical obligation... by rdean400 · · Score: 4, Interesting

    to facilitate a competitor (that is, to make changes to its software so that a competitor's software will run). It does, however, have the moral and legal obligation as a monopoly to not change its license in anti-competitive means.

    If VMWare can show that it's as much about anti-competition as it is anti-piracy, they have a valid argument.

  13. Re:Virtualization in the OS? by weave · · Score: 3, Insightful

    From the article: "When quizzed on Microsoft's plans, Mr. Ballmer replied, "Our view is that virtualization is something that should be built into the operating system.""

    What really belongs in the OS is a self-defense mechanism against malware and viruses, but for whatever reason Microsoft has chosen to let bottom feeders like Symantec live.

    Anti-virus should be an included part of the OS along with updates. It's addressing flaws in the product.

  14. Well, now is the time... by Aaron+Isotton · · Score: 3, Informative

    ...to support VMWare and buy a license for a great piece of software which you're probably using anyway. I am a Debian user and free software enthusiast, but I bought my license for VMWare workstation years ago and never looked back. VMWare is one of the very few commercial programs which I consider worth spending money on. I never had any real problems with it (at least since version 5, which is what I bought), it's fast and a pleasure to use. Maybe Xen or KVM will replace it in the long run, but I'm sure I'll keep on using VMWare for at least another two years.

    I know this sounds like an ad, but even their Linux support is great. I had some issues with VMWare 4 (I was using the trial) and asked on the newsgroup; the answers were quick and helpful.

    VMWare is exactly the way software should be. If you use it and like it you should really consider buying it.

  15. I guess that VMWare should not have played in MS.. by WindBourne · · Score: 3, Insightful

    backyard. Eveyr company wants to play in MS's backyard, build it up to be profitable, and then are surprised that the hog wants their profits through any means possible. What amazes me is that companies have not learned that if they put their best work on MS and slight or even not build on other platforms, they kill their long term viability. Several others that are slowly disappearing are Adobe and Intuit.

    --
    I prefer the "u" in honour as it seems to be missing these days.
  16. Re:Virtualization in the OS? by babbling · · Score: 4, Insightful

    Symantec are not the problem. Symantec is the partial/flawed solution to a problem that Microsoft hasn't fixed. The problem is so large that there is an entire market created by it.

  17. No, this is *very* clever. by babbling · · Score: 4, Insightful

    This is evil-genius-style clever.

    If Microsoft used the license agreement against Virtual Machines at the same time as releasing their own, they'd get into legal trouble. Legal trouble is a pain in the neck, so what they're doing is saying that "Virtual Machines are a security flaw" and banning them from the operating system. Then, later on, as a complete coincidence Microsoft is going to create "a Virtual Machine that is safe". Luckily for them, the coincidence that they have crafted doesn't involve any competitors!

    1. Re:No, this is *very* clever. by Watson+Ladd · · Score: 4, Insightful

      And when has Microsoft ever made something safe? Their solution to buffer overruns is not ASLR(address space layout randomization) but making all programs run in a VM. This doesn't work as a lot of apps still will use unmanaged code and a lot of flaws exist in the security model of the VM. In over 30 years of work on the security model of Unix people still discover flaws, especially in X11. Microsoft only had a security model 7 years old, still in flux, and we are supposed to trust it? They have a horrible track record on security. For them to say that VM's are a security risk is hypocritical considering that .Net is a VM. And for them to say that they make something more secure then the completion would be laughable.

      --
      Inventions have long since reached their limit, and I see no hope for further development.-- Frontinus, 1st cent. AD
  18. Once again we have to ask... by TheNetAvenger · · Score: 3, Interesting

    Once again I as a consumer have to ask. What is MS doing that no one else is doing?

    Windows is a 'licensed use' 'closed source' OS. That up front should tell anyone what they need to know about it.

    So I have to ask, why is there such outcry that you can't install certain Vista versions in a VM for production or daily use? The last time I checked you can't install OSX in a VM NO MATTER WHAT according to the Apple license.

    So every user complaining about this policy from MS, should also write a letter to Apple demanding they let OSX run in VMs legally as well.

    At least MS fully licenses the non Home versions to work in VMs, and still allows developers to test home versions in VMs.

    So if this really angers you, then you have choices. First you should write Apple and all other Closed source OS companies that don't allow their OSes to run in VMs.

    Your next choice is simple, don't like it, don't freaking use it, there are plenty alternatives.

    If companies have a software product THEY NEED that only runs on Windows it would be FAR CHEAPER and easier to install a cheap Windows server and let users run that application via terminal services. Also a lot easier to deploy and support than mass amounts of VMs scattered throughout the offices.

    As for developers, most developers can get free or trial copies of any windows version for testing, and you can get by the 'license' if you need to test your product on Home Basic even in a VM.

    MS is also working with Xen and doing virtualization as a lot of OSS and technical people would want, yet because this puts VMWare at a disadvantage, they get to cry wolf and try to create some PR out of how they get hurt.

    If VMWare wants to cry about this, then fine let them cry. But if they want to succeed then they need to create a product that is simply BETTER than MS's VM or anything out there. That is the only way they will succeed, especially considering they have the entire *nix VM Host market as MS doesn't even try to make a non Windows Host version of their VM software.

    So get over it VMWare and just do what you do best.

    If this was REALLY about OS licensing to run under VMs, then they would also be talking about OSX and tons of other OSes that do not allow usage in VMs; instead they are focusing only on two versions of MS Vista.

    This should have been the first clue to everyone that VMWares motives are not as pure or consumer minded as they want people to believe.

  19. Re:Virtualization in the OS? by msobkow · · Score: 3, Insightful

    "And Microsoft has no obligation to facilitate a competitor."

    But VMWare only is a "competitor" because VMWare was making some money and Microsoft just couldn't let their cash vaccuum miss any potential revenue. Had Microsoft stuck to what they do "best", VMWare wouldn't be a competitor and that whole aspect of the argument would be moot.

    --
    I do not fail; I succeed at finding out what does not work.
  20. Re:Virtualization in the OS? by swillden · · Score: 3, Interesting

    Anti-virus should be an included part of the OS along with updates.

    What's I find interesting about your comment is that Microsoft sees virtualization as a major component of their future anti-virus solution.

    How's that?

    It's what they used to call Palladium, and a key component is the use of virtualization as a kind of a souped-up chroot jail for attack-prone apps -- if you run the browser in its own VM (on top of a minimal, secure OS), then when you close the browser and shut down the VM, any viruses that were able to get in via the browser die with it, assuming they couldn't write themselves into some persistent storage.

    Traditional Windows apps couldn't run in such VMs, of course, but it offers a way to have secure apps without losing the ability to run old apps -- insecurely, of course.

    Oh, and it would also enable all of the strong DRM crud, because it would provide a nice way to protect certain VM'd apps from manipulation/debugging by the user.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  21. Re:But when Apple does this... by itsdapead · · Score: 3, Insightful

    When Apple discourages virtual machines running OSX, this is reluctantly accepted [slashdot.org] because, well... gee, they're Apple and we won't do this unless they say we can.

    Yes there is a double standard - one standard for a small/medium player in a competetive market, and another standard for a company with a near-total monopoly.

    Yes, Apple have a restrictive license that only allows you to run OSX on genuine, non-virtual Apple iron.

    BUT If you don't like that then you are perfectly free to vote with your feet and buy one of the 95%+ of other computer systems available that don't run come with OSX.

    Except... nearly all of those other 95% of systems are running MS software. Even if you complete the uphill struggle to buy one without MS Windows included and run Linux/*BSD/BeOS then sooner or later the 95% of the world who didn't bother will oblige you to use Windows for some task or other.

    Are you saying that Apple, with a few % of the market, should be subject to anti-monopoly rules because their only competetor has a near-monopoly??

    In short, if Apple ever gain 50%+ of the desktop computing market they'll have to face the same anti-trust responsibilities as Microsoft. The only area Apple are within a sniff of that is with iTMS, and then only if you don't count CD sales as digital music distribution. Until then, every time they decide on a restrictive license, impose a lock in, or piss off a software house by incorporating an application they have to balance the benefits to them against a genuine risk of losing customers to the competition.

    In the meantime, MS have - through their Vista licenses and the ridiculous premium charged for "stand alone" copies of Windows - made it extremely expensive to legally run Windows as anything other than your primary operating system.

    Sometime, Apple will have to support virtualization on OSX Server in order to compete with Linux and Windows. Currently, I don't think there is a significant demand (personally, I don't even see why you'd want to use OSX as a server, when its USP is its user interface).

    --
    In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.