This is my second install of ESXi 6.7 U1 and I'm seeing the same problem. The performance monitoring graph on the host and on individual VMs only shows the last few minutes, no matter how long it has been up. This is the case with all counters (CPU/Network/Memory/Disk). Screenshots attached. Running the free license. I have tried restarting hostd, running with/without NTP, and, obviously, a full re-install. Any suggestions?

I've found a lot of info about configuring passthrough and I've seen little snippets of info about different gpus that might be supported but nothing definitive. Hopefully you guys can help. We have a vsphere instance running a vm that's configured for what used to be terminal services. This terminal services is running a 30 machine computer lab but we are having a few little bottle necks that we need to work out, one being the GPU issue.

Morning Everyone,

I have a SQL VM Storage Policy defined like this:

1 Failure - Raid-1 Mirroring

Number of disk stripes per object = 1

IOPs limit for object = 0

Thick provisioning

Is this optimal for SQL Tier 1 performance (maximizing IOPS)?  

Will increasing the number of stripes per object increase performance?

Thank you, I award points!

This showed up on our ESXi 5.0 (where we only have ONE Virtual Machine) and there's a number of files in the datastore that I suspect are removable.

However, I certainly don't want to risk a complete failure by deleting files that shouldn't be deleted, hence this post.

Here's a listing of the files present and their size in the datastore:

Server_01.nvram, 8,48 KB, modified 5 May 2019

Server_01.vmdk, 262 144 000,00 KB, modified 17 Apr 2015

Server_01.vmsd, 1,44 KB, modified 15 Mar 2019

Server_01.vmx, 2,88 KB, modified 6 May 2019

Server_01.vmxf, 0,26 KB, modified 31 May 2018

Server_01-000001.vmdk, 2 327 552,00 KB, modified 15 May 2015

Server_01-000002.vmdk, 103 892 000,00 KB, modified 31 May 2018

Server_01-000003.vmdk, 61 604 860,00 KB, modified 15 Mar 2019

Server_01-000004.vmdk, 43 697 150,00 KB, modified 15 Mar 2019

Server_01-Snapshot3.vmsn, 27,81 KB, modified 31 May 2018

vmmcores-1.gz, 5 114,64 KB, modified 15 Oct 2015

vmmcores-2.gz, 16 672,00 KB, modified 6 May 2019

vmware.log, 30,71 KB, modified 6 May 2019

vmware-19.log, 80,31 KB, modified 31 May 2018

vmware-20.log, 112,06 KB, modified 1 Oct 2018

vmware-21.log, 81,49 KB, modified 14 Dec 2018

vmware-22.log, 133,43 KB, modified 6 May 2019

vmware-23.log, 31,05 KB, modified 6 May 2019

vmware-24.log, 30,71 KB, modified 6 May 2019

According to the VM Properties Server_01-000004.vmdk is used as the Virtual Disk.

Can I just delete any of the oldest vmdk's or are the somehow depending of each other?

The System Requirements of the disk of the server running as a VM is just 75 GB so the vmdk's seems to be very large, especially if they're dependent of each other...

Hope someone can help me with this!

BR,

Micael

Hi all,

I've been trying to install vcenter 6.7 into the ESXi host 6.0.

Unfortunately in the deployment process, it stuck in "validating network settings" which is shown in the attached image.

I would appreciate If someone can help me to sort this out.

it worth mentioning that the DNS is in place with the correct name and IP address.

Morning everyone,

Working on improving SQL on vSAN and here is one of the recommendations:

• While a single disk group per host is fully supported, it is recommended to have at least two disk groups per host, or more. Multiple disk groups can improve throughput in many cases and it provides better resilience to certain drive failure scenarios.

How do you configure this, and or how do you check if this is active?

Thank you, and I award points!

vSphere 6.5

I have 9 ESXI hosts all but one is 6.5 the one is 6.0

Trying to update this host having issues with vmTools and thought I would get the host up to date.

My error

The install completes OK

Any ideas or suggestions?

Thank you

Tom

Hi guys,

I am having a little problem with GPU passthrough on my Dell R610 running ESX 6.0U3 and AMD 7870 GPU.

I have 2 Xeon 5675 in my server and Intel Virtualization is enabled so all that should be covered. I can also see the device within PCI passthrough list and is capable of Passthrough just marked as "Disabled".

