VMWare Workstation 10 - Nested - ESXi5 PXE TFTP Timeout after DHCP received.

Similar Questions

• More small footprint of guest operating system that can run in nested ESXi5

  Hi friends,

  I use VMWARE workstation 8 drive ESXi5 and vCenter. Now I want to test the HA, can someone please suggest the guest operating system, I only need networking in this guest operating system, so I can test the AP. As it is nested ESXi5, all other Windows OS has taken a lot of time to install and operate.

  The m0n0wall firewall application uses about 16 MB for storage and 64 MB - http://m0n0.ch/wall/downloads.php.  You might find some that needs less than that.

• 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

• VMware workstation, crashes when I try to create a new virtual machine

  Hello

  I never had this problem before, but I didn't create a new virtual machine in a very long time. Last time I created one was making Workstation 9 I think. Some time after the upgrade to Workstation 10 or 8.1 of Windows Update 1 it has started.

  In 10 Workstation running on Windows 8.1, I select the file > new Virtual Machine dialog coming upwards and in a few seconds crashes of VMware workstation and closes.

  So I checked the Windows event logs and find

  Warning "VMware Workstation to function properly, must be reinstalled after the upgrade to Windows."

  So, I upgraded from 10.0.2 to 10.0.3 and it uninstalled and reinstalled but I still get this warning.

  Followed by an error

  ***

  Journal name:	Application
  Source:	Application error
  Date:	15/08/2014 23:33:53
  Event ID:	1000

  Task category: (100)

  Level:	Error
  Keywords:	Classic
  User:	N/A
  Computer:	P7Win8MC

  Description:

  Name of the failing application: vmware.exe, version: 10.0.3.48389, time stamp: 0x539a4fb0

  Name of the failed module: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea24a5

  Exception code: 0xc0000005

  Offset: 0x0003bece

  ID of the process failed: 0 x 1788

  Start time of application vulnerabilities: 0x01cfb902de541c11

  The failing application path: C:\Program Files (x 86) \VMware\VMware Workstation\vmware.exe

  Path of the failing module: C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll

  Report ID: 24d5effb-24f6-11e4-bedd-20cf30780548

  ***

  So I need help to track down what I am not sure what VMware paper to look to maybe see what is happening.

  Thank you

  Rainey

  Well, I found the problem.

  I looked in the UNK file and found a few ISO files wrongs tracks.

  I had mounted some ISO in the past and they have made the entry in this file of preferences such as "isoLocationMRUx".

  I'd change the leter this ISO file player so they could not be found as input, once I corrected the paths I can now create a new virtual machine.

  He is responsible for ion BONE the new virtual machine now.

• After installation of solaris 10 x 86 get hardware error of the kernel on VMware workstation 6.5

  Find attached error mesg file I get when I installed the new solaris 10 VM on successful VMware workstation installation but when I retsart machine after the installation I had the following error mesg.

  Failure of kernel VM stack

  -If you have found this information useful, please consider awarding points to 'Correct' or 'Useful'. Thank you!!!

  Thank you

  Pitoux

  • Journey to the "virtual world".

  11/06 is updated 3.  If you have an Intel family 6 with a number greater than 15 model, this version of Solaris does not start on your processor, a virtual machine or in native mode.

  You may be able to work around this problem by usurpation of the model number of your processor.  You can try adding the following to your conifguration VM file:

  cpuid.1.eax="----:0000:0000:0000:----:----:1111:0110"
  

• 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.

