|
From: Kari M. <kar...@tr...> - 2008-03-03 22:44:32
|
Bruce Smith wrote: >>>>> What is the advantage of the VMware modules that come with DL, over >>>>> running DL in a VM without the modules? >>>> Advantages: >>>> Performance (especially the network driver), >>> Do I use the VMware module as the NIC driver (instead of pcnet32), >>> or do I load the module along with pcnet32? >> You use vmxnet instead of pcnet32. > > OK. > >> If you use a 64 bit guest OS, then the driver has to be the e1000. > > vmxnet doesn't work on a 64 bit guest? Bruce, start with http://www.vmware.com/technology/virtual-networking/networking-basics.html continue with http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf ...and the flexible you see with v3.5.x is just that. ESX automagically chooses the best for you. Both depending on what drivers you have loaded, and what capabilities the Guest OS has. >>>> some better memory management, >>> Does the hypervisor only take the memory that the guest is actually >>> using, instead of the entire amount reserved for the guest OS? >>> Only with the module loaded? >> I'm not 100% sure, but I think the module plays a key role. >> There are various parameters you can set for the over commit. > > Parameters to the module load? > >> I'm not too familiar with the ESX server, > > Me neither, except for the couple days I spent playing with the eval. If you end up working with ESX/VI3, you'll end up knowing it well :-) > During the ESX 3.5 install, I saw Linux kernel messages run by, and the > install screens looked a whole lot like the standard Redhat install > screens, with the Redhat logo replaced by the VMware logo. As documented by VMware, it is RHEL3. (Previous ESX 2.x was RHAS2.1) > After ESX installed, I saw more Linux kernel messages during the boot, > and I logged into the console as root and confirmed I was running Linux > with a 2.4 kernel, and VMware services were running. Actually, the Linux, Service Console, is at that time running as a VM inside vmkernel. It kind of "turns the glass upside down" during startup. It is a special VM with access to management, hardware, etc. > ESX 3i is different, as all traces of Linux, or any underlying OS, are > gone (or hidden). It claims to be much smaller and it appears like the > hypervisor is running directly on the hardware without the Linux layer. > > Some of the fancy (expensive) VMware features aren't supported with 3i, > but IMO it's more secure and less overhead. I'm leaning toward buying > 3i for work after evaluating both. How are you going to manage 3i? "Full ESX 3.5" works standalone, too... > My major complaint with both versions of ESX is the client (required to > manage the hypervisor and the guest OS's) is Windows only. Yuck! For daily tasks, you get, with the full ESX, WebUI, which includes VM console, too. It reduces Windows requirement. At least somewhat. In my mind VMware made a mistake by going to .net-only management for ESX3. Sad mistake. > And the VMware infrastructure software (expensive features we're not > buying now) requires a standalone Windows server running a SQL-server or > Oracle database! Triple Yuck!!! You can use the built-in, or free editions of those, but yes, I understand.. Choosing Windows could only be a marketing decision.. Sad. Again. (Guess who's advertising in the sig below..) //Kari M >> I use the free one at home. > > Me too! :-) > > - BS > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |