| 8 | | * VMware製品各種での設定がまとめられている |
| | 8 | * VMware製品各種での設定がまとめられている |
| | 9 | * http://communities.vmware.com/docs/DOC-8970/version/30 VMware Workstation 7以前の情報 |
| | 10 | > Running 32-bit nested VMs with binary translation under ESX(i) 4.x, ESXi 5.0, Workstation 7.x, Player 3.x or Fusion 3.x is the only officially supported configuration. Other configurations may work, but are entirely unsupported. |
| | 11 | > === Guest Hypervisors Under VMware Hypervisors === |
| | 12 | > ==== Enabling Intel VT-x for the Outer Guest ==== |
| | 13 | > ===== ESX 3.0, Workstation 6.0 and Fusion 1.0 ===== |
| | 14 | > {{{ |
| | 15 | > monitor_control.vt32 = TRUE |
| | 16 | > }}} |
| | 17 | > ===== Workstation 6.5 (or later), Fusion 2.0 (or later) and ESX 4.0 (or later) ===== |
| | 18 | > {{{ |
| | 19 | > monitor.virtual_exec = hardware |
| | 20 | > }}} |
| | 21 | > Note that this is the default for any 64-bit guest OS type on Intel hardware, so you do not have to edit the configuration file to select hardware-assisted virtualization if you have specified a 64-bit guest OS. |
| | 22 | > ==== Enabling AMD-V for the Outer Guest ==== |
| | 23 | > Family 0FH Rev F and later AMD64 processors provide hardware support for AMD-V, but current VMware products only support AMD-V on Family 10H or later AMD64 processors (Barcelona/Shanghai/Istanbul or Phenom/Phenom II). You can use AMD-V on Family 0FH Rev F and Rev G processors with ESX 3.0 and Workstation 6.0. However, you need a Family 10H or later processor to use AMD-V with any later products. |
| | 24 | > ===== ESX 3.0 and Workstation 6.0 ===== |
| | 25 | > {{{ |
| | 26 | > monitor_control.enable_svm = TRUE |
| | 27 | > }}} |
| | 28 | > ===== ESX 3.5 ===== |
| | 29 | > {{{ |
| | 30 | > monitor.virtual_mmu = hardware |
| | 31 | > }}} |
| | 32 | > ===== Workstation 6.5 (or later) and ESX(i) 4.0 (or later) ===== |
| | 33 | > {{{ |
| | 34 | > monitor.virtual_exec = hardware |
| | 35 | > }}} |
| | 36 | > ==== Networking in Nested Guests ==== |
| | 37 | > see vmware:287 (Linux hosts) or vmware:1004099 (ESX hosts). No special configuration is required for Windows hosts. |
| | 38 | > ==== VMware Products as Guest Hypervisors ==== |
| | 39 | > * ESXi 5.0, you will be able to run 64-bit nested guests |
| | 40 | > * VMWare products prior to ESXi 5.0 => you will be restricted to running only 32-bit nested guests using binary translation under any VMware product as the guest hypervisor. |
| | 41 | > ===== ESX(i) as a Guest Hypervisor ===== |
| | 42 | > * Workstation 7.0/Player 3.0/Fusion 3.0 => select "ESX Server 4" |
| | 43 | > * ESX(i) 4.1 => manually edit the VM configuration file and select guestOS="vmkernel" |
| | 44 | > * ESXi 5.0 => select "ESX Server 4" or "ESX Server 5" |
| | 45 | > ===== Other VMware Products as Guest Hypervisors ===== |
| | 46 | > If you plan to run VMware Tools in your inner VM, you will need an additional configuration option to restrict the backdoor interface to the host hypervisor. For guest OS types other than "ESX Server 4" or "ESX Server 5", you should add the following line to the configuration file for the outer guest: |
| | 47 | > {{{ |
| | 48 | > monitor_control.restrict_backdoor = TRUE |
| | 49 | > }}} |
| | 50 | > You should not install VMware Tools in the outer guest. |
| | 51 | > ==== Virtualizing HV (VT-x or AMD-V) ==== |
| | 52 | > With ESXi 5.0 as the host hypervisor, it is possible to virtualize the hardware-assisted virtualization capabilities of the physical processor. This feature is used internally within VMware for testing purposes, but it is not recommended for production systems. This feature is also not recommended for systems without hardware-assisted MMU virtualization (EPT or RVI), because of its abysmal performance without that hardware support. |
| | 53 | > |
| | 54 | > This feature is disabled by default. To permit the use of this feature, the ESXi administrator must add the following configuration option to the /etc/vmware/config file on the physical host: |
| | 55 | > {{{ |
| | 56 | > vhv.allow = TRUE |
| | 57 | > }}} |
| | 58 | > Once allowed by the ESXi administrator, virtualized HV will be enabled by default for all hardware version 8 VMs with guest OS type "ESX Server 4" and "ESX Server 5." To enable virtualized HV for other guests, add the following lines to the outer guest's configuration file: |
| | 59 | > {{{ |
| | 60 | > cpuid.1.ecx="----:----:----:----:----:----:--h-:----" |
| | 61 | > cpuid.80000001.ecx.amd="----:----:----:----:----:----:----:-h--" |
| | 62 | > cpuid.8000000a.eax.amd="hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh" |
| | 63 | > cpuid.8000000a.ebx.amd="hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh" |
| | 64 | > cpuid.8000000a.edx.amd="hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh" |
| | 65 | > }}} |
| | 66 | > With virtual HV enabled in the outer guest, you should be able to run any guest hypervisor that requires hardware-assisted virtualization. In particular, this means that you will be able to run 64-bit nested guests under VMware guest hypervisors. |
| | 67 | > ===== KVM as a Guest Hypervisor ===== |
| | 68 | > KVM performs relatively poorly in a nested VM using virtualized VT-x. This situation is much improved with Linux kernel versions 3.0 and greater. |
| | 69 | > === VMware Guest Hypervisors Under Foreign Hypervisors === |
| | 70 | > If we detect that a VMware product is running under a foreign hypervisor, we will refuse to power on a nested VM. To bypass this constraint, add the following option to your nested VM configuration file: |
| | 71 | > {{{ |
| | 72 | > vmx.allowNested = TRUE |
| | 73 | > }}} |
