Hi, I am running Workstation Player V12.5.8 on a Windows 10. I am running a Windows XP guest and cannot get on to the internet with Internet Explorer. I have set up the network using both Bridged and NAT and both show that I am connected to the network. When I open a command window, I am able to ping both google and 8.8.8.8. Has anyone experienced this or know a fix?

A PC died. It had Macrium Reflect running, which took a disk image every night. I want to use one of these to create a VM of the machine, so I can make sure I've got everything off it.

I used Reflect to create a vhd file from the latest disk image, and now want to use that in VM Player 14. According to a few places I've seen (such as the comment to this SO answer, and this blog post), I should be able to do this. However, I can't see any way to tell VM Player to use the vhd file.

Any suggestions? Thanks

Running vmware player 14.0.0 on Linux.

Tried kernel versions 4.9.x and 4.14.x with an unofficial Patch for the vmmon kernel module.

Everything works fine on a Lenovo ThinkCentre m93p tiny and an HP Compaq 8200 Elite with both kernel versions.

Problems arise on a FUJITSU Esprimo P956, no matter which mode we select for the parallel port in the BIOS.

Disabling the port in the BIOS, or removing the following lines from the .vmx fixes the problem:

parallel0.present = "TRUE"

parallel0.startConnected = "TRUE"

parallel0.fileType = "device"

parallel0.fileName = "/dev/parport0"

parallel0.bidirectional = "TRUE"

parallel0.autodetect = "FALSE"

On vmware 12.5.7, the parallel port worked just fine on that machine.

I recently imported the XP Mode VM from a windows 7 PC to VMware Player 14.  It works great.  Can I now uninstall, from Windows 7 PC, the XP Mode and the Virtual PC programs and continue to use the virtual machine that was created via the import?

Thanks

Glenn

Hi

I use Workstation Player 14.0.0 on a Win 7 Pro 64bit. I use a virtual machine with Win XP Pro.

In the past with 12.5 I had no issues.

Now with 14.0 I have a strange problem:

- at first start of virtual machine, only a part of the effective resolution is used, the other part is black

- when I restart the emulated Win XP, the whole screen of the program window is used

e.g. resolution of the VM 1280 x 1024, first start only 1280 x about 800 is usable, the other part is black and also the mouse pointer is not in sync, after reboot of Win XP, the resolution is fully usuable and the mouse pointer is in sync.

I did already reinstall VMware tools and VGA device. But the problem is still there.

Hi,

I'm running VMWare Player 12 on a Windows 8.1 laptop as host and CentOS 6.9 as guest. One issue I've not been able to resolve is a connection between host and guest to use internet via a wifi connection. Host is tethered to iPhone via wifi and works fine, though guest doesn't have any connectivity at all. When using a wired network all is good. I have Bridged connection set on the guest for both wired and wireless, though when going wireless I get nothing, I suspect its a routing issue though can't be sure.

Has anyone seen this same issue or have a resolution, if need more details like ip addr or netstat -rn off guest or ipconfig off host then let me know.

Cheers,

Thornton

Hi there !

I am using Lenovo X250 win 8.1 with Total Graphic memory of 4352 MB and Dedicated Video Memory of 512MB and rest as shared

I installed OS X 10.11 El Capitan using VMware workstation 12.

IN System Report aS:

Display:

Type: GPU

  Bus: PCI

  VRAM (Total): 128 MB

  Device ID: 0x0405

  Revision ID: 0x0000

  Displays:

Display:

  Resolution: 1366 x 768

  Pixel Depth: 32-Bit Color (ARGB8888)

  Main Display: Yes

  Mirror: Off

  Online: Yes

  Vendor ID: 0x15ad

My problem : I can't Install final Cut Pro !!! (My ultimate aim of using VMware )

1. Tried to install Final Cut pro 7 (as could be installed in 128MB VRam) but got below and can't Install:

• Final Cut Studio Installer requires that your system have 128 MB of VRAM; this system has only 0 MB of VRAM.

