couples of times in a day my vcenter disconnect and when i connect back all esxi hosts update SSL thumprint registry update message is completed.

esxi 5.5U3

vcenter 5.5

vsphere Replication is enabled with no SRM

any suggestion?

Hello Everyone,

I have a Q170 based motherboard and have successfully loaded ESXi 6.5.0. However, ESXi does not display any Hardware Sensor Data and reports "No Sensor Data Available".

Does ESXi require BMC or IMPI to obtain hardware database? Does it not get at least basic sensor information from the CPU sensors, etc.?

Thanks

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.

Hi,

I'm a bit confused. I have a one CPU VM with 4GB of RAM running with some other VMs on a 2 socket 8 core hyper-threading ESX 6.5 host with 128GB RAM.

When you have a look at the screenshot you see a VM with GID 253323 which uses NRMEM. How is that possible with a single CPU VM?

Thanks for your thoughts.

Wolfgang

Hello,

I have VM with VMXNET3 and Windows Server 2016

Receive Side Scaling is Enabled:

PS C:\Windows\system32> Get-NetAdapterRss

Name                                            : Ethernet0

InterfaceDescription                            : vmxnet3 Ethernet Adapter

Enabled                                         : True

NumberOfReceiveQueues                           : 4

Profile                                         : NUMAStatic

BaseProcessor: [Group:Number]                   : 0:0

MaxProcessor: [Group:Number]                    : 0:3

MaxProcessors                                   : 4

RssProcessorArray: [Group:Number/NUMA Distance] : 0:0/0  0:1/0  0:2/0  0:3/0

IndirectionTable: [Group:Number]                :

C:\Windows\system32>netsh int tcp show global

Querying active state...

TCP Global Parameters

----------------------------------------------

Receive-Side Scaling State          : enabled

Chimney Offload State               : disabled

NetDMA State                        : disabled

Direct Cache Access (DCA)           : disabled

Receive Window Auto-Tuning Level    : normal

Add-On Congestion Control Provider  : none

ECN Capability                      : enabled

RFC 1323 Timestamps                 : disabled

Initial RTO                         : 3000

Receive Segment Coalescing State    : enabled

Non Sack Rtt Resiliency             : disabled

Max SYN Retransmissions             : 2

TCP Fast Open                       : disabled

but, RSS not work on this adapter:

PS C:\Windows\system32> Get-SmbServerNetworkInterface

Scope Name Interface Index RSS Capable RDMA Capable Speed   IpAddress

---------- --------------- ----------- ------------ -----   ---------

*          3               False       False        10 Gbps 192.168.0.100

PS C:\Windows\system32> Get-SmbClientNetworkInterface

Interface Index RSS Capable RDMA Capable Speed    IpAddresses               Friendly Name

--------------- ----------- ------------ -----    -----------               -------------

3               False       False        10 Gbps  {192.168.0.100}            Ethernet0

2               False       False        100 Kbps {fe80::5efe:192.168.0.100} isatap.*******

Why RSS Capable is False???

Hi everyone,

I am the happy owner of six Dell R630 with the free ESXi 6 stantard image (VMware ESXi 6.0.0 build-3620759) installed on SD cards.

The ESXis are split in two different datacenter. There is no shared storage and no vCenter. There are 4 to 12 VMs and plenty of spare resources on each host.

Sometimes, apparently at random, I experience what I can only call an "Unknown:" syslog messages storm from a host or another. Like... millions of them in a few minutes.

The log messages are just rows of :

2017-01-15T20:48:58Z Unknown:

2017-01-15T20:48:58Z Unknown:

2017-01-15T20:48:58Z Unknown:

2017-01-15T20:48:58Z Unknown:

2017-01-15T20:48:58Z Unknown:

2017-01-15T20:48:58Z Unknown:

Enough to blow the 7 logrotate history in less than a minute:

-rw-------    1 root     root          2628 Jan 15 20:48 syslog.0.gz

-rw-------    1 root     root          2629 Jan 15 20:48 syslog.1.gz

-rw-------    1 root     root          2627 Jan 15 20:48 syslog.2.gz

-rw-------    1 root     root          2626 Jan 15 20:48 syslog.3.gz

-rw-------    1 root     root          2630 Jan 15 20:48 syslog.4.gz

-rw-------    1 root     root          2628 Jan 15 20:48 syslog.5.gz

-rw-------    1 root     root          2630 Jan 15 20:48 syslog.6.gz

