Hello everybody.

I had some problems with one host.

I removed it from distributed switch, then from vCenter, reinstall fresh ESXi and trying to add host to the cluster.

Error occurred while applying profile:

And now all portgroups does not work at new host. After migrating VM to the host with troubles network card is turned off. If I turn it on manually, link is going up,but VM have not connection...

Please help me figure out the situation...

When I got this Nessus ticket from my Cyber Security Section I said no big deal I went over to vSphere and renewed the certificate.  It renewed with the date of of 20 March 20 and was good 5 years. I thought no problem. This ticket will go away. I am not sure why Nessus won't trust a self signed cert from VMWARE but it won't.  So I thought super easy I will just create some of my MS CA certificate Authority.  

I followed these instructions but when it came time to add the certificate to the certificate store MS did not show the template I created:

VMware Knowledge Base

The problem is these instruction talk about Windows 2003 and Windows 2008 and our CA is a Windows 2012 R2 server and the choices it gives me is on the Compatibility Tab is Certificate Authroity Windows Server 2012 R2(or Windows Server 2012) and the Certificate recipient(Windows 8.1/Windows Server 2012 R2) and ((Windows 8/Windows Server 2012).

So the final problem is when I follow step Right-click Certificate Templates and click New > Certificate Template to Issue. The new certificate template I created is not in there not only that is does NOT show up in the web request page (https://CA/certsrv). 

Any ideas?

Any possibility I can just do this as a standard web request.

We are tried perform patching at environment at cluster level.( by VUM )

We have 4 hosts in cluster.

hosts: ESXi 6u1

Example name of Hosts:

CMP1

CMP2

CMP3

CMP4

We start install patches on 1st host with successful.

During vMotion from second host and now  4th host ( We dont tested yet cmp3 ) tasks stuck at 13%

Some advices ?

Looking for any suggestions on this PSOD.

Thanks in advance.

My building had an unexpected power interruption and my ESXi 6.0.0 host was shut down. After starting up, one of my VM won't boot up (the most important one). Here is the full error message:

**************

Failed to start the virtual machine.

Module Disk power on failed.

Cannot open the disk '/vmfs/volumes/.../dataserver.SouthBay.local/dataserver.SouthBay.local_1.vmdk' or one of the snapshot disks it depends on.

The system cannot find the file specified

VMware ESX cannot find the virtual disk "/vmfs/volumes/.../dataserver.SouthBay.local/dataserver.SouthBay.local_1.vmdk". Verify the path is valid and try again.

**************

I look at Datastore Browser and I see files below"

dataserver.SouthBay.local.nvram

dataserver.SouthBay.local.vmx

dataserver.SouthBay.local.vmdk (very large size)

dataserver.SouthBay.local.vmxf

dataserver.SouthBay.local.vmsd

dataserver.SouthBay.local-ctk.vmdk

vmware.log

vmware-50.log

vmware-51.log

vmware-52.log

vmware-53.log

I'm fairly new to ESXi and I am not exactly sure where or how to start on this. I did some research and I think I have a missing virtual machine disk descriptor file. Any advice is much appreciated.

VM Version: 11

James C.

I've noticed this on multiple installations on different hardware.

I have a fresh install of Vmware Esxi 6.5 U3.

After inital testing, I move the phsyical network cable thats plugged into a single unteamed nic used by the Management Network from one switch to another. Now there is no netowkr connectivity. It does not matter if I try DHCP or static assignment, there is no connectivity... ICMP fails etc.

Whats the deal here.. is there a security feature that if the primary Management network NIC is changed, that it just cuts off access?

Does anyone know how to resolve this... I've done lots of searching and cant really find anything.

I have ESXi 5.5 HPE installed on my ProLiant ML350 G6 server and I want to use the web client to manage it. I have downloaded the vSphere 5.5 package and tried to install the vCenter Single Sign-On as a prerequisite to the vSphere Web Client but it fails. According to the log file it is failing while trying to install TCServer version 5.5. Any help to get the web client working would be great. Thanks.

Hi users,

I should update a vsphere HP proliant 460 blade host, 6.0 installed with hp custom image: Build 6765062.

The latest hp custom image I found on vmware website is ESXi 6.0 Update 3, HPE Custom Image for VMware ESXi 6.0 U3 Install CD.

VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019.iso    Release Date: 2019-09-09

on the same page I found also offline bundle

VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip  Release Date: 2019-09-09

Question before update:

Is it correct that I can proceed in two ways?:

1) shut down all VMs, Enter in mantenace mode, restart host with boot 6.0U3 boot CD and follow istruction.

or

2) shut down all VMs, Enter in mantenace mode, copy VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip on a folder in datastore, and then launch command:  esxcli software vib install -d /vmfs/volumes/MyDatastoreID/patchrepository/VMware-ESXi-6.0.0-Update3-13635687-HPE-Gen9plus-600.10.4.5.15-Sep2019-depot.zip