• Final Cut Studio Installer recommends a screen resolution of 1280x800; this system currently has a screen resolution of 1366x768.

• Final Cut Studio Installer requires that your system have a Quartz Extreme capable video card.

2. Tried to Install Final Cut Pro 10.2.1 but can't open and got report as attached as "final cut pro 10.2.1 problem" and display image as attached.

Kindly help me on either option so that i could use final Cut pro. pls find the VMX file attached "OS X 10.11 El Capitan" and suggest if can be edit.

Pls do share me idea to proceed and viber/whatsapp at : +9779801005633

Looking for help on solving why i can not connect a physical serial port in workstation 14.

I am using workstation 14 hosted on Ubuntu 16.04 LTS  7.5GB, 64bit.

Guest is Windows XP Pro.  I have no problem running to vm.

when a I add a serial port to the VM settings:  connect at power on checked, Use a physical serial port: checked, Device: Auto detect(this is the only option).

when powering on i get:

Cannot connect the virtual device serial1 because no corresponding device is available.on the host.

Do you want to try to connect this virtual device every time you power on the virtual machine?

Yes

Next window

Error toggling removable device: Serial port serial1 connection operation failed.

ok

Any ideas of how to get the serial ports to show up?

Thank

Todd

Hi all,

I have noticed that with my VMs running in VM Player, when I launch them, they go to full screen mode straight off the bat, which is what I want, and this works great when I am out and about, because they launch with the correct resolution to run full screen (just using my laptop monitor).  When I am docked and have 2 additional screens that run a slightly different resolution to my laptop (screens are 1920 x 1200 and laptop is 1920 x 1080), if I use Win + Shift + Left Cur to move the VM to my left most screen (1920 x 1200) off my laptop screen (1920 x 1080), with the VM in full screen mode, VM Player does not trigger to recalculate the resolution that the VM should be running in.

Its not a massive issue, but an annoying one as it means I have to exit full screen mode and then re-enter it, which is a PITA.

Is this a known bug?  Is there a way to work around it by hitting a shortcut keycombo to trigger a refresh of the GFX res that VMWare uses?

Thanks

Hello guys,

this is my first virtualization project in vmware player. I decided to "virtualize" two machines with windows XP OS and put it on one new machine with windows 7 as host.

Machines A and B had a network connection between them and this connection was used by some applications installed on them. In addition to these connections, both machines had their own network connection to other networks.

For example machine A had two LAN connections: IP address 10.0.0.15 and 192.168.0.1, and machine B had IP address 172.20.0.15 and 192168.0.2. IP addresses 192.168.xxx.xxx. were used between these two machines.

Since these machines will be virtualized, I need one new host machine with only two LAN interfaces (third network is between virtual machines i.e. internal network).

So I used standalone converter and successfully made two VMs and I set up internal network between them. I have test the communication between them and it is OK

So, right now, I need to set up network connection on virtual machine A to network 10.0.0.xxx and network connection on virtual machine B to network 172.20.0.xxx.

Should I set up virtual network adapters as NAT or Bridged? I have tried the following:

- I have set up first LAN interface of host machine to IP address of machine A (10.0.0.15), and second to 172.20.0.15

- In properties of virtual machine A I have set up virtual network adapter to Bridged and I have chosen physical network card  (configure adapter) with address 10.0.0.15

- In  properties of virtual machine B I have set up virtual network adapter to Bridged and I have chosen physical network card with address 172.20.0.15

The result is that I have a limited connectivity and cannot ping network 10.0.0.xxx from VMA and I also cannot ping network 172.20.0.xxx from VMB

If I chose NAT, then how can I be sure that VMA cannot access network 172.20.0.xxx? This should not be the case.

Basically I want that my virtual network adapter from VMA can only be bridged to host network card with IP address 10.0.0.15 and VMB to be bridged to 172.20.0.15.

Attached, please find my block diagram that.

Thank you very much for your help.

Hi!