-rw-------    1 root     root          2630 Jan 15 20:48 syslog.7.gz

-rw-------    1 root     root        420397 Jan 15 21:08 syslog.log

And fill up our 60Go remote syslog server in a few hours (~5 hours, and more or less 405000000 rows, for only one server storming).

Killing the vmsyslogd processes is enough to stop the storm. They are automatically restarted, and i receive normal syslog messages afterward...until the next storm...

I'll dig again in the remote syslog history tomorrow. With a little luck there will be something useful but so far, nothing...

If anyone knows something about my problem or have any clue...help appreciated.

Thanks in advance.

Hi, I recently bought this motherboard

https://www.supermicro.com/products/motherboard/Xeon/C236_C232/X11SSH-CTF.cfm

I paired the board with a Xeon E3-1245. I am trying to install ESXI 6.5 directly on the hard drive in the board, however whenever I try, I get No network adapters found. I also note that during init process nfs41client does not load. there are other modules which dont but by the time i can read it its gone.

I have checked though the forums and i have noted that the board has 2 10 Gbps NIC and it connected to a 1Gbps Switch and it is running in 1Gbps mode. I also see that there is an updated VIB file for this but i am not sure how to package it with the installer.

Could someone help a beginner out? This is my first time trying out in an actual machine rather than VMware player.

I am no longer able to connect USB hard drives to any guest.  I have the them connected directly to the host, but when I try to connect it to a guest in vSphere it is not listed.  I can see the USB devices when I do a lsusb in the shell.  I have verified that the USB controller is installed on the guest.

I have tried restarting the usbarbitrator service by:

/etc/init.d/usbarbitrator stop

/etc/init.d/usbarbitrator start

I don't receive any errors when it starts.

I have also restarted the host.

I am running ESXi 5.0 on a single host and the guests are on hardware version 8.

Hi,

I am experiencing issues when using the Automation Tool (ESXi 5.1 Update 1).

When following the step-by-step process:

1. Update the Single-Sign on SSL Certificate

Once this certificate is updated we find we can no longer log into the MOB. However, we continue onto the next steps regardless:

2.  Update Inventory Service trust to Single Sign-On

3.  Update the Inventory Service SSL Certficiate

4.  Update vCenter Server trust to Single Sign-On

Then at step 5 it fails:   Update the vCenter Server SSL Certificate

The errors are:     HTTP ERROR:  Unable to read or open Page

                          HTTP ERROR:  401 Basic Auth Error

We are 100% sure the password are correct (unless these are being changed by something else in this process?) and all of our certificates look ok.

I can't believe I am the first one to ask this question, but search here and on the Internet in general did not produce any hits.

OMB mandated Fed Gov to enable dual stack which we complied with in my environment to include esxi 5.5 hosts

We still want to prefer ipv4 for everything, since we are not ready to go ipv6 only, and we want to avoid having some services using one stack and other services using the other. This creates extra overhead, complexity, troubleshooting issues, etc.

Right now we are dealing with the fact that a dual-stack esxi host uses ipv6 for syslog. While there are tons of info on how to prefer ipv4 on dual-stack Linux servers, there is nothing for ESXi.

Any help would be appreciated.

Hello all-

just attempted to update my ESXi server from 5.1 799733 to 5.1U1 1065491.  During the upgrade the process hangs at 24% completion with the error message as above:

OSError: [Errno 39] Directory not empty: '/vmfs/volumes/3934f7e6-f070467f-afd0-f0ef312248d9/state.7173326'

I have retried a second time with the same result.  Is there any workaround?  Or can I perform a clean install and just import the VMs from the datastores without any problems?

Hello,

ESXi 6 host with 2* 6 core Xeon 2,53GHz

VM with 6 vCPU (Windows Server 2008 R2)

VM OS monitored via PRTG.

When PRTG show VM OS CPU load ~80%, vSphere Client Performance Chart show CPU usage ~8255 MHz.

Very strange.

6*2.53GHz = 15180 MHz

80% * 15180 =  12144 MHz

Why vSphere Client Performance Chart show only 8255 MHz?

I am at 6.0 ESXi hosts.   Browsing at a few datastores, I see some VMs have vswp files that are months older than today's date.  Would not the file be the current date, or is the time stamp from when the file was created?  To clear/reset this, would I just power off the machine and power it back on?  I  happened to notice this since a few datastores are needing space and I am looking to cleanup the files first.

Hi,