• 6u2 ESXi host nested on VMware Workstation for Linux referee v12

  Hello all, I have

  I have a lab environment virtual running in VMware Workstation for Linux v12, and my ESXi hosts do not work correctly on one of the virtual networks. All my troubleshooting suggests a problem with nested ESXi hosts that may be a bug, but I want to assure you that I did everything properly first. That's why I post here with the hope that if I made a mistake that maybe someone else can point out he me.

  Physical system

  8 core Intel Xeon 2.1 GHz CPU

  128 GB of RAM

  OS - kernel Linux 64 - bit w/3.19.0-32-generic Linux Mint 17.3 (fully updated from this announcement)

  VMware Workstation 12 Pro - 12.1.1. Build-3770994 (fully updated from this announcement)

  Nested ESXi host VM

  ESXi v6.0.0 (Build 3825889, completely updated from this announcement)

  4 cards 'physical' (only 3 used for now)

  -all use the e1000 NIC hardware virtual, but also tried vmxnet3 NIC with no difference

  -vSwitch0 use vmnic0 & 1 vmnet16 of virtual network in a pair of active / standby

  -vSwitch1 uses vmnic2 on network virtual vmnet18

  -vmk0 used for management on vSwitch0 and vmk1 for iSCSI on vSwitch1

  -"Promiscuous" mode and forged passes enabled on all Port vSwitch groups (activating or turning off these features makes no difference)

  Test performed until now

  I checked that all the IP addresses and network masks used are correct.

  With the help of vmkping I ping other nodes on the network vmnet16 with success.

  With the help of vmkping I tried to ping the other nodes in the network vmnet18, but that has failed.

  I have depolyed other non - ESXi VMs on the vmnet18 network, and they are able to ping each other, but are unable to ping or ping by the ESXI host.

  I tried various material virtual NIC as mentioned before, but without changes in the results.

  I tried to use only local network instead of the vmnet18 guest network segments with no change in results.

  When I find out the status of the network adapters on the ESXi host through vCenter or host incorporated client vmnic0 & 1 time display network information, but vmnic2 shows no networks. Yet, I know that there is a network with different VM communicate on it. Moreover, I was able to get all of this work on a Windows system running 10 Workstation (this is the laptop that my employer gives me with).

  Having built nested ESXi labs on different platforms as well as physical environments in the past, I'm very confused as to why I can't get this special configuration to work. At this point my gut tells me that this is probably a bug any with the nested themselves ESXi hosts. Since I can get all this work on vmnet16 including the management of ESXi hosts and the VCSA that I use, I am sure that my vSwitch configuration is correct (other than the IP address space and vmnic configurations is bascially the same). Because I can get other virtual machines to communicate over the network vmnet18 I don't see how can be a VMware Workstation for the issue physical Linux host. Is there something obvious I'm missing here? I read on the ESXi hosts nested under VMware Workstation after having known problems and bugs with networking. If anyone else has experienced this?

  Thanks for any help others can provide!

  Kind regards

  Patrick

  Well, the problem is now resolved. The problem was what covelli was trying to explain, but I couldn't because the physical host network adapters being mentioned.

  The problem on the Linux host, but it was a problem of permissions with the virtual Ethernet adapters. The following article has the fix:
  With the help of Ethernet virtual cards in Promiscuous Mode on a Linux host (287) | VMware KB

  Even if I launched the workstation under the root user I have yet met this problem and which still makes no sense to me, but change the permissions solve the problem. I was not getting an error message on my Linux Mint and Ubuntu system, but when I tried on a second box of Linux Mint that I just got the error has been generated, and the error message was the above link it contains.

  So, here's what I learned:

  (1) the question has nothing to with a VMware Workstation definition that you can configure.

  (2) the question has nothing to do with a physical network card.
  (3) the question has nothing to do with any vmnic on the nested ESXi host.

  (4) apparently virtual Ethernet adapters are not the correct permissions when created.

  All you have to do to fix this is:

  (1) open a terminal.

  (2) run the command ' sudo chmod a + rw/dev/vmnet * "(don't forget to run this each time that you create a new virtual network).

  You can also create a group, as shown in the link above and simply give this group the correct permissions. Personally, I think it's easier to just give everyone the rw permission.

  I appreciate the help that others have offered. I did not understand what was asked for in previous answers because of the terms that have been used.

• Unable to Boot PXE under VMWare Workstation

  Note: This is a LABORATORY environment!

  I have 2 servers

  SRV1 - DHCP, ADDS

  SRV2 - WDS

  Both are installed in VMWare Workstation 12 and is assigned to a Segment named "Server LAN" local network.

  I have 2 Workstation

  WKS1 - no BONES and Belonged to a local Network Segment named "LAN Workstation"

  WKS2 - with OS (Win8) and Belonged to a local Network Segment named "LAN Workstation"

  1 Virtual router connected both the Segment of LAN 'Server LAN' and 'LAN workstation.

  Virtual router is configufed for transfer/DHCP relay.

  I can say that the DHCP relay works because WKS2 can get an ip address from the SRV1 when starting Windows 8. However, WKS1 and WKS2 in PXE startup I get this message.
  

  Any ideas?

  I solved the problem, it turns out that option 66 and 67 was not configured in my DHCP for the scope that has been maintaining the "LAN workstation.

  I have configured the DHCP in SRV1

  Option 66 for point on my WDS server.

  

  and Option 67 to point to the 64-bit version of wdsnbsp.com in the wds server.

  

