Hi folks,

Has anyone seen those annoying messages filling up vmkernel.log and vmkwarning.log?

Environment:

ESXi 6.7.0 build-10302608

10 Node vSAN Cluster

vmkwarning.log

2019-05-21T21:14:48.893Z cpu28:423720880)WARNING: LinuxThread: 423: sh: Error cloning thread: -28 (bad0081)

2019-05-21T21:14:48.917Z cpu32:423720883)WARNING: LinuxThread: 423: sh: Error cloning thread: -28 (bad0081)

2019-05-21T21:14:48.941Z cpu10:423720886)WARNING: LinuxThread: 423: sh: Error cloning thread: -28 (bad0081)

2019-05-21T21:14:48.960Z cpu52:423720889)WARNING: LinuxThread: 423: sh: Error cloning thread: -28 (bad0081)

vmkernel.log

2019-05-21T21:15:10.156Z cpu38:423724588)WARNING: LinuxThread: 423: sh: Error cloning thread: -28 (bad0081)

2019-05-21T21:15:10.169Z cpu44:423724591)MemSchedAdmit: 470: Admission failure in path: init/sh.423724593/uw.423724593

2019-05-21T21:15:10.169Z cpu44:423724591)MemSchedAdmit: 477: uw.423724593 (3361511604) extraMin/extraFromParent: 17254/17254, init (806) childEmin/eMinLimit: 54286/56320

2019-05-21T21:15:10.169Z cpu44:423724591)WARNING: LinuxThread: 423: sh: Error cloning thread: -28 (bad0081)

2019-05-21T21:15:10.184Z cpu14:423724594)MemSchedAdmit: 470: Admission failure in path: init/sh.423724596/uw.423724596

2019-05-21T21:15:10.184Z cpu14:423724594)MemSchedAdmit: 477: uw.423724596 (3361511628) extraMin/extraFromParent: 17254/17254, init (806) childEmin/eMinLimit: 54286/56320

2019-05-21T21:15:10.184Z cpu14:423724594)WARNING: LinuxThread: 423: sh: Error cloning thread: -28 (bad0081)

2019-05-21T21:15:10.204Z cpu54:423724597)MemSchedAdmit: 470: Admission failure in path: init/sh.423724599/uw.423724599

2019-05-21T21:15:10.204Z cpu54:423724597)MemSchedAdmit: 477: uw.423724599 (3361511652) extraMin/extraFromParent: 17254/17254, init (806) childEmin/eMinLimit: 54286/56320

2019-05-21T21:15:10.204Z cpu54:423724597)WARNING: LinuxThread: 423: sh: Error cloning thread: -28 (bad0081)

2019-05-21T21:15:10.225Z cpu14:423724600)MemSchedAdmit: 470: Admission failure in path: init/sh.423724602/uw.423724602

2019-05-21T21:15:10.225Z cpu14:423724600)MemSchedAdmit: 477: uw.423724602 (3361511676) extraMin/extraFromParent: 17254/17254, init (806) childEmin/eMinLimit: 54286/56320

2019-05-21T21:15:10.225Z cpu14:423724600)WARNING: LinuxThread: 423: sh: Error cloning thread: -28 (bad0081)

Hi all,

Horizon 7.10

Windows 10 1903

Linked Clones

We have two different types of clients which uses two separate types of audio hardware. Our issues is that a subset of users are having to set the audio driver every time they login. 

The default audio driver in the golden image is Vmware audio driver.

We have some users that use a zero client to connect to our VDI environment and use a headset with microphone. The only way to get headset and mic to work on the headset is use to the Teradici audio driver. 

each user has the audio output option of Vmware or Teradici.  When they choose the audio driver, its reset after logoff/logon.

how can we solve this?

Thank you.

i have a lab environment that the AD domain - labtwo.local exists on DNS server and would like to build vSphere 7 under this domain name.

however, i'm not so sure about which option to choose in the "SSO configuration" page in the installer. as shown in figure below which is obtained from internet.

the demand is to join the vCenter under the domain "labtwo.local".

A little bit confused. so the questions are:

