VMware Communities
martynovich
Contributor
Contributor

PANIC: MXUserAllocSerialNumber: too many locks!

Dear developers,

we are using VMware Workstation Player 12.1.1 on Windows 10 and Windows 8 x64, Guest VM is a stripped down version of Linux (kernel 3.10) using latest open-vm-tools. To communicate to VM we're using VIX and vsock,

After a few hours of normal operation a window of VMware pops up saying "PANIC: MXUserAllocSerialNumber: too many locks!".

VIX Log file and vmsupport is attached.

0 Kudos
5 Replies
tracywang
Expert
Expert

Thanks for using Workstation. Is it possible for your to share your vix and vsocks scripts to me so that I could manage to reproduce this issue?

0 Kudos
HuanguoZhong
VMware Employee
VMware Employee

Thanks for coming to Workstation community. From the log, your VM added virtual disk by using physical disks. But current user don't have access right to the physical disk.

Please make sure the user have access right to access the physical disks. And you can try to power on the VM manually from Player UI first, if it works, then try with your script, hope it helps.Smiley Happy

0 Kudos
Kentzo
Enthusiast
Enthusiast

Could you confirm (or deny) that Host-side VIX implementation use similar code as in open-vm-tools ? If it's so, then this is exactly the problem we have.

0 Kudos
martynovich
Contributor
Contributor

This is a simple modification of VMware VIX "powerOn" sample. Run it like this:

cscript powerOn.wsf <path to vmx>

Wait until "Result" reaches something like 8.5 million (it will take around 20 hours), and then it will panic.

0 Kudos
martynovich
Contributor
Contributor

HuanguoZhong‌ The VM hasn't added any virtual disks ever. Neither did the Player, neither did our program.

0 Kudos