I would point to second way because on proliant blade I should attach a virtual image or burn a CD.

Is it correct?

ps: Then, could I apply the latest VMware patch ESXi600-202002001 build  15517548  released on february 2020, even if hypervisor is HP customized?

Or do I have to waith an hp patch?

Thank you

Is VMFS5 compatible with vSphere 7?  

Seeing the following lines in vmkernel.log

Line 4495: 2020-03-25T19:40:48.006Z cpu11:2097843)ntg3:0000:02:00.1:Ntg3APESendEvent:243:APE event 0x10000 sent

Line 4495: 2020-03-25T19:40:48.006Z cpu11:2097843)ntg3:0000:02:00.1:Ntg3APESendEvent:243:APE event 0x10000 sent

Line 4496: 2020-03-25T19:40:48.006Z cpu11:2097843)ntg3:0000:02:00.1:Ntg3HwReset:607:Starting HW Reset

Line 4496: 2020-03-25T19:40:48.006Z cpu11:2097843)ntg3:0000:02:00.1:Ntg3HwReset:607:Starting HW Reset

Line 4497: 2020-03-25T19:40:48.130Z cpu11:2097843)ntg3:0000:02:00.1:Ntg3HwReset:636:HW Reset Completed

Line 4497: 2020-03-25T19:40:48.130Z cpu11:2097843)ntg3:0000:02:00.1:Ntg3HwReset:636:HW Reset Completed

Vmware forum/blog page says to change the driver for the broadcom from ntg3 to tg3.

However, this is 6.7u3 and there's no tg3 driver for anything after 6.5.

Looking for some ideas as to how to proceed.

So thanks to the lockdown due to covid-19, I've been building a new home lab. (ESXi 6.7u3) with two HP Z600's with additional NIC cards etc. etc.

Anyhow, all 3 NICs show up in the ESXi Networking screen in Physical NICs. vSwitch0 shows 2 port groups, 3 uplinks.  I have VM Network (vmk1) and Management Network (vmk0) in the port groups showing with Active ports and connected to vSwitch0.  TCP/IP stack shows VMKernel NICs.

At this stage all looks good, I can access the esxi on the IP set in the Management Network (vmk0).  I configured vmhba64 in storage adapters, configured the Software iSCSI, and connected my NAS, and it shows up fine in Storage as a Datastore, which I can browse. and upload ISO image to.  All looking good still.

So, go to create a new Virtual machine, Select name, compatibility 6.7 virtual machine, Guest OS, OS family, Guest OS version, select datastore (local VMFS6), virtual hardware.  This is where I hit a brick wall.  Network Adapter 1 is greyed out, no drop-down.  I can expand and select Status, Adapter type and MAC address bits, bit no drop down not the Network Adapter to select VM Network.

On the iSCSI NAS, I placed a previously build and used VM and then imported that, and in the Network adapter if shows as "VM Network (Disconnected)" .  If I got to edit the VM under network adapter this is now also greyed out an has no value in there.

This is the same on both boxes.  I tried a reset of the netowrking, and then just adding a VM with the default DHCP on the server management address and again got the same issue.

Given the access to ESXi and that the iSCSI connection to the NAS works, iI don't think it's a problem with the physical NICs, and one of these actually worked fine before on ESXi 6.5x (I did a clean install to 6.7 and not an upgrade - silly me!).

I messed copying/creating a VM between vCenter 6 and 6.7.  I logged into my ESXi server and located my vm and all I have left is a test-000001-delta.vmdk. 