1. if i select the "join the existing SSO domain" then this indicate that the vCenter can utilize my AD domain's user account directly for login instead of creating a "vSphere.local" and using "administrator@vsphere.local" as login account?

2. is choosing "join the existing SSO domain" meaning that the vCenter server will join the AD domain at the same time?

just want to clarify my doubts about the ESXi virtual switch(VSS/VDS).

I'm planning to setup lab environment with ESXi 7 and the physical switch(which the ESXi is connecting to) ports' setting are now VLAN trunk mode.

if each kernel network/VM network is set to specific VLAN ID respectively(say VLAN ID 99 for vMotion) then the network should still working???(assume that other configurations are correct.)

does the VSS/VDS work the same way as physical switch?

sorry for such dumb question.

I'm building a 1909 Win 10 gold image vm and i'm running into an issue of a black screen delay when windows begins to login.

6.7U3

Horizon 7.10

DEM 7.11

1.  Hosts are using physical Nvidia GPUs.

2.  Ran the OSOT allowing Windows updates along with a couple apps (calculator etc.)  Everything else is pretty much default using the Windows 10 1909-2004 template.

3.  I'm currently running an earlier build in production, during logon, all i see is waiting with a delayed spinning circle, which eventually goes to Preparing Desktop (circle runs smoother in this stage) followed by an immediate Windows desktop.  In the current 1909 build that i'm getting prepared for production, it goes through at logon with applying vmware dem, gpos etc displayed on the screen, once thats complete it goes to preparing for a few seconds and goes to a solid black screen that is delayed by like 15 seconds...  it also seems that the startup apps take longer to start in this build post optimizations as well.  Has anyone experienced this?

4.  Lastly, everything else is great other than the dreaded start menu click delaying for 3 seconds or so , sometimes its immediate, but most times there is a noticable delay with the start button as well as Windows search.  Is there anything that addresses this outside of the OSOT that i'm missing?

Thanks for any insight!

Never had this problem with the prior version.  This has happened to me a number of times on workstation 15 running on Windows 10 1909.  A VM would go wrong and I need it to reboot.  I'd try to  either Power Off or Shut Down Guest.  It would fail and the workstation just hangs.  I'd use Task Manager to terminate the Workstation process and try to restart the VM again, but then it gives me this:

"Failed to get exclusive lock on the configuration file. Another VMWARE process might be running"

I'd try to delete all the .lck folders, cashes folder, but unable to delete the .vmem file no matter how I try.  The workstation won't start.  The only way I can get it running again is by rebooting the host machine, which diminishes the purpose of running virtual machines.  If I have a number of machines running and if I have to reboot the host machine, then I have to shutdown all the other working & running VMs.

Anyhow, once I reboot the host machine, then I can delete the .lck folders, cache folder, & .vmem file.  Then I can start the VM again.

It gets really annoying and time consuming whenever one of the VMs is in trouble because the only working solution is to reboot the host machine.  Is there a way we can release a VMware Workstation VMX lock on files (.lck folders, cache folder, .vmem file)?  I'm looking for a way to be able to start the troubled VM without compromise other VMs and the host machine.

When I connect my esxi host by remote location give no peer certificate found

On my MacBook Air, Catalina 10.15 I am not able to get the camera working in Skype and VMware Horizon Client 5.4.2

VmwAmcAp.exe from my windows horizon client session, is showing perfect image from camera. When opening Skype and and starting a meeting, the activation light from camera is showing up and then turned off.

From logs VDCAssistant:

001199.704065 vmware-remotemks@(null): AppleUSBHostUserClient::start: missing entitlement com.apple.ibridge.control

001199.708966 vmware-remotemks@(null): AppleUSBHostUserClient::start: missing entitlement com.apple.ibridge.control

[guid:0x8020000005ac8514] SetPropertyState <private> for client 22023

CMIOHardware.cpp:357:CMIOObjectGetPropertyData no object property for given ID 33

CMIO_Unit_Input_Device.cpp:246:GetPropertyInfo CMIOUInputFromProcs::GetPropertyInfo() failed for id 102, Error: -67456

[guid:0x8020000005ac8514] BulkStreamHandler  Got a transfer out of sequence: last: 67, this: 0

