now downloading vCenter Server 6.0 Update 3a | 21 MAR 2017......
just released
now downloading vCenter Server 6.0 Update 3a | 21 MAR 2017......
just released
are you using this in vmware workstation or physical esxi server
I'm afraid this won't work. Although you may be abl to present a virtual disk to multiple VM's, it's actually the guest OS which need to support shared access to a volume. Unless I'm missing something this option for NTFS is only availably for Hyper-V. Unless supported by the OS you will most likely corrupt the file system with accessing it simultaneously from different VMs.
André
Just following up here... Further testing suggests that the issue is drive-related. I tested with a different USB drive, and the issue does not present.
The drive with a problem is an old Western Digital 320GB ‘My Passport’ drive for what it’s worth.
I had same problem and cause is in proxy configuration. If you configure proxy using GUI, proxy are configured only for http.
In VCSA console try this command:
com.vmware.appliance.version1.networking.proxy.get
If you can set proxy for https to, you can make this throw this command:
com.vmware.appliance.version1.networking.proxy.set --protocol https --server proxy.server --port port_number
After this, Check update finish succesfully
((( VMware Compatibility Guide )))
LINK: http://www.vmware.com/resources/compatibility/search.php
Keyword: SuperMicro X10SRI-F
Server Device and Model Information will help you find the answers to your issue.
"The detailed lists show actual vendor devices that are either physically tested or
are similar to the devices tested by VMware or VMware partners."
Raul.
VMware VDI Administrator
Hey everyone,
Trying 6.5 in my testlab and I'm trying to get the application HA working. But it keeps breaking everytime I run it!
The error is "A general system error occurred: Failed to ssh connect peer node x.x.x.x"
It will successfully clone the Peer node, but then when it goes to ssh in for whatever reason it cannot. I've made sure SSH is enabled on the node, but it's all to no avail.
If anyone has any suggestions, I've given myself a headache trying to think of things.
Hi,
I've just installed my first esxi 5.5 u3 host on Fujitsu Primergy Rx300 S6 server. Server is connected via switch to only one client computer (lab environment). Esxi detected all my NIC cards and I assigned static ip address to one of the NIC. Problem is, I can't ping esxi host from client machine (tried both NIC's). I dont have any vlans or gateways configured. Is it possible that Intel 82575EB NIC card is not supported?
Both host and client machine are on the same subnet of course
My past experience with VMware goes back several years, so I am not up to date, yet. I have tried to locate the documentation on how to assigning static IP to the VM through vSphere client. I have few new VMs on the host. I have the MAC addresses, DNS server address, gateway, etc., and everything is in place. The VMs are not connected to the Management network. The question is how to assign the static IP.
Is there any reference on how to set it up step-by-step?
Hello,
I too have seen this exact problem with ESXi 6.5, with the latest patch (released March 14th 2017) installed. However, I only have it when I hit "enter" after typing in the password. I do not get the error when I click "Log In".
I can completely re-create this error on 2 different ESXi 6.5 systems.
Hit enter after password: "unhandled exception" error.
Click Login: Everything works perfectly.
This issue does exist on Chrome (latest version as of March 20th), but does not exist on Microsoft Edge, the other browser I have installed. So at this moment I am deducting it to be one of two problems: 1) There is a problem with Chrome and ESXi web client that needs to be fixed in Chrome, or 2) There is a problem in the ESXi web client that needs to be fixed.
Since this problem does not exist on any other HTML5 websites in Chrome, I am inclined to think there is a coding error in the ESXi web client that has not yet been found.
I am not impacted as clicking "Log In" works.... but oh man, I do wish VMWare did not abandon the "thick client" idea.....
I just had a slight heart clutching moment with 2 VMs during vmotion. I'm in the process of patching my esxi 6.0 hosts, so I was moving VMs from one that needs to be patched to one that I patched this morning. I've had several VMs running for several hours this morning, so I vmotioned about 30 more with no problem (mostly Linux guests). Then I grabbed another batch of 15 or so, and 2 of them displayed errors like this at the same time:
***
Disconnected from virtual machine
Time: ...
Target: forms1
vCenter Server: fqdn of our vcenter server
Asyncsocket error
Failed to establish transport connection (9): There is no VMware process running for config file /vmfs/volumes/55e627f3-234c9b5a-c329-842b2b7291a5/forms/forms.vmx.
Unable to load configuration file '/vmfs/volumes/55e627f3-234c9b5a-c329-842b2b7291a5/forms/forms.vmx'.
Disconnected from virtual machine.
***
On the source host, the vmfs paths showed up where the VMs were for about 10 seconds, then they disappeared. The VMs both finished migrating successfully, so everything looked good in the client and on the actual VMs. We migrated those VMs around a couple of more times and got no errors.
These hosts are in the same cluster, and I was doing host vmotion only, not to different LUNs. All of our VMs are in LUNs on an Equallogic group connected via 10g switches, and all of this has been running for months with no problems. Any idea what might have caused this?
Welcome to the Community,
static IP addresses for the host are assigned for VMkernel port groups, e.g. the Management Network, vMotion, iSCSI initiators, ...
For the VMs there's noting you need to assign on the ESXi host side. A VM's network configuration is done within the guest OS itself, as if it was installed on a physical hardware.
André
Also do let me know if I need to post this on a different forum.
Do the NICs show up as "Connected" in the host's DCUI (direct console)?
André
I have created three VMs through the .OVA files (Linux-based).
They are not included into the Management network. I have the cluster, and few hosts. All three VMs are located on the same host.
I am not sure where to proceed, still.
The "Management Network" is not related to the virtual machines. It's in place for the ESXi host's management.
In order to use VMs you only need a "Virtual Machine Port Group" on a vSwitch with uplinks to a physical switch/router. The uplinks can be used by the VM Port Groups, and the Management Network, so there's no need for dedicated vSwitches.
André
I've been looking though the logs on my ESXi 6.5 servers with vRealize Log Insight and I noticed that two of my hosts (of 16 total) show errors like the following for different VMs a few times a day. Is this something I need to be concerned about? I haven't been able to find anything by searching by any parts of any of the error messages, but since it seems to be limited to just two hosts i'm thinking there has to be something wrong somewhere, even though operationally I haven't noticed any issues or have had any reported by any of my users.
2017-03-21T20:27:47.980Z esx.mydomain.local Hostd: info hostd[12940B70] [Originator@6876 sub=Libs opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] OBJLIB-LIB: ObjLib_GetNameSpaceObjectUniqueIdFromPath : failed backend does not store object unique id in path
2017-03-21T20:27:47.980Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx': One of the parameters supplied is invalid.
2017-03-21T20:27:47.980Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmxf': Success.
2017-03-21T20:27:47.981Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.nvram': Success.
2017-03-21T20:27:47.981Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmsd': Success.
2017-03-21T20:27:47.982Z esx.mydomain.local Hostd: warning hostd[12940B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine.vmx opID=PowerOnResolver-applyOnMultiEntity-1429936-ngc-b1-01-01-01-01-4c-d68b user=vpxuser] File - failed to get objectId, '/vmfs/volumes/58be03d8-8d1b8309-184b-484d7e596291/a-MyVirtualMachine_2/a-MyVirtualMachine_2-flat.vmdk': Success.
Summary tab will usually show you the warning condition.
SSH or ESXi Shell being enabled will show up here as a warning --disable to clear the warning
HA heartbeat datastores --if you don't have at least 2 it will cause a warning condition.