This has been happening since at least Saturday, and others have reported this as well (in the regular Hypervisor forums).

https://my.vmware.com/group/vmware/evalcenter?p=free-esxi6

Neither the "manually download" nor the "Download Manager" links do anything.

I've tried 6 different computers (Windows XP and Windows 7 Home and Windows 7 Enterprise), 4 different web browsers (IE10, IE11, Firefox, chrome), and 3 different ISP (Verizon FIOS, Road Runner, and whoever supplies our Corporate LAN--AT&T or something).

I'm not sure VMware is even aware that there's an issue.

Hello.

I've a problem - install esxi 6.5 on Supermicro X8DT3 and it work fine, except terrible fans noise. Its run over 16000 RPM.

From IPMI:

The same data in BIOS.

But in esxi:

So it look like wrong sensors data reading in esxi.

I'm update BIOS and IPMI to the last available version. Set Energy Save Mode in Bios and in Esxi. Set in ipmi thresholds for fans to 10000 RPM:

But fans still scream.

May be someone know what to do?

p.s. sorry for my poor english

I got a win 2008R2 vm that is very slow when clicking on and navigating D drive.

C drive is fine

Any idea?

both are on the same Datastore

Hi,

Yesterday without any warning one of our VMs crashed unexpectedly.

In the Windows event log there is nothing (only the system shutdown was unexpected).

In the vcenter the error is: Error message from vmhost: VMware ESX unrecoverable error: (vcpu-7) MXUserAllocSerialNumber: too many locks!

In the vmware-12.log I found this:

2017-05-03T07:48:00.237Z| vcpu-7| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.237Z| vcpu-7| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.266Z| vcpu-5| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.266Z| vcpu-5| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.310Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.310Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.375Z| vcpu-6| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.375Z| vcpu-6| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.376Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.376Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.468Z| vcpu-6| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.468Z| vcpu-6| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.643Z| vcpu-7| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.643Z| vcpu-7| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.697Z| vcpu-2| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.697Z| vcpu-2| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.950Z| vcpu-5| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:00.950Z| vcpu-5| I125: GuestMsg: Too many channels opened.

2017-05-03T07:48:26.721Z| vcpu-3| I125: GuestMsg: channel 3: wrong cookie, discarding message.

2017-05-03T07:48:26.721Z| vcpu-3| I125: GuestMsg: channel 3: wrong cookie, discarding message.

2017-05-03T08:01:54.819Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2017-05-03T08:06:16.394Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-05-03T08:07:26.721Z| vcpu-7| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-05-03T08:07:26.721Z| vcpu-7| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-05-03T08:08:27.016Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-05-03T08:09:52.647Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-05-03T08:11:05.321Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-05-03T08:11:06.852Z| vcpu-7| E105: PANIC: MXUserAllocSerialNumber: too many locks!

This is a production environment and I appreciate any suggestion.

Thanks,

Nir

This time on any ATA disk attached to the P420 (p420i) controller in HBA mode (hbamode=on):

2018-05-29T10:33:49.969Z cpu3:2098605 opID=25f29edd)World: 11942: VC opID 1d67307f maps to vmkernel opID 25f29edd

2018-05-29T10:33:49.968Z cpu3:2098605 opID=25f29edd)LVM: 12674: LVMProbeDevice failed with status "Device does not contain a logical volume".

2018-05-29T10:33:50.004Z cpu0:2097163)nhpsa: hpsa_vmkScsiCmdDone:6512: Sense data: error code: 0x70, key: 0x5, info:00 00 00 00 , cmdInfo:00 00 00 00 , CmdSN: 0xbef7, worldId: 0x0, Cmd: 0x16, ASC: 0x20, ASCQ: 0x0

2018-05-29T10:33:50.004Z cpu0:2097705)ScsiDeviceIO: 3029: Cmd(0x459a40cffc80) 0x16, CmdSN 0xbef7 from world 0 to dev "naa.55cd2e404b7784c7" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-05-29T10:33:50.006Z cpu3:2098605 opID=25f29edd)LVM: 10419: LVMProbeDevice failed on (3798550880, naa.55cd2e404b7784c7:1): Device does not contain a logical volume