Anybody had similar issue and solution ?

Hello, there was a vmfs6 datastore, where while clear installing ESXi7 on USB Flash, was configured Scratch "ScratchConfig.ConfiguredScratchLocation = /vmfs/volumes/5ee3e9a8-68963958-785a-90b11c4fb057/.locker"

I whanted to delete this datastore, but always reciaved message about it is locked. So, i enable maintanence mode, created new datastore, on this datastore i created .locker directory, and changed parameter ScratchConfig.ConfiguredScratchLocation to new dadastore. System told me that everything is OK. I unmaunted old datastore, deleted it, rebooted server, and after reboot i reciave old value of "ScratchConfig.ConfiguredScratchLocation = /vmfs/volumes/5ee3e9a8-68963958-785a-90b11c4fb057/.locker". But for now, datastore 5ee3e9a8-68963958-785a-90b11c4fb057 dont even exists in system . I also tryed to change ScratchConfig.ConfiguredScratchLocation from SSH, everytime after reboot, the value return to "ScratchConfig.ConfiguredScratchLocation = /vmfs/volumes/5ee3e9a8-68963958-785a-90b11c4fb057/.locker" . Please, help me

I'm not sure what happened.  VMWare Fusion was working after I upgraded to macOS Mojave and then some time later stopped working.  I'm getting:

> Could not open /dev/vmmon: Broken pipe

> Please make sure that the kernel module 'vmmon' is loaded

followed by:

> Failed to initialize monitor device

followed by:

> Transport (VMDB) error -14: Pip connection has been broken

I uninstalled VMWare Fusion including the manual cleanup as documented in https://kb.vmware.com/s/article/1017838.

, emptied the trash, rebooted, re-downloaded the installee, reinstalled, and I still get the same errors.  I still get the error and, oddly, even after doing all all the uninstall and cleanup, Fusion still knows my license key. 

Any suggestions on where the problem is?

Ken

Has anyone installed Teams MSI or EXE on a non-persistent environment?

As I see it there are 4 potential options,

1. Install on Master image

2. Install as app stack

3. User install on Writable UIA Vol

4. Thin App

I have tried the first three and every time i log off and log back in Teams is gone and I haven't had success yet on an App stack or on the Master image. I wanted to start up a discussion on this so we could get this as stable as possible. I also am running windows 7 and need to install Workplace Joined to get the VM's in Azure AD as Hybrid Azure AD joined.

Thanks

Hi friends, I really need some advices about vSphere replication.

Our both Data Center have different version of vSphere.

DC A version is 6.7 and DC B is 6.0

We are planning to update all host in DC B from 6.0 to 6.7. But we need to failover all VM from DC B to DC A.

And my question is

1. Can we pairing vsphere replication accross different version?

Let say my DC A using vSphere replication 8.1 and my DC B using vSphere Replication 6.1. Is it possible pair both of them?

2. Can we install vSphere Replication 8.1 in vSphere 6.0 environment?

I read the vSphere documentation that vSphere replication 8.1 fully support in vCenter 6.0 environment.

I would be very happy if someone can share their experience about vSphere Replication

Thank you

I'm running vCenter 6.7 w/ three host also running ESXI 6.7.

I had certain alerts send me email notifications (like if a host lost power) and for whatever reason it just stopped working. For testing proposes, I'm testing an alert when a VM powers off to send me and email notification. After powering ff the VM, it has yet to send me a successful email. I'm not sure if some updates has stopped this from happening or what. Is anyone else having this issue?

I've seemed to have lost that ability to have vCenter email notifications. Like I said, it was working in the past.

I do get other mail alerts from other apps like Veeam everyday, so I know the Office 365 email address or the SMTP server isn't the issue.

What am I missing in vCenter?

Hello,

I have a problem deleting tenant using LCM. I get an error that states:

Deleting T01 tenant is not allowed as there are some product associations which still exist.

The message is clear for me but I dont know how to remove vRA 8.1 association with T01 tenant. There is an option to add new association but I can't find the way to remove it.

Could you please tell me how to remove product association to make it possoble to remove tenant.