I need to install the Tools on Server 2000 with SP4

I read this article: kb.vmware.com/kb/2007120 and install the KB835732. But I Keep getting this message.

What can I do???

The Player Version is 6.0.1 build 1379776

Regards

Hi,

I have some VM deployed on my windows 10 laptop.

I try different versions of VM player with same result.

I use the Bridge mode.

I try the LAN and Wifi with same result.

All the VM can access the network.

Let's say that my VM receive 10.0.1.120

my guest host (my own laptop) have 10.0.1.115

the vm can access without any issue Internet and any server within the 10.0.1.0/24

the guest host can access without any issue internet and any server within the 10.0.1.0/24

connectivity is working fine on all case.

except once the VM try to ping or access the guest IP address or the revert.

10.0.1.200 cannot ping 10.0.1.115

10.0.1.115 cannot ping 10.0.1.200

but 10.0.1.115 & 10.0.1.120 can ping the default gateway 10.0.1.1

I check the ARP on both devices and seems that there is no connectivity at all.

I manually enter (static) add the ARP on each side, still no connectivity.

Envoi d’une requête 'Ping'  10.0.1.120 avec 32 octets de données :

Réponse de 10.0.1.115 : Impossible de joindre l’hôte de destination.

Réponse de 10.0.1.115 : Impossible de joindre l’hôte de destination.

Réponse de 10.0.1.115 : Impossible de joindre l’hôte de destination.

Réponse de 10.0.1.115 : Impossible de joindre l’hôte de destination.

The VM is a Kali but I have the same behavior if the VM is a windows.

I run 2 VM and both VM can reach each other.

The only issue is within VM and guest.

Thanks for any feedback or advice.

Steve

I installed the latest Player 14 on a windows 10 machine.  Everything looked fine.  After a while, mouse clicks stopped working in the VM.  Mouse would move and keyboard was still functioning.  Later on, mouse clicks worked again.  I uninstalled and went back to 12.5.x.  Everything worked fine.

Last week, I built a new computer with a fresh copy of windows 10.  Installed Player 14 again.  Same thing happened after some time.  Again, went back to 12.5.x and mouse works all the time.  This happens with Windows 10 and Ubuntu virtual machines.

Has anyone else ran into this and found a solution?

Thanks!

Had been using V12 fine but just installed 14 on an Ubuntu 16.04 machine.

If I try to create or open a virtual machine the machine does not get put in the list (on the left under home).

If I use my file manager to get to a vmx file and click on it the player runs for the vm but still the player will not list the VM.

Without getting the VM in the list I am unable to change settings before launching the VM.

Is this a bug? 

Hey yall!

I'm trying to setup High Sierra in a virtual machine to reduce the number of times I have to reboot in order to develop software for different platforms. I like to support Mac, Windows, and Linux when I write my applications! I managed to get macOS 10.13 High Sierra running as a guest VM with VMware Fusion 10 on macOS 13.13 High Sierra host, without too much trouble. Here's my VMX for macOS hosts:

https://gist.github.com/mcandre/48f90963d9a24315024319cd62142f6a