My question is it possible to create new VM with the delta vmdk? I tried in vCenter 6.7 to create new vm with existing disk and browsed to that folder but it doesn't show up.  I see in the filesystem when I ssh into the ESXi server.

If there is command line option to create new vm with -delta.vmdk, I would appreciate that.

Hello,

I noticed that every 30 seconds, all of my hypervisors have this in their syslog. "office.local" is our domain.

I presume that there is some issue with DNS records for our AD controller? What should I look for?

2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 0
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 0
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 0
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'OFFICE.LOCAL', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 100
2020-04-03T08:01:24Z lwsmd: [netlogon] Looking for a DC in domain 'office.local', site '<null>' with flags 140

Thank you

Hello All,

Some of my Mac OS VMs are having issues while running some tools which fails with graphic related errors.

I want to increase memory from 128 up to 256 to see if that helps.

I do set 256 Video Card -> Total Video memory.

When I power on Mac OS VM I still see 128 MB as display memory.

Thank you.

vmware not detecting storage on hpe proliant dl360 gen10

hello,

the network is being lost and the solution is to going to the console and enable and disable the nic card or rebooting

I tried updating firmware and bios to the latest version but it has no luck

there was no issue on vmware 6.0 before

I belive there was such an issue with 6.0 4 years ago that it was a bug from esxi that solved those days

Thank You

Hi

I want to automatically connect USB devices to a virtual machine in Esxi

The problem:

When HOST is turned off or restarted the settings disappear and need to be manually added again (controller remains)

Do you know a solution?

Thanks

I have several ESXi hosts and I'm trying to get them to join AD so I can roll out administrative permissions through AD groups.   I have joined the servers to the domain and that part worked as expected.

Now, when I go into Permissions to add a group, as soon as I choose my domain in the dropdown, I get the following error:

"A general system error occurred: Error accessing directory: Can't bind to LDAP server for domain <domain name>.   Call "UserDirectory.RetrieveUserGroups" for object "ha-user-directory" on ESXi "<hostname>" failed."

This is occurring on 5 of my 7 ESXi hosts, and there's nothing that I'm aware of that's different on the other two.  

Could this be a problem with requiring LDAPS on my domain?   If so, why would it work on the other two servers?   Just weird.

Any tips would be appreciated.   Thanks!    

Hey, sorry to revive an old thread but I'm trying to do this exact thing and I'm having problems getting this to work using ESXi 6.7 (VM version 14) with a vm hosted on vSphere.

I've edited the vmx file as listed above to add a usb drive:

• ehci.present = "TRUE"
• ehci:0.present = "TRUE"
• ehci:0.deviceType = "disk"
• ehci:0.fileName = "genericdiskname.vmdk"

And upon boot it added:

• ehci.pciSlotNumber = "34"

But then I also noticed it added:

• usb_xhci:4.present = "TRUE"
• usb_xhci:4.deviceType = "hid"
• usb_xhci:4.port = "4"
• usb_xhci:4.parent = "-1"

When the machine hit windows I was unable to see the drives. Is there anything else needed to make this work?

HPE Customized Image ESXi 6.5.0 Update 2 version 650.U2.10.3.5.  Recently updated from a non customized image 6.5.0 Update 2.  I can get the previous build number if needed.

Been having a problem with one of the guests.  Guest is Server 2016 fully patched.  Its having issues with tools timing out in the event log.  I can also see it go from running to no running in the esxi interface.  The error messages are:

Event ID 7011

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the VMTools service.

Event ID 7046

The following service has repeatedly stopped responding to service control requests: VMware Tools

Contact the service vendor or the system administrator about whether to disable this service until the problem is identified.

You may have to restart the computer in safe mode before you can disable the service.

Steps taken.  I updated the ESXI OS to the HPE image specified above.  I updated VMWare tools from 10.2.1.4164 to 10.3.2-9925305 and then ultimately the latest 10.3.5-10430147 with no difference.  The error first showed up 10/2/18.  The Guest is a Veeam Backup Server that seems to run ok despite the error.  The ESXI host has three AWS gateway appliances running on it with out any issues. 

Any ideas?  Suggestions?  Thanks in advance