Run on a 16" Macbook Pro. I'm struggling to get clear text on my Windows 10 vm. I'm NOT running full screen or unity.

I'm confused by the various VM Display settings ...

What is recommended?

thanks.

i am using below code to fetch the vc alerts. i would like to add below two variables in existing code.

variables

VMWARE_ALARM_EVENTDESCRIPTION

VMWARE_ALARM_ALARMVALUE

foreach ($dc in (Get-Datacenter | where { $_.ExtensionData.triggeredAlarmState })) {

    foreach ($alarmState in $dc.ExtensionData.TriggeredAlarmState) {

        $entity = Get-View $alarmState.Entity -Server $vcenter | Get-VIObjectByVIView

        $alarm = Get-View $alarmState.Alarm -Server $vcenter

        $event = Get-VIEventPlus -Entity $entity -EventType AlarmStatusChangedEvent -Start $alarmState.Time -Finish $alarmState.Time.AddSeconds(1)

        $alarmState | select @{N = 'vCenter'; E = { $vcenter = $dc.Uid.Split('@:')[1]; $vcenter } },

        @{N = "Entity"; E = { $entity.Name } },

        @{N = "Alarm"; E = { $alarm.Info.Name } },

        @{N = 'Description'; E = { $alarm.Info.Description } },

        @{N = 'Previous State'; E = { $event.From } },

        @{N = 'New State'; E = { $event.To } },

        @{N = 'Message'; E = { $event.FullFormattedMessage } },

        Time, OverallStatus

    }

}

kernel modules won't build after upgrade to kernel 5.7.6-201.fc32.x86_64 in fedora

[CODE]

[theodore@teras vmmon-only]$ make

Using kernel build system.

make -C /lib/modules/5.7.6-201.fc32.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Entering directory '/usr/src/kernels/5.7.6-201.fc32.x86_64'

  CC [M]  /home/theodore/Downloads/vmware1/vmware-vmx/lib/modules/source/vmmon-only/linux/driver.o

/home/theodore/Downloads/vmware1/vmware-vmx/lib/modules/source/vmmon-only/linux/driver.c:668:1: warning: ‘always_inline’ function might not be inlinable [-Wattributes]

  668 | LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min

      | ^~~~~~~~~~~~~~~~~~~~~~~

/home/theodore/Downloads/vmware1/vmware-vmx/lib/modules/source/vmmon-only/linux/driver.o: warning: objtool: .text.__x86_indirect_thunk_rax+0x0: unsupported intra-function call

/home/theodore/Downloads/vmware1/vmware-vmx/lib/modules/source/vmmon-only/linux/driver.o: warning: objtool: If this is a retpoline, please patch it in with alternatives and annotate it with ANNOTATE_NOSPEC_ALTERNATIVE.

make[2]: *** [scripts/Makefile.build:267: /home/theodore/Downloads/vmware1/vmware-vmx/lib/modules/source/vmmon-only/linux/driver.o] Error 255

make[2]: *** Deleting file '/home/theodore/Downloads/vmware1/vmware-vmx/lib/modules/source/vmmon-only/linux/driver.o'

make[1]: *** [Makefile:1732: /home/theodore/Downloads/vmware1/vmware-vmx/lib/modules/source/vmmon-only] Error 2

make[1]: Leaving directory '/usr/src/kernels/5.7.6-201.fc32.x86_64'

make: *** [Makefile:117: vmmon.ko] Error 2

[theodore@teras vmmon-only]$

[/CODE]

The IP scheme in one of my remote offices changed today. We changed the IP address

on the local desktop computer. But when we went to print from their VDI the option

to print locally was no longer there. How does one setup printing on a local Windows

machine and then have that local printer visible to the windows Horizon virtual desktop?

My own desktop seems to have just done it with no extra effort on my part. But

I don't know how to show someone else how to do it.

Has anyone else been seeing apps the would install and run in a version 2x of App Volumes perfectly fine not run at all when installed in App Volumes 4x?

Even during the provisioning stage, once the application is installed, it will not run.

Errors are different for different apps but if I do the exact same procedure on a 2x provisioning VM, it installs and runs just fine.