2018-05-29T10:33:50.006Z cpu3:2098605 opID=25f29edd)FSS: 2350: Failed to create FS on dev [naa.55cd2e404b7784c7:1] fs [SSD] type [vmfs6] fbSize 1048576 => Not supported

All of my drives (both SAS and SATA) were cleaned with diskpart (select disk x then clean).  The SAS drives are fine but all three of my SATA drives behave as above.

Is this another case of needing to DBAN the drives before trying to work with them in ESXi?  partedUtil isn't helping with these...

Hello,

today one of my datastores went full and I got a message like this

'There is no more space for virtual disk xxxx.vmdk. You might be able to continue this session by freeing disk space on the relevant volume, and clicking Retry. Click Cancel to terminate this session.'

Because I didn't want to have any issues with other VMs on the datastore and it's a VM that can be shut down without business impact, I clicked Cancel and the VM shut down. Then I saw that it runs on a snapshot, which I deleted and then set the second disk to independent because it's unnecessary to be snapshotted.

But now I can neither start the VM, consolidate or move it to another datastore. When starting, I get the following error

An error was received from the ESX host while powering on VM XX.

Failed to start the virtual machine.

Cannot open the disk '/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/XX/XX-000003.vmdk' or one of the snapshot disks it depends on.

Failed to lock the file

Module Disk power on failed.

Cannot open the disk '/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/XX/XX-000001.vmdk' or one of the snapshot disks it depends on.

Failed to lock the file

The vmdk files are existing though and there are NO lock files on the datastore.

After a few tries to boot it up I tried to create another snapshot and deleted it again, but then the error came up that disk consolidation is needed. This doesn't work either:

An error occurred while consolidating disks: msg.snapshot.error-DISKLOCKED.

I already read KB10051 about disk locks, but the owner IDs of the disks are only zeroes instead of an MAC-address.

[root@at0195:/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/AT1124] vmkfstools -D /vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/AT1124/XX-000003.vmdk

Lock [type 10c00001 offset 228986880 v 123, hb offset 4157440

gen 49, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2666079

num 0 gblnum 0 gblgen 0 gblbrk 0]

Addr <4, 529, 58>, gen 115, links 1, type reg, flags 0, uid 0, gid 0, mode 600

len 388, nb 0 tbz 0, cow 0, newSinceEpoch 0, zla 4305, bs 8192

I already tried restarting the management services on all my hosts all well as restarting the vCenter service.

I also cannot migrate the machine to a datastore with more free space. Host migration is working, but on datastore migration, I get the following

Error caused by file '/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/XX/XX-000001.vmdk'

Cloning the VM also doesn't work because of

Unable to access file'/vmfs/volumes/575d6dd1-27e4cd9e-ab07-2880239d1af0/XX/XX-000003.vmdk' since it is locked

Does anybody have an idea what I can do? I sure do not have a backup of that damn server..

Hello, where is problem ? ESX host frozen with purple error message.

Source virtual machine is replicated from source VCenter to destination VCenter.

Both VCenters are the same version - either 5.5 or 6.5

During replication process we get VM configuration from source VCenter and transfer that VM configuration to destination side, where ReconfigVM() is called.

Everything works fine, we can replicate VM multiple times... until we change configuration for source VM

Let's say we add one more network adapter

Next time we do replication - ReconfigVM() called on destination side for destination VCenter fails with error message : Invalid configuration for device '1'

Did anyone see that problem ?

Thank you.

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

Here is original configuration for source VM

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

<?xml version="1.0" encoding="utf-8" ?>

<VirtualMachineConfigSpec>

  <alternateGuestName />

  <annotation />

<bootOptions>

  <bootDelay>0</bootDelay>

  <enterBIOSSetup>false</enterBIOSSetup>

  </bootOptions>

  <changeVersion>2018-05-22T21:57:45.599698Z</changeVersion>

<cpuAllocation>

  <expandableReservation>false</expandableReservation>

  <limit>-1</limit>

  <reservation>0</reservation>

  </cpuAllocation>