I am unable to figure out why our ESXi 6.0.0 randomly reboots. When that happens, the two virtual servers running off it, just disappear from the network of course, only to come back about 20 minutes later. It almost looks like the ESXi is crashing, rebooting and automatically launching the virtual servers. I have connected it to a new UPS (a week old or so), which is connected to a separate outlet from the rest of the gear (switches, routers, etc...). The ESXi is the only thing connected to this new UPS. There is a USB cable connected from the back of the UPS to the ESXi. I have collected two sets of logs, one from a month ago or so, which I'll post first, and one from today, which I'll post second:

First Set of Logs (about a month old):

[root@KETKHST001:~] cat /var/log/vmksummary.log | grep bootstop

2017-01-07T05:57:43Z bootstop: Host has booted

2017-01-20T14:15:15Z bootstop: Host has booted

2017-01-20T23:02:58Z bootstop: Host has booted

2017-02-03T22:19:14Z bootstop: Host has booted

2017-02-15T14:14:56Z bootstop: Host has booted

2017-02-18T15:13:32Z bootstop: Host has booted

2017-03-04T14:29:44Z bootstop: Host has booted

2017-03-18T13:46:02Z bootstop: Host has booted

2017-04-01T13:02:04Z bootstop: Host has booted

2017-04-15T12:18:18Z bootstop: Host has booted

2017-04-24T22:19:35Z bootstop: Host has booted

2017-05-08T21:35:46Z bootstop: Host has booted

2017-05-21T20:13:12Z bootstop: Host has booted

2017-05-26T11:13:53Z bootstop: Host has booted

2017-05-30T15:25:07Z bootstop: Host is rebooting

2017-05-30T16:02:22Z bootstop: Host has booted

2017-06-09T10:30:05Z bootstop: Host has booted

2017-06-15T20:07:00Z bootstop: Host has booted

[root@KETKHST001:~] esxcfg-advcfg -g /Misc/BlueSreenTimeout

Exception occured: Unable to find option BlueSreenTimeout

[root@KETKHST001:~] cat /var/log/hostd.log | grep poweroff

[root@KETKHST001:~] cat /var/log/hostd.log | grep shutdown

2017-06-15T20:06:48.559Z info hostd[FFCFDA80] [Originator@6876 sub=Solo.VmwareCLI] (vim.EsxCLI.system.shutdown) ha-cli-handler-system-shutdown created

2017-06-15T20:06:53.700Z info hostd[FFCFDA80] [Originator@6876 sub=TagExtractor] 8: Rule type=[N5Hostd6Common31MethodNameBasedTagExtractorRuleE:0x1f450560], id=rule[VMFoundryOpRule], tag=IsVMFoundryOp, regex=vim\.VirtualMachine\.(acquireMksTicket|clone|createSecondary|createSnapshot|customize|disableSecondary|enableSecondary|makePrimary|migrate|mountToolsInstaller|powerOff|powerOn|rebootGuest|reconfigure|reload|reloadFromPath|relocate|removeAllSnapshots|turnOffFaultTolerance|recommendHostsForSecondaryVm|rename|reset|resetGuestInformation|retrieveScreenshot|revertToCurrentSnapshot|revertToSnapshot|screenshot|setScreenResolution|shutdownGuest|standbyGuest|startRecording|startReplaying|stopRecording|stopReplaying|suspend|terminate|terminateFaultTolerantVM|unmountToolsInstaller|unregister|upgradeTools|upgradeVirtualHardware) - Identifies Virtual Machine operat

[root@KETKHST001:~] cat /var/log/hostd.log | grep reboot

2017-06-15T20:06:53.700Z info hostd[FFCFDA80] [Originator@6876 sub=TagExtractor] 8: Rule type=[N5Hostd6Common31MethodNameBasedTagExtractorRuleE:0x1f450560], id=rule[VMFoundryOpRule], tag=IsVMFoundryOp, regex=vim\.VirtualMachine\.(acquireMksTicket|clone|createSecondary|createSnapshot|customize|disableSecondary|enableSecondary|makePrimary|migrate|mountToolsInstaller|powerOff|powerOn|rebootGuest|reconfigure|reload|reloadFromPath|relocate|removeAllSnapshots|turnOffFaultTolerance|recommendHostsForSecondaryVm|rename|reset|resetGuestInformation|retrieveScreenshot|revertToCurrentSnapshot|revertToSnapshot|screenshot|setScreenResolution|shutdownGuest|standbyGuest|startRecording|startReplaying|stopRecording|stopReplaying|suspend|terminate|terminateFaultTolerantVM|unmountToolsInstaller|unregister|upgradeTools|upgradeVirtualHardware) - Identifies Virtual Machine operat