It's strange because other apps that are re-provisioned are good. There doesn't seen to be a common cause of the problem.

I ve installed vspehere 7.0 with the following specs (Gigabyte Aorus Elite x570 Motherboard, AMD Rizen x3700 CPU and Samsung 970 EVO Plus 2 NVMe 2TB (storage)

After few days the server crashed each time.

Please adivse to how solve this issue?

Regards,

Ram

/var/log/LogEFI.log shows

2020-06-13T15:12:15.682Z cpu1:1061755)VMware ESXi 7.0.0 [Releasebuild-15843807 x86_64]

#GP Exception 13 in world 1061755:vmm0:Win_Ext @ 0x4200360ded93

2020-06-13T15:12:15.684Z cpu1:1061755)cr0=0x80050033 cr2=0x0 cr3=0x1ea9f2000 cr4=0x150668

2020-06-13T15:12:15.685Z cpu1:1061755)FMS=17/71/0 uCode=0x8701013

2020-06-13T15:12:15.686Z cpu1:1061755)frame=0x451a1671b970 ip=0x4200360ded93 err=0 rflags=0x10016

2020-06-13T15:12:15.687Z cpu1:1061755)rax=0x6ac84800003bc rbx=0x451a19aa1100 rcx=0x1000

2020-06-13T15:12:15.687Z cpu1:1061755)rdx=0xef rbp=0xef rsi=0x1

2020-06-13T15:12:15.688Z cpu1:1061755)rdi=0x4519c00f0000 r8=0x430076aeb770 r9=0x430076aebb90

2020-06-13T15:12:15.689Z cpu1:1061755)r10=0xe036a0 r11=0x0 r12=0xef

2020-06-13T15:12:15.689Z cpu1:1061755)r13=0x0 r14=0x0 r15=0x42003613e378

*PCPU1:1061755/vmm0:Win_Ext

PCPU  0: SVVSVSVUSVVIVIVS

2020-06-13T15:12:15.691Z cpu1:1061755)Code start: 0x420036000000 VMK uptime: 9:06:30:50.522

2020-06-13T15:12:15.693Z cpu1:1061755)0x451a1671ba30:[0x4200360ded93]IntrCookie_DoInterrupt@vmkernel#nover+0x53 stack: 0x0

2020-06-13T15:12:15.695Z cpu1:1061755)0x451a1671bae0:[0x4200360df3b9]IntrCookie_VmkernelInterrupt@vmkernel#nover+0x3a stack: 0xffffffffffffffef

2020-06-13T15:12:15.696Z cpu1:1061755)0x451a1671bb00:[0x42003613e414]IDT_IntrHandler@vmkernel#nover+0x9d stack: 0x0

2020-06-13T15:12:15.697Z cpu1:1061755)0x451a1671bb20:[0x420036154067]gate_entry@vmkernel#nover+0x68 stack: 0x0

2020-06-13T15:12:15.699Z cpu1:1061755)0x451a1671bbe8:[0x420036086ab7]Power_ArchPerformWait@vmkernel#nover+0xc3 stack: 0x420040400880

2020-06-13T15:12:15.701Z cpu1:1061755)0x451a1671bbf0:[0x420036086bd2]Power_ArchSetCState@vmkernel#nover+0x8f stack: 0x800000000

2020-06-13T15:12:15.702Z cpu1:1061755)0x451a1671bc40:[0x42003635a304]CpuSchedIdleLoopInt@vmkernel#nover+0x23d stack: 0x420040400108

2020-06-13T15:12:15.704Z cpu1:1061755)0x451a1671bcb0:[0x42003635d19e]CpuSchedDispatch@vmkernel#nover+0x14d3 stack: 0x420040400120

2020-06-13T15:12:15.705Z cpu1:1061755)0x451a1671bee0:[0x42003635e1d8]CpuSchedWait@vmkernel#nover+0x275 stack: 0x1

2020-06-13T15:12:15.707Z cpu1:1061755)0x451a1671bf50:[0x42003635e9a3]CpuSched_VcpuHalt@vmkernel#nover+0x13c stack: 0x1e

