Slashdot Mirror


VMware ESX 2 vs. MS Virtual Server?

Saqib Ali asks: "I m sure most of you have heard that Connectix, the makers of Virtual PC/Server, have been acquired by Microsoft. Based on the technology acquired, MS has developed a new product called Microsoft Virtual Server, using which a Windows Server 2003 based server can run multiple operating systems concurrently. I am doing a preliminary analysis of using MS Virtual Server vs. running VMware ESX Server 2.0 on Clustered Linux Environment. Both solutions offer a way of running multiple OSes in a virtual environment using the same underlying OS (Windows 2003 or Linux). Of course, running VMware on Linux, offers the stability, scalability, and reliability of Linux, and also prevents a business form being locked into one single vendor. However running Microsoft Virtual Server does have some merits from a business perspective (vendor viability, reduced licensing costs etc). Any thoughts on merits/benefits/downside of using either of the technology stacks?"

68 comments

  1. I wouldn't consider a Microsoft Virtual Server by DA-MAN · · Score: 5, Funny

    Why trust a company to produce a virtual server, when they have yet to produce a working actual server!!!

    ust my .02 cents.

    --
    Can I get an eye poke?
    Dog House Forum
    1. Re:I wouldn't consider a Microsoft Virtual Server by stonebeat.org · · Score: 2, Informative

      well they didnt actually "produced" the virtual server, they just bought the technology from Connectix. So we should be evaluating how good of product Connectix produced.

    2. Re:I wouldn't consider a Microsoft Virtual Server by DA-MAN · · Score: 2, Interesting

      I don't remember Connectix having a Virtual Server Product. They did have Virtual PC, but that was mostly aimed at running on Mac's.

      I wonder how Microsoft will bastardize this one, Visio use to be nice before it became Microsoft Visio....

      Once again, just my $0.02

      --
      Can I get an eye poke?
      Dog House Forum
    3. Re:I wouldn't consider a Microsoft Virtual Server by Anonymous Coward · · Score: 0

      > Visio use to be nice before it became Microsoft Visio....

      Agree. Same as FoxPro

    4. Re:I wouldn't consider a Microsoft Virtual Server by cmdrbuzz · · Score: 1

      Virtual Server for Windows was in (early) beta when MS bought Connectix.

  2. License? by LennyDotCom · · Score: 2, Interesting

    Virtual Server helps resolve the issues associated with older servers that are out of warranty and diminishing support for earlier hardware and operating systems.
    That sounds fine but if youir running NT4 on an old server and want to move it to a new box running win2003 on a vitual server do you have to buy a new license?
    and what about the fact that M$ has or wil stop supporting NT4

    --
    http://Lenny.com
    1. Re:License? by stonebeat.org · · Score: 1

      MS will stop supporting NT4 if it hasn't yet already, nevertheless there are applications that run only on NT. So businesses will be running NT - whether they use it in a Virtual Evironment or not is a different question.

    2. Re:License? by Jeremiah+Cornelius · · Score: 1
      What is MS's history of treting customers?

      Has VMWare shown they think of you as their hostage?

      What will happen to the MS product if it dominates the market?

      If these were questions people asked when evaluating MS vs. Ashton-Tate, Borland, Lotus, WordPerfect and Novell - things would look quite a bit different.

      Vote with your dollars, and don't support the further monopolization of mid-range IT by MS. The repercussions extend deeper than one product.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
  3. What I want to know is... by HotNeedleOfInquiry · · Score: 3, Funny
    scoff mode

    Do you still have to pay SCO $699 for each Linux instance that you run. Or are they covered by the Microsoft Unix license.

    /scoff mode

    --
    "Eve of Destruction", it's not just for old hippies anymore...
    1. Re:What I want to know is... by the_other_one · · Score: 1, Funny

      Could you have multiple instances on linux running on a Windows box at $699 a pop. You could create a beowulf cluster and have the worlds most expensive, slowest, and most unstable super computer.

      --
      134340: I am not a number. I am a free planet!
    2. Re:What I want to know is... by Josh+Booth · · Score: 2, Funny

      Say you were trying to use VMWare under Linux to create a beowulf cluster of Linux virtual machines each running VMWare each running a beowulf cluster of Linux virtual machines each....

      Ooooohhhh, my head hurts.

    3. Re:What I want to know is... by Thing+1 · · Score: 1
      Say you were trying to use VMWare under Linux to create a beowulf cluster of Linux virtual machines each running VMWare each running a beowulf cluster of Linux virtual machines each....

      Sorry, VMware knows when it's running inside itself and won't allow it. Not sure how, but I know the network "card" and video "card" have "VMware" in their identifier string, so that's a good bet...

      However, there's nothing stopping you from combining technologies -- so you could have VMware under Linux, running a beowulf cluster of Windows Server 2003 virtual machines. Each of these is running MS Virtual Server (which probably has the same checks as VMware so it won't run recursively -- but probably doesn't check to see if it's inside VMware). Set up a beowulf cluster of Linux VMs under MS Virtual Server, and then run VMware instances inside of those. Iterate recursively until you can't use the machine any more. ;-)

      Anyone up to testing this?

      --
      I feel fantastic, and I'm still alive.
  4. 1) It's pre-beta! 2) licensing cheaper? by anon+mouse-cow-aard · · Score: 1

    Who the heck is going to have experience with
    the product, given that it isn't even beta yet?

    Is there any benefit on the licensing side?
    I understood there was no reduced cost for any licenses for virtual machines. MS requires you have a legal copy of the OS for each virtual machine.

  5. VMWare works by Anonymous Coward · · Score: 0

    And it's not Microsoft. That should be enough. I wouldn't be shocked if, in the future, Microsoft products stopped playing nicely with VMWare.

    1. Re:VMWare works by DA-MAN · · Score: 1

      It works, and it's available now. I guess the most important question is when will this guy need it!?!?

      The Microsoft Virtual Server is in pre-beta, and we all know how long it takes Microsoft to release a product, let alone get to the SP1 phase where people are willing to remotely give it trust.

      This guy needs to look at his timeline, this question is like askin what should I get Unreal 2003 or Duke Nukem Forever.

      --
      Can I get an eye poke?
      Dog House Forum
    2. Re:VMWare works by foooo · · Score: 3, Informative

      VMWare works, but Microsoft is trying to make you buy a license for every virtual image on the machine.

      so.... VMWare($300) on top of windows (at least $100) and
      on top of VMWare copies of windows (at least $100) and any copies of office or anything like that (X dollars) TIMES the number of virtual machines that you have saved.

      Or you could run virtual images of linux or whatever.

      But if you bought VMWare with the purpose of being able to inexpensively and quickly deal with multiple Images (for corporate imaging testing or what have you) or multiple MS operating systems.. then they try and rope you into a MSDN license.

      It's nutty

    3. Re:VMWare works by bhtooefr · · Score: 2, Informative

      But this guy is looking at VMware ESX Server 2 and MS Virtual Server. You're using the price for Workstation, which is probably much less than ESX (anyone got a quote?). Virtual PC 5 (for Windows) was approximately $130.

  6. ESX does not run under linux by QuantumG · · Score: 3, Informative

    it has it's own BSD style kernel which does more sophisticated (fair) scheduling and memory management (on-demand page sharing between VMs). People think it's linux based because it has the GNU toolchain ported to it (ie, they're morons).

    --
    How we know is more important than what we know.
    1. Re:ESX does not run under linux by stonebeat.org · · Score: 2, Informative

      Actually ESX technology is not based on either:
      The following is a passage from http://www.vmware.com/products/server/esx_faqs.htm l: "VMware's patented and patent-pending technology serves as the foundation for VMware ESX Server; it is not derived from Linux or FreeBSD." However vmware's GSX technology can run on either Linux or Windows.

    2. Re:ESX does not run under linux by BusterB · · Score: 1, Interesting

      We have two ESX servers running at work. They both came with Redhat as the core OS. The Linux kernel appears to just use a small chunk of memory and is modified to allow processes to grab memory external to their normally allowed virtual address space, while the ESX server software apparently manages the rest of the memory itself. But, the server also runs as a Linux process. It definitely relies in Linux's driver support to support the underlying real hardware. It's neat; they have more than just the GNU toolchain in the Linux instance; there is Perl too, and everything else you would expect.

    3. Re:ESX does not run under linux by spencerogden · · Score: 1

      It is also Linux related in that I believe it uses linux kernel modules for hardware support. However I think the kernel itself is written inhouse and has nothing to do with Linux or BSD. What toolchain to suggest instead of GNU?

    4. Re:ESX does not run under linux by Anonymous Coward · · Score: 4, Informative

      Vmware ESX server does not rely on Linux kernel modules for hardware support. It does rely on ESX kernel modules for hardware support.

      The console OS is Linux and can see any device Linux is capable of seeing with the proper driver. However, if the ESX kernel does not support your device (RAID controller, NIC, etc.) you can't assign it for use by virtual machines. Currently ESX server only supports a small subset of devices in comparison to Linux. The ESX kernel does use the kernel module paradigm, but that is as far as the similarity goes.

      The console OS (Redhat Linux) serves primarily as a bootloader for the ESX kernel. It does run processes which aid in I/O for Remote Console sessions among other things, but that's it. The ESX kernel sees the console OS as just another virtual machine.

    5. Re:ESX does not run under linux by sql*kitten · · Score: 1
      We have two ESX servers running at work. They both came with Redhat as the core OS.

      I wouldn't describe it as the "core" OS, it's just there to provide a basic interface so you can log in an administer the underlying virtualization layer. It's analogous to using DOS to boot Netware. From the docs:

      ESX Server runs natively on server hardware, without a host operating system. This allows it to more fully manage the hardware resources and provide the highest levels of security and performance isolation. ESX Server also incorporates a console operating system based on a Linux 2.4 kernel that is used to boot the ESX Server virtualization layer. It also runs ESX Server administration applications.
    6. Re:ESX does not run under linux by stonebeat.org · · Score: 1

      I made a mistake in the posting. I meant vmware GSX (which runs on Linux) and not vmware ESX

    7. Re:ESX does not run under linux by chunkwhite86 · · Score: 2, Informative

      it has it's own BSD style kernel which does more sophisticated (fair) scheduling and memory management (on-demand page sharing between VMs). People think it's linux based because it has the GNU toolchain ported to it (ie, they're morons).

      Yes, it does. ESX server is based on RedHat 7.2. It's a Linux kernel that boots when you power on the machine. Only at the end of the bootup process, the Linux kernel is swapped out into it's own single CPU VM, and the VMware kernel is swapped in and controls the remaining CPU's and the individual VM's.

      --
      I'd rather be a conservative nutjob than a liberal with no nuts and no job.
    8. Re:ESX does not run under linux by TheMellonCollied · · Score: 1

      The vmkernel is not BSD! It is a proprietary kernel completely developed in-house. Also, ESX definitely does not "run" on Linux. The Red Hat 7.2 is used as a bootstrap loader for the vmkernel. The Red Hat installation is the console OS (vmnix) and it runs a "privileged guest" of the vmkernel after the kernel starts. To say that ESX runs on Linux would be like saying Windows 2000 "runs" on ntldr.

  7. A major downside by Radical+Rad · · Score: 3, Funny
    Any thoughts on merits/benefits/downside of using either of the technology stacks?"

    Yeah, if I "consolidate" all my servers onto a Windows 2003 box running Connectix, then my servers (all non-MS) would go down every time some script kiddy wants to show the world how 3l337 he is with a new worm.

    1. Re:A major downside by stonebeat.org · · Score: 1

      Offcourse if I consolidate all my server/services on Windows 2003, I will make sure it is always patched up and behind a highly secure firewall, Intrusion detection system, and honey pots if applicable ;)

    2. Re:A major downside by Radical+Rad · · Score: 3, Funny
      Offcourse if I consolidate all my server/services on Windows 2003

      Was that a Freudian slip? Either you or your subconcious is very clever.

      Seriously, there have been enough MS exploits that use legitimate ports and spread so quickly that something would get through and take out the whole thing.

      I have heard the promises that people could consolidate many servers and domains to a lesser number running on one of these things but I can't help but chuckle at the thought of running windows in windows on windows in a production environment. This MS Virual Server is just a way to get people to pay more money for what they were promised years ago: a stable platform with separate memory spaces to keep apps from stepping on each other. Now instead of an nt server running 5 apps you can pay for an "enterprise" nt server and ms terminal server and 5 more copies of regular nt server plus the 5 apps and all the various "client access" licenses. But stability might be somewhat improved. Gartner should put that in their TCO pipe and smoke it... instead of crack.

    3. Re:A major downside by Anonymous Coward · · Score: 0

      No, the script kiddie would show how inept the admin is. OSs don't kill networks, people kill networks.

      Get a life!

    4. Re:A major downside by Anonymous Coward · · Score: 0

      Was that a Freudian slip? Either you or your subconcious is very clever...This MS Virual Server

      Et tu :)

      - Itwerx

      (posting AC because I've modded in this article)

  8. Still a Single Vendor by swdunlop · · Score: 2, Insightful


    Of course, running VMware on Linux, offers the stability, scalability, and reliability of Linux, and also prevents a business form being locked into one single vendor.

    You will still be locked into a single vendor; the one that supplies VMware, which is not Free Software; while this company doesn't have the reputation of jettisoning products on a marketing department's whim, you still need to worry about what happens if the company in question goes under, or is purchased by an aggressive competitor, like Microsoft.

    1. Re:Still a Single Vendor by stonebeat.org · · Score: 2, Insightful

      That is very valid argument. I didn't think of that.

      However with MS Virtual Server, there are 2 components (2003 and MS Virtual Server) that are locking into a vendor.
      On the other hand, in the Linux + VMware GSX solution, there only one component (vmware GSX) that is locking us in a vendor

    2. Re:Still a Single Vendor by swdunlop · · Score: 2, Interesting

      That is definately a key point, as there would be two licenses to worry about, instead of just one. If Microsoft terminated either product, your company would need to migrate. That being said, our site has been very happy using Linux+GSX for hosting multiple Win2k servers.

    3. Re:Still a Single Vendor by QuantumG · · Score: 1

      actually, it's the sales department which determines when each version of VMWare ships. Their customers tend to buy the product at their end of their budget cycle (gotta spend all the money you are given or you won't get as much next quarter) and if there isn't a release available there's hell to pay.

      --
      How we know is more important than what we know.
  9. GSX runs on Linux by stonebeat.org · · Score: 1

    I m sorry, I mentioned vmware ESX in the article, but instead it is GSX that is supported on Linux.

    ESX directly runs on System Hardware (kinda like an OS by itself) and is not based on Linux or BSD Kernel.

  10. What OS's are supported? by blogan · · Score: 1

    Microsoft's page isn't exactly clear what OS's are supported. I see they mention NT, 2000, 2003 and OS/2 (which shares some roots with NT). Maybe soon we'll see a patch submitted to Linus so new kernels work on this. I can see support for older OS's being a problem. "OS/2 doesn't work.", "Call IBM" "NT doesn't work.", "Sorry, it's no longer supported."

    1. Re:What OS's are supported? by bhtooefr · · Score: 1

      This isn't the server version, but here's something interesting (similar system requirements to VMware Workstation 4.0):

      http://www.microsoft.com/windowsxp/virtualpc/dow nl oads/trial.asp

      ALL Windows versions 3.1 and up, DOS, Netware, OS/2, Linux (they fucking specifically say Linux), etc., etc. It takes LOADS of HDD space, though (500 FSCKING MB FOR WINDOWS 95?!?!).

  11. Virtual Server is Connectix Virtual PC with more by Anonymous Coward · · Score: 0

    so many OSes that work in Virtual PC will work in Virtual Server. I think they did add some new features - SCSI support, to name one.
    it has VNC display support, a web interface.. I had an old beta from February. Was kinda buggy, some stuff wasnt implemented yet, etc.

  12. don't put words in my mouth by QuantumG · · Score: 2, Insightful

    it's BSD style, not "based on" FreeBSD.

    --
    How we know is more important than what we know.
  13. you're an idiot by QuantumG · · Score: 0, Offtopic

    that's all

    --
    How we know is more important than what we know.
  14. Hey! by pb · · Score: 0

    QuantumG, I didn't even realize it was you the first time! Sorry if I messed up your 'facts' there, buddy.

    Anyhow, here's the link; cheers!

    --
    pb Reply or e-mail; don't vaguely moderate.
    1. Re:Hey! by QuantumG · · Score: 1

      it's the console vm's kernel, you moron.

      --
      How we know is more important than what we know.
  15. Re:compiling the ESX kernel by bobv-pillars-net · · Score: 1
    ...(they recommend compiling it with gcc 2.9.6)

    Do you happen to have a link to that recommendation? I'd like a copy for my idiocy files. Blasted incompatible unreliable buggy (unprintable) version of a compiler!

    --
    The Web is like Usenet, but
    the elephants are untrained.
  16. MS didn't build the Virtual Server by BoomerSooner · · Score: 1

    it's based of Connectix work.

    That being said I have both Virtual PC and VMWare and VMWare is far superior on Windows. I haven't tried Virtual PC for the Mac but VMWare on Linux runs my offices demo server quite nicely.

  17. Re:compiling the ESX kernel by pb · · Score: 1

    it's in the README, which you can get from the link that I gave QuantumG, elsewhere in this thread; I'll quote it in full here:

    Included is the source for the following packages:

    1) vmnix kernel (linux/)
    Modified linux v2.4.9 kernel

    2) VMware ESX Server installer (installer/)
    Modified version of anaconda-7.2

    3) vmklinux
    Based on 2.2 and 2.4 linux kernel code

    4) vmkload_mod
    Based on insmod source from the modutils package

    5) rrdtool-1.0.40 and wu-ftpd-2.6.1 (COSApps)
    Tools included with the VMware ESX Service Console

    6) esxtop
    Based on the source for 'top' from the procps package

    You must be running redhat 7.2, with gcc 2.96 installed to compile
    these packages. See README files located in the subdirectories for
    descriptions and compilation instructions.

    Unless explicitly stated otherwise, all of the files in this package are
    distributed under the GNU General Public License - see the accompanying
    COPYING file for more details.

    --
    pb Reply or e-mail; don't vaguely moderate.
  18. Just start to THINK! by QaDeS · · Score: 1

    Even if the Microsoft thingy should support running any guest operating system NOW, they will most likely stop this as soon as they stomped VMware into the ground.

    I just can't believe people still jump on this stuff after M$ showed this kind of action on so many occasions.

  19. Support problem by macemoneta · · Score: 1

    How good do you think Microsoft's support is going to be when you have a problem with Linux in the VMs? VMWare is OS neutral; Microsoft is not. When a company calls a product you use a cancer, I don't think you want their help solving a problem; you lose all your leverage.

    --

    Can You Say Linux? I Knew That You Could.

  20. Oxymoron: (n) e.g. Microsoft and merit. by i_r_sensitive · · Score: 1
    However running Microsoft Virtual Server does have some merits from a business perspective (vendor viability, reduced licensing costs etc). Any thoughts on merits/benefits/downside of using either of the technology stacks?"
    Okay, you mention two "merits" here, let's discuss these: Vendor Viability: Sure, M$ is quickly maturing to the realm of death and taxes, abhorrent but inevitable. However, the benefit of this vendors perceived longevity needs to be balanced against the companies oft stated desire to monoplize Operating Systems. Even the announcement stresses the migration benefits of MSVS. While the claims may be dubious, the goal is not, to provide an environment which encourages migration to an M$ environment. The other item to balance off against this is the vendor's long-standing history of OS issues and application exploits. In the same week that M$ release five security advisories, many to do with flagship applications, I can't believe anyone would seriously be considering MSVS as an alternative. Reduced Licensing Costs: Compared to what? Running Vmware on 2k3? But, VMWare also runs on Linux, and if you have the in-house expertise to handle Linux, why would you incur the higher OS cost of using 2k3? Why would you take the higher overhead of an M$ OS for your host OS? The benefits to me seem minimal, and more than offset by the attendant liabilities.
    --
    "Talk minus action equals nothing" - Joey Shithead, D.O.A.
    "Talk minus action equals /." -
    1. Re:Oxymoron: (n) e.g. Microsoft and merit. by wfbush · · Score: 1
      The other item to balance off against this is the vendor's long-standing history of OS issues and application exploits.

      There's one more item, related to "vendor viability": Sure, M$ will likely be around for a while, but there is no guarantee that any of their products will be viable. They can and will stop supporting any product if they think they can get more money out of it i.e. force people to upgrade.

      So using VM software to run older OSes and apps on newer hardware is probably less viable with an M$ product.

    2. Re:Oxymoron: (n) e.g. Microsoft and merit. by inteller · · Score: 1

      ....and if you have the in-house expertise to handle Linux. hey you just hit the nail on the head. Let's see which there are more of, qualified MS experts or qualified Linux experts. I bet on average you can get an MS expert a lot cheaper than a Linux expert. Invest in the infrasructure then hire the peons, not skimp on infrastructure and hire a snobby Linux zealot with a god complex.

    3. Re:Oxymoron: (n) e.g. Microsoft and merit. by i_r_sensitive · · Score: 1
      ....and if you have the in-house expertise to handle Linux. hey you just hit the nail on the head. Let's see which there are more of, qualified MS experts or qualified Linux experts. I bet on average you can get an MS expert a lot cheaper than a Linux expert. Invest in the infrasructure then hire the peons, not skimp on infrastructure and hire a snobby Linux zealot with a god complex.

      Now you, my friend, have hit it exactly on the head.

      Ever heard the old adage you get what you pay for? Comparing a qualified Linux expert to the average MCSE is like comparing a PhD in Nuclear Physics to Billy-Bob at your local Shell Station. They aren't comparable. Sure your PhD can pump his own gas, but I ain't lettin' my good ol' boy Billy Bob anywhere near my cyclotron, know what I mean?

      Okay, I'll be charitable, let's replace Billy-Bob with an O-line breaking, quarterback-smooshing, running-back-defiling ogre of a Defensive Tackle who can't read a dinner menu. He's still a trained professional, but I'm still not letting him near my cyclotron.

      An MCSE is (in my experience: hiring some, supervising many, firing almost _ALL_) very like someone who got through high school, but is still functionally illiterate. I've worked with MCSEs who don't know what a hosts table is FCS! Functional illiteracy comparatively.

      So, if you want to spend a bunch of money on a great infrastructure and then turn it over to a bunch of functional illiterates and call that an effective computing environment, you go right ahead. My point is that if you have the snobby Linux zealot, you may not need that infrastructure, or you may, but you can be assured that you are going to get all the bang for all those bucks you spent on that infrastructure. If you turn it over to your local dime a dozen MCSE, you'll get dime a dozen performance. Even if you are going to use M$ products, you are still better off with a competent Unix professional, at least they understand what is going on behind the point and click interface, unlike your average MCSE, who is lucky to know what is going on in front of the point and click interface.

      Mod me down, here comes the troll!

      MCSE - A shorter acronym for PEBCAK
      --
      "Talk minus action equals nothing" - Joey Shithead, D.O.A.
      "Talk minus action equals /." -
  21. as I said by QuantumG · · Score: 1
    It doesn't run under linux. This kind of confusion is the reason why ESX doesn't sell. People see the RedHat bootup and think ESX is just a preinstall of GSX on Linux. Even when you tell them that it has it's own kernel they say "but it runs under linux right?".. here's a tip, a kernel doesn't run under anything, otherwise it's not a kernel.. that's the definition of 'kernel', it's the piece of software that doesn't run underneigth anything else on your machine.

    Of course, sales and marketing have told engineering about this since the first day the product launched, but engineering doesn't do anything about it.

    --
    How we know is more important than what we know.
    1. Re:as I said by Tony-A · · Score: 1

      here's a tip, a kernel doesn't run under anything, otherwise it's not a kernel
      But the definition of a VM is that one or more kernels run under the VM.

      Other than backdoors into the VM, the kernel is incapable of even knowing that it is running under a VM.

      Boot into DOS. This is DOS running in Real Mode.
      Load a memory manager. Now the memory manager has control of the hardware. DOS is running in V86 Mode, the exact same DOS. If the memory manager decided to excercise it's control, it would be capable of doing anything it wanted, mostly without the knowledge of and certainly without any cooperation from DOS.

  22. Paper about ESX by Anonymous Coward · · Score: 0

    If you're evaluating these products in detail, check out http://www.waldspurger.org/carl/papers/esx-mem-osd i02.pdf (which won best paper at OSDI 2002) for a detailed discussion of memory management in ESX. Among other neat things, the ESX kernel can transparently share duplicated pages of memory between VMs, allowing you to run, say, 6 gigs of guest memory on a 3 gig host machine without swapping to disk. The paper is definitely worthwhile for anybody interested in operating systems.

  23. Virtual server doesn't exist by JohnZed · · Score: 1

    Microsoft Virtual Server is the most extreme example of vaporware I've seen in a LOOONG time. Connectix announced it in 2002, and now Microsoft is saying that it won't be ready until 2004. Meanwhile, ESX has been used in production at Fortune 500 companies for 2 years+. Hmm...

  24. viable vendor by Anonymous Coward · · Score: 0

    umm, vmware isn't a viable vendor?

  25. which one? by pb · · Score: 1

    I'll admit, details are a bit sparse in the documentation; still, it does say that vmnix is the modified linux kernel (2.4.9) that VMware ESX server runs, which sounds pretty telling to me, O uncivil one.

    --
    pb Reply or e-mail; don't vaguely moderate.
    1. Re:which one? by QuantumG · · Score: 1
      VMware ESX server runs

      and there it is... The VMware ESX kernel runs the modified linux kernel.

      --
      How we know is more important than what we know.
  26. Better off with GSX server by nurb432 · · Score: 1

    Its the 'native' version of vmware.. From what I have seen, its a better product then ESX, for either host OS. ( guest OS is not relevant in this context )

    --
    ---- Booth was a patriot ----
  27. Arrgh by nurb432 · · Score: 1

    Ingore my post.. i got the 2 products backwards again...

    They should have had a better naming system...

    Move on, nothing else to see here...

    --
    ---- Booth was a patriot ----
  28. Virtualization vs Emulation by cmdrbuzz · · Score: 1
    Don't forget that Virtual PC is emulating the CPU and VMware is virtualizing the CPU.

    Thats why there is a Virtual PC for Mac (PowerPC) and no VMware for Mac.

    VMware is a lot similar to IBM's z/VM, in that non-privileged CPU instructions run directly on the hardware.
    Think VM assists in MVS (ala z/OS).

    So VMware will always be faster, but will never leave the x86 arch in its current form.

    1. Re:Virtualization vs Emulation by drinkypoo · · Score: 1

      Maybe the reason virtual server isn't out yet is that they're working on a virtualizing emulator. Or, well, a virtualizer. But you know what I mean, kind of like you can use bochs with plex86 now, or do I have that backwards?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Virtualization vs Emulation by Anonymous Coward · · Score: 0

      Actually, Virtual PC for Windows virtualizes the CPU too. It's Virtual PC for Macintosh which does emulation.

  29. don't be an idiot by Anonymous Coward · · Score: 0
  30. that certainly is one possible interpretation by pb · · Score: 1

    [nt]

    --
    pb Reply or e-mail; don't vaguely moderate.
  31. test by Anonymous Coward · · Score: 0


    test