Slashdot Mirror


VMware to Make Server Product Free (as in beer)

yahyamf writes "CNET News.com is reporting that in the face of increasing competition in the OS virtualization market VMWare is going to give away its GSX server product for free, in the hope that customers who try it will eventually migrate to the more powerful ESX server. The company recently released a free VMWare Player which could only run but not create virtual machines. The company faces competition from rival products such as SWsoft's Virtuozzo, Mircrosoft's Virtual Server, as well as open source software like Xen"

50 of 216 comments (clear)

  1. hey don't leave out qemu by jomas1 · · Score: 3, Informative

    If you are going to list software that will let you run an operating system from within another don't leave out qemu ahref=http://fabrice.bellard.free.fr/qemu/rel=url2 html-2228http://fabrice.bellard.free.fr/qemu/>

    Qemu may not run as fast as vmware does now but it's here, it's free and you can change whatever you want about it. The same is not true for vmware

    1. Re:hey don't leave out qemu by birder · · Score: 4, Informative

      What are you talking about? VMware allows you to make the MAC address anything you want. Edit the config file and change the generatedAddress for the ethernet controller.

    2. Re:hey don't leave out qemu by kbnielsen · · Score: 2, Insightful

      No, vmware lets you assign a MAC address inside the range 00:50:56:XX:YY:ZZ, which is quite reasonable, since this block is assigned to VMWare, and thereby they avoid to conflict with other MAC's on the ether... They also avoid a whole host of problems with people faking mac addresses and such, so I think it's quite reasonable to have this practice...

    3. Re:hey don't leave out qemu by Professor_UNIX · · Score: 5, Insightful

      Why do proprietary fanatics think they need to be apologists for commercial software? Because VMWare produces some fantastic products. I couldn't care less if software is commercial or not as long as it fits my needs and my budget. There is simply no open source alternative to VMWare right now that even comes close to what it does at the speeds it does it. Quit being a blind open source fanatic and look around the world sometime. The vast majority of people have no problem paying for software if it fits their needs.

    4. Re:hey don't leave out qemu by floop · · Score: 2, Informative
      The original statement that VMWare doens't permit arbitrary MAC addresse is true. You are restricted to the VMWare OUI. This doesn't allow for Multicast MAC assignemnt along with a ton of other legitimate reasons to manually set a MAC outside the OUI.

      The "vast majority of people" live on 2 dollars a day and don't have computers. The vast majority of computer users don't purchase software that didn't come on their computer. The vast majority of IT depts don't purchase software without some sort of justification. A good IT person would be able to evaluate their needs and match to the appropriate solution given resources available.

      Doesn't mean that VMWare doesn't rock. Just that there are considerations you and other failed to take into account when marking the parent as flamebait.

    5. Re:hey don't leave out qemu by Tim+C · · Score: 2, Informative

      And what it makes to you that your os of choice (OS/2) have disapeared despite quite a fan base just because it was closed source ?

      What makes you think OS/2 was his OS of choice? It was only one of several that he listed.

      Don't you think that you should invest in non-closed source knowledge ?

      He ends his post by saying "I also support OSS that does a better job than commercial alternatives. It's about choice.". Did you even read it?

  2. Mmm? by Anonymous Coward · · Score: 5, Funny

    So where can I find this free beer everyone keeps talking about?

  3. Mircrosoft by raffe · · Score: 2, Insightful

    I bet this is more because og Mircrosoft than Xen. When Mircrosoft is moving into a field competitors usally shiver....

    1. Re:Mircrosoft by oni · · Score: 2, Insightful

      I can't speak for anyone else, but I have absolutely zero interest in Microsoft's VM products.

      Yeah, but the way the world works is that people who wouldn't normally even think about VMs will think about them for no other reason than the fact that it came for free with their OS. Microsoft will have a button somewhere labeled, "click here to make this a VM" and people who don't even know what a VM is will click it.

      Don't believe me? Take a look at the form that comes up after you install Win2k3 advanced server. The form is labeled "Configure this Server" and it has a checkbox labeled, "make this a DNS server" and the word DNS is underlined. When you click it, if gives you the definition of DNS. Isn't that great? If you don't already know what DNS is, then you don't have any business setting one up. But that's the microsoft way. That's their target audience.

      How hard is it to sell a DNS server to these people? "Do we need DNS? Wait, don't we already have that in windows?" VMWare is understandably worried that their product will soon be viewed in exactly the same way. "A VM? Do we need that? Wait, we already have it right here, just click that button"

  4. Intel VT by lisaparratt · · Score: 4, Interesting

    I would have thought the most scary thing facing VMware is Intel Virtualisation Technology - it makes what was previously very hard fairly simple. It also doesn't require the guest OSes to be hacked, ala Xen.

    I suspect we can expect to see a huge swathe of hypervisors being released over the next few months, if only so x86 Mac users can run Windows apps!

    1. Re:Intel VT by rfinnvik · · Score: 5, Insightful

      VMWare's real "killer app" in my opinion is VirtualCenter/VMotion. The management tool is better than anything else I've seen for managing virtual infrastructure - and the ability to move live VMs between hardware nodes is just impressive :)

    2. Re:Intel VT by lisaparratt · · Score: 2, Insightful

      The hard part of virtualising x86 is having to rewrite guest code on the fly to make sure it doesn't do anything that'd break it out of it's sand box. Vanderpool alleiviates the need to do this.

      This changes writing a hypervisor like VMWare from a very, very difficult challenge to just moderately taxing.

      This totally changes the landscape - VMWare won't be obsolete, it's just going to have an awful lot more competition in future. The few technical advantages it has over the competition are now handed to everyone on a plate. They've now got to focus on mindshare and administrative ease, since they can no longer rest on their technical laurels.

    3. Re:Intel VT by TheRaven64 · · Score: 4, Informative
      There are two parts to virtualisation:
      1. CPU virtualisation.
      2. Peripheral virtualisation
      The first of these is practically impossible on x86. VMWare and VirtualPC (x86 edition) manage it using some really, really, ugly hacks that kill performance (and then some more hacks to boost performance). Xen works by ignoring the problem. An operating system on Xen must be ported to not use any of the x86 instructions that don't easily allow virtualisation.

      The second is not very hard conceptually. You just need to do some kind of multiplexing and then expose your devices as if they are a fairly general device of the category. While this is conceptually simple, it is practically a lot of work. Again, Xen dodges the problem here slightly be requiring that the domain 0 OS supports the hardware, and then providing generic virtualisation routines for various categories of device (consumer VMWare and VPC do the same - not sure about the server lines).

      VT / Vanderpool / whatever make the first of these much easier (about as easy as it's been on RISC machines for the past decade or so and on mainframes for the past three. Yay for x86). They do very little for the second part of the puzzle. On PowerPC or SPARC, it might be possible to implement OpenFirmware drivers for hardware that are virtualisation-aware (IBM's servers do something a bit like this). I don't know if EFI has this capability; if it does then things like VMWare might become obsolete.

      Oh, the final part of the puzzle is clustering. Xen and the server-grade VM systems provide clustering support which allows virtual machines to be transparently migrated between cluster nodes. This is quite useful, since you can run N VMs on M machines, and squeeze the low-activity ones onto a small number of nodes, then have then migrated to their own node when they are under high load.

      --
      I am TheRaven on Soylent News
    4. Re:Intel VT by ThePhilips · · Score: 2, Interesting

      It definitely sounds good. At least it removes another 'contra' from long list of IA-32/AMD64 and PowerPC differences. As many of you have known for some time people who run Linux on PPC enjoyed free ride with Mac-On-Linux project. Check http://maconlinux.org/

      On side note, after seeing how easy virtualization can happen with Open Source kernels - e.g. User Mode Linux, Xen, Plex, coLinux, etc - me keeps wandering why M$ haven't done that with WinNT kernels. There are only few true obstacles in x86 "architecture" which prevent effective virtualization - VMware is solving all of them at very high level and of course tried in past to charge premium for that. Xen modifies kernel so that overhead of virtualization is negligible - it's not another computer emulator, it's just kernel running as a ordinary OS process. (Anyway, user tasks see computer only as it is reflected by kernel and device drivers (-: )

      I know M$ likes only good cash cows (like M$ Office franchise) but as OS kernel concerned, the modifications to allow it to run in virtual machine are truly not that big. Check-out the coLinux - it's neat. http://wiki.colinux.org/cgi-bin/ConvertingDistribu tions

      P.S. Or is it what M$ Windows Advanced Server for?

      --
      All hope abandon ye who enter here.
    5. Re:Intel VT by jcnnghm · · Score: 3, Interesting

      Xen can also move live VMs between hardware nodes (only non-responsive for tens of milliseconds). It's going to be a very powerful tool once all chips have virtualization capabilities.

      --
      You don't make the poor richer by making the rich poorer. - Winston Churchill
    6. Re:Intel VT by cruelfood · · Score: 3, Insightful

      You're a bit misinformed about device virtualization, at least the way VMware does it.

      Devices aren't merely multiplexed. They're virtualized (or emulated, if you prefer that term.)

      What's the difference? For disks, the virtual machine doesn't see the actual disk controller or disk. It sees an emulated IDE or SCSI controller, and the virtual machine's disk storage is backed by a file in the host operating system. Reads and writes to the disk file go through normal Windows or Linux file APIs on the host. (Raw disk passthrough is possible, but it's still more complicated than multiplexing.)

      For network devices, the virtual machine sees an emulated NIC. (AMD PCNet32, Intel E1000, or VMware vmxnet device, depending on the VM.) Packets are sent on the physical network via the Windows or Linux networking layers. To receive incoming packets, the host's network card is put in promiscuous mode, and packets destined for the virtual machine's MAC are filtered to it.

      Other types of devices are fully emulated. Video? The VM has a VMware SVGA card. Updates to video are emulated, and the contents of the virtual frame buffer can be displayed via VNC, the VMware remote console, or drawn via X or Windows GDI calls via the local UI. Other types of devices in the virtual machine, like interrupt controllers, the chipset, and so on, are fully implemented in software. No "multiplexing" is done with these devices.

      I also disagree that the processor emulation is a "hack" that "kills performance." While x86 is not trap-and-emulate style virtualizable, binary translation is hardly a "hack". And it hardly kills performance. Projects like Dynamo have been improving performance of compiled code by dynamically translating it. And Intel announced plans to kill off x86 emulation in IA-64 hardware, because their software solution was good enough.

  5. What about existing customers? by tumutbound · · Score: 5, Interesting

    I'd certainly be pissed off if I'd just paid $1400 for GSX only to be told this week it's free.
    I've been paying for regular updates to VMWorkstation over the years, does this mean I can stop and just use the free products?
    That said, it's still worth the money I've been paying.

    1. Re:What about existing customers? by ds_job · · Score: 2, Interesting

      Just imagine if you've just been done for downloading it off a p2p network and applying a cracked serial. That'd hurt. I'm not speaking from experience, just imagining...

    2. Re:What about existing customers? by meringuoid · · Score: 3, Insightful
      I'd certainly be pissed off if I'd just paid $1400 for GSX only to be told this week it's free.

      Why? If you thought $1400 was too much for the product, you wouldn't have bought it. Since you bought the product, clearly you thought that what you were getting was worth more than what you were paying for it. So you were happy with the deal you made with VMware. Surely you are not petty enough to begrudge others the better deal that they are now getting?

      Though I'm certainly not the religious sort, I'm reminded of the Christian parable of the workers in the vineyard. You made your own deal with VMware, and you were happy with it. What business is it of yours if, since then, they have changed their plans and now offer better deals to others?

      --
      Real Daleks don't climb stairs - they level the building.
  6. Limitations? by Comatose51 · · Score: 5, Interesting
    This is not a troll comment but can it run on a cluster? Will it detect that it's running on a Linux cluster and refuse to run? Here's what I'm thinking, a bunch of older computers clustered using one of those Live CDs that make them part a cluster just by popping the CDs in. I believe the software, can't remember the name, also does single system image or something like that where the cluster appears as a single system to the applications. Then run VMWare on top and run any OS you want! In my scenario, I'll be running Windows because our software is written for Windows but takes forever to run. I've considered building a cluster but couldn't think of an easy way to make it run on Linux. I was going to try Xen but VMWare is super easy to use, if my experience using it on Windows carries over to Linux.

    Very exciting indeed.

    --
    EvilCON - Made Famous by /.
    1. Re:Limitations? by hal2814 · · Score: 2, Insightful

      I'm not so sure that shoehorning an app (and an OS for that matter) that thinks it's running on a signle node into a cluster is such a good idea. The benefits of a cluster are typically only realized when the underlying software has some idea of what's going on and can organize data sufficiently accross the nodes. At best case, I'm guessing there will be an awfully chatty system in place that may get marginally better performance or may even get worse performance than running the app on a single node.

    2. Re:Limitations? by stikves · · Score: 2, Informative

      "This is not a troll comment but can it run on a cluster?"

      No it's not troll, but it's totally uniformed. Currently SMP (multiprocessor/multithreaded) VMware is only supported on ESX server as an addon. As ESX runs on bare hardware (it's GSX who runs as a Linux application), there is currently no support for "virtual multiple CPUs in Linux". (Xen does this, but it's not the issue now).

      Additionally OpenMOSIX (which comes with ClusterKnoppix - I guess you meant this by "those Live CDs"), does not to "SMP like" processing. Instead it combines the processes in a "global system view" state. (Too much technical details here, but a multiple threads are not migrated -- see HOWTO).

      Moreover, it would be slow because of obvious issues -- as in network based access to disk and shared memory!

      Finally multiple GSX servers managed from a single point is already possible with VMWare virtual center (google this yourselves is left for an exercise).

      Sorry, but your suggestion will not work (at least under current circumstances).

  7. Re:Good Move! by jaseuk · · Score: 3, Interesting

    GSX does all you need. So why if GSX is free would you need workstation?

    Jason.

  8. Re:Good Move! by jruschme · · Score: 4, Interesting

    Which leaves the even bigger question of where this all leaves Workstation?

    Player makes sense... small run-only environment, embeddable, etc.

    But if GSX goes free what would a pricy workstation offer?

  9. Strange thing to say ... by cablepokerface · · Score: 4, Interesting

    in the hope that customers who try it will eventually migrate to the more powerful ESX server

    It's not only more powerful, it's fundamentally different. It's requires a different sort of administration. Also, the usage is different. gsx wil rarely be actively used in high uptime required production environments, esx will. esx also enables functionalities such als vmotion (if you have a san that is) and will be used more often in blade server configs.

    I really wonder if people will view esx as an 'upgrade' to gsx.

  10. Why Not Use Patents? by ObsessiveMathsFreak · · Score: 3, Insightful

    To play devils advocate here, why isn't VMWare resorting to patents to muscle out the competition? Why compete when a government monopoly can take care of competition for you?

    Are all their patents pending?

    --
    May the Maths Be with you!
    1. Re:Why Not Use Patents? by Dr.+Evil · · Score: 3, Funny

      VMWare is not in a good position to use patents to protect their IP.

      The reason being that they actually have a product. This means they can be countersued for things like using a drop down menu, displaying a rectangle on a screen, ingenious stuff like that.

  11. Why no free VMware Workstation? by Mark+Gillespie · · Score: 2, Interesting

    Seems that GSX Server does everything VMWare Workstation does, so why would anyone buy VMware Workstation, when GSX Server is free? Don't quite understand that bit...

    1. Re:Why no free VMware Workstation? by Real_Handy · · Score: 2, Informative

      Because GSX won't run on all of those XP machines? Server only (win2x and linux afaik).

    2. Re:Why no free VMware Workstation? by JustASlashDotGuy · · Score: 2, Insightful


      Workstation is probably more widely used the GSX server. They are
      different Animals. Even tho GSX server may end up being free, we may
      install it to a single production server. However, we will also
      continue buying Workstation for testing. There are several people with
      Workstation installed to the laptops so they can create/run various
      VM's. On my laptop alone, I hav about 8 VM's that I use for testing
      (various OS, VPN softwares, script design, etc). I would never install
      GSX to my laptop.

    3. Re:Why no free VMware Workstation? by paradizelost · · Score: 2, Informative

      Workstation provides for multiple snapshots that you can switch between, GSX only allows for 1 snapshot. you can take a snapshot, then revert to that snapshot, undoing everything you've just done. w/ workstatino, you can have 30 snapshots( at time's i've been almost to that point) and switch between them as you please.

      --
      "In a world without walls and fences, who needs Windows and Gates?"
  12. Re:Good Move! by greyspk · · Score: 2, Insightful

    I haven't compared them 1 to 1, but I would expect that GSX has higher requirements for your server, both memory and CPU wise. If that is not the case, you're absolutely right - GSX is all I'm going to need. One more positive side is that open sourcing GSX may trigger few separate public projects based on it (depends on what license GSX sources will be provided under).

  13. Wait a second.... by Anonymous Coward · · Score: 4, Informative

    Doesn't TFA say they are "expected" to make their product free?

    expected != will

  14. Speculation by Simon+(S2) · · Score: 2, Funny

    This is all news.com.com.com.com speculation. In TFA they state: "VMware may gain two advantages from the move..." blablabla "VMware didn't immediately respond to requests for comment."
    So the title "VMware to Make Server Product Free (as in beer)" is misleading at best.

    --
    I just don't trust anything that bleeds for five days and doesn't die.
    1. Re:Speculation by NetJunkie · · Score: 2, Informative

      It's not speculation. I've heard it from VMware people this week.

  15. Virtualiazation isn't going to be . . . by base3 · · Score: 2, Insightful

    . . . of much commercial value for long, given that the model of computing is headed for a TCPA/Palladium/Remote attestation/Client assurance/DRM lockdown. Emulating "trusted" computing would defeat the whole purpose of the "content" and computing industries' march towards that model. That, and they'll buy laws making even attempting such emulation punishable by just short of death.

    --
    One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
  16. Re:Good Move! by Zathrus · · Score: 2, Informative

    q[One more positive side is that open sourcing GSX may trigger few separate public projects based on it (depends on what license GSX sources will be provided under).]q

    It's provided under the "here are the binaries; you may not reverse engineer them" license.

    Read the topic again -- free as in beer, not free as in speech. Just because I give you the beer for free doesn't mean I have to provide you the recipe.

  17. Re:Good Move! by StDave · · Score: 2, Interesting

    It is free as in beer, not as in speech. The source will not be opened from what the article says.

  18. Related Stories? by gmf · · Score: 3, Funny

    What is it with this "Related Stories" thing? Is that new, or why did I never notice it before?

    And most importantly: Will it also list the dupes? :)

  19. Not GSX by Anonymous Coward · · Score: 2, Informative

    The free product will be called VMware Server, not GSX. I am not sure if they will continue with GSX as a separate product, but I was under the impression that they will. I had initially heard about this here.

  20. Re:Good Move! by jaseuk · · Score: 5, Interesting

    Well the only major difference between GSX and workstation is that GSX allows you to control startup / shutdown of virtual machines so that they can start at windows boot, it also supports remote administration and I believe you can manage the machines through their other tools such as VirtualCentre. I don't believe there is any great difference in system requirements for GSX over Workstation.

    Ultimately GSX, Workstation and player are all essentially the same technology. ESX only differs by being a custom linux distribution making it very easy to install and a web interface to control operation and a few enterprise features such as VLANS and the VMotion addons. They've also moved some of the virtual machine I/O and handling into a kernel module rather than running in userland to gain some sort of performance advantage. Rather strangely ESX seems to be slow at supporting iSCSI. Of course there are also tools to limit bandwidth and control CPU usage on individual machines, whereas with GSX and Workstation it's a free for all.

    Personally after trialling VMWARE ESX and GSX I actually prefer GSX. The "grow on use" disk type available for GSX is certainly better for small single use servers, flexibility to grow and keeps image sizes down for backups. I also really miss the client CD-ROM and floppy support which again is absent from ESX. The control panel also seems quite flakey.

    Personally I feel that VMWARE have got the pricing structure wrong somehow. The only way to truely consolidate is to use big machines (20-30GB RAM) the problem here is that the cost of 4GB RAM modules is rather prohibitive, then add in some server redundancy and all the VMWARE licensing fees and it doesn't make sense any more. I'd actually prefer to pay a reasonable cost per active virtual machine, that way we can keep redundant hardware and move machines around as we see fit for performance or DR purposes.

    I'm quite keen for GSX to be free or cheap, it'll then make cost sense to consider a VMWare strategy.

    Jason.

  21. You can make your own VMs for VMware player by soboroff · · Score: 4, Informative
    "The company recently released a free VMWare Player which could only run but not create virtual machines."

    Sure you can. Take a gander at http://www.hackaday.com/entry/1234000153064739/

    What you don't get with VMware player is the nifty GUI to help you with the setup.
  22. Re:Good Move! by jbarr · · Score: 3, Informative
    jaseuk wrote:
    "GSX does all you need. So why if GSX is free would you need workstation?"

    According to the Data Sheets found here:

    http://www.vmware.com/pdf/gsx_specs.pdf
    http://www.vmware.com/pdf/ws_specs.pdf

    GSX requires a "server" host, while Workstation does not:

    GSX:
    Host Operating Systems
    Runs on Microsoft Windows 2000 Server and Advanced Server; Windows Server 2003, Web, Standard, Enterprise and x64 Editions, and Linux server host OSes

    Workstation:
    Host Operating Systems
    Windows 2000 Professional and Server, Windows XP (32- and 64-bit), Windows Server 2003 (32- and 64-bit)
    Popular 32-bit Linux distributions from Red Hat, SUSE, Ubuntu and Mandrake; select RHEL and SLES 64-bit

    -Jim Barr
    http://jimstips.com/
    --
    My mom always said, "Jim, you're 1 in a million." Given the current population, there are 7000 of me. God help us all!
  23. Re:Good Move! by paradizelost · · Score: 4, Informative

    Multiple Snapshots. GSX Does not have them, workstation does. and let me tell you, It's damn nice.

    --
    "In a world without walls and fences, who needs Windows and Gates?"
  24. Re:SECONDED by j0217995 · · Score: 4, Informative

    I use a combination of them as well to run Linux on my windows box. If you use qemu to create the image file in vmware format you can then setup any vmplayer file to run any operating system. Currently I have the following image files, Ubuntu (Breezy), Ubuntu (Dapper), Windows 2003 Server, Debian, and BSD. All files were created first in qemu then I installed through VMPlayer. Runs as well as an official VM Player file available for download. See https://wiki.ubuntu.com/VMwarePlayerAndQemu for more information.

  25. Re:Good Move! by koadic · · Score: 2, Informative

    As the parent says, Workstation lets you keep a practically unlimited tree of snapshots, which is great for testing. Server can only take a single snapshot. (Sure, it can be copied and stashed somewhere manually, but the Workstation interface is much nicer and the incremental shapshots more efficient.)

  26. Re:Good Move! by andersbergh · · Score: 3, Informative

    I've successfully used GSX in XP. It doesn't even tell you that your OS is unsupported when you install it.

  27. Why I switched from VMWare to Qemu by this+great+guy · · Score: 2, Informative

    I use virtualization a lot, both at work and for for personal needs. I have got about 20 disk images, and my work typically requires me to run 2 or 3 virtual machines concurrently. Three or 4 years ago, I was using VMWare because it was basically the only product that worked well at the time. However I have switched to Qemu since then, because IMHO it is technically superior. Here is why:

    • Qemu copy-on-write disk image formats allows me to have as many different disk images of the same OS while using MUCH LESS disk space than VMWare. For example at work, I have N images of Windows XP, each configured with a different set of applications, parameters, etc, and all of them can be run concurrently. For me the lack of this feature in VMWare is clearly a showstopper, if I had to use VMWare I would have to create litteraly N different images, and it would use N times the disk space of Qemu (!). I cannot understand why VMWare STILL doesn't offer you such a feature after so many years.
    • Qemu copy-on-write disk image formats also allows me to create a new disk image instantly (less than 1 sec). The closest existing VMWare feature ("snapshot") is slow and not as convenient.
    • Qemu offers the option of being run on a machine without an X server. This is useful because my servers running Qemu don't need to be bloated with X, they are also more secure (no exported X display, etc). It is also much faster to run, create and manage virtual machines using Qemu's command line tools than using VMWare's GUI. And graphical guest OSes are usually accessed over VNC-like protocols so the lack of X doesn't matter.
    • Qemu, like VMWare, uses a kernel module to implement different techniques to speed up virtualization. However Qemu kernel module is smaller (less potential security vulns) and more stable (in my experience).
    • Qemu offers you the possibility of NOT using this kernel module. It can be very useful when you need to fire it up on a random machine: you don't have the obtain its kernel headers and you don't need to compile a kernel module.
    • Qemu offers a CLI tool to create, convert, commit (copy-on-write) disk images; the main Qemu binary is also a CLI tool; and the monitor device can also be redirected to standard input/output. The obvious advantage of this is that the whole Qemu suite is scriptable and flexible. I have written quite a few scripts to ease my life, you can control basically everything: start, shutdown, reboot, eject CD drives, save screenshots, pause/continue emulation, etc. I know that VMWare has recently introduced a Perl API, but I don't know if it is as complete as what you can do with Qemu.
    • Qemu is open-source, relies on standard kernel components and is generally better engineered. For example it uses the existing tun/tap driver and lets the users use iptables, to create virtual network interfaces and do NAT/bridging, etc. While VMWare re-implements THEIR virtual interfaces, THEIR nat code and THEIR bridging code, unnecessarily adding potential bugs and complexity to the whole system. VMWare has to do this because they have to support other technically inferior host OSes (Windows has no tun/tap driver, its firewall is not as powerful as iptables, etc).

    The only feature I would like to see implemented in Qemu is the one allowing you to make real USB devices available to guest OSes. But anyway VMWare has so many disadvantages (see above) that for me it's a clear no-go. I think people praising VMWare are maybe too close-minded and don't realize its disadvantages because they have no experience with other virtualization softwares...

  28. Re:WTF by civilizedINTENSITY · · Score: 4, Informative

    What the fuck does "free as in beer" mean?

    It used to be that on election day the political machines would send men out to all the bars to buy everyone beer to toast their candidate. The idea was that the free beer would lead them to vote for the guy. Since there is an implied obligation to vote their way, the beer wasn't really free. This is then contrasted (in the "free as in beer or free as in speech") to freedom of speech, which is obviously a different sort of "free". Likewise, "Live Free or Die" doesn't imply life without cost, but rather the cost of living free.

  29. Re:SECONDED by martinultima · · Score: 2, Interesting

    Well, even though I've used QEMU quite a while (and even wrote the first version of its Wikipedia article!), I have to say that I prefer VMware myself. For one thing it's a lot faster – very important if you need to test the next version of a Linux system right now without any delays – and I also just like the program better.

    And then there's the licensing issue – while I appreciate QEMU being free and all, I don't like how the KQEMU module's proprietary software that can't be freely distributed. I'd much prefer to just have a completely proprietary solution that works than to have a half-free solution that doesn't really do much for me. Although if I knew how to write virtualization software I'd have my own solution anyway ;-)

    Oh, and remember Bochs, what we used to have before QEMU? I remember spending hours just toying around with that program... ran Windows 95 pretty nicely, and before I switched to Linux it was rather nice to have a virtualization program that ran reliably on Windows 98SE.

    Although now I'm a Linux user and addicted to VMware, so why should it matter? ;-)

    --
    Creative misinterpretation is your friend.