[root@KETKHST001:~]

Second Set of Logs (happened today):

[root@KETKHST001:~] cat /var/log/vmksummary.log | grep bootstop

2017-01-07T05:57:43Z bootstop: Host has booted

2017-01-20T14:15:15Z bootstop: Host has booted

2017-01-20T23:02:58Z bootstop: Host has booted

2017-02-03T22:19:14Z bootstop: Host has booted

2017-02-15T14:14:56Z bootstop: Host has booted

2017-02-18T15:13:32Z bootstop: Host has booted

2017-03-04T14:29:44Z bootstop: Host has booted

2017-03-18T13:46:02Z bootstop: Host has booted

2017-04-01T13:02:04Z bootstop: Host has booted

2017-04-15T12:18:18Z bootstop: Host has booted

2017-04-24T22:19:35Z bootstop: Host has booted

2017-05-08T21:35:46Z bootstop: Host has booted

2017-05-21T20:13:12Z bootstop: Host has booted

2017-05-26T11:13:53Z bootstop: Host has booted

2017-05-30T15:25:07Z bootstop: Host is rebooting

2017-05-30T16:02:22Z bootstop: Host has booted

2017-06-09T10:30:05Z bootstop: Host has booted

2017-06-15T20:07:00Z bootstop: Host has booted

2017-06-23T20:01:55Z bootstop: Host is powering off

2017-06-23T20:09:05Z bootstop: Host has booted

2017-07-07T17:42:08Z bootstop: Host has booted <----- This happened today

2017-07-07T17:57:44Z bootstop: Host is rebooting

2017-07-07T18:12:47Z bootstop: Host has booted <----- After auto reboot of the ESXi, one of the VM got stuck in "powering on" so I had to force shutdown the ESXi and reboot again

[root@KETKHST001:~] esxcfg-advcfg -g /Misc/BlueSreenTimeout

Exception occured: Unable to find option BlueSreenTimeout

[root@KETKHST001:~] cat /var/log/hostd.log | grep poweroff

[root@KETKHST001:~] cat /var/log/hostd.log | grep shutdown

2017-07-07T17:41:55.653Z info hostd[FFB8BA80] [Originator@6876 sub=Solo.VmwareCLI] (vim.EsxCLI.system.shutdown) ha-cli-handler-system-shutdown created

2017-07-07T17:42:01.377Z info hostd[FFB8BA80] [Originator@6876 sub=TagExtractor] 8: Rule type=[N5Hostd6Common31MethodNameBasedTagExtractorRuleE:0x28529e08], id=rule[VMFoundryOpRule], tag=IsVMFoundryOp, regex=vim\.VirtualMachine\.(acquireMksTicket|clone|createSecondary|createSnapshot|customize|disableSecondary|enableSecondary|makePrimary|migrate|mountToolsInstaller|powerOff|powerOn|rebootGuest|reconfigure|reload|reloadFromPath|relocate|removeAllSnapshots|turnOffFaultTolerance|recommendHostsForSecondaryVm|rename|reset|resetGuestInformation|retrieveScreenshot|revertToCurrentSnapshot|revertToSnapshot|screenshot|setScreenResolution|shutdownGuest|standbyGuest|startRecording|startReplaying|stopRecording|stopReplaying|suspend|terminate|terminateFaultTolerantVM|unmountToolsInstaller|unregister|upgradeTools|upgradeVirtualHardware) - Identifies Virtual Machine operat

2017-07-07T18:12:34.575Z info hostd[FFCC9A80] [Originator@6876 sub=Solo.VmwareCLI] (vim.EsxCLI.system.shutdown) ha-cli-handler-system-shutdown created

2017-07-07T18:12:39.303Z info hostd[FFCC9A80] [Originator@6876 sub=TagExtractor] 8: Rule type=[N5Hostd6Common31MethodNameBasedTagExtractorRuleE:0x57821eb8], id=rule[VMFoundryOpRule], tag=IsVMFoundryOp, regex=vim\.VirtualMachine\.(acquireMksTicket|clone|createSecondary|createSnapshot|customize|disableSecondary|enableSecondary|makePrimary|migrate|mountToolsInstaller|powerOff|powerOn|rebootGuest|reconfigure|reload|reloadFromPath|relocate|removeAllSnapshots|turnOffFaultTolerance|recommendHostsForSecondaryVm|rename|reset|resetGuestInformation|retrieveScreenshot|revertToCurrentSnapshot|revertToSnapshot|screenshot|setScreenResolution|shutdownGuest|standbyGuest|startRecording|startReplaying|stopRecording|stopReplaying|suspend|terminate|terminateFaultTolerantVM|unmountToolsInstaller|unregister|upgradeTools|upgradeVirtualHardware) - Identifies Virtual Machine operat