<files>

  <logDirectory>[dc2-west-datastore4] VK_VM_LL_2/</logDirectory>

  <snapshotDirectory>[dc2-west-datastore4] VK_VM_LL_2/</snapshotDirectory>

  <suspendDirectory>[dc2-west-datastore4] VK_VM_LL_2/</suspendDirectory>

  <vmPathName>[dc2-west-datastore4] VK_VM_LL_2/VK_VM_LL_2.vmx</vmPathName>

  </files>

<flags>

  <disableAcceleration>false</disableAcceleration>

  <diskUuidEnabled>false</diskUuidEnabled>

  <enableLogging>true</enableLogging>

  <htSharing>any</htSharing>

  <monitorType>release</monitorType>

  <runWithDebugInfo>false</runWithDebugInfo>

  <snapshotDisabled>false</snapshotDisabled>

  <snapshotLocked>false</snapshotLocked>

  <snapshotPowerOffBehavior>powerOff</snapshotPowerOffBehavior>

  <useToe>false</useToe>

  <virtualExecUsage>hvAuto</virtualExecUsage>

  <virtualMmuUsage>automatic</virtualMmuUsage>

  </flags>

  <guestId>rhel6_64Guest</guestId>

  <locationId>564d2520-c30d-530a-cb46-143f4e00b299</locationId>

<memoryAllocation>

  <expandableReservation>false</expandableReservation>

  <limit>-1</limit>

  <overheadLimit>45</overheadLimit>

  <reservation>0</reservation>

<shares>

  <shares>20480</shares>

  </shares>

  </memoryAllocation>

  <memoryMB>2048</memoryMB>

<VirtualDevices>

<VirtualDevice>

  <key>4000</key>

  <controllerKey>100</controllerKey>

  <unitNumber>7</unitNumber>

  <deviceType>2</deviceType>

  <addressType>assigned</addressType>

  <macAddress>00:50:56:a2:1b:02</macAddress>

  <wakeOnLanEnabled>true</wakeOnLanEnabled>

  <ethType>5</ethType>

<backing>

  <ethBackingType>1</ethBackingType>

  <deviceName>VM Internal</deviceName>

  <useAutoDetect>false</useAutoDetect>

  </backing>

<connectable>

  <allowGuestControl>true</allowGuestControl>

  <connected>true</connected>

  <startConnected>true</startConnected>

  <status>ok</status>

  </connectable>

<deviceInfo>

  <label>Network adapter 1</label>

  <summary>VM Internal</summary>

  </deviceInfo>

  </VirtualDevice>

  </VirtualDevices>

  <name>VK_VM_LL_2</name>

  <npivWorldWideNameType />

  <numCPU>1</numCPU>

<tools>

  <afterPowerOn>true</afterPowerOn>

  <afterResume>true</afterResume>

  <beforeGuestShutdown>true</beforeGuestShutdown>

  <beforeGuestStandby>true</beforeGuestStandby>

  <syncTimeWithHost>false</syncTimeWithHost>

  <toolsUpgradePolicy>manual</toolsUpgradePolicy>

  <toolsVersion>0</toolsVersion>

</tools>

<uuid>4222e019-3615-f170-85a2-1b35060026c4</uuid>

<version>vmx-08</version>

</VirtualMachineConfigSpec>

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

Here is MODIFIED configuration for source VM

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

<?xml version="1.0" encoding="utf-8" ?>

<VirtualMachineConfigSpec>

  <alternateGuestName />

  <annotation />

<bootOptions>

  <bootDelay>0</bootDelay>

  <enterBIOSSetup>false</enterBIOSSetup>

  </bootOptions>

  <changeVersion>2018-05-23T13:37:15.062934Z</changeVersion>

<cpuAllocation>

  <expandableReservation>false</expandableReservation>

  <limit>-1</limit>

  <reservation>0</reservation>

  </cpuAllocation>

<files>

  <logDirectory>[dc2-west-datastore4] VK_VM_LL_2/</logDirectory>

  <snapshotDirectory>[dc2-west-datastore4] VK_VM_LL_2/</snapshotDirectory>

  <suspendDirectory>[dc2-west-datastore4] VK_VM_LL_2/</suspendDirectory>

  <vmPathName>[dc2-west-datastore4] VK_VM_LL_2/VK_VM_LL_2.vmx</vmPathName>

  </files>

