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."'"

52 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 ThePhilips · · Score: 2, Insightful

      Get back to us when you have 100s of VMs to host.

      Get back to us when you have really managed 100s of VMs.

      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. (*)

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

      Needless to add, people did the same under Linux for ages with User-Mode-Linux and (what now is called) Xen. But again, the solutions to be manageable heavily rely on the fact that guest and host systems are the very same Linux (with little differences on kernel side).

      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.

      (*) Okay, I know the post is pointless, since CPU cycles are now the cheapest resource. But yet, even to my surprise, there are people who care about how fit their systems are and do not tolerate another layer which in hardware/software solves OSs problems.

      --
      All hope abandon ye who enter here.
    3. Re:Everybody now by Tim+C · · Score: 2, Insightful

      I work at a web agency/hosting/application management company, and we're starting to move from dedicated separate boxes to VMs on a single, beefy box for our dev and test servers. That way we can have two machines hosting (typically) two load-balanced web/app servers and a database server, rather than 6. (In reality, in dev at least we'd skip the load-balancing and any associated clustering to save on hardware)

      It takes up less space in the hosting centre (thus reducing hosting costs) and our machine room, it costs less in hardware (even with the VMWare licences and beefier boxes, and we mostly use Linux as the server OS) and costs less in power.

      I can't comment on management issues (as I'm a developer), but the set up on my last project has been running for about 18 months with very very few issues.

    4. 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.

    5. Re:Everybody now by Anonymous Coward · · Score: 2, Insightful

      I don't care if you use a VM or not but I can tell your opinions are not data center based.
      I can tell you several advantages of using VM's though.

      First and formost when thinking virtual is not every server and every server process makes sense running in a virtual environment. VMWare provides tools and guidance for you to determine if a specific server you have running right now at your site is a good candidate. No one ever claimed everything should be run virtualized. Basically, consistent high disk I/O, mem, or cpu is not a good candidate. Sounds like every server ever deployed would be a bad candidate but you would be surprised how many machine sit there not doing much. Remember, we are talking average IT infastructure here, not Yahoo's DB servers and not youtubes file servers.

      We are talking about dhcp servers, fax servers, domain controllers, document indexing servers, access control or RAS servers, SQL, management stations, smtp scanning servers, virus management consoles, web monitoring like Websense, document management servers, message routing servers, Blackberry and Blackberry attachment servers, IT stuff like backup exec or whatever backup solution you use. Portal front ends and auth servers for public wireless access, Citrix front ends like Nfuse, Outlook Web access... The list goes on and on and on.

      Consolidation of hardware and redundancy of those types of servers are easier and cheaper with a virtual solution.
      I'll use MS clusters for an example. Assume you have a DHCP, SQL, Exchange, and a file server for an office of 600 people. You could have one physical server for each node of the cluster and one virtual node for the second node. The virtual server can be spec'd out to meet the demand of the highest of those four servers (most likely Exchange). Now, you have a two cluster node for each of those servers listed above for the cost of one physical server. Each has redundancy that you did not have before.

      Take it a few steps further now. Lets say you want to run some utility servers on the VM servers as well. Trend micro virus scanning, an Enterprise Blackberry server, and some cost recovery system that accounting needs. Those can be placed on that SAME Virtual server. Now you have your second nodes of the cluster and some actual active servers running as well.
      Take it one more step.. You add a second virtual server because you are expanding and you want redundacy with the virtual servers. You now add 5-15 more virtual machines and the total of 20 machines can be shared between the two virtual servers. VMWare provides tools for automatically moving virtual machines between virtual servers while running to balance load across all virtual servers.

      Assue a year from now, you want to add a third virtual server but decide to get a much larger unit from IBM instead of Dell. Wow, different HD controllers, different network cards, different video. Windows 2003 is going to freak out and not work on that new server. Oh wait, the hardware is virtualized through VMWare and the virtual machines can move back and forth with NO problems.

      One note, A SAN or common storage is required to move and share virtual machines between virtual servers.

      We have two HP DL380's with 8GB ram running 8 virtual machines each and we are getting more Virtual servers as our leases expire on our physical servers. There are numerous possibilities of things we can do, specially with the ability to assign a virtual machine to a different VM network switch which may be on a different vlan or even a different network segment all together. We can manage and deploy servers to our public and private lan from the same place.

      Think of virtualization for the typcial IT department in the business world, not an ISP or a data providers or developers world.

      A side note. If you have more then one virtual server running the same OS, as much of the memory as possible is shared between the running virtual machines. In laymans terms, if you are running sol.exe o

  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.

    1. Re:Sigh... by scsirob · · Score: 2, Insightful

      MS may not have an obligation to facilitate it's competitors, but they are damn well obliged to facilitate their customers.

      Since MS wants to play in the high-end comuting environment, they must play nice with the computing wishes of these demanding users or they will be dropped like a hot potatoe by datacenters. VMWare is currently the only real game in town for datacenter consolidation, MS Virtual Server and XEN are waaay behind.

      --
      To Terminate, or not to Terminate, that's the question - SCSIROB
    2. Re:Sigh... by gnalre · · Score: 2, Insightful

      Actually I thought ever since MS was found to be a de-facto monopoly they did in fact have a legal requirement to help there competitors. For example anti-virus firms, even though MS has its own MS product,

      --
      Choose your allies carefully, it is highly unlikely you will be held accountable for the actions of your enemies
  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.
    1. Re:Not news by paganizer · · Score: 2, Insightful

      No, I apparently can not. There doesn't seem to be a link out there; however, this is what my memory can serve up. When XP came out, DOD CERT checked it, and said that it should not be used on any network where classified material was available; after SP1, they checked it again, and still it was banned. I left government work for a while after that, and did not keep up with it. Then, about 3 years ago, a friend was wanting to get my opinion on some laptops he was getting for his unit; he forwarded me a link to the systems, and they only came with XP home, I told him that as far as I remembered, XP was not allowed. He said that a few months back, Microsoft had done a big deal with the folks at the pentagon who do the policy on what is allowed, and after something like 3 million XP licenses were added to the deal, the security restriction from DOD CERT went away. This could be some really good mental memory hallucination, I DO hate XP and the way that MS has tried to kill Win2k in its favor, but I'm pretty sure that was the deal; I have to think that someone else on /. remembers it. NOTE: there are some posts that come up on google referencing this, but they do not provide an informational link to a press report or anything like that.

      --
      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

    1. Re:Bring it on. by artgeeq · · Score: 2, Insightful

      VMWare ESX is the enterprise-class product from VMWare for the data center. It is not clear that the licensing changes would effect VMWare ESX, which is, I believe, a modified version of Linux that can host many virtual machines, or that they could be enforced.

      I tend to agree more with the post, and not so much with the article. This is not like the Netscape fiasco. We are dealing with reliable systems and disaster recovery here, not how information is presented. What scares me a bit is that comeone at the executive level, somewhere, is going to get the idea that the product that is less reliable and less mature is somehow better because of licensing or because it is "free" (and that grunts such as myself will have to painfully explain to them otherwise). The major cost of software, especially this type of software, is not in its initial purchase price.

  8. Re:No VMs? Fine. by mumblestheclown · · Score: 2, Insightful

    microsoft, with its billions, is blind in making strategic business decisions, but you, some slashdot postager, is the one who truly understands what is best for microsoft's business. right.

  9. 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 growse · · Score: 2, Interesting

      But in the same way, my windows desktop at home is hardware independent. If I remove the BIOS chip and hard disk from my computer, and plug it into a different computer with the same components, that's technically a different machine, but you could also say that my windows installation is a physical installation rather than a virtual one. The OS doesn't necessarily know it's running on a different CPU.

      In my view, an OS instance is an OS instance. GP is right - what's wrong with just another small SW layer between the hardware and the OS? How does that make what the OS instance is any different?

      --
      There is nothing interesting going on at my blog
    2. 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.

    3. Re:restricting windows on VMWare? by Professor_UNIX · · Score: 2, Informative

      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.
      VMWare doesn't make any attempt at hiding the fact that you're running in a virtual machine. Where did you get the idea that it did? For example, if you're running a Linux guest, just take a look at the dmesg output after bootup and count the number of times you see VMWare in the list. Go into the Windows hardware device manager and count the number of times you see VMWare in there too. They COULD fake the hardware names returned to the OS and Microsoft would be none the wiser unless they took additional steps to try and figure it out, but they don't. A simple look at the devices attached to the system will quickly show it's a VM.
    4. 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.

  10. 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.

  11. 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.

  12. Re:Virtualization in the OS? by TapeCutter · · Score: 2, Interesting

    "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.""

    VM == Virtually Microsoft's?

    --
    And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
  13. 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.

  14. 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.

    1. Re:Microsoft has no technical obligation... by vhogemann · · Score: 2, Interesting

      The funny thing is... VMWare actually adds value to Windows.

      I think that this is a very bad move from Microsoft... as usual, they can't be satisfied with just a piece of the pie, they want everything. VMWare is a mature application, that adds real value to their product. If people can't use VMWare + Windows probably they'll switch to VMWare+Linux, or KVM, or Xen.

      What if Microsoft's Virtual PC just don't catch on? They're risking to loose this entire virtualization market to Linux, both as host and guest OS.

      --
      ---- You know how some doctors have the Messiah complex - they need to save the world? You've got the "Rubik's" complex
  15. Re:Virtualization in the OS? by ocbwilg · · Score: 2, 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."" VM == Virtually Microsoft's?

    The problem with Ballmer's comment (not yours) is that the Operating System is what we want to virtualize. While VMWare ESX is probably almost as much of an operating system as Windows is, it's definitely a lot more stripped down and tightly focused on doing only one thing (providing virtualization) and doing it well. If you have a general purpose OS that also supports VMs, and you run VMs inside that OS, then you're asking for problems. Not just from a performance standpoint, but security as well. This kind of thinking is one of the reasons why their Virtual Server product is so far behind VMWare's ESX.

  16. Bye bye, VMware.... by Caspian · · Score: 2, Insightful

    It was a good run. Seriously-- once MS decides to push you out of the market, you're as good as dead.

    Example 1: WinCE vs. PalmOS
    Example 2: Xbox 360 vs. Playstation 3
    Example 3: Internet Explorer vs. Netscape
    Example 4: Doubledisk/doublespace vs. Stacker
    Example 5: Windows vs. OS/2

    etc. etc. etc. Sometimes, it takes a while-- like how they're still struggling to make MSN relevant-- but, in the end, they always get what they want. They simply have too much money-- and, therefore, too much clout-- not to.

    I'm not saying I agree with this. Quite the opposite, in fact. However, VMware is doomed. (Film at eleven.) You read it here first. Call me a pessimist, but I've seen the writing on the wall. I should have seen it coming when Microsoft released Virtual PC as freeware.

    --
    With spending like this, exactly what are "conservatives" conserving?
    1. Re:Bye bye, VMware.... by -noefordeg- · · Score: 2, Informative

      I don't catch your point...

      In two weeks we (I and someone else from my company) are going to VMWare presentation.
      We are already using VMWare, but currently only for testing. Our plan is to move several systems over to a few new servers (from Dell) running VMWare with Linux guest OS's.
      Why is VMWare doomed?
      I can't see the connection between anything MS does and what VMWare get from us...

      Right now, we've got one computer left here running Windows. The rest are all OSX or Ubuntu.

    2. Re:Bye bye, VMware.... by jellomizer · · Score: 2, Interesting

      Example 1: WinCE vs. PalmOS
      Really? PalmOS is still widely used. Look at the smart Phones being sold There is usually at least 2 with PalmOS maybe 3 with Windows CE, and the rest are blackberries.

      Example 2: Xbox 360 vs. Playstation 3
      Don't Blame Microsoft on this on Sony was just SUPID! Too little to Late, way to expensive. Sony played a Vista with its Playstation 3.

      Example 3: Internet Explorer vs. Netscape
      Well netscape went underground and opened its source for the Mozilla foundation. Then Firefox came along based on Netscape Code.

      Example 4: Doubledisk/doublespace vs. Stacker
      Didn't Microsoft steal that code? And just use a hex editor to change the name or something. Also for software like this you really can't blame MS as an attempt to kill the competition it is more of a way to give functionality to their OS. Programs like Stacker, Desqview, Quemm... Are really hacks to the current OS, that do what the OS Should do anyways.

      Example 5: Windows vs. OS/2
      I guess some of the blame can go to Microsoft and some evil, because they advertised Windows 95 to be far more then what it was, Windows Vista is one step closer to offering what Microsoft promised us in Windows 95. So when people had to choose they had to pick of OS/2 Warp or Windows 95 With Microsoft making seem like the ultimate OS vs. OS/2 more legit advertisements got people wanting Windows 95 mostly because of fears of OS/2 Running DOS/Windows Apps Slower then windows 3.1. Which in reality I doubt anyone except for people you need to benchmark that stuff will notice the difference. Also OS/2 did a lousy marketing job on OS/2 Warp. I saw the add when it was released and I knew what the product was before the add. But to anyone who didn't know what OS/2 Warp was wouldn't get it. "It was a bunch of people going wow this is cool" but that is about it.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  17. 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.

  18. 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.

  19. 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.
  20. 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.

  21. 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
  22. Re:Competitors? by _Shad0w_ · · Score: 2, Insightful

    Microsoft makes Virtual PC, which is a competitor to VMWare's products. Not much of a competitor admitidly.

    --

    Yeah, I had a sig once; I got bored of it.

  23. 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.

  24. 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.
  25. And who does this? No one in the data center. by gelfling · · Score: 2, Informative

    Aside from developers and a tiny group of specialists who need access to a particular app? In the datacenter world this is anathema. No one running a gaggle of boxes would ever seriously consider this and get paid for it. Cheaper and easier by far to throw up one more server and spend the 0.04 FTE (1/25th of a person) it takes to run it.

    And if you seriously considering multi image same system partitioning of Windows then you my friend need to re examine what it is you're doing. LPARs are not for Windows code. Go out and by an iSeries midrange or an AIX machine.

    1. Re:And who does this? No one in the data center. by ibbieta · · Score: 2, Informative

      Aside from developers and a tiny group of specialists who need access to a particular app? In the datacenter world this is anathema. No one running a gaggle of boxes would ever seriously consider this and get paid for it. Cheaper and easier by far to throw up one more server and spend the 0.04 FTE (1/25th of a person) it takes to run it. I assume you mean that you think it irresponsible to be running Windows in a virtuallized environment? If so, I hate to tell you this but I'm seeing more and more companies, some with very large and capable tech staff, doing just that. At first it was for testing and development, true, but it just became easier to copy the image files onto the production VM serves. I even know of one credit union that has ALL production Windows servers as VMs.

      The ease of backups-restores is one big reason for the love being directed at VM servers. Just shut the machine down, copy some files, and boom! a point-in-time backup. Moving an application from testing to production, same things as a backup with just loading the files into a new VMWare (banks require physical separation of hardware between development/testing/production so these files are actually copied to a new VMserver).

      To be honest, I'm an old systems admin, too, and thought VMs were just for testing and development and was a bit disturbed to see big, careful companies using them for production. Worse, I'm a consultant installing some heavy Windows applications that can overwhelm even beefy machines and virtuallizing my servers just slows them down. I am not privy to the reasons for why the move to VMs but I think management was getting tired of all the problem tickets that amounted to "hardware problem with ServerX, moving to new hardware -- 20 hours". (Yeah, way too long to move a server, but at large institutions everything takes longer than it should; in my network, creating a new VM image takes about 15 minutes, with the procedures and paperwork at the credit union this will take 2 hours and require 5 people be involved.)

      --ibbieta

  26. Re:Virtualization in the OS? by SlOrbA · · Score: 2, Insightful

    If it isn't in the Operating System it can't be embedded into the Windows and so MicroSoft can't kill other implementations.

    Actually in x86 platforms Virtualisation should be at least on the OS because if there is no virtualisation initialisation the system can be exposed to a virualisation enabled malware.

  27. IBM screwed up OS/2 all by themselves. by cdn-programmer · · Score: 2, Interesting

    Example 5: Windows vs. OS/2
    These are the ones that matter. MS won the desktop war by convincing manufacturers to bundle Windows with every PC. IE won the browser wars by being bundled with Windows, and therefore most PCs. Bundling the virtualization with Windows will be a major advantage for MS, but it's still no guarantee. They don't even own the server market like they do with desktops


    Bull! IBM shot themselves in the foot so many times I am suprised they could still find feet to shoot.

    I used OS/2 for years on a dual head set up. The 1st nightmare was configuring the dual heads. Finally a chap in Boca Raton was nice enough to tell me the magic - all was undocumented of course. It worked. The 8514 card and the Svga card actually worked as advertised (by IBM in their Red Books - which I bought)

    But... when I switched from a DOS window it froze and blanked the screen. If I switched from an OS/2 session it just froze the screen. I think it was some perverse manager who figured that in order to encourage running OS/2 apps and discourage running DOS apps that they should pull this dirty little trick. As a developer - it just made my life difficult and meant that I couldn't tell my clients how great OS/2 really was... and why? Because it wasn't. How would anyone feel if the moment a window lost focus the OS blanked it? Hell - you don't need to look at your code buddy when you are running the app! What do you want a 2nd monitor for anyways? But in an OS/2 session they didn't need to blank anything.

    Next - the single thread problem and the OS locking up. It was never fixed that I know of. I never did upgrade past Warp. I ended up buying NT4.0 much as I hated to do so - and it ran beautifully and ran the monitors properly too.

    Then, a blessing was OS/2 apps! Microsoft did it right. I used Brief under NT4.0 - the OS/2 version. It ran BETTER in NT than it ever did on OS/2 and I didn't have to put up with Frozen screens.

    Oh.. tech support! I bought and paid for tech support the whole time I had OS/2. I used it many more times than I wanted too. IBM made me wait on hold - and when the level #1 intake operators came on line they INSISTED on getting every hardware configuration detail and details of my CONFIG.SYS file.. and others. This was even if I already KNEW what the problem was and wanted to simply ask for a work around. This happened OVER and OVER and OVER and OVER.

    I offered to write a program for IBM which would collect all this information and send it via modem to their tech support people. My GAWD but it was horrible having to give them the same damn information every damn time. How hard would it have been for a company like IBM to set up a damn database indexed for instance by my phone number and record the conf once? Nope!

    I wrote letters to them and suggested setting up an app to scan the system for pertinant config and hardware information... so it could be xmitted via modem. I never heard back from them.

    Well - I bought Warp. I replaced it with NT 4.0. I have never looked back.

    IBM did it all by themselves. It was their own arrogance and incompetance which destroyed the product. Even the simplest issues could not be effectively dealt with.

  28. Propaganda and FUD by mqatrombone · · Score: 2, Informative

    This smells like FUD to me. I'm only aware of three changes in licensing about Microsoft operating systems.

    1) Windows Server 2003 R2 - 4 licenses for VMs running on Server 2003 Enterprise and unlimited VMs running on Server 2003 Datacenter
    2) Windows Vista - Can be run only in a VM on Ultimate and Enterprise, but Enterprise does give you 4 licenses of itself to run in a VM on Enterprise. Value add from Software Assurance? Say it isn't so.
    3) Windows Server 2003 R2 - A VM that isn't being run isn't considered to be a license in use.

    What is VMWare complaining about? I'm really curious about this white paper.

    --
    If 76 Trombones really led the big parade, why did they have anyone else in it?
  29. Re:No VMs? Fine. by mgblst · · Score: 2, Funny

    Microsoft got bigger, Windows got more complicated with already so many features, one customer became less important as they got bigger, and no doubt that more than one customer asked for something stupid or impossible.

  30. 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.
  31. 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.
  32. Re:Virtualization in the OS? by kabz · · Score: 2, Interesting

    Seems like Microsoft Windows is just starting to be regarded as a giant, expensive to configure application that runs Office, and a few other corporately vital apps.

    As such, it makes complete sense to commoditize it by treating it as an app to run in a virtual machine.

    I already have my XP virtualized in Parallels, where it is occasionally fired up to run IE controls. Windows is so delicate, and such a pain to configure, that it makes complete sense to make one image then deploy it using virtualization.

    --
    -- "It's not stalking if you're married!" My Wife.
  33. Re:Virtualization in the OS? by plalonde2 · · Score: 2, Insightful

    The anti-virus products are actually the virus. They drain more system and system administration resources than the viruses they block (and do *nothing* against the others) and their presence lets the OS vendors who should be dealing with security issues directy shirk that duty. Symantec and co. are the problem, not its cure.