So I tick the GPU and enable passthrough, then ESXi tell me I must reboot the host and the GPU passthrough is enabled. I do as ESXi says and reboot the host, however, when it comes up it is "Disabled" again. I have been through this cycle about 5 times and am pulling my hair out. I also have an NVidia GTX1060 I can test this with.

Can someone please help before I give up?

Thank you,

Caleb

VMware vCenter 6.5

9 ESXI hosts all but one is ESXI 6.5

The one is ESXI 6.0  It was at 6.5 but the USB drive failed an upon installing on new usb drive I was unable to install 6.5 So I installed 6.0

When I migrated 3 VM's from my ESXI 6.5 Host to the 6.0 ESXI host I get this warning on the VM

VMWare Tools is outdated on the Virtual Machine    Update VMWare Tools

When I click on the Update VMware tools I get an error

So since the VM's came from an ESXI 6.5 host I tried to uninstall VMTools and then lost my mouse so I could not do any thing on the console.

I tried manually to install the VMTools from the 6.0 host but everything I tried failed.

I migrated the VM to a 6.5 Host and was able to install the VMtools from 6.5

What can I do to et rid of this message

Thank you

Tom

I saw that Photon TP2 is out and would like to update AppCatalyst to use it.  What is the easiest way to do that?

The update_check.sh did not report any newer versions as available.

I see that the /opt/vmware/appcatalyst/photonvm contains the VM files.  What is the easiest way to replace that content?

Regards,

Mark

Hi!

I have this server setup at home:

SuperMicro X10SLL-F

Intel Xeon E3-1241 v3

32GB 3CC 1600

LSI 8708EM2

2x Velociraptor 10k 300gb RAID 1

4x WD Red 2TB Raid 5

I was running Vsphere 6.0 since a long time, and I decided to go over 6.7. Installation worked fine, I have access to everything, all is working... Except 2 things:

1. I can't get my LSI 8708EM2 (detected as a 1078) to show drive status

2. Can't get my Storage Manager to access disk info or rebuild raid.

When I was on vSphere 6.0, I was able to see my drive status (and veeam one could alert me), and with my WIndows VM, I had LSI MSM and I was able to configure the raid card.

So what I did:

Install SAS driver I was using in version 6 --> not working

Installed the SMIS I had  --> not working

Installed lastest SMIS  --> not working

Disabled the Firewall --> not working

I have no idea what else I can do. I know it's an old card, but I got it for cheap. Any idea how can I get this fixed?

Thanks

Trying to migrate several Windows 10 VMS to my ESXI 6.0 Host

Getting this error

The virtual machine version is not capable with this version of the host

I powered the VM down and still unable to migrate the vm.

All my VMs are on a Shared storage with all my hosts.

Any ideas.

Thank you

Tom

And what version is that?

And how do I find it?

Cheers

Machine: 4GB RAM, Intel Core 2 Duo 2.5GHz, SATA RAID 0 with 2, 1TB WD RE3 drives.  NO SCSI

Can anyone tell me why I am stuck in this continuous rebooting cycle?  I put the iso CD in, wait for the "Loading VMware ISO" (photo attached) bar to  go across the screen and then some wierd cahracters show up at the end of the bar for nonosecond and BAM a reboot. It happens so fast I had to capture with a video/phone and frame by frame through it to see what the message said.

If I remove the CDduring the post, the machine tried to boot to the HDs and since there is nothing on them, I get an error.  I reinstall the CD rom, re-boot and  "Loading VMware ISO" bar to reboot cycle continues.

I removed all RAID features and tried to install to one SATA drive - same thing.  I even installed an IDE drive and again, no joy.

Any help is much appreciated.  Thank you!

Has anyone tried VP 4.0? I am at lost trying to set workload to run. Is there any pre-defined workloads came with VP 4.0? Any hint? Thanks.

Hi,

In the release notes (VMware View Planner 4.0 Release Notes ), it says:

Known Issues

• Outlook 2016 is not supported.
• Virtual machines under test are rebooted at the start of each run. This must be manually disabled in the harness configuration by setting VM_FORCE_REBOOT to 0 for instant clone tests.

Does this means that instant clones can be used for the View Planner tests?  We have a Horizon solution based on Instant Clones rather than Linked Clones and it would be good to be able to leverage that setup rather than having to deploy View Composer to run View Planner tests.

CC