However, I would like to be able to use High Sierra from Windows 10 hosts (e.g. Boot Camp'ed on Apple hardware). I'm following a dozen online tutorials for this, and can work around most glitches like ensuring that

smc.version = "0"

and patching VMware with the unlocker, and ensuring that the drive interfaces are SATA. However, I am not able to boot up the full macOS SetupAssistant installer. From a Windows host, I just get boot looping between the Apple logo and the VMware logo. Any tips for fixing this?

Screenshots

https://imgur.com/a/tHJ94

Also posting this to Stack Exchange, InsanelyMac, tonymacx86, and osx86.net in case other communities can help, too!

Hi!

I just installed VMWare Player 12 (12.5.7 build-5813279) and tried to install Windows Server 2016 Essentials. However, the configuration of Windows Server is stall at 17% - and it doesn't move further (screen shot attached). I tried it on two different computers - same thing. It's impossible to work with Windows Server until initial configuration is finished. From this I conclude this is something with VMWare.

Windows 10 Pro 64 trying to install 12.5.

Says another install is running.

What to do?

Hi, so I've been running around in circles trying to figure out how to increase the space available on my Ubuntu 64-bit on Workstation (player) 12.0 virtual machine.

Essentially I followed this guide: (How to Increase Disk Space in VMware (with Pictures) - wikiHow  Method 1)

But when I get to step 6, there is no other disk other than disk 0.

After looking through a handful of articles and investigating what the problem could be, I think it could be related to the fact that my .vmdk is where older workstation locations usually are, and that my .vmdk is split up in a way I don't understand, so I am unable to map it to a virtual disk and see the partitioned disk that would allow me to expand the volume. However, I am very ignorant about all of this, despite having spent hours reading. Does anyone know how I could finish expanding my disk space for use on the Ubuntu virtual machine?

Hello, I was wondering if you could help me out, I am running Kali Linux 2017.3, and I'm trying to get VMware player 14.0.0-6661328.x86_64 running but I can't.

It installs fine, but when i wan't to load the program, a pop up called VMware Kernel Module Updater appears and does this:

Stopping VMware Services    -->    OK

Compiling:

     Virtual Machine Moniter    --> Warning

Running depmod                   --> OK

Starting VMware Services     --> Error

Then it tells me that before I can run VMware, several modules must be compiled and loaded into the running kernel. I click on install and it starts al over again:

Stopping Vmware Services    -->    OK

Compiling:

     Virtual Machine Moniter    --> Warning

Running depmod                   --> OK

Starting VMware Services     --> Error

but gives me an error:

"Unable to start Services

See log file.

and it gives the "before VMware can run, several modules must be compiled and loaded into the running Kernel" again, and again

Is there any solution to this? I would greatly appreciate your help. The log file is below

This is the output of the log file:

2017-12-11T18:04:38.731-07:00| vthread-1| I125: Log for VMware Workstation pid=8801 version=14.0.0 build=build-6661328 option=Release

2017-12-11T18:04:38.731-07:00| vthread-1| I125: The process is 64-bit.

2017-12-11T18:04:38.731-07:00| vthread-1| I125: Host codepage=UTF-8 encoding=UTF-8

2017-12-11T18:04:38.731-07:00| vthread-1| I125: Host is Linux 4.14.0-kali1-amd64 Kali GNU/Linux Rolling

2017-12-11T18:04:38.731-07:00| vthread-1| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2017-12-11T18:04:38.731-07:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2017-12-11T18:04:38.731-07:00| vthread-1| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2017-12-11T18:04:38.731-07:00| vthread-1| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2017-12-11T18:04:38.731-07:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.

2017-12-11T18:04:38.731-07:00| vthread-1| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2017-12-11T18:04:38.731-07:00| vthread-1| I125: DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.

2017-12-11T18:04:38.731-07:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.

2017-12-11T18:04:38.731-07:00| vthread-1| I125: PREF Optional preferences file not found at /root/.vmware/preferences. Using default values.

2017-12-11T18:04:38.793-07:00| vthread-1| W115: Logging to /tmp/vmware-root/vmware-8801.log

2017-12-11T18:04:38.819-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:04:38.819-07:00| vthread-1| I125: Created new pathsHash.

2017-12-11T18:04:38.819-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:04:38.819-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:04:38.819-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:04:38.819-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:04:38.819-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:04:38.831-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:04:38.831-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:04:38.952-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:04:38.952-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:04:38.973-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:04:38.973-07:00| vthread-1| I125: Reading in info for the vmmon module.

2017-12-11T18:04:38.973-07:00| vthread-1| I125: Reading in info for the vmnet module.

2017-12-11T18:04:38.973-07:00| vthread-1| I125: Reading in info for the vmblock module.

2017-12-11T18:04:38.973-07:00| vthread-1| I125: Reading in info for the vmci module.

2017-12-11T18:04:38.973-07:00| vthread-1| I125: Reading in info for the vsock module.

2017-12-11T18:04:38.973-07:00| vthread-1| I125: Setting vsock to depend on vmci.

2017-12-11T18:04:38.973-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:04:38.976-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:04:38.976-07:00| vthread-1| I125: Invoking modinfo on "vmnet".

2017-12-11T18:04:38.979-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 0.

2017-12-11T18:04:38.979-07:00| vthread-1| I125: Invoking modinfo on "vmblock".

2017-12-11T18:04:38.981-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:04:38.982-07:00| vthread-1| I125: Invoking modinfo on "vmci".

2017-12-11T18:04:38.984-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:04:38.984-07:00| vthread-1| I125: Invoking modinfo on "vsock".

2017-12-11T18:04:38.987-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 0.

2017-12-11T18:04:39.005-07:00| vthread-1| I125: to be installed: vmmon status: 0

2017-12-11T18:04:39.016-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:04:39.016-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:04:39.016-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:04:39.016-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:04:39.016-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:04:39.016-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:04:39.028-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:04:39.028-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:04:39.149-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:04:39.149-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:04:39.169-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:04:39.169-07:00| vthread-1| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.14.0-kali1-amd64/build/include

2017-12-11T18:04:39.169-07:00| vthread-1| I125: Update kernel header path to /lib/modules/4.14.0-kali1-amd64/build/include

2017-12-11T18:04:39.169-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:04:39.169-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:04:39.169-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:04:39.169-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:04:39.182-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:04:39.182-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:04:39.184-07:00| vthread-1| I125: Found compiler at "/usr/bin/gcc"

2017-12-11T18:04:39.188-07:00| vthread-1| I125: Got gcc version "7".

2017-12-11T18:04:39.188-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:04:39.192-07:00| vthread-1| I125: Got gcc version "7".

2017-12-11T18:04:39.192-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:04:39.194-07:00| vthread-1| I125: Trying to find a suitable PBM set for kernel "4.14.0-kali1-amd64".

2017-12-11T18:04:39.194-07:00| vthread-1| I125: No matching PBM set was found for kernel "4.14.0-kali1-amd64".

2017-12-11T18:04:39.194-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:04:39.194-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:04:39.194-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:04:39.194-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:04:39.194-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:04:39.204-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:04:39.204-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:04:39.207-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:04:39.207-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:04:39.207-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:04:39.207-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:04:39.207-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:04:39.219-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:04:39.219-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:04:39.219-07:00| vthread-1| I125: Using temp dir "/tmp".

2017-12-11T18:04:39.222-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:04:39.222-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:04:39.222-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:04:39.222-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:04:39.222-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:04:39.222-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:04:39.234-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:04:39.234-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:04:39.354-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:04:39.354-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:04:39.375-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:04:39.375-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:04:39.379-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:04:39.559-07:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.14.0-kali1-amd64/misc/vmmon.ko".

2017-12-11T18:04:39.559-07:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-12-11T18:04:39.573-07:00| vthread-1| I125: Successfully extracted the vmmon source.

2017-12-11T18:04:39.574-07:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-IPy7uz/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-12-11T18:04:42.459-07:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

2017-12-11T18:09:53.092-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:09:53.092-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:09:53.092-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:09:53.092-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:09:53.092-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:09:53.106-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:09:53.106-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:09:53.106-07:00| vthread-1| I125: Using temp dir "/tmp".

2017-12-11T18:09:53.109-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:09:53.109-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:09:53.109-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:09:53.109-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:09:53.109-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:09:53.109-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:09:53.120-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:09:53.120-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:09:53.239-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:09:53.240-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:09:53.260-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:09:53.260-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:09:53.266-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:09:53.973-07:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.14.0-kali1-amd64/misc/vmmon.ko".

2017-12-11T18:09:53.974-07:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-12-11T18:09:53.989-07:00| vthread-1| I125: Successfully extracted the vmmon source.

2017-12-11T18:09:53.989-07:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-2IQ4io/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-12-11T18:09:56.912-07:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

2017-12-11T18:14:12.145-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:14:12.145-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:14:12.145-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:14:12.145-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:14:12.145-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:14:12.159-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:14:12.159-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:14:12.159-07:00| vthread-1| I125: Using temp dir "/tmp".

2017-12-11T18:14:12.161-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:14:12.161-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:14:12.161-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:14:12.161-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:14:12.161-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:14:12.161-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:14:12.173-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:14:12.173-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:14:12.295-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:14:12.295-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:14:12.316-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:14:12.316-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:14:12.322-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:14:13.056-07:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.14.0-kali1-amd64/misc/vmmon.ko".

2017-12-11T18:14:13.056-07:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-12-11T18:14:13.070-07:00| vthread-1| I125: Successfully extracted the vmmon source.

2017-12-11T18:14:13.070-07:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-qnQrEL/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-12-11T18:14:16.004-07:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

2017-12-11T18:18:20.143-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:18:20.143-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:18:20.143-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:18:20.143-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:18:20.143-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:18:20.156-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:18:20.156-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:18:20.156-07:00| vthread-1| I125: Using temp dir "/tmp".

2017-12-11T18:18:20.158-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:18:20.158-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:18:20.158-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:18:20.158-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:18:20.158-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:18:20.158-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:18:20.169-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:18:20.169-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:18:20.292-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:18:20.292-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:18:20.312-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:18:20.312-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:18:20.318-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:18:21.079-07:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.14.0-kali1-amd64/misc/vmmon.ko".

2017-12-11T18:18:21.080-07:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-12-11T18:18:21.100-07:00| vthread-1| I125: Successfully extracted the vmmon source.

2017-12-11T18:18:21.100-07:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-83XV04/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-12-11T18:18:24.066-07:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

2017-12-11T18:18:58.917-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:18:58.918-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:18:58.918-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:18:58.918-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:18:58.918-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:18:58.931-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:18:58.931-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:18:58.931-07:00| vthread-1| I125: Using temp dir "/tmp".

2017-12-11T18:18:58.933-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:18:58.933-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:18:58.933-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:18:58.933-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:18:58.933-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:18:58.933-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:18:58.945-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:18:58.945-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:18:59.066-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:18:59.066-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:18:59.087-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:18:59.087-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:18:59.093-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:18:59.804-07:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.14.0-kali1-amd64/misc/vmmon.ko".

2017-12-11T18:18:59.805-07:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-12-11T18:18:59.823-07:00| vthread-1| I125: Successfully extracted the vmmon source.

2017-12-11T18:18:59.823-07:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-leg4sz/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-12-11T18:19:02.737-07:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

2017-12-11T18:19:24.237-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:19:24.237-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:19:24.237-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:19:24.237-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:19:24.237-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:19:24.250-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:19:24.250-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:19:24.250-07:00| vthread-1| I125: Using temp dir "/tmp".

2017-12-11T18:19:24.252-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:19:24.252-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:19:24.252-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:19:24.252-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:19:24.252-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:19:24.252-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:19:24.264-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:19:24.264-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:19:24.393-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:19:24.393-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:19:24.413-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:19:24.413-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:19:24.420-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:19:25.191-07:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.14.0-kali1-amd64/misc/vmmon.ko".

2017-12-11T18:19:25.192-07:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-12-11T18:19:25.212-07:00| vthread-1| I125: Successfully extracted the vmmon source.

2017-12-11T18:19:25.212-07:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-e6Ih8t/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-12-11T18:19:28.106-07:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

2017-12-11T18:19:51.716-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:19:51.716-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:19:51.716-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:19:51.716-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:19:51.716-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:19:51.730-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:19:51.730-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:19:51.731-07:00| vthread-1| I125: Using temp dir "/tmp".

2017-12-11T18:19:51.732-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:19:51.732-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:19:51.732-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:19:51.732-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:19:51.732-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:19:51.732-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:19:51.744-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:19:51.744-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:19:51.864-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:19:51.864-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:19:51.885-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:19:51.885-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:19:51.891-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:19:52.642-07:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.14.0-kali1-amd64/misc/vmmon.ko".

2017-12-11T18:19:52.643-07:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-12-11T18:19:52.661-07:00| vthread-1| I125: Successfully extracted the vmmon source.

2017-12-11T18:19:52.661-07:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-3O4uxW/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-12-11T18:19:55.556-07:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

2017-12-11T18:20:17.899-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:20:17.899-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:20:17.899-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:20:17.899-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:20:17.899-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:20:17.911-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:20:17.911-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:20:17.911-07:00| vthread-1| I125: Using temp dir "/tmp".

2017-12-11T18:20:17.913-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:20:17.913-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:20:17.913-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:20:17.913-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:20:17.913-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:20:17.913-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:20:17.925-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:20:17.925-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:20:18.046-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:20:18.046-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:20:18.066-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:20:18.066-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:20:18.073-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:20:18.845-07:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.14.0-kali1-amd64/misc/vmmon.ko".

2017-12-11T18:20:18.846-07:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-12-11T18:20:18.864-07:00| vthread-1| I125: Successfully extracted the vmmon source.

2017-12-11T18:20:18.864-07:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-w1fS9R/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-12-11T18:20:21.771-07:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

2017-12-11T18:22:24.997-07:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-12-11T18:22:24.997-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:22:24.997-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:22:24.998-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:22:24.998-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:22:25.011-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:22:25.011-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:22:25.011-07:00| vthread-1| I125: Using temp dir "/tmp".

2017-12-11T18:22:25.013-07:00| vthread-1| I125: Obtaining info using the running kernel.

2017-12-11T18:22:25.013-07:00| vthread-1| I125: Setting header path for 4.14.0-kali1-amd64 to "/lib/modules/4.14.0-kali1-amd64/build/include".

2017-12-11T18:22:25.013-07:00| vthread-1| I125: Validating path "/lib/modules/4.14.0-kali1-amd64/build/include" for kernel release "4.14.0-kali1-amd64".

2017-12-11T18:22:25.013-07:00| vthread-1| I125: Failed to find /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h

2017-12-11T18:22:25.013-07:00| vthread-1| I125: /lib/modules/4.14.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-12-11T18:22:25.013-07:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2017-12-11T18:22:25.027-07:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.14.0-kali1-amd64".

2017-12-11T18:22:25.027-07:00| vthread-1| I125: The header path "/lib/modules/4.14.0-kali1-amd64/build/include" for the kernel "4.14.0-kali1-amd64" is valid.  Whoohoo!

2017-12-11T18:22:25.148-07:00| vthread-1| I125: found symbol version file /lib/modules/4.14.0-kali1-amd64/build/Module.symvers

2017-12-11T18:22:25.148-07:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.14.0-kali1-amd64/build/Module.symvers.

2017-12-11T18:22:25.168-07:00| vthread-1| I125: Read 19842 symbol versions

2017-12-11T18:22:25.168-07:00| vthread-1| I125: Invoking modinfo on "vmmon".

2017-12-11T18:22:25.176-07:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2017-12-11T18:22:25.959-07:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.14.0-kali1-amd64/misc/vmmon.ko".

2017-12-11T18:22:25.961-07:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-12-11T18:22:25.982-07:00| vthread-1| I125: Successfully extracted the vmmon source.

2017-12-11T18:22:25.982-07:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-nahNAW/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-12-11T18:22:28.927-07:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

So I googled how to fix this problem and none of the fixes worked

This is the log

https://pastebin.com/raw/Thb3eQXW

I was wondering if this has something to do with my computers bios settings? Because I remembered that when I was using an Android Emulator I had to enable virtualization somewhere in the BIOS. Would that be the case here?