Quantcast
Channel: VMware Communities : Discussion List - Workstation Player
Viewing all 4347 articles
Browse latest View live

VM Player 14 not listing VMs after open or creation

$
0
0

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? 


High Sierra boot loop?

$
0
0

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!

VMWare Player crashing on Windows Guest Shutdown

$
0
0

Over the last 10 days or so, for some reason every time I attempt to shutdown or restart Windows (Windows guest - Arch is the host), VMWare immediately freezes and the process cannot be killed to the point I need to do a hard reboot because I can't even shutdown my system cleanly (although my system is totally responsive in every other way before I shutdown with the exception of VMWare) and I get the following showing up when I run dmesg:

 

[ 1954.873606] BUG: unable to handle kernel paging request at ffffffffc057f14e

[ 1954.873651] IP: report_bug+0x94/0x120

[ 1954.873666] PGD 23ba0c067

[ 1954.873666] P4D 23ba0c067

[ 1954.873677] PUD 23ba0e067

[ 1954.873688] PMD 32ed01067

[ 1954.873700] PTE 800000032edf7161

[ 1954.873730] Oops: 0003 [#1] PREEMPT SMP

[ 1954.873744] Modules linked in: dm_mod dax ctr ccm cmac rfcomm vmnet(O) ppdev parport_pc parport fuse vmw_vsock_vmci_transport vsock vmw_vmci vmmon(O) arc4 bnep bbswitch(O) intel_rapl dell_wmi x86_pkg_temp_thermal intel_powerclamp sparse_keymap iTCO_wdt coretemp iTCO_vendor_support kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc dell_laptop dell_smbios dcdbas aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf btusb psmouse btrtl btbcm i915 pcspkr btintel bluetooth i2c_i801 iwlmvm snd_hda_codec_hdmi mac80211 ecdh_generic snd_hda_codec_realtek snd_hda_codec_generic input_leds evdev led_class joydev mousedev mac_hid iwlwifi snd_hda_intel atl1c lpc_ich cfg80211 drm_kms_helper snd_hda_codec uvcvideo videobuf2_vmalloc drm snd_hda_core

[ 1954.873979]  videobuf2_memops snd_hwdep rfkill videobuf2_v4l2 snd_pcm videobuf2_core intel_gtt syscopyarea videodev snd_timer mei_me sysfillrect snd sysimgblt fb_sys_fops media mei soundcore i2c_algo_bit shpchp thermal wmi battery dell_smo8800 video tpm_tis button tpm_tis_core ac tpm sch_fq_codel ip_tables x_tables ext4 crc16 jbd2 fscrypto mbcache sd_mod hid_generic usbhid hid serio_raw atkbd libps2 xhci_pci xhci_hcd ahci libahci libata scsi_mod ehci_pci ehci_hcd usbcore usb_common i8042 serio

[ 1954.874130] CPU: 3 PID: 5334 Comm: vmx-vcpu-0 Tainted: G   O4.12.6-1-ARCH #1

[ 1954.874156] Hardware name: Dell Inc.  Dell System XPS 15Z/0MFNCV, BIOS A12 09/07/2012

[ 1954.874184] task: ffff89daea7a8e40 task.stack: ffffa34688da4000

[ 1954.874204] RIP: 0010:report_bug+0x94/0x120

[ 1954.874219] RSP: 0018:ffffa34688da7b10 EFLAGS: 00010202

[ 1954.874237] RAX: 0000000000000907 RBX: ffffa34688da7c78 RCX: ffffffffc057f144

[ 1954.874260] RDX: 0000000000000001 RSI: 0000000000000ed2 RDI: 0000000000000001

[ 1954.874283] RBP: ffffa34688da7b30 R08: ffffa34688da8000 R09: 000000000000034e

[ 1954.874306] R10: ffffffffa6a06a80 R11: ffff89daea7a8e00 R12: ffffffffc0532e34

[ 1954.874329] R13: ffffffffc0577366 R14: 0000000000000004 R15: ffffa34688da7c78

[ 1954.874353] FS:  00007fb1dd387700(0000) GS:ffff89daffac0000(0000) knlGS:0000000000000000

[ 1954.874379] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

[ 1954.874398] CR2: ffffffffc057f14e CR3: 000000032aea2000 CR4: 00000000000406e0

[ 1954.874421] Call Trace:

[ 1954.874439]  ? ext4_set_page_dirty+0x44/0x60 [ext4]

[ 1954.874459]  fixup_bug+0x2e/0x50

[ 1954.874474]  do_trap+0x119/0x150

[ 1954.874487]  do_error_trap+0x89/0x110

[ 1954.874504]  ? ext4_set_page_dirty+0x44/0x60 [ext4]

[ 1954.874522]  ? __enqueue_entity+0x6c/0x70

[ 1954.874537]  ? enqueue_entity+0x109/0x740

[ 1954.874553]  do_invalid_op+0x20/0x30

[ 1954.874567]  invalid_op+0x1e/0x30

[ 1954.874582] RIP: 0010:ext4_set_page_dirty+0x44/0x60 [ext4]

[ 1954.874600] RSP: 0018:ffffa34688da7d28 EFLAGS: 00010246

[ 1954.874618] RAX: 017fff0000001068 RBX: ffffdee80b6ad200 RCX: 0000000000000000

[ 1954.874642] RDX: 0000000000000000 RSI: 0000000000000041 RDI: ffffdee80b6ad200

[ 1954.874665] RBP: ffffa34688da7d28 R08: ffff89daef2ce240 R09: 0000000180400037

[ 1954.874688] R10: ffffa34688da7d48 R11: ffff89daea7a8e00 R12: 0000000000000041

[ 1954.874711] R13: 0000000000000001 R14: ffff89dace1dc860 R15: 0000000000000000

[ 1954.874745]  set_page_dirty+0x5b/0xb0

[ 1954.874767]  qp_release_pages+0x64/0x80 [vmw_vmci]

[ 1954.874792]  qp_host_unregister_user_memory.isra.20+0x27/0x80 [vmw_vmci]

[ 1954.874825]  vmci_qp_broker_detach+0x245/0x3f0 [vmw_vmci]

[ 1954.874854]  vmci_host_unlocked_ioctl+0x18e/0xa30 [vmw_vmci]

[ 1954.874887]  do_vfs_ioctl+0xa5/0x600

[ 1954.874908]  ? __fget+0x6e/0x90

[ 1954.874927]  SyS_ioctl+0x79/0x90

[ 1954.874947]  entry_SYSCALL_64_fastpath+0x1a/0xa5

[ 1954.874970] RIP: 0033:0x7fb34cf8f8b7

[ 1954.874990] RSP: 002b:00007fb1dd37eb28 EFLAGS: 00003246 ORIG_RAX: 0000000000000010

[ 1954.875029] RAX: ffffffffffffffda RBX: 00007fb1dd386580 RCX: 00007fb34cf8f8b7

[ 1954.875066] RDX: 00007fb1dd37eb40 RSI: 00000000000007aa RDI: 0000000000000065

[ 1954.875106] RBP: 0000000000000006 R08: 0000000000000002 R09: 00007fb1dd37ecd0

[ 1954.875147] R10: 00007fb1dd386bfe R11: 0000000000003246 R12: 00007fb34b8be010

[ 1954.875191] R13: 00000000747ff0ec R14: ffffffffffffffff R15: 0000000000000006

[ 1954.875236] Code: 74 59 0f b7 41 0a 4c 63 69 04 0f b7 71 08 89 c7 49 01 cd 83 e7 01 a8 02 74 15 66 85 ff 74 10 a8 04 ba 01 00 00 00 75 26 83 c8 04 <66> 89 41 0a 66 85 ff 74 49 0f b6 49 0b 4c 89 e2 45 31 c9 49 89

[ 1954.875365] RIP: report_bug+0x94/0x120 RSP: ffffa34688da7b10

[ 1954.876980] CR2: ffffffffc057f14e

[ 1954.886476] ---[ end trace cdf1cc11c1557bdd ]---

I've now tried kernels 4.12.{3,5,6,8}, with VMWare 12.5.6 as well as 12.5.7. The issue also persists with existing and clean installs of Windows 10.

 

I can't think of anything else that's changed, and everything has worked fine for a very long time up to this point.

 

Any ideas as to what might be going on?

VMWare Player 12.5 Install says "Another Install is Running" ??? directly after reboot?

$
0
0

Windows 10 Pro 64 trying to install 12.5.

Says another install is running.

What to do?

Unable to expand vmware ubuntu diskspace, no disk on disk management?

$
0
0

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.

prob_1.PNG

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?

prob_2.PNG

prob_3.PNG

prob_4.PNG

Problem with Workstation Player 14 Kali Linux

$
0
0

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.

VMWare Black Screen

$
0
0

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?

VMware Player 14 Not loading Virtual Machine Even After Confirming It Was Installed

$
0
0

I have 64 bit VMware® Workstation 14 Player version 14.0.0 build-6661328 installed on Linux Mint 18.3 x64. My laptop is a Lenovo Ideapad z510 and I've made sure the virtual machine option in BIOS is enabled. The installation of VMware Player 14 on Mint was successful and VMware Player also opens without issues.

 

Whenever I choose "Create a New Virtual Machine", it lets me go thru all the appropriate steps. It allows me to pick an ISO and goes thru the full installation process without issues. VMware Player confirms that the virtual machine was installed successful and the virtual machine even boots fine after it's done with the initial installation.

 

However, the minute I shutdown the virtual machine, I can no longer open it again. It's not listed in the Home panel either. I've tried using the "Open a Virtual Machine" option, but nothing happens when I choose the vmx file.

 

I get the same symptom when using the ISO file of Kali Linux (kali-linux-2017.3-amd64.iso) and when using the virtual machine version of Kali Linux (kali-linux-2017.3-vm-amd64.ova)

 

Attached is a screen shot of the files found in the vmware folder (I believe these are for kali-linux-2017.3-vm-amd64.ova) . I've also included a screen shot of the empty Home panel.

 

Can someone please help? Don't understand why this is happening if all signs confirmed the virtual machine was installed. Selection_001.pngSelection_002.png


VMs freeze on VMware Player 6.0.3.

$
0
0

I've been having an issue with VMware Player 6.0.3. All my hosts freeze up eventually after a period of time. This seems to happen more often with my Linux VM as opposed to my windows VM. Both are getting very annoying.

I've tried adjusting memory and usage but all that doesn't seem to work.

My only temporary workaround is pausing the VMs and running them again. Graphics performance is poor afterwards.

Anyone experience anything like this?

Failed to import "Windows XP Mode".

$
0
0

0down vote  favorite  

 

Im having trouble when importing Windows XP Mode.

 

When I click "Import Windows XP Mode VM" then click Import, it says "Failed to import Windows XP Mode" with no following explanation.

 

My Windows XP Mode has been installed correctly and I've also tried to reinstall the vmware-player but nothing changes.

 

Im running on 64 bit Win7 Ultimate

NAT/Bridge settings missing from VM settings

$
0
0

They used to be in the vm properties, and I can't seem to find them anywhere.

Win7 VM's (if that's of any relevance)