• Networking question in VMware Workstation / nested ESXi network configuration problem

  Hi guys,.

  I am trying to set up a virtual lab, I setup a domain, a vcenter server and up to 1 ESXi host controller.

  I am really struggling with the network aspect in establishing a vmnic for storing shared, please see the attached screenshots and a few questions:

  1. Is a vmnic a real network map? or vmnic correspond to "network adapters" that you put in place since the setting of your virtual machine?

  I followed a tutorial and implement 3 NICs on the ESXi host, in Bridge mode, I tried this in my configuration of vmworkstation and I lose the connection to my server vcenter to the ESXi host.

  See screenshot attached to how I configured my ESXi host, screenshot is called 'screenshot2esxihost network', I run got each of the maps defined on NAT network.

  

  See also the screenshot of how I have my configuration of network settings in my VMWare Workstation, screenshot is called "screenshot1. the tutorial does not show how it has its editor of the virtual network configuration, but it puts its ESXi host NICs in BRIDGED mode, and I'm guessing that you can set this time within the virtual network adapter. If someone could tell me what changes should I make in there and on the network cards in my ESXi host, which would be really useful.

  

  My domain controller, server ESXi hosts and vcenter are currently on the 192.168.86 range, which currently stood at NAT

  See also a screenshot from the vsphere client - I don't see a vmnic "vmnic0", my goal is to be able to add a "vmnic2" for a separate storage network.

  

  any help would be received with gratitude, I VCP510 review at the end of the month and really hope to be able to get my lab setup as soon as possible.

  The vmnic is the rising 'physical' of an ESXi host. So with the 3 network cards that you configured for the host in VMware Workstation you will see under "Network adapters" and you can use them to vSwitches in the section "network".

  André

• ESXi5 in Vmware Workstation

  Hello friends, ESXi only 5 runs virtualized VMware Workstation 8? I tried to put it in version 7 and I got an error.

  I am able to uninstall Workstation 7 8 to install, the stands of the screen install again, without showing what it is, nor let go.

  Thank you!

  For the white screen problem, take a look at http://kb.vmware.com/kb/1027986 and follow the steps in this KB. Most likely, the second part on the ActiveX will solve the problem.

  André

• VSA install with hosts of nested ESXi5 (Player 4.0)

  Hello

  I use a lab with VMware Player 4.0 (DC, vCenter Server, 2 x nested ESXi5 hosts) and I try to install the Manager of VSA via command line.

  I changed the tomcat dev.properties file to bypass checking for VCA (evc.config = false), which works very well.

  However, the command-line installation complains that the VSA VM doesn't start after the deployment of the FVO and customization models of the virtual computer.

  I see that it could be a problem with nested running 64-bit VMs - where this article not that Player 4.0 is supported for this.

  I see also that nested VSA VMs is possible in Workstation 8.0 - according to this.  Tried to set the processor virtualization engine mode ESXi5 of 'Intel VT-x/EPT or AMD-V/IVR' to see if this allows virtualization of material to get through, but it has no effect on the VSA system.

  I just need to bite the bullet and pay for licensed Workstation 8.0, or is there something that can be done to get working in Player 4.0 VSA.

  All advice appreciated.

  Change this entry on this value in dev.properties

  svaservice.detect.time=15
  
  after you save the filenet stop vctomcatnet start vctomcat
  
  Keep in mind this has never been done successfully on vmplayer.
  
  Current success is on Workstation 8 and ESX.
  

• Interwoven VMware Workstation clients and 64-bit.

  I found a lot of information on nested ESXi, but nothing useful on desktop. Instructions for ESXi doesn't really work with all upwards I'm reaching for the unknown me reason.

  Here's what I'm trying to do:

  Few comments x 64 (Win7, Linux, any other OS)

  |

  VMware Workstation 10

  |

  Windows 7 x 64 virtual office

  |

  vSphere 5.5 Ent more

  |

  Dell PowerEdge R720 with all the

  Things of virtualization enabled.

  We will be deployed in the near future of VDI and I would like to provide users who have and use the workstation software work with Virtual Office almost identical to their current work stations.

  Any help would be greatly appreciated.

  P. S.

  Their virtual machines running in vSphere, and by giving them access to that and ditching Workstation is not an option, or a workstation connection to vSphere.

  I added vhv.allow = "TRUE" in the configuration of VMware and restarted host without success.

  By using the web client, go to the settings screen of the processor for the external client to Windows 7. Check the box "Expose hardware support for virtualization to the guest operating system."  Guest must be turned off when you make this change.

