Source: https://kb.altiris.com


Article ID: 40812

Using WinPE 2.1 with VMWare virtual machines


Applies To

• Deployment Solution 6.9



Question

How do I use WinPE* 2.1 with VMware* virtual machines?



Answer

You must use Intel E1000 network card emulation instead of AMD pcnet network card emulation. See http://www.symantec.com/connect/blogs/tweaking-vmware-work-winpe-2x-and-microsoft-vista for instructions.
Excerpts from the link:

The following works for VMware WorkStation 5.5 and 6.0 and VMware Server 1.0+. By make the following alterations, WinPE 2.x will work seamlessly with network drivers.

  1. Make sure VMware is not running. Stop any virtual machines running and close VMware.
  2. Browse to the Virtual machine files and open the .vmx file with your favorite text editor.
  3. Add the following to the <Path to VM> .vmx file:

    ethernet0.virtualDev = “e1000″

    This is right after the ethernet0.present = “TRUE”.

  4. Save the changes.
  5. Start your virtual machine.

Virtual machines with installed operating systems such as Microsoft Windows Vista or Microsoft Windows XP might have an issue with the drivers after this change. Change the network drivers and point to c:\windows\system32 for the drivers. Or download the latest e1000(Intel) driver.



The information contained in the Altiris Knowledgebase is subject to the Terms of Use as outlined at http://www.altiris.com/legal/termsofuse.asp.

Reblog this post [with Zemanta]

Eric Siebert published an very nice article about Memory usage in vCenter Server 4.0:

If you are using vCenter Server and plan on upgrading to vSphere you should be aware that vCenter Server 4.0 uses much more memory than vCenter Server 2.5 does. According to the official documentation for both 2.5 and 4.0, the system requirements are very similar:

  • 2.0 GHz or faster Intel or AMD x86 processor. Processor requirements can be more if your database runs on the same hardware.
  • 2 GB RAM. You might need more RAM if your database runs on the same hardware.

But VMware has a note in the vSphere documentation that states:

vCenter Server includes a service called VMware vCenter Management Webservices. This service requires128MB to 1.5GB of additional memory. The vCenter Management Webservices process allocates the required memory at startup.

This Webservices component is a Windows service called VMware VirtualCenter Management Webservices. It’s a Tomcat Java application server that is a component of the vCenter Server. You will see this service listed in Task Manager as tomcat6.exe as vCenter Server 4.0 uses the newer Tomcat 6 version. In vCenter Server 2.5, this service was listed as tomcat5.exe, vCenter Server 2.5 uses the older Tomcat 5.5 version. The Webservices component is not used just for Web browsers to access the vCenter Server, many other services rely on this component. If you stop this service component, vCenter Server will still work but anything that relies on Webservices will no longer work (i.e. plug-ins, Converter).


Read complete article on http://itknowledgeexchange.techtarget.com/

Reblog this post [with Zemanta]

© 2010 http://www.vmwarenews.de Creative Commons License
http://www.vmwarenews.de steht unter einer Creative Commons Namensnennung-Weitergabe unter gleichen Bedingungen 3.0 Deutschland Lizenz
Suffusion WordPress theme by Sayontan Sinha