Workstation 12

ESXi 6.0

VMware Player unrecoverable error: (vcpu-0)

$
0
0

/Hi, can anybody help me to solve this?

 

I have tried different versions, the errors are the same:

 

VMware Player unrecoverable error: (vcpu-0)  vcpu-0:VERIFY vmcore/vmm/main/cpuid.c:382 bugNr=1036521  A log file is available in "C:\Users\run20\Documents\Virtual Machines\Oracle11g\vmware.log". 

Only first left mouse is registered on VMware player 14.

$
0
0

When I run a VM in VMWare Player 14, it is only able to register the first left mouse click. After that i need to keep pressing Ctrl+Alt and then clicking twice to register a single left click before repeating it again to get another left click. I have tried adding vmmouse.present = "FALSE" to the vmx file but it does not help.

 

My guest OS is Windows Server 2012.

Black screen after login to Ubuntu

$
0
0

I am working on a Windows 10 host system with Workstation Player 14 and the guest system is Ubuntu 17.04

 

After I login to my Ubuntu session, the screen gets black and that's it, i can't perform any other actions.

 

Help would be really appreciated, I can't get my school work done on Windows

 

Thank you and have a nice day

Windows 10 + Device/Confidential Guard

$
0
0

Having tried to run VMWare Player under Windows 10 I was redirected to this article: VMware Knowledge Base Powering on a vm in VMware Workstation on Windows 10 host where Credential Guard/Device Guard is enabled fails with BSOD (2146361)

 