2020-06-13T15:12:15.708Z cpu1:1061755)0x451a1671bfa0:[0x42003612a2b6]VMMVMKCall_Call@vmkernel#nover+0xf7 stack: 0x0

2020-06-13T15:12:15.710Z cpu1:1061755)0x451a1671bfe0:[0x42003614e0c5]VMKVMM_ArchEnterVMKernel@vmkernel#nover+0xe stack: 0x42003614e0b8

2020-06-13T15:12:15.712Z cpu1:1061755)base fs=0x0 gs=0x420040400000 Kgs=0x0

2020-06-19T11:01:10.694Z cpu0:1049326)VMware ESXi 7.0.0 [Releasebuild-15843807 x86_64]

VERIFY bora/vmkernel/sched/cpusched.c:10893

2020-06-19T11:01:10.696Z cpu0:1049326)cr0=0x8001003d cr2=0x430000ede000 cr3=0xdcc7e000 cr4=0x10016c

2020-06-19T11:01:10.697Z cpu0:1049326)FMS=17/71/0 uCode=0x8701013

*PCPU0:1049326/tq:tcpip4

PCPU  0: SSSSUUSVIISVIISV

2020-06-19T11:01:10.698Z cpu0:1049326)Code start: 0x420021000000 VMK uptime: 5:18:44:21.568

2020-06-19T11:01:10.700Z cpu0:1049326)0x451a10b9bc50:[0x4200210fc6ce]PanicvPanicInt@vmkernel#nover+0x2c6 stack: 0x4200210fc6ce

2020-06-19T11:01:10.701Z cpu0:1049326)0x451a10b9bd00:[0x4200210fcbac]Panic_NoSave@vmkernel#nover+0x4d stack: 0x451a10b9bd60

2020-06-19T11:01:10.703Z cpu0:1049326)0x451a10b9bd60:[0x4200210fd155]Panic_OnAssertAt@vmkernel#nover+0xd2 stack: 0x2a8d00000000

2020-06-19T11:01:10.704Z cpu0:1049326)0x451a10b9bdf0:[0x42002113e0eb]Int6_UD2Assert@vmkernel#nover+0x1f8 stack: 0x0

2020-06-19T11:01:10.706Z cpu0:1049326)0x451a10b9be10:[0x420021154067]gate_entry@vmkernel#nover+0x68 stack: 0x0

2020-06-19T11:01:10.707Z cpu0:1049326)0x451a10b9bed0:[0x42002135e1b8]CpuSchedWait@vmkernel#nover+0x254 stack: 0x4abd4317deed2704

2020-06-19T11:01:10.709Z cpu0:1049326)0x451a10b9bf40:[0x42002135e2b8]CpuSched_NoEvqWait@vmkernel#nover+0x19 stack: 0x0

2020-06-19T11:01:10.711Z cpu0:1049326)0x451a10b9bf50:[0x42002102eb80]VmkTimerQueueWorldFunc@vmkernel#nover+0x319 stack: 0x4abd4317deed2704

2020-06-19T11:01:10.712Z cpu0:1049326)0x451a10b9bfe0:[0x42002135ef79]CpuSched_StartWorld@vmkernel#nover+0x82 stack: 0x0

2020-06-19T11:01:10.713Z cpu0:1049326)0x451a10b9c000:[0x4200210c5303]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0

2020-06-19T11:01:10.716Z cpu0:1049326)base fs=0x0 gs=0x420040000000 Kgs=0x0

2020-06-19T22:15:58.953Z cpu0:1048841)VMware ESXi 7.0.0 [Releasebuild-15843807 x86_64]

CPU 0 / World 1048841 tried to re-acquire lock

2020-06-19T22:15:58.955Z cpu0:1048841)cr0=0x8001003d cr2=0xf cr3=0xdcc7e000 cr4=0x10016c

2020-06-19T22:15:58.956Z cpu0:1048841)FMS=17/71/0 uCode=0x8701013

*PCPU0:1048841/VSCSIPoll

PCPU  0: SSVSVSVUVVVVVVVS

