Hi everyone, In the original post, the screen shot shows that the portgroup on the vswitch has a vmkernel interface attached to it. Portgroups with vmkernel interfaces are not available to att...
See more...
Hi everyone, In the original post, the screen shot shows that the portgroup on the vswitch has a vmkernel interface attached to it. Portgroups with vmkernel interfaces are not available to attach to VM virtual network adapters. To create a VM network in the ESXi Host Client you would click on Networking, then Port groups, then Add port group. You can then choose the vswitch you want to use and any security settings. i.e.
Hi all, If the host client is not doing The Right Thing, then it's because I did it wrong Can someone explain to me the consequences of not aligning to 1MB?
Hi, I have recently become aware of this issue. It seems to be specific to Firefox and IE. Chrome is unaffected. I believe I have a fix, which will be included in a soon to be released fling ...
See more...
Hi, I have recently become aware of this issue. It seems to be specific to Firefox and IE. Chrome is unaffected. I believe I have a fix, which will be included in a soon to be released fling and the upcoming first patch update for ESXi 6.5 Can you use Chrome for now?
Hi everyone, I think I have some insight into this failure now. For VMs that have been exported with ovftool using the --compress argument, the Host Client is unable to deploy them because the...
See more...
Hi everyone, I think I have some insight into this failure now. For VMs that have been exported with ovftool using the --compress argument, the Host Client is unable to deploy them because the ESXi host expects the uncompressed disk images to be uploaded, and we have, unfortunately, no good way to un-gzip those disk images using the web browser at the moment. For now, you will have to use ovftool to import VMs with compressed disk images.
Thanks for confirming! For the benefit of others, the latest version of the Host Client Fling, version 1.13.0, available at [1] now has a new panel, Host -> Monitor -> Hardware -> Storage whi...
See more...
Thanks for confirming! For the benefit of others, the latest version of the Host Client Fling, version 1.13.0, available at [1] now has a new panel, Host -> Monitor -> Hardware -> Storage which displays storage health data. [1] ESXi Embedded Host Client
OK, the answer was staring me right in the face: wmks.min.js:1 2016-11-03T05:24:54.101Z [Info ] Using authentication scheme: 2 wmks.min.js:1 2016-11-03T05:24:54.101Z [Info ] vnc authentica...
See more...
OK, the answer was staring me right in the face: wmks.min.js:1 2016-11-03T05:24:54.101Z [Info ] Using authentication scheme: 2 wmks.min.js:1 2016-11-03T05:24:54.101Z [Info ] vnc authentication not implemented The HTML console does not currently support VNC authentication. Do you have the following set in the VMX file? RemoteDisplay.vnc.password Actually, upon further testing, you can have that key set, but if you have RemoteDisplay.vnc.enabled = "FALSE" then you can still use the HTML console. So you just need to disable VNC for that VM. Etienne
Thanks for supplying the info. I'm still investigating, it would also be useful if you could provide us the vmware.log file from a VM on the host where the console is not working, after you attem...
See more...
Thanks for supplying the info. I'm still investigating, it would also be useful if you could provide us the vmware.log file from a VM on the host where the console is not working, after you attempt to open a console. You may have to enable logging in the VM's settings under VM options.
Hi there, Firstly, can you confirm a couple of things for me on the non-working host. 1) Has this host been upgraded from a previous version of ESXi? 2) Can you post the contents of /etc...
See more...
Hi there, Firstly, can you confirm a couple of things for me on the non-working host. 1) Has this host been upgraded from a previous version of ESXi? 2) Can you post the contents of /etc/vmware/rhttpproxy/endpoints.conf
Hi there, It's likely that changes you made to the reverse proxy configuration have been reverted on reboot, unfortunately. In 5.0, the configuration is held in /etc/vmware/hostd/proxy.xm...
See more...
Hi there, It's likely that changes you made to the reverse proxy configuration have been reverted on reboot, unfortunately. In 5.0, the configuration is held in /etc/vmware/hostd/proxy.xml. Find an entry that looks like: <e id="2"> <_type>vim.ProxyService.LocalServiceSpec</_type> <accessMode>httpsWithRedirect</accessMode> <por>8308</port> <serverNamespace>/ui</serverNamespace> </e> Remove that entry. Unfortunately, there is still more to do. You need to re-number the other entries, and change the <_length> value at the top of the file. Restart hostd and now, your host client should work! You still have to have the trailing / though.
Hi, We fixed this issue some time ago, and will be releasing an updated version with the next 6.0 Patch release. For now, you could install the latest fling release: labs.vmware.com/flings/...
See more...
Hi, We fixed this issue some time ago, and will be releasing an updated version with the next 6.0 Patch release. For now, you could install the latest fling release: labs.vmware.com/flings/esxi-embedded-host-client
Thanks for reporting this issue. We have resolved it in new versions of the Host Client. Could you try the latest fling release? labs.vmware.com/flings/esxi-embedded-host-client
Hi all, We fixed an issue in the recently released host client version 1.9.1 that could cause a large OVA to fail to deploy. The VIB is available here: http://labs.vmware.com/flings/esxi-embed...
See more...
Hi all, We fixed an issue in the recently released host client version 1.9.1 that could cause a large OVA to fail to deploy. The VIB is available here: http://labs.vmware.com/flings/esxi-embedded-host-client Would any of you be able to try that and confirm if the issue is resolved? I'd also be interested to know which browser/OS you're using. I apologise for the long delay in finding this.