I can not start my virtual machines after an error occurs by Re: ESXi 6.5a VM panic crash VMware ESX unrecoverable error: (vcpu-7) MXUserAllocSerialNumber: too many locks !.

the error rebooted the machines but they can no longer load the operating system.

This is part of the log:

2018-07-13T20:07:35.892Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150
2018-07-13T21:42:44.143Z| vcpu-1| I125: GuestMsg: Too many channels opened.
2018-07-13T21:42:44.143Z| vcpu-1| I125: GuestMsg: Too many channels opened.
2018-07-13T23:29:04.422Z| vcpu-0| I125: GuestRpc: Channel conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1
2018-07-14T16:17:19.542Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150
2018-07-14T16:59:58.822Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150
2018-07-14T22:51:15.633Z| vcpu-0| I125: GuestMsg: Too many channels opened.
2018-07-14T22:51:15.633Z| vcpu-0| I125: GuestMsg: Too many channels opened.
2018-07-15T00:07:30.436Z| vcpu-0| I125: GuestRpc: Channel conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1
2018-07-15T07:24:54.067Z| vcpu-0| E105: PANIC: MXUserAllocSerialNumber: too many locks!
2018-07-15T07:24:59.174Z| vcpu-0| W115: A core file is available in "/vmfs/volumes/5afc6e41-4fb78070-ce50-842b2bf9694c/WINSAAI-TJMEX/vmx-zdump.001"
2018-07-15T07:24:59.174Z| mks| W115: Panic in progress... ungrabbing
2018-07-15T07:24:59.174Z| mks| I125: MKS: Release starting (Panic)
2018-07-15T07:24:59.174Z| mks| I125: MKS: Release finished (Panic)
2018-07-15T07:24:59.183Z| vcpu-0| I125: Writing monitor file `vmmcores.gz`
2018-07-15T07:24:59.195Z| vcpu-0| W115: Dumping core for vcpu-0
2018-07-15T07:24:59.195Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges
2018-07-15T07:24:59.195Z| vcpu-0| I125: VMK Stack for vcpu 0 is at 0x439201493000
2018-07-15T07:24:59.195Z| vcpu-0| I125: Beginning monitor coredump
2018-07-15T07:25:00.176Z| mks| W115: Panic in progress... ungrabbing
2018-07-15T07:25:00.176Z| mks| I125: MKS: Release starting (Panic)
2018-07-15T07:25:00.176Z| mks| I125: MKS: Release finished (Panic)
2018-07-15T07:25:00.244Z| vcpu-0| I125: End monitor coredump
2018-07-15T07:25:00.244Z| vcpu-0| W115: Dumping core for vcpu-1
2018-07-15T07:25:00.244Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges
2018-07-15T07:25:00.245Z| vcpu-0| I125: VMK Stack for vcpu 1 is at 0x439201693000
2018-07-15T07:25:00.245Z| vcpu-0| I125: Beginning monitor coredump
2018-07-15T07:25:01.090Z| vcpu-0| I125: End monitor coredump
2018-07-15T07:25:01.090Z| vcpu-0| W115: Dumping core for vcpu-2
2018-07-15T07:25:01.090Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges
2018-07-15T07:25:01.090Z| vcpu-0| I125: VMK Stack for vcpu 2 is at 0x439201713000
2018-07-15T07:25:01.090Z| vcpu-0| I125: Beginning monitor coredump
2018-07-15T07:25:01.178Z| mks| W115: Panic in progress... ungrabbing
2018-07-15T07:25:01.178Z| mks| I125: MKS: Release starting (Panic)
2018-07-15T07:25:01.178Z| mks| I125: MKS: Release finished (Panic)
2018-07-15T07:25:01.932Z| vcpu-0| I125: End monitor coredump
2018-07-15T07:25:01.933Z| vcpu-0| W115: Dumping core for vcpu-3
2018-07-15T07:25:01.933Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges
2018-07-15T07:25:01.933Z| vcpu-0| I125: VMK Stack for vcpu 3 is at 0x439201793000
2018-07-15T07:25:01.933Z| vcpu-0| I125: Beginning monitor coredump
2018-07-15T07:25:02.180Z| mks| W115: Panic in progress... ungrabbing
2018-07-15T07:25:02.180Z| mks| I125: MKS: Release starting (Panic)
2018-07-15T07:25:02.180Z| mks| I125: MKS: Release finished (Panic)
2018-07-15T07:25:02.766Z| vcpu-0| I125: End monitor coredump
2018-07-15T07:25:02.767Z| vcpu-0| W115: Dumping core for vcpu-4
2018-07-15T07:25:02.767Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges
2018-07-15T07:25:02.767Z| vcpu-0| I125: VMK Stack for vcpu 4 is at 0x439201813000
2018-07-15T07:25:02.767Z| vcpu-0| I125: Beginning monitor coredump
2018-07-15T07:25:03.182Z| mks| W115: Panic in progress... ungrabbing
2018-07-15T07:25:03.182Z| mks| I125: MKS: Release starting (Panic)
2018-07-15T07:25:03.182Z| mks| I125: MKS: Release finished (Panic)
2018-07-15T07:25:03.590Z| vcpu-0| I125: End monitor coredump
2018-07-15T07:25:03.590Z| vcpu-0| W115: Dumping core for vcpu-5
2018-07-15T07:25:03.590Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges
2018-07-15T07:25:03.591Z| vcpu-0| I125: VMK Stack for vcpu 5 is at 0x439201893000
2018-07-15T07:25:03.591Z| vcpu-0| I125: Beginning monitor coredump
2018-07-15T07:25:04.184Z| mks| W115: Panic in progress... ungrabbing
2018-07-15T07:25:04.184Z| mks| I125: MKS: Release starting (Panic)
2018-07-15T07:25:04.184Z| mks| I125: MKS: Release finished (Panic)
2018-07-15T07:25:04.418Z| vcpu-0| I125: End monitor coredump
2018-07-15T07:25:05.186Z| mks| W115: Panic in progress... ungrabbing
2018-07-15T07:25:05.186Z| mks| I125: MKS: Release starting (Panic)
2018-07-15T07:25:05.186Z| mks| I125: MKS: Release finished (Panic)
2018-07-15T07:25:06.187Z| mks| W115: Panic in progress... ungrabbing
2018-07-15T07:25:06.187Z| mks| I125: MKS: Release starting (Panic)
2018-07-15T07:25:06.187Z| mks| I125: MKS: Release finished (Panic)
2018-07-15T07:25:07.189Z| mks| W115: Panic in progress... ungrabbing
2018-07-15T07:25:07.189Z| mks| I125: MKS: Release starting (Panic)
2018-07-15T07:25:07.189Z| mks| I125: MKS: Release finished (Panic)
2018-07-15T07:25:07.279Z| vcpu-0| I125: Printing loaded objects
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC437B7000-0xC4486D4F4): /bin/vmx
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC84E67000-0xC84E7E448): /lib64/libpthread.so.0
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC85084000-0xC85085F00): /lib64/libdl.so.2
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC85288000-0xC85290F9C): /lib64/librt.so.1
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC854A4000-0xC857391C4): /lib64/libcrypto.so.1.0.2
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC8596A000-0xC859D2B1C): /lib64/libssl.so.1.0.2
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC85BDE000-0xC85CF24DC): /lib64/libX11.so.6
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC85EF9000-0xC85F0801C): /lib64/libXext.so.6
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC86109000-0xC861ED341): /lib64/libstdc++.so.6
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC8640C000-0xC8648BDA4): /lib64/libm.so.6
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC8668E000-0xC866A2BC4): /lib64/libgcc_s.so.1
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC868A4000-0xC86A04DD4): /lib64/libc.so.6
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC44C46000-0xC44C637D8): /lib64/ld-linux-x86-64.so.2
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC86C0F000-0xC86C29634): /lib64/libxcb.so.1
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC86E2B000-0xC86E2C95C): /lib64/libXau.so.6
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC873FB000-0xC874904B4): /usr/lib64/vmware/plugin/objLib/upitObjBE.so
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC876A9000-0xC877FEF64): /usr/lib64/vmware/plugin/objLib/vsanObjBE.so
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC87A96000-0xC87AAAF94): /lib64/libz.so.1
2018-07-15T07:25:07.279Z| vcpu-0| I125: [0xC87EF5000-0xC87F001D0): /lib64/libnss_files.so.2
2018-07-15T07:25:07.279Z| vcpu-0| I125: End printing loaded objects
2018-07-15T07:25:07.279Z| vcpu-0| I125: Backtrace:
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[0] 0000000c898861d0 rip=0000000c43e30c47 rbx=0000000c43e30740 rbp=0000000c898861f0 r12=0000000000000000 r13=0000000000000001 r14=0000000c4527ecf0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[1] 0000000c89886200 rip=0000000c43975a8c rbx=0000000c89886220 rbp=0000000c89886700 r12=0000000c44ac5c10 r13=0000000000000001 r14=0000000c4527ecf0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[2] 0000000c89886710 rip=0000000c43de5300 rbx=0000000c45066580 rbp=0000000c89886710 r12=0000000c44efacd0 r13=00000000ff000000 r14=0000000c4527ecf0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[3] 0000000c89886720 rip=0000000c43de3ee8 rbx=0000000c45066580 rbp=0000000c89886740 r12=0000000c44efacd0 r13=00000000ff000000 r14=0000000c4527ecf0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[4] 0000000c89886750 rip=0000000c44299969 rbx=0000000c4526f0b0 rbp=0000000c89886760 r12=0000000000000001 r13=0000000c4526f020 r14=0000000c4527ecf0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[5] 0000000c89886770 rip=0000000c43b9a768 rbx=0000000c4526f0b0 rbp=0000000c89886780 r12=0000000000000001 r13=0000000c4526f020 r14=0000000c4527ecf0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[6] 0000000c89886790 rip=0000000c43b996cc rbx=0000000000000069 rbp=0000000c898867d0 r12=0000000000000001 r13=0000000c4526f020 r14=0000000c4527ecf0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[7] 0000000c898867e0 rip=0000000c43b9db9b rbx=0000000c89886890 rbp=0000000c89886810 r12=0000000c4527eca0 r13=0000000c4527ee80 r14=0000000c4527ecf0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[8] 0000000c89886820 rip=0000000c43b9d1bb rbx=0000000c4527eca0 rbp=0000000c898868d0 r12=0000000c4505a220 r13=0000000c4527ee80 r14=0000000c4527ecf0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[9] 0000000c898868e0 rip=0000000c43b9da97 rbx=0000000c4505a220 rbp=0000000c89886930 r12=0000000c4527eca0 r13=0000000c4527ecf0 r14=0000000c898868f0 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[10] 0000000c89886940 rip=0000000c43a892f2 rbx=0000000c4505a220 rbp=0000000c89886950 r12=0000000c4524f340 r13=00000000fffffffe r14=0000000000000038 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[11] 0000000c89886960 rip=0000000c43a8c702 rbx=0000000c8813c560 rbp=0000000c898869a0 r12=0000000000000038 r13=00000000fffffffe r14=0000000000000038 r15=0000000000000038
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[12] 0000000c898869b0 rip=0000000c43a8bd22 rbx=0000000c88151020 rbp=0000000c89886a30 r12=0000000c45241fd0 r13=0000000c4505a220 r14=0000000000000038 r15=0000000c898869b0
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[13] 0000000c89886a40 rip=0000000c43d7f301 rbx=0000000c44bd9da8 rbp=0000000c89886a70 r12=0000000c4492d410 r13=0000000000000153 r14=0000000c44fd47d0 r15=0000000000000000
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[14] 0000000c89886a80 rip=0000000c43da6b56 rbx=000000000000012d rbp=0000000c89886ac0 r12=0000000c44ac5c10 r13=0000000c44bd16e0 r14=0000000c44aaba60 r15=0000000000000000
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[15] 0000000c89886ad0 rip=0000000c43d7f3e8 rbx=0000000000000000 rbp=0000000c89886ae0 r12=0000000c89886b00 r13=0000000c44f7d550 r14=0000000c44e64040 r15=0000000000000003
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[16] 0000000c89886af0 rip=0000000c43e1c225 rbx=0000000c44bdb3a0 rbp=0000000c89886c40 r12=0000000c89886b00 r13=0000000c44f7d550 r14=0000000c44e64040 r15=0000000000000003
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[17] 0000000c89886c50 rip=0000000c84e6eddc rbx=0000000000000000 rbp=0000000000000000 r12=00000311f5b4ca30 r13=0000000c898879c0 r14=0000000c44e64040 r15=0000000000000003
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[18] 0000000c89886d60 rip=0000000c8697600d rbx=0000000000000000 rbp=0000000000000000 r12=00000311f5b4ca30 r13=0000000c898879c0 r14=0000000c44e64040 r15=0000000000000003
2018-07-15T07:25:07.280Z| vcpu-0| I125: Backtrace[19] 0000000c89886d68 rip=0000000000000000 rbx=0000000000000000 rbp=0000000000000000 r12=00000311f5b4ca30 r13=0000000c898879c0 r14=0000000c44e64040 r15=0000000000000003
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[0] 0000000c898861d0 rip=0000000c43e30c47 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[1] 0000000c89886200 rip=0000000c43975a8c in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[2] 0000000c89886710 rip=0000000c43de5300 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[3] 0000000c89886720 rip=0000000c43de3ee8 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[4] 0000000c89886750 rip=0000000c44299969 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[5] 0000000c89886770 rip=0000000c43b9a768 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[6] 0000000c89886790 rip=0000000c43b996cc in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[7] 0000000c898867e0 rip=0000000c43b9db9b in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[8] 0000000c89886820 rip=0000000c43b9d1bb in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[9] 0000000c898868e0 rip=0000000c43b9da97 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[10] 0000000c89886940 rip=0000000c43a892f2 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[11] 0000000c89886960 rip=0000000c43a8c702 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[12] 0000000c898869b0 rip=0000000c43a8bd22 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[13] 0000000c89886a40 rip=0000000c43d7f301 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[14] 0000000c89886a80 rip=0000000c43da6b56 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[15] 0000000c89886ad0 rip=0000000c43d7f3e8 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[16] 0000000c89886af0 rip=0000000c43e1c225 in function (null) in object /bin/vmx loaded at 0000000c437b7000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[17] 0000000c89886c50 rip=0000000c84e6eddc in function (null) in object /lib64/libpthread.so.0 loaded at 0000000c84e67000
2018-07-15T07:25:07.280Z| vcpu-0| I125: SymBacktrace[18] 0000000c89886d60 rip=0000000c8697600d in function clone in object /lib64/libc.so.6 loaded at 0000000c868a4000
2018-07-15T07:25:07.281Z| vcpu-0| I125: SymBacktrace[19] 0000000c89886d68 rip=0000000000000000
2018-07-15T07:25:07.281Z| vcpu-0| I125: Msg_Post: Error
2018-07-15T07:25:07.281Z| vcpu-0| I125: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vcpu-0)
2018-07-15T07:25:07.281Z| vcpu-0| I125+ MXUserAllocSerialNumber: too many locks!
2018-07-15T07:25:07.281Z| vcpu-0| I125: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/5afc6e41-4fb78070-ce50-842b2bf9694c/WINSAAI-TJMEX/vmware.log". 
2018-07-15T07:25:07.281Z| vcpu-0| I125: [msg.panic.requestSupport.withoutLog] You can request support. 
2018-07-15T07:25:07.281Z| vcpu-0| I125: [msg.panic.requestSupport.vmSupport.vmx86]
2018-07-15T07:25:07.281Z| vcpu-0| I125+ To collect data to submit to VMware technical support, run "vm-support".
2018-07-15T07:25:07.281Z| vcpu-0| I125: [msg.panic.response] We will respond on the basis of your support entitlement.
2018-07-15T07:25:07.281Z| vcpu-0| I125: ----------------------------------------
2018-07-15T07:25:07.282Z| vcpu-0| I125: Exiting

When try start my server the virtual hard drive 0 Bites

can you help me please

Cause: TypeError: Cannot set property 'endSector' of undefined

Version: 1.25.0

Build: 7872652

ESXi: 6.7.0

Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.131 Safari/537.36

Exception stack:

TypeError: Cannot set property 'endSector' of undefined

  at Object.fn (https://192.168.8.101/ui/scripts/main.js:359:17770)

  at n.$digest (https://192.168.8.101/ui/scripts/main.js:320:16345)

  at n.$apply (https://192.168.8.101/ui/scripts/main.js:320:17775)

  at https://192.168.8.101/ui/scripts/main.js:320:24200

  at e (https://192.168.8.101/ui/scripts/main.js:319:5691)

  at https://192.168.8.101/ui/scripts/main.js:319:7797

i was using chrome?

Hello.

How can I clone a VM in VMware ESXi 6.7? When I clone a VM and modify it the can if affect to the original VM?

Thank you.

I just installed a new vCenter 6.5 appliance on my ESXI 6.5 Host.  I was very sluggish

Migrated to another host added more CPU

But the logon is taking a very long time

This is from my conso0le.

Any ideas?

Thank you

Tom