I disabled the Group Policy setting as outlined and turned off Hyper-V (steps 1, 2 and 3 in the article.)

 

I opened a command prompt but when I entered 'mountvol x: /s' I get 'The parameter is incorrect'. I've tried different drive letters in substituttion of 'x' but with the same result.

 

Can anyone provide a solution?

 

Thanks


Issue Network-Editor WS-Player 12.5.8+14.0 under Win 10-1709 (Creators Fall)

$
0
0

I found a problem using the Player on Windows 10-1709 (Creators Fall).
Trying Player V12.5.8 and the V14.0, the network interface no longer works (see Attach)
I often got the same Issue with VMware Player's the past few years.
In any case, the solution was an update by VMware.
Solution: I turned back to Windows 10-1703 (Creators), waiting for V14.0.1.

Resolution keeps reseting itself

$
0
0

how can i keep a specific resolution in the host?

i noticed 2 things:

1) if 3D accelaration is not enabled, the resolution keeps resetting to 640x480

2) if it is enabled, it keeps resetting the resolution to 'fit screen' (even if the "auto fit" is not selected!)

 

3) how can i set a permanent resolution?

Windows 10 Guest Activation Troubleshooting (Linux Host)

$
0
0

Windows 10 was activated when I first installed it in the Virtual Machine and installed the VMware Tools, but now only a couple-few days after the installation it is not activated. I tried uninstalling and reinstalling the VMware Tools and it still will not reactivate. I tried repairing the VMware Tools installation and get an error during the install. Please note that this is a copy of Windows 10 that was obtained for free a year or two ago when Microsoft was allowing users of Windows 7 or 8 to upgrade to Windows 10 for free, and was already previously activated on this same physical machine as a host operating system, but I have now decided to switch over and run Windows as a guest operating system under Linux Mint as the host. I shouldn't need a product key to activate this copy of Windows 10, I would think, but I'm not sure what to do in this situation, and I am looking for help from the VMware community before I even consider contacting Microsoft for help. What are the likely causes of this problem and what might be a solution? Please help! Thank you for your time and attention.