<flags>

  <disableAcceleration>false</disableAcceleration>

  <diskUuidEnabled>false</diskUuidEnabled>

  <enableLogging>true</enableLogging>

  <htSharing>any</htSharing>

  <monitorType>release</monitorType>

  <runWithDebugInfo>false</runWithDebugInfo>

  <snapshotDisabled>false</snapshotDisabled>

  <snapshotLocked>false</snapshotLocked>

  <snapshotPowerOffBehavior>powerOff</snapshotPowerOffBehavior>

  <useToe>false</useToe>

  <virtualExecUsage>hvAuto</virtualExecUsage>

  <virtualMmuUsage>automatic</virtualMmuUsage>

  </flags>

  <guestId>rhel6_64Guest</guestId>

  <locationId>564d2520-c30d-530a-cb46-143f4e00b299</locationId>

<memoryAllocation>

  <expandableReservation>false</expandableReservation>

  <limit>-1</limit>

  <overheadLimit>135</overheadLimit>

  <reservation>0</reservation>

<shares>

  <shares>20480</shares>

  </shares>

  </memoryAllocation>

  <memoryMB>2048</memoryMB>

<VirtualDevices>

<VirtualDevice>

  <key>4000</key>

  <controllerKey>100</controllerKey>

  <unitNumber>7</unitNumber>

  <deviceType>2</deviceType>

  <addressType>assigned</addressType>

  <macAddress>00:50:56:a2:1b:02</macAddress>

  <wakeOnLanEnabled>true</wakeOnLanEnabled>

  <ethType>5</ethType>

<backing>

  <ethBackingType>1</ethBackingType>

  <deviceName>VM Internal</deviceName>

  <useAutoDetect>false</useAutoDetect>

  </backing>

<connectable>

  <allowGuestControl>true</allowGuestControl>

  <connected>true</connected>

  <startConnected>true</startConnected>

  <status>ok</status>

  </connectable>

<deviceInfo>

  <label>Network adapter 1</label>

  <summary>VM Internal</summary>

  </deviceInfo>

  </VirtualDevice>

<VirtualDevice>

  <key>4001</key>

  <controllerKey>100</controllerKey>

  <unitNumber>8</unitNumber>

  <deviceType>2</deviceType>

  <addressType>assigned</addressType>

  <macAddress>00:50:56:a2:41:03</macAddress>

  <wakeOnLanEnabled>true</wakeOnLanEnabled>

  <ethType>5</ethType>

<backing>

  <ethBackingType>1</ethBackingType>

  <deviceName>VM Internal</deviceName>

  <useAutoDetect>false</useAutoDetect>

  </backing>

<connectable>

  <allowGuestControl>true</allowGuestControl>

  <connected>true</connected>

  <startConnected>true</startConnected>

  <status>ok</status>

  </connectable>

<deviceInfo>

  <label>Network adapter 2</label>

  <summary>VM Internal</summary>

  </deviceInfo>

  </VirtualDevice>

  </VirtualDevices>

  <name>VK_VM_LL_2</name>

  <npivWorldWideNameType />

  <numCPU>1</numCPU>

<tools>

  <afterPowerOn>true</afterPowerOn>

  <afterResume>true</afterResume>

  <beforeGuestShutdown>true</beforeGuestShutdown>

  <beforeGuestStandby>true</beforeGuestStandby>

  <syncTimeWithHost>false</syncTimeWithHost>

  <toolsUpgradePolicy>manual</toolsUpgradePolicy>

  <toolsVersion>0</toolsVersion>

</tools>

<uuid>4222e019-3615-f170-85a2-1b35060026c4</uuid>

<version>vmx-08</version>

</VirtualMachineConfigSpec>

Buenas tardes.

Mi nombre es Daniel, tenemos un servidor ESXI con varias máquina virtuales.

Esta es nuestra version de ESXI

Ayer por la tarde noche una de nuestras máquinas vistuales se paró repentinamente, esta mañana en la oficinal al intentar acceder a el no se podía, accedí al cliente vsphere para arrancar la maquina y traté de arrancarla, pero se quedaba parado el arranque nada más empezar con este mensaje:

Piix4_SMBus: 000:00:07.3: Host SMBus controller bus not enabled

