Once we click Host->Manage->Networking Tab-> vSwitches there is list of vswitches created on host in first column, and second column is for Discovered issues. Please find screenshot attached for the same.
What is it used for? and What type issues are listed in this section?
Thanks,
Abhijeet D
Hi folks,
I'm running into a brick wall with an issue I'm having with snapshots. At some point a few nights ago a configuration change was made to one of our VMs while a snapshot existed for that VM. Afterwards, snapshots have not been functioning properly.
The original snapshot which was there when the configuration change occurred seems to have consolidated into the base disk. However, the snapshot files are still there (1mb in size) and are still there in the snapshot manager.
Creating snapshots on top of that one works fine, but they cannot be consolidated:
An error occurred while consolidating disks: msg.snapshot.error-DUPLICATEDISK.
Examining the .vmsn files shows that the first snapshot and the second snapshot point to the same base disk, rather than the second snapshot pointing to the first snapshot.
I've attached a .zip of all files that seem to be relevant.
My thinking is this: Since we know the first snapshot doesn't contain valuable data (the deltas are empty; they were not growing between the time the first consolidation 'failed' and the second snapshot was created) can we edit the .vmsd of the VM and remove references to the first, broken snapshot? Would this allow the consolidation to ignore that first useless snapshot which points to the same disks as the second and finish successfully?
Thanks!
Hi,
We have a strange problem/bug in our new VMware cluster.
Environment
BL460 gen10 with HP FlexFabric 20Gb 2-port 650FLB Adapter
HPE C7000 chassis
vSphere 6.0 (build 6775062)
ESX01,ESX03 and ESX03 are in chassi01
ESX04,ESX05 and ESX are in chassi02
VMs intermittent loses network connectivity.
When this happens the “remedy” is to migrate the specific VM to some other host in the cluster.
So far it seems that it doesn’t matter if I migrate the VM to a VMhost inside the same chassis or to the other chassis , just a migration seems to solve the issue. (I can’t migrate it back to the same host though)
I have around 150 VMs in this cluster and so far I’ve had issues with 5-6 of them , completely random.
They could be on any of my VMhosts in the cluster.
Haven’t created any support case with VMware or HPE yet , this forum post is my first advance to tackle this problem.
All firmware is updated to the latest from HPE
Someone who have seen similar issues?
Regards
Johan
Hi,
I am using ESXi 5.5. The VM have VMware Tools installed with SVGA driver. I can't change the resolution higher than 1280X800. You know why? You know how to crank to 1920x1980 ?
Thank you,
HI
i have upgraded only one host from esxi5.1 to esxi5.5 u 3 in the cluster.but vmotion struct at 14%. from esxi5.1 to esxi5.5.
what could be the reason for this issue.
I created an account on my local esxi server with admin role but cannot login with the password I set
any idea?
Running ESXi v6.5u1.
I would like to shutdown all running VM's except for one.
Running /sbin/shutdown.sh will shutdown all running VM's (auto started vm's with vmware tools installed, that is) but I need one VM to stay alive.
Is there a way to accomplish this?
Hi,
I face the followings problem when installing EXSI 6.5 Update into SuperServer 6018R-TD.
Error Loading /User.b00
Compressed MD5: 5f56957c8e7b16358db3bf32c31d27065
Decompressed mD5: 000000000000000000000000000000000
Fatal Error: 10 (out of resource)
Any one have any ideal what result in this problem?
Best Regards,
Albert
Hello,
I'm trying to install updates from a zip file but always gives the same error. "No Space Left On Device"
But there is a plenty of space on Device.
When i try to run
esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201703001.zip
it gives that error:
[InstallationError]
[Errno 28] No space left on device
vibs = VMware_bootbank_misc-drivers_6.0.0-3.57.5050593
Please refer to the log file for more details.
And in the log file:
2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list | grep /stagebootbank && localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.
2017-04-02T00:13:50Z esxupdate: BootBankInstaller.pyc: WARNING: Cannot remove staging directory: [Errno 16] Device or resource busy: '/tmp/stagebootbank'
2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list | grep /stagebootbank && localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.
2017-04-02T00:13:51Z esxupdate: root: ERROR: Traceback (most recent call last):
2017-04-02T00:13:51Z esxupdate: root: ERROR: File "/usr/lib/vmware/esxcli-software", line 462, in <module>
2017-04-02T00:13:51Z esxupdate: root: ERROR: main()
2017-04-02T00:13:51Z esxupdate: root: ERROR: File "/usr/lib/vmware/esxcli-software", line 453, in main
2017-04-02T00:13:51Z esxupdate: root: ERROR: ret = CMDTABLE[command](options)
2017-04-02T00:13:51Z esxupdate: root: ERROR: File "/usr/lib/vmware/esxcli-software", line 362, in VibInstallCmd
2017-04-02T00:13:51Z esxupdate: root: ERROR: checkacceptance=checkacceptance)
2017-04-02T00:13:51Z esxupdate: root: ERROR: File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 250, in InstallVibsFromSources
2017-04-02T00:13:51Z esxupdate: root: ERROR: File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 356, in _installVibs
2017-04-02T00:13:51Z esxupdate: root: ERROR: File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 399, in _validateAndInstallProfile
2017-04-02T00:13:51Z esxupdate: root: ERROR: File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 710, in Stage
2017-04-02T00:13:51Z esxupdate: root: ERROR: File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 483, in _download_and_stage
2017-04-02T00:13:51Z esxupdate: root: ERROR: InstallationError: ('VMware_bootbank_vsanhealth_6.0.0-3000000.3.0.3.58.5224738', '[Errno 28] No space left on device')
"vdf -h" Output
Ramdisk Size Used Available Use% Mounted on
root 32M 244K 31M 0% --
etc 28M 204K 27M 0% --
opt 32M 0B 32M 0% --
var 48M 428K 47M 0% --
tmp 256M 20K 255M 0% --
iofilters 32M 0B 32M 0% --
hostdstats 303M 2M 300M 0% --
As you can see %0 is used on /tmp i dont know why gives that error.
How can i fix this problem ? I cant update my esxi 3620759 to 5224934.
Dear,
We encountering connectivity issue on newly install esxi 6.5 on PE R430
Whenever we preform file copy (30-40GB files size) from one of the VM Guest to another machine thought network (100MB), it end up with connectivity issue.
Both VM guest and host became inaccessible thought network.
ESX console can still be access, try with "restart management network" and use "testing management network" with result OK on default gateway or other machine.
But unable to access both guest and host thought network.
Connection become normal after shutdown / restart the esx host.
Check with VM guest OS event log, indicated that it should still be running during issue and following the auto shutdown/startup setting of esx host.
Look into log and found the following warning keep prompt during copy task perform.
cpu## :67701)WARNING: ntg3-throttled: Ntg3XmitPktList:372: vmnic0:TX ring full (0)
I wonder if anyone with suggestion on this issue? thx
This happened to me a few months ago on a fresh install of the vcenter appliance 6.5. It just stopped working a week or two after applying an update. Services would not start and there was no indication as to why. It wasn't a space issue, it wasn't that other issue with a duplicate value in the vpostgres database I read about either. I finally gave up and wiped it out to redeploy from scratch.
Well low and behold, sometime last night vcenter stopped working again. This time it wasn't even a full week after having applied the 6.5.0c patch. Only two services start, none of the others will. My deployment is two appliances, a PSC and the vCenter. The PSC appears fine and the services are showing healthy. The vCenter turned to garbage again. Here's an output of service-control:
root@mp1vsivcs501 [ ~ ]# service-control --status Running: lwsmd vmafdd Stopped: applmgmt vmcam vmonapi vmware-cm vmware-content-library vmware-eam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-rbd-watchdog vmware-rhttpproxy vmware-sca vmware-sps vmware-statsmonitor vmware-updatemgr vmware-vapi-endpoint vmware-vcha vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui
Trying to start any service produces a similar output:
root@mp1vsivcs501 [ ~ ]# service-control --start vmware-vpxd-svcs
Perform start operation. vmon_profile=None, svc_names=['vmware-vpxd-svcs'], include_coreossvcs=False, include_leafossvcs=False
2017-04-24T19:36:49.136Z Running command: ['/usr/bin/systemctl', 'set-environment', 'VMON_PROFILE=NONE']
2017-04-24T19:36:49.140Z Done running command
2017-04-24T19:36:49.143Z Running command: ['/usr/bin/systemctl', 'daemon-reload']
2017-04-24T19:36:49.222Z Done running command
2017-04-24T19:36:49.222Z Running command: ['/usr/bin/systemctl', 'set-property', u'vmware-vmon.service', 'MemoryAccounting=true', 'CPUAccounting=true', 'BlockIOAccounting=true']
2017-04-24T19:36:49.227Z Done running command
2017-04-24T19:36:49.231Z RC = 1
Stdout =
Stderr = Failed to execute operation: Unit file is masked
2017-04-24T19:36:49.231Z { "resolution": null, "detail": [ { "args": [ "Stderr: Failed to execute operation: Unit file is masked\n" ], "id": "install.ciscommon.command.errinvoke", "localized": "An error occurred while invoking external command : 'Stderr: Failed to execute operation: Unit file is masked\n'", "translatable": "An error occurred while invoking external command : '%(0)s'" } ], "componentKey": null, "problemId": null
}
2017-04-24T19:36:49.231Z Running command: ['/usr/bin/systemctl', 'unset-environment', 'VMON_PROFILE']
2017-04-24T19:36:49.235Z Done running command
Error executing start on service vpxd-svcs. Details { "resolution": null, "detail": [ { "args": [ "vmware-vmon" ], "id": "install.ciscommon.service.failstart", "localized": "An error occurred while starting service 'vmware-vmon'", "translatable": "An error occurred while starting service '%(0)s'" } ], "componentKey": null, "problemId": null
}
Service-control failed. Error { "resolution": null, "detail": [ { "args": [ "vmware-vmon" ], "id": "install.ciscommon.service.failstart", "localized": "An error occurred while starting service 'vmware-vmon'", "translatable": "An error occurred while starting service '%(0)s'" } ], "componentKey": null, "problemId": null
}
The first thing that pops out for me is line 11, "Failed to execute operation: Unit file is masked". I get that on every service I attempt to start and I'm not finding anything in VMware's knowledge portal about it. This is extremely frustrating.
**Additional info**
Running a search on just unit file is masked took me to a generic ubuntu thread about systemctl showing masked unit files. Here's the output of the systemctl list-unit-files:
root@mp1vsivcs501 [ ~ ]# systemctl list-unit-files | grep vmware vmware-bigsister.service static vmware-cm.service masked vmware-content-library.service masked vmware-eam.service masked vmware-firewall.service enabled vmware-imagebuilder.service masked vmware-mbcs.service masked vmware-netdump.service masked vmware-perfcharts.service masked vmware-rbd-watchdog.service masked vmware-rhttpproxy.service masked vmware-sca.service masked vmware-sps.service masked vmware-statsmonitor.service masked vmware-updatemgr.service masked vmware-vapi.service masked vmware-vcha.service masked vmware-vmon.service masked vmware-vmonapi.service masked vmware-vpostgres.service masked vmware-vpxd-svcs.service masked vmware-vpxd.service masked vmware-vsan-health.service masked vmware-vsm.service masked vmware-bigsister.timer disabled
Not sure if that's normal or not, but it appears to be what the error message is complaining about?
Message was edited by: jhboricua
I have handful of Win2k8 64bit vm's on esx5.5 update 2 that are showing "VMware Vista Physical Disk Helper" have the error 'This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)'. The VMware Tools versions vary, either 9.4.0 build-1585188, 9.4.5 build-1598834, or 9.4.10 build-2068191.
Google has failed me for the most part. I can't find any concrete information on what this virtual device is or what it does specifically, except that it may be involved in creating quiesced snapshots.
Also, the device appears to be attached to the vmrawdsk service, which doesn't exist on the server. These VM's were not P2V, they were created from win iso.
Any guesses on what this is and how I might be able to fix it?
After patching the VCSA to 6.0 u3d, we patched our DL380 Gen9 ESXi hosts with ESXi600-201801001 (patch and microcode). After reboot, the two hpsa P440 and P440ar storage controllers were not visible in vCenter. Obviously this wreaked havoc on the vSAN which is how I discovered the issue. I found that there were driver and firmware updates on them so I updated both, then tried the install again and had the same issue. I have a ticket open with VMware right now and awaiting a response. Wondering if anyone else is having this issue.
hi,
Are you able to get or use a HTML5 client when you connect directly to a Esxi host instead of the flash version?
i.e can you use a interface like the vsphere client for vcenter. but for a direct connection to a Esxi Host.
Matt
Hello all!
Anybody complete this quest?
How fix this issue
Purpose of this post is simple and obvious... bring back development to thick client. THANKS!
hello,
i am testing gpu passthrough to my vm(s). i have 2 gpus in the host, and i'm able to pass through gpu#1 to the vm. gpu#2 is used by esxi.
now i would like to add a second vm, and pass gpu#2 to it. for this i need to make sure that esxi doesn't use the gpu at boot time.
so essentially, i would like to turn esx into a headless system.
the only thing i found in the docs was this
"You can set the headless flag in the ACPI FADT table to mark a system as headless"
can someone explain how that is done exactly?
Anyone know why ESXi-5.5.0-20180104001-standard is missing from hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml as of tonight? I'm in the middle of patching some hosts and it disappeared yet the 6.0 & 6.5 profiles are still there.
System Information
Microsoft Edge 41.16299.15.0
Microsoft EdgeHTML 16.16299
Windows 10 Pro
Version 1709
OS Build 16299.192
ESXi 6.5.0 Update 1 (Build 7526125)
This is more of a bug report. The work around is to use another web browser.
I was creating a new VM and step 4 Customize settings appeared with the data fields blank and an error message triggered by the validation rules. This has not been the only time I have had this happen to me with Edge. Using Chrome I do not have the same problem.
Attached is a screen shot of what I saw. I did not change any settings. This is how the form looked when I navigated from step 3 Select storage.
The Edge developer tools do not report any JavaScript errors.
I understand nested ESXi instances may not be supported. I would like to report that something has changed recently with the ESXi 6.0 and ESXi 6.5 that breaks network communications for nested ESXi guests.
The setup is the following.
An ESXi host has a guest with ESXi 6.5 installed. In the nested ESXi instance a guest is created. The nested guest cannot connect to hosts beyond the nested host though the network. This setup worked as of Monday last week. The changes are each ESXi Host has likely had the latest patches applied. Upon rebooting the nested ESXi's guests network connections failed to work.
Hardware -> ESXi Host -> (guest) nested ESXi -> (nested guest)
The symptoms of the network connections are as follows. A nested guest is unable to obtain an IP though DHCP. If the nested guest is assigned a static IP it is able to ping the nested ESXi host. The nested guest cannot ping the gateway address, DNS servers or other hosts on the same network subnet that are not nested guests. The nested guest does not get ARP data for the network subnet.
I first encountered this issue when I patched two nested ESXi 6.5 to build 7526125. Both of these instances had existing guests and the networking was working correctly before the patch. The patch required the nested ESXi host to reboot. Upon reboot the nested ESXi guests network connections failed to work. All settings appeared correct. The physical hardware hypervisor in this situation is ESXi 6.0. I do not know what patches it has.
To see if the issue is repeatable I tested the following.
In each of the tests the nested guests were tested with PFSense, Windows 10, and Ubuntu Desktop.
1. Create a new install of a nested ESXi 6.6 on the ESXi 6.0 host. Apply patches but not apply the 7526125 patch.
Hardware -> ESXi 6.0 Host -> (guest) nested ESXi 6.5 -> nested guest
Upon each patch I would test and if it failed I would recreate the nested ESXi instance and upgrade the patch before the last and test. In all tests the nested guest failed to obtain a network connection.
Something with the ESXi 6.0 host could be causing the problem.
2. My home ESXi servers were already patched to 7526125. I attempted the same tests created a nested ESXi 6.5 with different guests. Each time I had the same result. The nested guest DHCP would not work and the static IP would only ping the nested host but no other computer on the subnet.
3. I created an ESXi 6.5 guest in VMWare Fusion 8.x. I patched it to 7526125 and a nested guest was able to communicate with the network. The ESXi 6.5 guest network was setup as a proxy sharing the host's network connection.
This is more of a bug report. I don't know if there are any redacted patches for 6.0 but it looks like 6.5 7526125 might have been redacted.
As of now my nested ESXi setup is dead. I can't figure out how to recover the network connectivity. I think if the ESXi 6.0 or 6.5 host is patched to a build it does not matter what version the nested ESXi guest is running. A nested guest's network connections will not work correctly.