All VMs Start with Black Screen

$
0
0

Recently moved all my VMs from Host Win7-64bit to Win8-64bit.

Fresh install of Player v 5.0.2 build-1031769

Computer is Acer Aspire M Intel i5 @ 1.8Ghz

Graphics is Intel HD 4000

 

When any of the various VMs are started from the Powered Off state, the player window will open and a big black screen will appear where the guest display should be shown. The guest OS does indeed boot, right up to the login screen although with no display visible. If I try to click on the close button in the upper right corner, I get a dialog box that says "The Virtual Machine is Busy". My only option is to end the vmplayer.exe task using task manager. Once I do that, the VM shows state as Powered On in the Library. If I Play it the 2nd time, the VM will resume operating correctly with the proper display at the immediate point where I expected it to be when I ended the vmplayer.exe task earlier.

Presence or absence of Tools in Guest does not affect the problem.

 

All 3 of my VMs have the exact same behavior. Guest operating Systems are: WinXP-SP3-32bit, Win7-64bit built from the VMware Converter, and Server 2008 from the MS eval ISO.

 

Any ideas? Once the play/end task/play sequence is performed the VM works correctly. Until it is shutdown or hibernated. A VM restart does not exhibit this symptom. The problem is reproducible with all VMs every time.

 

Provided vmx for the XP VM and a few logs.

Thanks in advance. I'm so close to having this work it's even more frustrating than if it didn't work at all.

Where to find Windows 7

$
0
0

Hello all,

 

I apologize if this question has already been covered, I’m new to vmware and I haven’t installed it yet.  I would like to use VMware player to run windows 7 on my computer that has windows 10. My trouble (so far) has been locating a Windows 7 iso file to download. I would like to ask if anyone knows where to obtain this? I want to do everything legal and I’ve been running in circles trying to learn if I need an OEM or a retail version. It sounds like a retail version would be great but I can’t find one.

 

I sincerely thank anyone that might be able to help me with this problem.

 

Thank you,

Viewing all 4347 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>