- 論壇徽章:
- 0
|
參考下面資料： http://skabelka.com/node/40
VMWare ESX 3i and VMWare ESX3/ESX4 on Desktop PC
Submitted by Alexander on Sun, 12/13/2009 - 21:16 Sometimes it's really useful to setup whole VMWare ESX Infrastructure not on proper Server hardware for Production purposes but on local Desktop PC for study and testing functionality. Let's do it with several easy steps.
This installation guide was tested on Dell Latitude D620 Laptop computer.
Following conditions are required to be able to start VMWare ESX3i/ESX3/ESX4 just on your Desktop PC:
AMD-V or Intel VT processor
Min 2GB RAM (4GB is recommended)
ESX or ESXi Media(ISO)
VMWare Workstation 6 or 6.5
Instructions (see below)
Step1: check if processor is compatible with AMD-V or Intel VT technologies
Find out the model of processor on your computer via "Computer management" console.
Computer Management: get model of processor
Just follow the link Intel components info for your Intel processor and
check Intel VT-X processor compatibility. Make sure that VT-X is option for your type of processor. Otherwise it will never work.
http://ark.intel.com: Processor details
Step2: Create new VM(Virtual machine)
(...will be soon...)
Step3: Install ESX
(...will be soon...)
VMWare VMWare ESX 3 VMWare ESX3i
» Alexander's blog
Submitted by Alexander on Sun, 12/13/2009 - 23:37. #
Intel first introduced VT-x on late-model P4 processors (codenamed Paxville). Many Core, Core 2, Core i3, Core i5 and Core i7 processors are VT-capable (as are their Xeon-branded counterparts). However, some skus of these models are not VT-capable. (For example, the Q8200 Intel Core 2 Quad Processor is not VT-capable). You can check to see if your processor is VT-capable here.
On Intel CPUs, it is expected that the BIOS (or other firmware) will either enable or disable VT-x at boot, and will then lock the setting so that it cannot be subsequently changed without powering down the CPU. Note that VT-x must be both enabled and locked before software can make use of the VMX extensions. This operation must be performed for each core of a multi-core system, and for each thread of a multi-threaded system.
Because the VT-x setting is typically locked at power on, it is necessary to fully power down the system after changing any VT-x options in the BIOS. A simple reboot is not sufficient! After saving your BIOS changes, I recommend that you either switch off the power supply itself or pull the power cord(s) out of the wall and wait ten seconds. For laptop systems, you may have to remove the battery as well, although such extreme measures are rarely necessary.
Some BIOSes do not have VT-x enable/disable options. Some BIOSes with such an option fail to enable/disable VT-x on each core of a multi-core system or on each thread of a multi-threaded system. To verify that VT-x is enabled and locked on each core/thread of your system, download the attached ISO, burn it to a CD, and boot your host from the CD.
For each core (or thread, for HT CPUs) on your system, the ISO will report one or more of the following:
CPU : This core does not support long mode
CPU : This core does not support VT
CPU : Feature control MSR is unlocked!
CPU : VT is disabled in the feature control MSR!
CPU : VT is enabled on this core.
If the ISO reports that some core(s) do not support long mode, you will not be able to use VT-x with current VMware products. You can use VT-x for 32-bit guests with Workstation 5.5 or 6.0.x, Fusion 1.0, or ESX 3.0, but this configuration is not supported. See VMware Products and Hardware-Assisted Virtualization (VT-x/AMD-V).
If the ISO reports that some core(s) do not support VT, but your CPU(s) should support VT, you may have encountered an Intel chip erratum (possibly AW67 or AV69, depending on the CPU). The effect of this erratum is that some CPU features are reported incorrectly after a particular machine specific register has been updated by the BIOS. The solution to this problem is to obtain an updated BIOS from your system vendor.
If the ISO reports that the feature control MSR is unlocked some core(s), a workaround is available for current VMware hosted products. Simply add the following option to your system-wide configuration file:
hv.enableIfUnlocked = TRUE
On Linux systems, the system-wide configuration file is /etc/vmware/config. On Windows systems, the system-wide configuration file varies according to VMware product and Windows version. For VMware Workstation on XP hosts, the system-wide configuration file is C:\Documents and Settings\All Users\Application Data\VMware\VMware Workstation\config.ini. For VMware Workstation on Vista hosts, the system-wide configuration file is C:\ProgramData\VMware\VMware Workstation\config.ini. For other VMware products, adjust the path appropriately.
Note that this workaround can also be helpful if your BIOS fails to enable and lock VT-x when waking from hibernation. However, the ISO is not helpful in diagnosing this failure. If VT-x works after a power-cycle but fails after resuming from hibernation, then you should try the above workaround.
If the ISO reports that VT is disabled on some core(s) and it does not also report that the feature control MSR is unlocked on the same core(s), then it is impossible to enable VT-x through software.
Note that VT-x is typically unavailable to normal software if you have enabled "trusted execution," which may restrict VT-x to "trusted" code. You should disable trusted execution in the BIOS and power-cycle the system.
Original: http://communities.vmware.com/docs/DOC-8978
iso: http://communities.vmware.com/se ... ad/8978-13-16491...
reply Submitted by Alexander on Mon, 12/14/2009 - 00:18. #
Requirements
It is only possible to run nested VMs when the outer VM uses hardware-assisted virtualization (Intel VT-x or AMD-V) and the inner VM uses classic software virtualization (binary translation). You may run any 32-bit or 64-bit operating system as the outer guest. You may only run 32-bit operating systems as the inner guest. Running nested VMs under ESX 4.0 (or ESXi 4.0) under Workstation 7 is the only officially supported configuration. Other configurations may work, but are entirely unsupported.
Nested VMs are only possible when the host is running ESX 3.0 (with some caveats), ESX 3.5 (some AMD CPUs only), Workstation 6.0 (or later), or Fusion. Note that you cannot run nested VMs on Intel systems when the host is running ESX 3.5.
See the appropriate section below for the configuration options required for the two guests.
Intel VT-x Hosts
Intel VT-x is supported on many Core, Core 2, Core i3, Core i5 and Core i7 processors, and on some late-model P4 processors. Current VMware products only support VT-x on 64-bit (EM64T) Intel processors. For more information on enabling VT-x, see Verifying that VT-x is Enabled and Locked at Boot.
ESX 3.0
The configuration file for the outer guest should contain the following line:
{font:courier}
monitor_control.vt32 = TRUE
{font}
The configuration file for the inner guest should contain the following line:
{font:courier}
vmx.allowNested = TRUE
{font}
Note that the {font:courier}vmx.allowNested{font} option is not supported by older VMware products. For nested VMs to work on an ESX 3.0 host, the VMware product running in the outer guest must be Workstation 6.0 or later or ESX 3.5 or later. Furthermore, you must not use the backdoor in the inner guest. In particular, this means that you must not install VMware tools in the inner guest.
Workstation 6.0 and Fusion 1.x
The configuration file for the outer guest should contain the following lines:
{font:courier}
monitor_control.vt32 = TRUE
monitor_control.restrict_backdoor = TRUE
{font}
Workstation 6.5 or later, Fusion 2.0 or later and ESX 4.0
The configuration file for the outer guest should contain the following lines:
{font:courier}
monitor.virtual_exec = hardware
monitor_control.restrict_backdoor = TRUE
{font}
AMD-V Hosts
AMD-V is supported on Rev F and later Family 0FH AMD64 processors, but current VMware products only support AMD-V on Family 10H or later AMD64 processors (Barcelona or Phenom). Thus, you can use AMD-V on Family 0FH Rev F and Rev G processors with Workstation 6.0. However, you need a Family 10H processor to use AMD-V with ESX 3.5 and Workstation 6.5 (or later).
ESX 3.0
The configuration file for the outer guest should contain the following line:
{font:courier}
monitor_control.enable_svm = TRUE
{font}
The configuration file for the inner guest should contain the following line:
{font:courier}
vmx.allowNested = TRUE
{font}
Note that the {font:courier}vmx.allowNested{font} option is not supported by older VMware products. For nested VMs to work on an ESX 3.0 host, the VMware product running in the outer guest must be Workstation 6.0 or later or ESX 3.5 or later. Furthermore, you must not use the backdoor in the inner guest. In particular, this means that you must not install VMware tools in the inner guest.
Workstation 6.0
The configuration file for the outer guest should contain the following lines:
{font:courier}
monitor_control.enable_svm = TRUE
monitor_control.restrict_backdoor = TRUE
{font}
ESX 3.5
The configuration file for the outer guest should contain the following lines:
{font:courier}
monitor.virtual_mmu = hardware
monitor_control.restrict_backdoor = TRUE
{font}
Workstation 6.5 or later and ESX 4.0
The configuration file for the outer guest should contain the following lines:
{font:courier}
monitor.virtual_exec = hardware
monitor_control.restrict_backdoor = TRUE
{font}
Original: Running Nested VMs
Created on: Nov 30, 2008 6:17 PM by jmattson - Last Modified: Dec 11, 2009 9:06 AM by jmattson
reply Submitted by Alexander on Fri, 12/25/2009 - 23:02. #
There was one important thing I have to do for solving the installation problem - on my DELL Latitude D620 I was needed to upgrade BIOS to last available one A10 and had to enable Virtualization in Post Behaviour section. So right now I finished it and it works fine - both ESX3i and ESX4.
reply |
|
免費(fèi)注冊(cè)
發(fā)表于 2011-04-29 11:41