2020-06-19T22:15:58.957Z cpu0:1048841)Code start: 0x42000f000000 VMK uptime: 0:09:24:18.812

2020-06-19T22:15:58.959Z cpu0:1048841)0x451a0849b830:[0x42000f0fc6ce]PanicvPanicInt@vmkernel#nover+0x2c6 stack: 0x42000f0fc6ce

2020-06-19T22:15:58.961Z cpu0:1048841)0x451a0849b8e0:[0x42000f0fcbac]Panic_NoSave@vmkernel#nover+0x4d stack: 0x451a0849b940

2020-06-19T22:15:58.962Z cpu0:1048841)0x451a0849b940:[0x42000f01eaac]LockCheckSelfDeadlockInt@vmkernel#nover+0x95 stack: 0x52f6be00000000

2020-06-19T22:15:58.964Z cpu0:1048841)0x451a0849b950:[0x42000f1063e7]SP_WaitLockIRQ@vmkernel#nover+0x190 stack: 0x451a084a1000

2020-06-19T22:15:58.965Z cpu0:1048841)0x451a0849b9a0:[0x42000f106455]SPLockIRQWork@vmkernel#nover+0x3e stack: 0x420040000000

2020-06-19T22:15:58.967Z cpu0:1048841)0x451a0849b9c0:[0x42000f359b02]CpuSched_IdleHaltEnd@vmkernel#nover+0x3b stack: 0xef

2020-06-19T22:15:58.968Z cpu0:1048841)0x451a0849ba00:[0x42000f0df201]IntrCookie_DoInterrupt@vmkernel#nover+0x4c2 stack: 0x0

2020-06-19T22:15:58.970Z cpu0:1048841)0x451a0849bab0:[0x42000f0df3b9]IntrCookie_VmkernelInterrupt@vmkernel#nover+0x3a stack: 0xffffffffffffffef

2020-06-19T22:15:58.972Z cpu0:1048841)0x451a0849bad0:[0x42000f13e414]IDT_IntrHandler@vmkernel#nover+0x9d stack: 0x0

2020-06-19T22:15:58.973Z cpu0:1048841)0x451a0849baf0:[0x42000f154067]gate_entry@vmkernel#nover+0x68 stack: 0x0

2020-06-19T22:15:58.975Z cpu0:1048841)0x451a0849bbb8:[0x42000f086ab7]Power_ArchPerformWait@vmkernel#nover+0xc3 stack: 0x420040000880

2020-06-19T22:15:58.976Z cpu0:1048841)0x451a0849bbc0:[0x42000f086bd2]Power_ArchSetCState@vmkernel#nover+0x8f stack: 0x800000000

2020-06-19T22:15:58.978Z cpu0:1048841)0x451a0849bc10:[0x42000f35a304]CpuSchedIdleLoopInt@vmkernel#nover+0x23d stack: 0x420040000108

2020-06-19T22:15:58.980Z cpu0:1048841)0x451a0849bc80:[0x42000f35d19e]CpuSchedDispatch@vmkernel#nover+0x14d3 stack: 0x420040000120

2020-06-19T22:15:58.981Z cpu0:1048841)0x451a0849beb0:[0x42000f35e1d8]CpuSchedWait@vmkernel#nover+0x275 stack: 0x1

2020-06-19T22:15:58.983Z cpu0:1048841)0x451a0849bf20:[0x42000f35e37d]CpuSchedSleepUntilTC@vmkernel#nover+0xbe stack: 0x4519c0000430

2020-06-19T22:15:58.984Z cpu0:1048841)0x451a0849bfb0:[0x42000f4b2382]VSCSIPollCallback@vmkernel#nover+0x123 stack: 0x451a084a1100

2020-06-19T22:15:58.986Z cpu0:1048841)0x451a0849bfe0:[0x42000f35ef79]CpuSched_StartWorld@vmkernel#nover+0x82 stack: 0x0

2020-06-19T22:15:58.987Z cpu0:1048841)0x451a0849c000:[0x42000f0c5303]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0

2020-06-19T22:15:58.989Z cpu0:1048841)base fs=0x0 gs=0x420040000000 Kgs=0x0