[root@KETKHST001:~]

Can anything be gleaned from the information above? If not, what would you recommend the next step be? I'm not really familiar with ESXi and I am not sure, for example, if a system was setup to send the logs to a different log server. Any information would be greatly appreciated.

Here is a quick update on the Nested ESXi enviornment I am trying to build on my production cluster.

I have a vDS port group created and Set all security on that port group promiscuous mode : accept , MAC Address Changes : accept and Forged Transmits: Accept and disable the windows firewall on the source VM. I followed this link to install the nested ESXI : http://www.virtuallyghetto.com/2012/08/how-to-enable-nested-esxi-other.html and the hardware version selected is 9 and ESxi5.1 later and I am using ESXi 5.5 build 3116895. I confirmed with my networking team there are unable to see the MAC of the nested ESXi in the physical switch whereas the windows VM is ruining fine it is visible in the switch .Nested ESXi VM is using E1000 adapter and VMWARE tools not updated. With the same configuration mean subnet gateway and DNS set to 8.8.8.8 traceroute to 8.8.8.8 works for the windows VM but fails for the nested ESXi VM. Also I have both the VM's on the same host and have tried disabling the ecurity on that port group promiscuous mode : accept , MAC Address Changes : accept and Forged Transmits: Accept and disable the windows firewall on the source VM. But still there is no connectivity between the 2 VM's i.e windows VM and the nested ESXi .

Please advise

Hey Guys,

Got a really odd one here, for the last week I noticed all VM backups (Veeam 9.5) blew out by 35-45mins each. The problem is with 70+ VMs this pushed us outside the backup Window. In terms of troubleshooting so far we haven't got far, I've reviewed the vCenter logs and rebooted EVERYTHING. What we found from this is that when we reboot vCenter we have no issues for about 15 snapshots. The second thing we tried was snapshots from vCenter (rather than Veeam) but we have the same issue and it's only in creation, not removal. No matter how large or small the VM they all take the same time (even a 5GB CentOS Server) roughly 35-45mins. All tha past tasks looking at the vCeneter logs were between 10-130seconds for the

From what i can see in the vCenter logs there is a timeout peroid that is hit causing the task to be canceled/stopped but this is not causing a failure or any issues, everything still works fine. Its just takes 40mins longer per VM for any snapshots.

Here are the the vCenter logs:

2017-04-14T23:07:39.287+10:00 error vpxd[05084] [Originator@6876 sub=MoEvent opID=4569d102] [EventManagerMoImpl::EventBatchAppender::EventAppenderJob::PostJob] VirtualCenter did not respond to the request to append events after 2400 seconds

2017-04-14T23:07:39.291+10:00 error vpxd[05084] [Originator@6876 sub=Vmomi opID=4569d102] [VpxVmomi] IO exception while sending fault

2017-04-14T23:07:39.291+10:00 info vpxd[05084] [Originator@6876 sub=vpxLro opID=4569d102] [VpxLRO] -- FINISH task-internal-27952

2017-04-14T23:07:39.291+10:00 info vpxd[05084] [Originator@6876 sub=Default opID=4569d102] [VpxLRO] -- ERROR task-internal-27952 -- EventManager -- vim.event.EventManager.logUserEvent: vmodl.fault.UnexpectedFault:

--> Result:

--> (vmodl.fault.UnexpectedFault) {

-->    faultCause = (vmodl.MethodFault) null,

-->    faultName = "vim.fault.Timedout",

-->    fault = (vmodl.MethodFault) null,

-->    msg = ""

--> }

--> Args:

-->

--> Arg entity:

--> 'vim.VirtualMachine:vm-2741'

--> Arg msg:

--> "Source: Veeam Backup

--> Action: Job "Backup"

--> Operation: Stopped

--> Status: Success

--> ID: 9444fd99-6cb7-45c0-90b7-cead7533a244

--> Description: "

2017-04-14T23:07:39.297+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] VpxdInvtVm::ProcessVmInfo [ProcessVmInfoTime] took 1477703 ms

