Talk:VMware ESX Server

From Wikipedia, the free encyclopedia

Contents 1 Great Idea & First Question 2 Network Protocol Section 3 List of guest OSes supported 4 Architecture

[edit] Great Idea & First Question

I like the idea of a separated page for the ESX Server.

One question: In the first paragraph, there is written 'The basic server requires some form of persistent storage - typically an array of hard disk drives - for storing core system files and virtual machines.' Why is there the emphasis on storage? Also every ESX Server needs CPU, RAM, Network, ...?

--Sophis 08:42, 22 September 2007 (UTC)

The intent here was to explain the main difference between ESX 3.0 and 3i in the first pargraph. As I understand it, 3.0 needs to be installed on a persistent storage medium, like a hard disk array, whereas 3i will be integrated into the system's firmware. I just reworded it slightly to better emphasize this difference. If you can make this any clearer, then please do so. — EagleOne\^Talk 02:41, 25 September 2007 (UTC)

[edit] Network Protocol Section

Just an FYI - This section should probably be removed or at least moved to either the Workstation or VMware Server page since it is not related to ESX. The terms Bridged and NAT'd are not applicable to the ESX architecture. I am sure the original author was using one of the HOSTED (Workstation or Server) products which does employ these types of concepts/terms for the host NICs. I'll leave this task for one of the more experienced WIKIPeople to handle though. 68.164.207.118 (talk) 05:06, 5 December 2007 (UTC) CCOSTAN

[edit] List of guest OSes supported

No list of supported guest OSes in the industry-leading hypervisor article? —Preceding unsigned comment added by 221.128.181.104 (talk) 20:00, 4 February 2008 (UTC)

[edit] Architecture

Because there is so little information available about how ESX server differs from Linux+GSX server, I may be getting some things wrong here. It seems to me that even in V3, the linux kernel loads first, provides the proc FS and a base for what the article refers to as the service OS (redhat linux userpsace), and is also used for its network and storage drivers. Unless I am mistaken, this makes Linux the actual bare hardware kernel.

Without some serious modification there are only 2 places for code to run on a linux system, in userspace or in the kernel itself. That includes the drivers, which, because they are GPL licensed, virally GPL anything you attach them to. Unless VMware has massively modified the linux kernel, this vmkernel either runs in userspace or is itself a module and thus derivative of the Linux kernel.

The whole thing looks like a license violation to me, and I'm not even that fond of the GPL. I hope someone proves me wrong. Mrsteveman1 (talk) 05:29, 17 February 2008 (UTC)

Actually there is a version of ESX available that does not uses the Linux kernel (called 3.5i). So your reasoning is false. There is some documentation available at e.g. http://scholar.google.com/scholar?hl=en&safe=off&q=esx+vmware&spell=1. —Preceding unsigned comment added by 76.202.117.76 (talk) 02:16, 13 April 2008 (UTC)