He buscado por google y se sugiere añadir a la blacklist el driver i2c-piix4 y el intel_powerclamp, así lo hicimos, arrancando en modo emergencia y añadiendo las lineas:

blacklist i2c-piix4

blacklist intel_powerclamp

De esta forma ya no salía ese mensaje, pero aun así no arrancaba, ya que se quedaba en la primera fase mostrando este mensaje por pantalla:

En el log de eventos del vsphere vimos esto:

Al ver la solución que indicaba el propio error, la aplicamos correctamente, era esta: VMware Knowledge Basehttps://kb.vmware.com/s/article/2149941

La arrancamos nuevamente y a lintentarlo se nos quedaba parado el arranque en la misma situación que antes.

Hemos entrado desde el modo emergencia y al intentar arrancar algunos servicios a mano, vemos que nos sale el mismo error que durante el arranque:

¿Tenéis alguna idea de que puede ocurrir? Estamos mirando aún pero nos gustaría saber si vosotros podriáis ayudarnos.

Muchas gracias y un saludo.

Hi

I'm getting repeated error messages "The ramdisk 'tmp' is full..." on an HP ESXi, 6.5.0, 5310538

In the /tmp folder I had a very large ql_ima.log which I deleted with the rm command.

If I do a vdf -h it shows the tmp folder as size 256M and used 256M with 0B available.

Doing an ls -lsa on the tmp and all its subfolders shows only 11M of used space.

The ql_ima.log has now grown to 1.6M

If I delete the ql_ima_sdm.log_old I can recover 4.7M and that shows in the vdf results. But that soon gets consumed by the ql_ima.log

Any idea what’s going on and how I can recover the lost free space would be much appreciated.

Paul

Hi,

I just face a event log as below:

Warning message from localhost.localdomain:

The guest OS has reported an error during

quiescing. The error code was: 5 The error

message was: 'VssSyncStart' operation failed:

IDispatch error #8449 (0x80042301)

warning

it caused the Acronis Backup software fail to backup

In Communities information, it seem relate to disk space and i/o speed.

For disk space, we should have enough disk space for OS.

Also i trust it is not heavy duty when backup, i/o should be enough

In knowledge base 1018194, resolution is reboot the virtual machine.

is it reboot the acronis appliance or our production os?

Any method to prevent the same?

Existing our version is EXSi 5.1 built 799733.

Thank you

Rgds,

Sun

i got a vm folder in a datrastore with on;ly a nvram file in it. safe to delete?

Dear reader

I am a sys-admin with 'some' VMware knowledge. Our IT partner helped us increase the server capacity with two additional drives.

First drive was added to the raid volume, the second one is branded as hot spare when one crashes.

The expanding via the ESX of the raidvolume worked perfectly. In Vcenter I can even see that VMware finds that the volume has increased.

Now, the following problem arises :

When trying to expand the existing Datastore:

- via the Vcenter directly it does not show any disk/LUN volume and you cannot continue.

- via the direct connection to the server:

     * it lets me use <Expand an existing VMFS datastore extent>

     * I can select <Local LSI Disk (naa...) Disk 3.27TB...

     * it shows me <Select partitioning options> where it shows me the 3.VMFS in blue and <Free space> 837.84GB in green.

     * when selecting the blue VMFS, you can see on the <After> that blue and green merges

     * when trying to finish it ends in the error "Cannot change the host configuration".

I have found that the GPT table was not as should be on the disk and I fixed this. Sadly enough that did not fix it.

I have checked the permissions for the logins I am using, being root & administrator, both have rights, doesn't change anything.

Going via Vcenter doesn't work, going via Server ends in error.

My IT Partner doesn't know the answer to this either and now suggest to update the hardware raidcontroller's drivers etc.

Vcenter: Version information: Version 6.5.0 Build 7515524

Selected servers (2 - Live & Backupserver (identical- Fujitsu RX2520 M1)) to upgrade: Hypervisor: VMware ESXi 6.5.0, 5969303

PS: This morning I saw the following under <Configure>

Local USB Direct-Access (mpx.vmhba32...) disk 3,73GB Attached HDD Block Adapter
Local LSI Disk (naa.6003...) disk 3,277TB HDD SAS

I personally don't know where to look anymore, any help would be welcome =)