• Fatal error VMware Workstation: (svga) Exception 0xc0000005 (access violation) - VMware keeps crashing and our controls engineer was not able to understand, can someone help to solve?

  
  So I'm a summer at a paper factory and my boss, the engineer of controls has not been able to understand why VMware Workstation on a certain laptop hangs. I tried to create the log file I see posted the number of threads, but what I have is a compressed file which doesn't seem to have the info I've seen... or at least not in the same format. So I'm a complete newbie to VMware, and I searched the knowledge base and could not find any direct matches, at - it ready to help a newb? Really appreciate it and it would really help me as far as my training goes. TQ ahead!

  Just in case where I did maybe right I have attached two support files that I created.

  https://www.thebuddyforum.com/demonbuddy-Forum/65752-video-drivers-constantly-crashing-VMware-9.html

  I noticed that many people have the same problem with my computer when their computer/laptop has an AMD/ATI video card. Here's all I did and I got now work stations facing up and running for a week without any apparent problem

  1 back up your Virtual Machines a safe place and uninstall the workstation

  2 uninstall the AMD/ATI drivers

  3 reinstall the drivers

  4 reinstall the workstation

  5 follow the instructions below exactly to make a registry change

  a. Open regedit.exe and backup the registry, if you don't know how just google it is incredibly easy to make and the instructions are abundant so I don't post them here.

  b. open Notepad and enter the following text, make sure it is correct that the registry change can be risky, but if you enter the text exactly as it is below, you shouldn't have any problems because I have none. I take no responsibility if you have errors after this regedit so do at your own risk. Be sure and enter all the notebook INSTRUCTIONS below. DO NOT WRITE THE INSTRUCTIONS IN NOTEPAD IN YOUR NOTEPAD FILE. Everything below.

  NOTEBOOK INSTRUCTIONS

  Windows Registry Editor Version 5.00

  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\DCI]

  "Timeout" = dword:00000014

  TdrDdiDelay "= dword:00000014".

  "TdrDelay" = dword:00000014

  "TdrLevel" = dword:000000

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]

  TdrDdiDelay "= dword:00000014".

  TdrDelay "= dword:00000014".

  TdrLevel "= dword:000000".

  END NOTEBOOK INSTRUCTIONS

  c. then navigate to the file and click on Save AS, when you arrive at the location you want to save the file, click the type box and change text to all documents, and then name the file regardless of your choice and add the .reg at the end. Once you have saved the file to its location and double click it to open it, windows will ask if you want to merge with the registry click Yes, windows will be also alert you on editing the registry and if you don't know that you want to try it go ahead and do it. So far, it has worked great for me.

  For more information about editing the registry, I used click here

• initializing iSCSI SAN in VMWare Workstation 9

  Hi all!

  I created an iSCSI Target (Debian Wheezy) and an iSCSI Initiator (CentOS 6). Installation of netinstall (of CentOS) on eth0 to LUN0 on eth1 worked very well. Adjusted BIOS on VMWare to boot from first e1000. At startup, the operating system tries immediately PXE boot, iSCSI not...

  Any big brain here know what I'm doing wrong? I got about 16 hours sunk trying to develop this project, so any help would be appreciated! Thanks in advance for your time!

  Here is the answer to my problem: VMWare Workstation 9 does not support iSCSI boot.  It requires 'PXE chainloading', where a gPXE (or iPXE), PXE loads image gives VMWare PXE allows to start an iSCSI target.  Here are some valuable pages, I found on the subject, even if none show my specific "PXE boot CentOS of Debian iSCSI in VMWare Workstation 9"... guess I am the only one to write this tutorial!

  PXE boot Ubuntu on an iSCSI drive

  http://www.Heath-bar.com/blog/?p=184

  Setting up PXE chainloading

  pxechaining - Etherboot/gPXE Wiki

  Using iSCSI on Debian Squeeze (initiator and target)

  http://www.HowtoForge.com/using-iSCSI-on-Debian-squeeze-initiator-and-target

• Problem installing VMWare Workstation on a Server Windows 2012

  Hello

  I have problems when trying to install VMWare Workstation on a Server Windows 2012. Windows Server is Amazon EC2 environment and a generic image extended release.

  The problem is that the installtion process fails because of "Hyper-V" during installation, but after investigating the option "Remove roles and features" I can see that it is not installed.

  Is there any fixes for this issue?

  I enclose three screenshots for you pleasure.

  Regards, Ray...

  Hello Ray,

  Welcome to the VMware community forums.

  You run an EC2 instance that has just 615 MB memory installed?

  It's kind of a weird for a host, much too low for Amazon memory configuration, even be profitable.

  I think that your server is running UNDER Hyper-V, for example. It is probably a Virtual Machine.

  You can easily check that yourself by running the script from this site:

  How Hyper-V to: detect if you are inside a virtual machine

  If it's a Hyper-V virtual computer then I don't think you can install VMware Workstation on the virtual machine and run the nested clients.

  You could do the opposite (invited running hyper-V in a workstation virtualized on vSphere) but is not very fast.

  As you have no control over which platform virtualization Amazon use for their windows servers, I'm afraid you will have to go for a dedicated server instead of a virtual machine.

  Hope this helps,

  --

  Wil