2017-04-14T23:07:39.297+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] VpxdInvtVm::ProcessVmChanges [ProcessVmChangesTime] took 1477703 ms

2017-04-14T23:07:39.300+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] [VpxdHostSync] ProcessChanges host:syd-sy1-ex02.cloud.local [ProcessChanges] took 1477706 ms

2017-04-14T23:07:39.301+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] [VpxdHostSync] DoHostSync:0000000004A81420 [DoHostSyncTime] took 1478249 ms

2017-04-14T23:07:39.301+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] InvtHostSyncLRO::StartWork [HostSyncTime] took 1478249 ms

2017-04-14T23:07:39.301+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] VpxLro::LroMain [TotalTime] took 1478249 ms

Going bonkers here guys, not idea whats going on. Thanks in advance for any help

I've created a project on Freelancer also:vmware vcenter | VMware

Cheer.

Hi!

Have a little problem.

Server gets 2 static IP from datacenter`s network. 1st IP "connected" to ESXi, 2nd - to virtual router (VM on ESXi), that routes traffic to other 2 VM (Win Server 2008, Win Server 2012).

Sometimes ESXi drops connections (so no ping) and nobody cant connect to ESXi Web GUI, but the connection to virtual router doesn`t drop. If i connect via RDP to any WinServer VM and stop it, the connection to ESXi restores after 1-2 minutes.

In vmkernel.log no info about ESXi connection drop. Free RAM - 20 Gb - too a lot for ESXi .

The server connected to network by 1 twisted pair cable, so there is no problem with physical NIC`s interface.

So how to solve this problem?

P.S.

ESXi 6.5 (5310538) is installed on IBM x3550 m3. NIC - QLogic NetXtreme II BCM5709 1000Base-T.

I made a mistake and enabled passthrough on the wrong device. Now I want to disable it. It seems that ESXi is stuck thinking that these devices should be in passthrough mode. I followed the instructions here (Changing from passthrough to non-passthrough devices fails to take effect after a reboot (1022011) | VMware KB), but they didn't work. After editing the /etc/vmware/esx.conf using vi and then rebooting, all the devices go back to passthrough mode. So I'm stuck unable to boot up my VMs.

Here's the devices section in my /etc/vmware/esx.conf file:

/device/000:000:31.2/owner = "passthru" 

/device/000:000:31.2/device = "1e02" 

/device/000:000:31.2/vmkname = "vmhba0" 

/device/000:000:31.2/vendor = "8086" 

/device/000:000:29.0/owner = "passthru" 

/device/000:000:29.0/device = "1e26" 

/device/000:000:29.0/vendor = "8086" 

/device/000:001:00.0/owner = "passthru" 

/device/000:001:00.0/device = "1142" 

/device/000:001:00.0/vendor = "1b21" 

/device/000:000:26.0/owner = "passthru" 

/device/000:000:26.0/device = "1e2d" 

/device/000:000:26.0/vendor = "8086" 

/device/000:000:25.0/vmkname = "vmnic0"

After editing, this is what it looks like.

/device/000:000:31.2/owner = "vmkernel" 

/device/000:000:31.2/device = "1e02" 

/device/000:000:31.2/vmkname = "vmhba0" 

/device/000:000:31.2/vendor = "8086" 

/device/000:000:29.0/owner = "vmkernel" 

/device/000:000:29.0/device = "1e26" 

/device/000:000:29.0/vendor = "8086" 

/device/000:001:00.0/owner = "vmkernel" 

/device/000:001:00.0/device = "1142" 

/device/000:001:00.0/vendor = "1b21" 

/device/000:000:26.0/owner = "vmkernel" 

/device/000:000:26.0/device = "1e2d" 

/device/000:000:26.0/vendor = "8086" 

/device/000:000:25.0/vmkname = "vmnic0"

I press :wq! to save and exit from vi editor. I then load the file again to verify it saved the changes and indeed, you can see "vmkernel" in the lines as shown above and none say "passthrough". Then, after rebooting ESXi, everything reverts back to "passthrough"..... Frustrating.

I had an ESXi5.5 host fail the other day and HA did it's job and spun the up VMs on other host.  What I'm trying to figure out is what VMs were on that host prior to the failure, I'm assuming I can find that in a log file?

I'm trying to configure a datastore on an ISCSI LUN from a QNAP .

I've created the LUN on the QNAP and I can see it as available in the new datastore wizard , however when I try to create it , it fails with the " host configuration error "

Thanks