Sinn3rman Posted June 24, 2015 Share Posted June 24, 2015 HI guys, Im going to make a cry for help. I just cannot get VMware player working on kali so I can run some labs I have looked deep online but the suggestions are just not working for me or im not really comprehending them. I was hoping someone here might have been thru this and would be able to offer some advise. Below is my log file. Its late and I need sleep so my apologies in advance and replys will follow. Im really struggling to understand whats actually going on here :| 2015-06-24T22:03:22.720+08:00| vthread-3| I120: Log for VMware Workstation pid=10638 version=9.0.4 build=build-1945795 option=Release2015-06-24T22:03:22.720+08:00| vthread-3| I120: The process is 64-bit.2015-06-24T22:03:22.720+08:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-82015-06-24T22:03:22.720+08:00| vthread-3| I120: Host is Linux 3.18.0-kali3-amd64 Kali GNU/Linux 1.1.02015-06-24T22:03:22.719+08:00| vthread-3| I120: Msg_Reset:2015-06-24T22:03:22.719+08:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.2015-06-24T22:03:22.719+08:00| vthread-3| I120: ----------------------------------------2015-06-24T22:03:22.719+08:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.2015-06-24T22:03:22.720+08:00| vthread-3| I120: Msg_Reset:2015-06-24T22:03:22.720+08:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.2015-06-24T22:03:22.720+08:00| vthread-3| I120: ----------------------------------------2015-06-24T22:03:22.720+08:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.2015-06-24T22:03:22.720+08:00| vthread-3| I120: Msg_Reset:2015-06-24T22:03:22.720+08:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.2015-06-24T22:03:22.720+08:00| vthread-3| I120: ----------------------------------------2015-06-24T22:03:22.720+08:00| vthread-3| I120: PREF Failed to load user preferences.2015-06-24T22:03:22.720+08:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-10638.log2015-06-24T22:03:22.778+08:00| vthread-3| I120: Obtaining info using the running kernel.2015-06-24T22:03:22.778+08:00| vthread-3| I120: Setting header path for 3.18.0-kali3-amd64 to "/lib/modules/3.18.0-kali3-amd64/build/include".2015-06-24T22:03:22.778+08:00| vthread-3| I120: Validating path "/lib/modules/3.18.0-kali3-amd64/build/include" for kernel release "3.18.0-kali3-amd64".2015-06-24T22:03:22.778+08:00| vthread-3| I120: Failed to find /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h2015-06-24T22:03:22.778+08:00| vthread-3| I120: /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.2015-06-24T22:03:22.778+08:00| vthread-3| I120: Created new pathsHash.2015-06-24T22:03:22.782+08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.18.0-kali3-amd64".2015-06-24T22:03:22.782+08:00| vthread-3| I120: The header path "/lib/modules/3.18.0-kali3-amd64/build/include" for the kernel "3.18.0-kali3-amd64" is valid. Whoohoo!2015-06-24T22:03:22.825+08:00| vthread-3| I120: Reading in info for the vmmon module.2015-06-24T22:03:22.825+08:00| vthread-3| I120: Reading in info for the vmnet module.2015-06-24T22:03:22.825+08:00| vthread-3| I120: Reading in info for the vmblock module.2015-06-24T22:03:22.825+08:00| vthread-3| I120: Reading in info for the vmci module.2015-06-24T22:03:22.825+08:00| vthread-3| I120: Reading in info for the vsock module.2015-06-24T22:03:22.825+08:00| vthread-3| I120: Setting vsock to depend on vmci.2015-06-24T22:03:22.825+08:00| vthread-3| I120: Invoking modinfo on "vmmon".2015-06-24T22:03:22.826+08:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.2015-06-24T22:03:22.826+08:00| vthread-3| I120: Invoking modinfo on "vmnet".2015-06-24T22:03:22.827+08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.2015-06-24T22:03:22.827+08:00| vthread-3| I120: Invoking modinfo on "vmblock".2015-06-24T22:03:22.828+08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.2015-06-24T22:03:22.828+08:00| vthread-3| I120: Invoking modinfo on "vmci".2015-06-24T22:03:22.829+08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.2015-06-24T22:03:22.829+08:00| vthread-3| I120: Invoking modinfo on "vsock".2015-06-24T22:03:22.830+08:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.2015-06-24T22:03:22.838+08:00| vthread-3| I120: to be installed: vmnet status: 02015-06-24T22:03:22.843+08:00| vthread-3| I120: Obtaining info using the running kernel.2015-06-24T22:03:22.843+08:00| vthread-3| I120: Setting header path for 3.18.0-kali3-amd64 to "/lib/modules/3.18.0-kali3-amd64/build/include".2015-06-24T22:03:22.843+08:00| vthread-3| I120: Validating path "/lib/modules/3.18.0-kali3-amd64/build/include" for kernel release "3.18.0-kali3-amd64".2015-06-24T22:03:22.843+08:00| vthread-3| I120: Failed to find /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h2015-06-24T22:03:22.843+08:00| vthread-3| I120: /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.2015-06-24T22:03:22.847+08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.18.0-kali3-amd64".2015-06-24T22:03:22.847+08:00| vthread-3| I120: The header path "/lib/modules/3.18.0-kali3-amd64/build/include" for the kernel "3.18.0-kali3-amd64" is valid. Whoohoo!2015-06-24T22:03:22.890+08:00| vthread-3| I120: Kernel header path retrieved from FileEntry: /lib/modules/3.18.0-kali3-amd64/build/include2015-06-24T22:03:22.890+08:00| vthread-3| I120: Update kernel header path to /lib/modules/3.18.0-kali3-amd64/build/include2015-06-24T22:03:22.890+08:00| vthread-3| I120: Validating path "/lib/modules/3.18.0-kali3-amd64/build/include" for kernel release "3.18.0-kali3-amd64".2015-06-24T22:03:22.890+08:00| vthread-3| I120: Failed to find /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h2015-06-24T22:03:22.890+08:00| vthread-3| I120: /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.2015-06-24T22:03:22.894+08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.18.0-kali3-amd64".2015-06-24T22:03:22.894+08:00| vthread-3| I120: The header path "/lib/modules/3.18.0-kali3-amd64/build/include" for the kernel "3.18.0-kali3-amd64" is valid. Whoohoo!2015-06-24T22:03:22.895+08:00| vthread-3| I120: Found compiler at "/usr/bin/gcc"2015-06-24T22:03:22.897+08:00| vthread-3| I120: Got gcc version "4.7".2015-06-24T22:03:22.897+08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.2015-06-24T22:03:22.897+08:00| vthread-3| I120: Using user supplied compiler "/usr/bin/gcc".2015-06-24T22:03:22.898+08:00| vthread-3| I120: Got gcc version "4.7".2015-06-24T22:03:22.898+08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.2015-06-24T22:03:22.901+08:00| vthread-3| I120: Trying to find a suitable PBM set for kernel "3.18.0-kali3-amd64".2015-06-24T22:03:22.901+08:00| vthread-3| I120: No matching PBM set was found for kernel "3.18.0-kali3-amd64".2015-06-24T22:03:22.901+08:00| vthread-3| I120: Validating path "/lib/modules/3.18.0-kali3-amd64/build/include" for kernel release "3.18.0-kali3-amd64".2015-06-24T22:03:22.901+08:00| vthread-3| I120: Failed to find /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h2015-06-24T22:03:22.901+08:00| vthread-3| I120: /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.2015-06-24T22:03:22.904+08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.18.0-kali3-amd64".2015-06-24T22:03:22.905+08:00| vthread-3| I120: The header path "/lib/modules/3.18.0-kali3-amd64/build/include" for the kernel "3.18.0-kali3-amd64" is valid. Whoohoo!2015-06-24T22:03:22.905+08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.2015-06-24T22:03:22.905+08:00| vthread-3| I120: Validating path "/lib/modules/3.18.0-kali3-amd64/build/include" for kernel release "3.18.0-kali3-amd64".2015-06-24T22:03:22.905+08:00| vthread-3| I120: Failed to find /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h2015-06-24T22:03:22.905+08:00| vthread-3| I120: /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.2015-06-24T22:03:22.909+08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.18.0-kali3-amd64".2015-06-24T22:03:22.909+08:00| vthread-3| I120: The header path "/lib/modules/3.18.0-kali3-amd64/build/include" for the kernel "3.18.0-kali3-amd64" is valid. Whoohoo!2015-06-24T22:03:22.909+08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.2015-06-24T22:03:22.909+08:00| vthread-3| I120: Using temp dir "/tmp".2015-06-24T22:03:22.910+08:00| vthread-3| I120: Obtaining info using the running kernel.2015-06-24T22:03:22.910+08:00| vthread-3| I120: Setting header path for 3.18.0-kali3-amd64 to "/lib/modules/3.18.0-kali3-amd64/build/include".2015-06-24T22:03:22.910+08:00| vthread-3| I120: Validating path "/lib/modules/3.18.0-kali3-amd64/build/include" for kernel release "3.18.0-kali3-amd64".2015-06-24T22:03:22.910+08:00| vthread-3| I120: Failed to find /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h2015-06-24T22:03:22.910+08:00| vthread-3| I120: /lib/modules/3.18.0-kali3-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.2015-06-24T22:03:22.913+08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.18.0-kali3-amd64".2015-06-24T22:03:22.914+08:00| vthread-3| I120: The header path "/lib/modules/3.18.0-kali3-amd64/build/include" for the kernel "3.18.0-kali3-amd64" is valid. Whoohoo!2015-06-24T22:03:22.956+08:00| vthread-3| I120: Invoking modinfo on "vmnet".2015-06-24T22:03:22.957+08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.2015-06-24T22:03:23.158+08:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/3.18.0-kali3-amd64/misc/vmnet.ko".2015-06-24T22:03:23.158+08:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".2015-06-24T22:03:23.161+08:00| vthread-3| I120: Successfully extracted the vmnet source.2015-06-24T22:03:23.161+08:00| vthread-3| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-LVWyaz/vmnet-only auto-build HEADER_DIR=/lib/modules/3.18.0-kali3-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"2015-06-24T22:03:24.099+08:00| vthread-3| W110: Failed to build vmnet. Failed to execute the build command. Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted June 24, 2015 Share Posted June 24, 2015 I don't know how to solve your issue, but you should REALLY choose a different host OS than Kali linux. Best Regards, Sebkinne Quote Link to comment Share on other sites More sharing options...
Sinn3rman Posted June 25, 2015 Author Share Posted June 25, 2015 Hi Seb ! My intent is to attack a kali vm using the tools in Kali but i am thinking i misunderstood the instructions so i think i may just install it on another boz i have lying around Quote Link to comment Share on other sites More sharing options...
cooper Posted June 25, 2015 Share Posted June 25, 2015 Sounds like you need to pick a "mere mortals" Linux and install vmware on that. Create 2 VMs, install Kali on both and then use the one to attack the other. Quote Link to comment Share on other sites More sharing options...
Sinn3rman Posted June 25, 2015 Author Share Posted June 25, 2015 Yep, was no problem on Xubuntu, heh, see sometimes you just need the input of your peers to re-think the plan. VM to VM - DUH Quote Link to comment Share on other sites More sharing options...
barry99705 Posted June 25, 2015 Share Posted June 25, 2015 Did you apt-get vmware or install it from vmware? I run player a few times a week in kali with no issues. I did find that when kali updates the kernel, player can't upgrade it's kernel extensions. It doesn't know what kali linux is, so you just have to reinstall player over and it works after that. Quote Link to comment Share on other sites More sharing options...
Sinn3rman Posted June 26, 2015 Author Share Posted June 26, 2015 Hi Barry, cant recall now, however I am now up and running as per Coopers suggested method. I know metasploitable is flawed by design but holy ... i did not think it would be so easy just starting off with rlogin and WTF is up with NFS that is dangerous :) im going to have to research how to secure that. Seems far far far too easy. I think I will setup a stock install of ubuntu on a box and see if I have as much luck. I am soo bitten by the bug right now. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.