Nested VMS (XenServer)

Similar Questions

• VMware® Workstation 8.0.4 you will only be able to run 32-bit nested vMs

  HI people,

  I did a forum search tried a few things suggested previously, but not joy.

  I get this error message

  Virtualized intel VT - x /EPT is disabled for this machine virtual esx
  you will only be able to run 32-bit nested vMs

  =================================

  The host OS is Windows Server 2008 Enterprise Edition, 64-bit 6.0.6002 Service Pack 2

  VMware® Workstation 8.0.4 build-744019

  
  The server is an HP ml350 g5 zeon 5420 cpu quad core server

  
  history esx 5i was installed on bare metal, I formatted and installed server 2008 x 64 sp2

  
  the bios is the last

  and these bios options are set

  Intel VT enabled,
  and no. execute activated too memory.

  ==============

  I understand that when these changes are made to the host should be recycled to power...

  
  This bios like many others after record changes usually f10, the changes are made and this server restarts

  is this normal?

  don't know what means VMware by power cycle

  I have disabled you options to see if I get an error that I saw the jpeg format

  (called) when the vt is disabled in the bios

  He talks about power cycle the host,

  I have the new option that was just to see if the vmworkstation was reacting to the bios actullaly.

  It has been.

  ============================================================

  
  all this should be good as the tool VMware-comments 64check - 5.5.0 - 18463

  reports

  This host is capable of running an operating system of 64 comments

  I ran it under this vmware product.when on my host Server 2008 x 64 sp2 enterprise.

  =============================

  I installed vmware workstion 8.0.4 on windows 2008 x 64 sp2 build-744019

  then I installed esxi 5 all right

  under custom options for the CPU, I chose Intel VT - x or Amd - V
  ==================================

  
  but when I opened esxi 5

  I get the error message #.

  Virtualized intel VT - x /EPT is disabled for this machine virtual esx
  you will only be able to run 32-bit nested vMs

  
  so I tried this

  
  Add the following line to C:\ProgramData\VMware\VMware Workstation\config.ini:

  hv.assumeEnabled = 'TRUE '.

  I also put this line

  hv.assumeEnabled = 'TRUE '.

  C:\Users\Administrator\AppData\Roaming\VMware\preferences.ini

  
  but still the same question after stop downs and restarts too

  I stop the physical server and restarts too

  =======================================

  = cpuid tool shows the processor is correct to because he had esxi 5 installed on bare metal before

  Information for processors
  -------------------------------------------------------------------------

  Processor 1 ID = 0
  Number of hearts 4 (max. 4)
  Number of threads 4 (max. 4)
  Name Intel Xeon E5420
  Codename Harpertown
  Specification Intel Xeon E5420 @ 2.50 GHz CPU < < < < < < < <
  Package (platform ID) Socket 771 LGA (0x6)
  CPUID 6.7.6
  Extended CPUID 6.17
  Core Stepping C0
  The 45 nm technology
  Basic speed 2500,0 MHz
  X FSB multiplier 7.5 x 333,3 MHz
  1333,3 MHz rated Bus speed
  2500 MHz frequency stock
  Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, > > > > > > > EM64T, VT - x < < < < < < < < < < < <
  Data L1 cache 4 x 32 KB, size 8-way line set associative, 64 bytes
  L1 instruction cache 4 x 32 KB 8-way line set associative, 64 byte size
  L2 cache 2 x 6144 KB, size 24 channels line set associative, 64 bytes
  FID/VID control Yes
  Range FID 6.0 x - x 7.5
  Max VID 1.225 V

  =========================================================
  My query

  These settimgs are supposed to be done in the two files above and in brackets ""

  must they be carried out before the esxi is actually installed in the workstation 8 or after.

  
  SO IMHO workstation notice 8 is misinterpreted something on my hardware.

  The ideas people?

  I have tried several combinations but no joy...

  
  Thank you
  chessguy

  chessguy wrote:

  @all

  Hmmmm...

  so with the options checked in workstation should it work,.

  (I tried it did not work)

  I don't know if I still need the lines edited in two places during the use of this option?

  and should it be done before that Esxi is installed in the workstation 8?

  or is the line of editing out of place now?

  Line editing is not relevant for your situation, since your CPU does not have the characteristics necessary for the virtualization of hardware support virtualized.

  If this server supports Esxi 5 bare metal because it was installed when I got it...

  First option get a processor that supports the corrrectly but if Intel specs are misleading where should I start... ???

  under kernel options for this doc of quickspecs ML350 g5 Server

  There are a variety of processors. any suggestions on one. ?

  http://h18000.www1.HP.com/products/QuickSpecs/12475_na/12475_na.html#core%20Options

  ========================

  None of these processors will help.  You need at least a CPU E55xx for HV virtualized.

  Option 2) now on this bare metal Esxi 5 with this current processor can I install 64-bit clients? (guess I'll try soon) but I would like to know... all ideas welcome...

  Yes, no problem.

  should I just particularly setttings in ESXi5?

  N °

  All the options for me to set up a laboratory for vsphere upward with this as is, or with the new processor?

  IMHO if not I could use 2 of these physical servers if I can get another assumption, that he would need to be the same?

  to try they full of features of vsphere. like HA, Vmotion etc.

  No, he would not have to be identical.  No matter what CPU Intel x 64 of this vintage, or later would be compatible with EVC (well well, with the exception of Atom).  You need only an identical processor for tolerance to failures.

• Virtualized ESXi5 - network problems with nested VMS

  Happy new year!

  I am facing some issues on my test environment, which is as follows:

  • -my host system is a step of laptop Linux Mint 11 (2.6.38 - 8-generic #42 - Ubuntu SMP)
  • -I'm using VMWare Workstation 8.0.1 build-528992
  • -J' I install bridged networking on a virtual interface (made with brctl) for all virtual machines and the host provides dhcp, dns, tftp, etc... facilities
  • -All virtual machines are on the network briged and all see each other, the host and the internet perfectly well

  Now the part ESXi:

  • -the server ESXi 5 (free basic license) is vitualized with a single vnic and bridged networks (same as all other virtual machines) and as a virtual machine of ESXi 5 (was a nice surprise to see that the 8 WS knows out-of-the-box)
  • -J' I install that some virtual machines nested in this virtual ESXi
  • -the VM ESXi can talk to other systems, that is, the host, the other virtual machines and its own virtual machines

  The problem is that nested virtual computers can talk to each other or the console, but not to the computer host or other virtual machines, except the ESXi itself.

  I have tried the following with no chance:

  • -Add an another vnic to the ESXi and devote a vswitch for virtual machines
  • -use NAT or network invited only for the VM ESXi
  • disable/unload the ESXi firewall

  The only thing that works are a little DHCP, although it seems the acknowledgement never reach nested VMs. However, they still get a correct, but after that IP address are not able to receive any ARP traffic. If you manually add arp entries and can see CIMP inquiry vnet0 (bridge) of VMs nested to other machines as well as the corresponding answers. If ping on the other hand, I see only the applications, which means that the traffic is not sent to the nested virtual machines.

  The vswitch ESXi is configured to accept the promiscuous mode, change MAC address and forged passes.

  Thanks in advance if anyone has an idea

  "Promiscuous" mode is enabled for/dev/vmnet0 on the physical host?  See http://kb.vmware.com/kb/287 for more details.

• Nesting of the VMs for vSphere in-a-box = network problems

  Hello all,.

  I am configuring a vSphere infrastructure of VMware Workstation 8.0.2 for training/tests. The problem is that nested VMS started inside, as virtual ESXi machines cannot reach the physical LAN, no matter if the vNIC is defined in (vmnet8) NAT or bridged.

  All the '1st level VMs' can ping each other and reach the outside world without problem. But if I try a virtual machine inside my virtual ESXi of spam, the virtual machine is unable to enter an IP address of the server DHCP VMNet8 embeeded or since our physical DHCP (with of the ESXi VM vNIC in "Bridged" mode).

  I tried to manually set an IP address to a nested on my VM ESX VM and I managed can ping it... but cannot ping the outside world.

  I'm getting VMware Workstation 8.0.2 on Ubuntu 12.04 LTS.

  For some reason, I do not understand everything works fine if I try to deploy the same environment using VMware Workstation for Windows... :-/

  I'll appreciate any help.

  Best regards.

  Check this KB: http://kb.vmware.com/kb/287

• Official support for nested virtualization VMware

  VMware officially supports virtualization nested in production with ESX 5.5 environments?

  This article implies VMware does not support, but fails to mention ESXI 5.5:

  VMware KB: Support for ESXi/ESX implementation as a nested virtualization solution

  This document is kind of contradict:

  Nested VMs running

  It is said:

  "Virtualisee HV is fully supported for hardware virtual version 9 or 10 virtual machines on the hosts that support Intel VT - x or AMD - V and EPT of IVR. To enable virtualized HV, select VM-> settings and navigate to the processor settings screen. Check the box next to 'Virtualiser Intel VT-x/EPT or AMD-V/IVR.'

  And a fe down paragraphs:

  "ESX (i) can be used as a hypervisor reviews to learn more about the VMware Server products, experiment with Server installation, training, show demos and configurations of test." VMware does not support nested ESX (i) servers running in production environments. ESX (i) problems running in a nested configuration fall outside the agreements of level of Service and Support of VMware. »

  The article quoted deals only ESXi as a guest.

  Virtualized HV is supported as a CPU function virtual when used by a Type 2 hypervisor running under any operating system supported by.

• Turn on F/T - ESXi nested / VM WS 9 Lab - help Pls (have done my research)

  Hello people,

  Before you start, I did my research on this topic, but not a lot of chance.

  PC: Mobo = Gigabyte GA-990FXA-UD3 / Proc = Core AMD FX 8320 8 / RAM = 32 GB / VMware Workstation 9 last Build / ESXi 5.1.0 build 1065491 (nested)

  Question: I just took the course install configure manage and noticed that the lab was nested and fault tolerance has been activated using these strings for a given virtual machine:

  replay.allowBTOnly = true

  replay.allowFT = true

  Replay.Supported = true

  Now I have a 64-bit Windows Server 2012 that starts well for the tests. Adding these lines to test F/T does not work well.

  I also added the "vhv.allow = TRUE" string in the config file of the ESXi server as shown in this link:

  http://communities.VMware.com/thread/341818?start=0 & tstart = 0

  Another link, that I ran was:

  virtuallyGhetto: how to enable nested vFT (virtual fault tolerance) in vSphere 5

  The error I get when shooting to the top of the virtual machine:

  This virtual computer is configured for 64-bit guest operating system. However, 64-bit performance is not possible. Longmode is disable for this virtual machine.

  Any help / suggestions are appreciated. I'm going out of town will be slow to respond back, but thanks to all for your time.

  PS: as suggested here, I also used this link to see if the option to "nestedHVsupported" was real and connect to my ESXi server.

  virtuallyGhetto: having trouble allowing nested ESXi in vSphere 5.1?

  Although the binary translation is supported for 64 bits on a physical AMD hardware customers, it is not supported for 64 - bit reduced nested in a virtual machine.  64-bit embedded host can be run with (virtualized) support virtualization.  Unfortunately, fault tolerance for a nested virtual machine requires the full binary translation, because the monitoring of the performance of the virtual processor unit is not able to provide the necessary support for fault tolerance using hardware-assisted virtualization.

  In short, you will only be able to perform fault tolerance on 32 bits of the nested VMs.

• WIN8 WP8 SDK + vmware player: I can't start any VMs

  Hi all, today I used vmware player for 3-4 virtual machines with different operating systems for testing my application on my PC, but now, when I try to start each VM I get this error.

  

  It all began when I installed visual studio 2012 and the kit of development Windows Phone 8, asking to add the role hyper-V for windows 8.

  So, I need two things in the VMs, Visual studio SDK WP8.
  How can I do?
  Thank you all.

  Drive does not well under Hyper-V.  If you only need 32-bit virtual machines, you can bypass this warning with the following configuration option:

  vmx.allowNested = TRUE

  Alternatively, you can use all your virtual machines, if you remove the role Hyper-V to your host and install Windows 8 and Hyper-V in a virtual machine under player (select Hyper-V as the guest OS type).

  Whatever it is, nested virtual machines performance will be worse than what you are used to, but nested VMs probably better work with reader as the hypervisor host with Hyper-V, the hypervisor of the host.

• Install ESXi 5.5 in the VM ESXi 5.5

  I am trying to create a nested environment ESXi 5.5 for testing purposes.

  The virtual machine should have drives IDE and CPU must use "use Intel VT-x/AMD-V" is there anything else I need to do, to be able to run ESXi in a virtual machine.

  can someone tell me please to a resource or a blog to guide me with this. I can't find.

  Thank you.

  "Promiscuous" mode and forged passes are usually the 'gotchya '.

  Info over here.

  http://www.virtuallyghetto.com/2013/11/Why-is-promiscuous-mode-forged.html

  http://wahlnetwork.com/2013/04/29/how-the-VMware-forged-transmits-security-policy-works/

  Some items.

  How to: install ESXi nested 5.5 | Cloud Solutions Architect

  or

  http://vmwaremine.com/2013/09/08/nested-ESXi-5-5/#sthash.ozOEUelR.DPBS

  More info here

  Nested VMs running

  Experience this adventure as well.

  http://www.virtuallyghetto.com/2014/08/new-VMware-fling-to-improve-networkcpu-performance-when-using-promiscuous-mode-for-nested-ESXi.html

• How to get the Hyper-V feature turned on in VMware Workstation VM?

  I think it's possible, but I can't find the corresponding thread more.

  Can someone enlighten me please on how I can enable the Hyper-V feature in a VMware Workstation VM?

  I know that it is not supported. But come with the new Microsoft Visual Studio 2015 there will be only a bundled Android emulator which seems to demand of Hyper-V.

  In my view, that nested VMs running is what you are looking for.

  André

  Note: Discussion left VMware Workstation for nested virtualization

• When the suspension/resumption blue screens Windows Hyper-V VM in ESXi 5.5

  ESX to virtualize ESXi and Windows Hyper-V machines for training scenarios. We have dozens (or even hundreds) of these virtual machines in use in a large farm of ESX host at any given time. Students are able to suspend their virtual machines at any time and come back later. It worked flawlessly on ESXi 5.1. Our troubles started when we went to ESXi 5.5. After the upgrade, Windows Hyper-V guests began to break up with a blue screen during the process of suspension/resumption. We have restored 5.1 on two of our boxes and the problem stopped. We may be forced to return all the servers to 5.1, but are really hoping to find a fix or a workaround. We are opening a case with VMware, but thought we ask here as well.

  
  Comments
  
  

  • We have the latest version of ESXi 5.5, build 1892794.
  • BSOD comments were held on all ESX hosts, we have. We have two server hardware configurations that are very similar (details below) and the BSOD occur with equal frequency on both.
  • BSOD happens in 2012 Windows R2 and Windows 2008 R2 VMs.
  • EDIT: BSOD occur if the two "hypervisor.cpuid.v0 = FALSE" is configured and the Hyper-V role is installed. No BSOD that Hyper-V is deleted or if happen "hypervisor.cpuid.v0 = FALSE" is deleted.
  • The "hypervisor.cpuid.v0 = FALSE" parameter is used to make Hyper-V think it runs on native hardware. Without it, Windows knows it is running in a virtual machine and the BSOD go. But Hyper-V won't start nested VMs. I wish we didn't need the arrangement, but, alas, we do.
  • We have never seen a BSOD that was triggered by a suspension/recovery.
  • Not every interruption/resumption will cause a BSOD. During testing, we see a BSOD about 20% of the time that a suspension/resumption is carried out.
  • This happens on ESXi hosts whether they are occupied or not. We took a server out of rotation of isolated tests and saw the exact same behavior.
  • There are various BSOD messages. The most common is 'IRQL_GT_ZERO_AT_SYSTEM_SERVICE' with a stop of 0x0000004A code. But there are several others.
  • We thought it might have something to do with the bug of processor Intel E5 (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2073791). However, we use E5 V1 processors, not V2. We have updated to the latest Dell BIOS (2.2.3) just in case. It made no difference.
  • We tried to turn off all the power settings in the BIOS of the server, as well as within ESX. This includes any definition performance max and disabling C States. No difference.
  • We have disabled all of the features available in the BIOS of the virtual machines, including all the caching options. No difference.
  • We use the following parameters to enable nested Virtualization:
    • CPU/MMU hardware
    • VHV. Enable = TRUE
    • Hypervisor.CPUID.v0 = FALSE
  • We tried to use "windowsHyperVGuest" as the identifier for OS invited instead of the above parameters. Nested virtualization has worked well, but the BSOD is still produced at the same rate.
  • EDIT: we tried the upgrade virtual machines since version 9 to version 10 of hardware equipment. This did not help.
  • EDIT: we tried the VMware Tools upgrade from version 9.0.0.782409 to 9.4.6.1770165. This did not help.
  • We tried allowing the CPU performance counter virtualization in virtual machines. No help.
  • We came home two of our servers to 5.1 and the BSOD disappeared completely. No other changes been made to the servers and virtual machines. Just go back to 5.1 fixes the problem.
  • We have noticed a dramatic amount of time difference to both versions of ESXi to suspend these VMs. ESXi 5.1 suspends these VMs within 2-3 seconds, while ESXi 5.5 takes 30 seconds to a minute. Certainly, something very different happens during the process of suspension. Suspend time 5.5 are longer or not a BSOD occurs.

  Our material

  • Dell PowerEdge R720xd OR Dell PowerEdge r.620
  • BIOS version: 2.2.3
  • Processors: 2 - Intel Xeon E5-2670 0 @ 2.60 GHz
  • RAM: 384GB (16 GB (buffered) synchronous DDR3 DIMMS matched Dell 24)
  • Controller: PERC H710P Mini 1 GB memory NVRAM
  • OS disc: 2-240GB S3500 SSD drives in a RAID 1 (Slot 00-01) mirror
  • VM storage drive: 7-480GB S3700 SSD in a RAID5 with a HS spare dedicated (Slot 02-09)
  • 1 - Intel 2 p X 540/2 p I350 rNDC
  • 1 - Intel Gigabit 4 p I350-t adapter

  The obvious solution is to roll back to 5.1. However, we completely independent questions with 5.1 (one topic for another post) that we don't have with 5.5 and prefer to stay with 5.5. But these BSOD is a deal breaker. Help or direction to solve the BSOD will be greatly appreciated!

  In some cases, a single byte stored in the checkpoint file is outdated.  This only affects nested customers.  During the recovery of a Hyper-V OS management from a corrupt checkpoint, a variety of BSOD can result.

  You must file a request for assistance for an express patch with a fix for the PR 1289485.

• translation of binary 64 bit is not supported in a virtual machine (automatic deployment)

  So I'm having some problems with a lab to deploy VMware Auto.

  I did some research and still not be able to find a solution.

  I get the following error:

  This virtual machine is configured for client operating systems 64-bit. However, 64-bit operations is not possible.

  translation of binary 64 bit is not supported in a virtual machine.

  Preferred mode is unavailable. using the binary translation instead.

  This host is not compatible AMD - V.

  Nested VMS are not supported with binary translation for external virtual machines. If you want to run virtual machines nested under ESX virtual machines, you need a host on which VMware Workstation supports Inet-VTx or AMD - V.

  The installation program:

  5.1 physical ESX

  -AMD Opteron 8356 (AMD-V supported and enabled in the bios)

  Machine virtual Virtual vCenter

  VMware workstation 10 on vCenter VM client

  I put the client VMware workstation Operating System in VMware ESX 5i and when I turn on immediately I get the message.

  Just for curiosity have defined the type of operating system Linux and the process works until the end where it reloading the kernel, so I guess that the message

  The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.

  Also note that the works of any progress when I use Auto deploy PXE starts a virtual machine.

  Unfortunately VMs cannot be managed in the profiles of the host, so I need to external devices as a host.

  Any help would be greatly done his apprenticeship

  Thank you

  In the processor for the vCenter VM settings, check the box of "Exposing material assistance to the guest operating system virtualization."  (This setting is not available in the classic c# client.  You must use the web client). See nested running VMs.

• 2012 hyper V within VSphere 5.5?

  Hello...

  I'm trying to implement a nested within VSphere 5.5, Windows 2012 Hyper-V environment but no matter what I try, I am unable to add the hyper-v role: Windows always reports "cannot install Hyper-V: a hypervisor is already running."

  I try to install on a machine of esxi 5.5, which has two Xeon E5540 CPU: I believe that according to http://ark.intel.com/products/37104/Intel-Xeon-Processor-E5540-8M-Cache-2_53-GHz-5_86-GTs-Intel-QPI that these processors will support what I'm trying to do.

  In the settings of the virtual machine, I activated the "expose hardware virtualization assisted for the guest OS' as described in the document of execution nested VMs. The virtual hardware is version 10.

  I do not know missing me something obvious - if someone can point me in the right direction, I would be very grateful.

  Thank you!

  If all else fails...

  Install Windows 2012 as usual.

  Select "display hardware virtualization assisted for the guest OS."

  Add the following advanced configuration option: hypervisor.cpuid.v0 = FALSE

• Running VMware player in a 2012 Windows guest running on ESXi5.5

  Hello

  One of our users want to run VMware player on a virtualized server Windows 2012 on ESXi5.5

  Is that supported?

  They get the Intel VT is disabled error when you try to run a 64-bit machine in VMware player.

  Thank you

  Erik

  Take a look at: Running nested VMs

  Also in the future you might want to ask questions like this in: nested virtualization

• Very slow performance

  Hi all

  I feel a slowdown in performance. The stay nested VM taped up to 02 minutes in power. (Screen of VMware).

  My hardware is that a 6 dual core 2.10 GHz Intel. (Total 24 lcpus)

  I use the latest stable version of ESXi 5.1.

  There is no VM or charge in nested ESXi, the first virtual machine windows 2003 32-bit server takes up to 10 minutes to start the installation. The installation is completed without error.

  Any ideas for this extreme slowness?

  I've attached a screenshot of the screen of VMware that nested vms stay delayed until 02 minutes.

  Thanks in advance, Emanoel (VCP - VTC)

  [RESOLVED] and works like a charm...

  I don't know why using software mmu, it was originally delayed and poor performance.

  2013 10-16 T 09: 20:53.305Z | VMX | I120: HV settings: virtual exec = "dynamic"; MMU virtual = "software".

  The way is forcing to use hardware exec insert parameters below to .vmx guest operating system.

  Monitor.virtual_exec = material

  Monitor.virtual_mmu = material

  Someone knows why you I must manually specify is available mode is BT HV HWMMU?

• How to activate the Hyper-V Server 2012 on Fusion 5?

  Dear members of the Forum,

  I have a Mac Pro early 2008 Intel Xeon, 16 GB under Snow Leopard and VMWare Fusion 5 installed, as well as a few virtual machines running perfectly. I decided to create a virtual computer that is running Windows Server 2012. The installation went well. However, when I tried to activate the Hyper-V technology I got in trouble.

  In the Virtual Machine settings > system settings > general: I chose "Hyper-V (not supported).

  In the processor and memory, I selected 4 cores, 4 GB and in advanced: enable applications to hypervisor...

  In other/advanced: the virtualization engine preferred: Intel VT - x with EFA

  and all the possible permutations of these selections. Nothing has worked.

  Error messages:

  Hyper-V cannot be installed. The processor has no virtualization required capabilities.

  Virtualized Intel VT-x/EPT is not supported on this platform.

  Preferred mode is unavailable. Using VT - x instead. This host does not support EFA.

  All this leads me to believe that my hardware configuration does not support the operation of computers virtual hyper-v in Fusion. According to your philosophy, we can consider this to be a reality: everything is always possible. However, what drives me nuts are guys on internet blogs, everybody saying he's working on their system! I would like to hear an authoritative voice if possible, or not.

  Thanks in advance

  EP

  Hi Eric and welcome on VMware communities!

  It is purely a matter of features of the CPU.  None of the processors that apple delivered in Early 2008 Mac Pro systems supports Extended Page Tables (EPT).  According to the list of the Mac Pro systems, the processor that you have will be E5462, E5472 or X 5482, as well as relevant on the (related) Intel Web site pages show no support for EFA everymac.com.

  Without EFA, we cannot virtualize VT - x.  In other words, the guest operating system cannot see and use virtualization assisted by material, although the merger itself will be able to make use of the hardware support of the functions of virtualization host to run the virtual machine: we can use VT - x, but cannot virtualize to make it available to a nested prompt.

  Hyper-V is entirely dependent on the hardware support for virtualization (VT - x for example), then it won't work as a guest nested in your configuration.

  Companions VMwarian jmattson produced a great entry on nested VMS requirements and functional combinations here: nested VMs running

  See you soon,.

  --

  Darius