I am trying to run the flash certification test

The ESXi server is installed on one of our XEON D CPU boards which has an SD Card interface that uses an SD to USB device so the flash appears as a USB device

The Configration, TLS Check, and flash basic tests pass but the flash durability fails after around 30 seconds with

2018-05-30 17:39:58 UTC [ MAIN      ] [0] ERROR: Trouble creating test instance, Failed to get the Product version for esxi.cam.eurotech.local. Error: @SDT/{:628::6:result@SDT/$0:0::9:exception@SDT/$S:30:java.lang.NullPointerException:7:errDesc@SDT/$S:30:Possible issue with STAF code::6:errMsg@SDT/$0:0::9:rootCause@SDT/$0:0::8:reqIdStr@SDT/$S:33:ssl://localhost@6550:vtaf_host:36:9:startTime@SDT/$S:22:05/30/2018 02:45:16 PM:7:endTime@SDT/$S:22:05/30/2018 02:45:16 PM:8:stkTrace@SDT/$S:251:com.vmware.qa.staf.vc.host.STAFHost.getHostVersion(STAFHost.java:395) ## com.vmware.qa.staf.vc.host.HostSTAFService.handleGetHostValue(HostSTAFService.java:6564) ## com.vmware.qa.staf.vc.host.HostSTAFService.acceptRequest(HostSTAFService.java:748) ## :13:rootException@SDT/$0:0::7:dbgInfo@SDT/$0:0:........................................................................................................

What I also notice is that although the flashbasic test passes I see this in the workbench console

2018-05-30 17:39:14 UTC [ UTILITY   ] [0] ERROR:  RC: 5001 ErrDesc: Possible issue with STAF code: Exception: java.lang.NullPointerException Trace: com.vmware.vcqa.vim.ComputeResource.getConfigurationEx(ComputeResource.java:281) ## com.vmware.qa.staf.vc.host.STAFHost.SetSwapFileLocation(STAFHost.java:8996) ## com.vmware.qa.staf.vc.host.HostSTAFService.handlesetSwapFileLocationFromHost(HostSTAFService.java:12082) ## com.vmware.qa.staf.vc.host.HostSTAFService.acceptRequest(HostSTAFService.java:875) ## ...........

2018-05-30 17:39:14 UTC [ LOGMANAGEM] [0] WARN: Failed to stop monitoring of log /var/log/vmkernel.log

2018-05-30 17:39:14 UTC Received the following error: STAFIsProcessRunning: Couldn't query the STAF process 46 on host esxi.cam.eurotech.local. STAF RC: 5

2018-05-30 17:39:14 UTC [ LOGMANAGEM] [0] WARN: Failed to retrieve log files from esxi.cam.eurotech.local ([exception base])...

2018-05-30 17:39:14 UTC [ LOGMANAGEM] [0] WARN: Failed to stop monitoring of log /var/log/hostd.log

2018-05-30 17:39:14 UTC Received the following error: STAFIsProcessRunning: Couldn't query the STAF process 49 on host esxi.cam.eurotech.local. STAF RC: 5

2018-05-30 17:39:25 UTC [ LOGMANAGEM] [0] WARN: Failed to retrieve log files from esxi.cam.eurotech.local ([exception base])..............................................................................................................................

Hi All,

Last week i downloaded ESXi 6.5 U2 from VMware website and the full name of the file was:

VMware-ESXi-6.5.0-Update2-8294253-HPE-Gen9plus-650.U2.10.2.0.14-May2018-depot.zip

Now i can't find this file and the only file that is available for download is:

VMware-ESXi-6.5.0-Update2-8294253-HPE-preGen9-650.U2.9.6.7.1-May2018-depot.zip

The update date is 29.5.2018... yesterday

I am using this link to download the file:

Download VMware vSphere

So i have both files, but i am afraid to upgrade my hosts, the main reason is that my servers are GEN9 and the latest version name is for  pre gen9.

Please help.

Basically, I really need to know if I am choosing the right product.

I have a customer that want's to virtualize one server, with perhaps adding a second server (both linux) within the year.

I don't need huge performance or uptime requirements, but do need to be able to back up consistently and often.  I am looking at Altaro for that (we use it for Hyper-Vs right now) and that's fine, but not sure how it interfaces with vSphere - does it need a separate machine?  Realize that's more of a question for Altaro.

My biggest concern is if I'm buying the right VMWare product for this customer.  Essentials looks perfect, but I don't see a way to download or test this, and see no trial version that I can run without buying a key, even for a few days.  That would be ideal for me, just being able to get hands-on with the full product and try it out.

I've contacted Sales four times, leaving messages that never get returned.  I've tweeted at them.  No response.  Is that normal?

Whenever I rescan iscsi hba, I keep getting this message in the events tab

Login to iSCSI target

iqn...... on vmhba40@vmk2 failed. The iscsi initiator could not establish a network connection to the target.

any idea why? The lun is online and accessible though

We support a few remote locations with very slow, high latency internet links. One issue has kept us with ESXi 5.5 and the fat C# client. The login page on ESXi 6.5 takes over 8 minutes to load, before you can type in your password. Even then, it doesn't actually login, just gives an error, which varies between timeout and lost connection, then it boots you back out again.

I can see a steady stream of data coming from the host via resource monitor, but it tops at 15Kb/sec. The link we're working with is a 600Kb/sec link and 300ms latency; this is under ideal conditions, which is rarely the case.

I can sort of replicate this with Workstation running a nested ESXi host. I've ruled out the site-to-site VPN being an issue, but going direct to the https port and nothing actually changes. I'm hoping someone will have had experience with this and would have any ideas on how to better cope with the low-speed & high latency combination.

Bill

Hi,

I am having issues with my VMs corrupting every couple of days on an ESXi bare metal setup.

I have about 7 or 8 VMs, one is a domain controller (windows server 2012), and the rest are dedicated workstations for groups of applications (windows 10), and one Linux Ubuntu VM.

I have had the most corruptions on the domain controller, but the others including the Linux machine have almost all corrupted at some point, which usually has resulted in me having to do a fresh install or full VM restore from a weekly backup.  By corruptions, I mean the OS tries to start goes into some sort of repair mode, or error mode, etc., and cannot load the OS, even in safe mode.

The VMs are stored on a NAS.  The NAS is split up into a iSCSI LUN with Thick Provisioning for my VM datastore, and the rest is just for simple network file storage on a separate volume.  The NAS is set up for RAID 5 and also has a scheduled backup every week onto a USB locally attached HDD.  The corruptions do not seem to coincide with the backing up of the LUN, they just seem random.  The NAS itself I would say is working fine, since there are no faults/errors, and all of my other file storage has had not issues.

Any ideas what could be causing this?

Hi,

due to our storage layout it is advantageous for us to have the snapshots created on HDDs and not SSDs. Mainly Snapshots are created during Backup Hours or Upgrades so the performance impact is acceptable. I also decided to move the swap file of some VMs to da dedicated location.

VMWare lists the following options for the vmx config file:

workingDir = "/vmfs/volumes/587939d7-a30f66a9-23a1-ecf4bbe1a868/snapshots/srv"

snapshot.redoNotWithParent = "true"

sched.swap.dir = "/vmfs/volumes/587939d7-a30f66a9-23a1-ecf4bbe1a868/swapdir/srv"

The host is running ESXi 6.5 with the latest 20180502001-standard bundle. When I clicked around the VM-Options on the ESXi Webinterface I found that neat and handy config file editor where you can edit and add vmx options.

I had no troubles adding those two lines:

snapshot.redoNotWithParent = "true"

sched.swap.dir = "/vmfs/volumes/587939d7-a30f66a9-23a1-ecf4bbe1a868/swapdir/srv"

however the

workingDir = "/vmfs/volumes/587939d7-a30f66a9-23a1-ecf4bbe1a868/snapshots/srv"

line won't get saved or persist after applying the change.

When I edit the vmx file via ssh and vi I can add the workingDir (reregister the vmx) but it still won't show in the ESXi Webinterface (however the option is persistent in the vmx file saved)

Is there a reason why this specific configuration option has to be done using a manual vmx edit? Editing and reregistering is not too complicated but opening ssh etc. are just a couple of more steps instead of just punching the parameters in the webui

regards,

Fabian