Sorry, I forgot to attach the log.
When Win7 is hanginging, vmware-vix always becomes 'daemon'.
Here is a part of the vmware-vix's log;
2017-08-31T17:04:24.751+09:00| vix| I125: UUID: Unable to open /sys/firmware/efi/systab: no such a directory, or file
2017-08-31T17:04:24.751+09:00| vix| I125: UUID: Unable to open /dev/mem: no permission
2017-08-31T17:04:24.751+09:00| vix| I125: UUID: Invalid gethostid routine. Value = 7F0100.
2017-08-31T17:04:24.751+09:00| vix| I125: vmxFilePath="/usr/lib/vmware/bin/vmware-vmx"
2017-08-31T17:04:24.751+09:00| vix| I125: vmxFilePathDebug="/usr/lib/vmware/bin/vmware-vmx-debug"
2017-08-31T17:04:24.751+09:00| vix| I125: vmxFilePathStats="/usr/lib/vmware/bin/vmware-vmx-stats"
2017-08-31T17:04:24.753+09:00| vix| I125: HostDeviceInfo_FindHostCDROMs: enumerating IDE CDROMs
2017-08-31T17:04:24.753+09:00| vix| I125: HostDeviceInfoFindHostIDECDROMs: /proc/ide could not be explored. Unable to enumerate host IDE cdroms.
2017-08-31T17:04:24.753+09:00| vix| I125: HostDeviceInfo_FindHostCDROMs: IDE CDROM enumerating completed
2017-08-31T17:04:24.753+09:00| vix| I125: HostDeviceInfo_FindHostCDROMs: enumerating SCSI CDROMs
2017-08-31T17:04:24.795+09:00| vix| I125: HostDeviceInfo_FindHostCDROMs: SCSI CDROM enumerating completed
2017-08-31T17:04:24.845+09:00| vix| I125: SMBIOS: can't open /dev/mem: Insufficient permission to access the file
2017-08-31T17:04:24.845+09:00| vix| I125: VmhsHostInfoPopulateSystem: Could not get information from smbios to populate VMDB.
2017-08-31T17:04:25.184+09:00| vix| I125: LOCALE ja_JP.UTF-8 -> NULL
This patch resolves only the compile error.
Even here on debian sid with kernel 4.13, vmware cannot start any vm since it complains about not available memory.
The mentoid patch was applied here too.
That's indeed the case. Vmware Workstation 12.5.7 is not compatible with kernel 4.13 stable. I do also experience memory errors when trying to resume vms from snapshots.
We need a patch for vmmon i guess
When hanging up, I get the lck folders as follows;
Windows 10 Professional.vmx.lck
Windows 7 x64.vmdx.lck
Windows 7 x64.vmx.lck
Windows 8 x64.vmx.lck
Windows XP Professional.vmx.lck
And each folder contains lck file;
WIndows 10 Professional.vmx,lck --> M61539.lck
Windows 7 x64.vmdk.lck --> M29833.lck
Windows 7 x64.vmx.lck --> M64595.lck
Windows 8 x64.vmx.lck --> M55107.lck
Windows XP Professional.vmx.lck --> M55094.lck
As you might know, these lck files are binary files. But I can't attach these on this HP.
With emacs, I can see in the M29833.lck;
bzMwfzRkqRnvdwAA 647206301(vmware-vmx) 1 X 6301 lc=3026799823^@@@@@@@@@@@...
Is this give you any hint to solve the problem?
In my case it does not start up after installation.
/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC symbol `clock_gettime'
$ uname -a
Linux mymachine 4.12.0-13-generic #14-Ubuntu SMP Sat Sep 2 15:52:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
(Ubuntu 17.10 beta)
$ ldd libbsd.so.0
linux-vdso.so.1 => (0x00007ffcdafe6000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fda779ee000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fda7760e000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fda773ef000)
$ objdump -d librt.so.1 | grep -B2 -A2 clock_gettime
51f0: 48 8b 05 d9 1d 20 00 mov 0x201dd9(%rip),%rax # 206fd0 <clock_nanosleep@@GLIBC_2.2.5+0x201db0>
51f7: c3 retq
The libraries are linked correctly, it seems that the error message is misleading.
Yes, finaly it works here too. Many thanks for that patches.
Thank you for the patch.
It helped on 12.5.7, but does not help on workstation pro 14.
vmmon does not compile
1 person found this helpful
It builds fine for me, you just need to resolve a trivial conflict. Version for 14.0.0 is here:
(Or just checkout the workstation-14.0.0 branch from the repository and build from those sources.)
Just curious. Where did you get kernel 4.13 for Debian Sid. I am running Sid with kernel 4.12.0-1-amd64 and had to back off of 4.12.0-2-amd64 because it would not run WS 12.5.7. But it works grea with the stock kernel - WS 14 - not at all.
I have the same problem with the memory and I would like to apply your patch, but I have no idea how - can you link me a guide where I can find how to do that, I am not very tech savy unfortunately
can you link me a guide where I can find how to do that
I've never seen a guide, but I can share with you how I do it. Keep in mind that I am certain there are better ways to do it, but mine is straight forward and works for me.
Get into your home directory, or somewhere you can store files temporarily
Copy the vmmon source tar ball to your temporary location
cp /usr/lib/vmware/modules/source/vmmon.tar .
You might want to keep a copy of the orginal vmmon.tar file if you think you might want to roll back. It is pretty broken right now though, so I didn't bother.
Extract the tar ball
tar xf vmmon.tar
Download the modified file that mkubecek posted and overwrite the one from the tar ball
For VMware Workstation 14:
wget -O ./vmmon-only/linux/hostif.c https://raw.githubusercontent.com/mkubecek/vmware-host-modules/fadedd9c8a4dd23f74da2b448572df95666dfe12/vmmon-only/linux/hostif.c
For VMware Workstation 12.5:
wget -O ./vmmon-only/linux/hostif.c https://raw.githubusercontent.com/mkubecek/vmware-host-modules/b50848c985f1a6c0a341187346d77f0119d0a835/vmmon-only/linux…
Wrap up the newly modified files into a tar ball replacing the original one
sudo tar cf /usr/lib/vmware/modules/source/vmmon.tar vmmon-only
Rebuild the VMware kernel modules
sudo vmware-modconfig --console --install-all
Reboot your system