VMWare Help

[Exmix]

When I try to install VMWare Workstation 12, it tells me it can't find a compatable GCC Version, so I point it to my gcc-6 in /usr/bin/ folder since it's looking for gcc 6.4.0. So it goes to install it but fails ar the "Virtual Network Device", so it fails at starting the service.

I try and run it through command line and I get this:

:~# /etc/init.d/vmware restart Stopping VMware services: VMware Authentication Daemon done VM communication interface socket family done Virtual machine communication interface done Virtual machine monitor done Blocking file system done Starting VMware services: Virtual machine monitor done Virtual machine communication interface done VM communication interface socket family done Blocking file system done Virtual ethernet failed VMware Authentication Daemon done

Here is the log file it gives me when it fails:

2017-10-11T23:22:51.459-04:00| vthread-4| I125: Log for VMware Workstation pid=1815 version=12.5.7 build=build-5813279 option=Release 2017-10-11T23:22:51.459-04:00| vthread-4| I125: The process is 64-bit. 2017-10-11T23:22:51.459-04:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8 2017-10-11T23:22:51.459-04:00| vthread-4| I125: Host is Linux 4.13.0-kali1-amd64 Kali GNU/Linux Rolling 2017-10-11T23:22:51.424-04:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory. 2017-10-11T23:22:51.424-04:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values. 2017-10-11T23:22:51.434-04:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory. 2017-10-11T23:22:51.434-04:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values. 2017-10-11T23:22:51.517-04:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-1815.log 2017-10-11T23:22:51.616-04:00| vthread-4| I125: Obtaining info using the running kernel. 2017-10-11T23:22:51.616-04:00| vthread-4| I125: Created new pathsHash. 2017-10-11T23:22:51.616-04:00| vthread-4| I125: Setting header path for 4.13.0-kali1-amd64 to "/lib/modules/4.13.0-kali1-amd64/build/include". 2017-10-11T23:22:51.616-04:00| vthread-4| I125: Validating path "/lib/modules/4.13.0-kali1-amd64/build/include" for kernel release "4.13.0-kali1-amd64". 2017-10-11T23:22:51.616-04:00| vthread-4| I125: Failed to find /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h 2017-10-11T23:22:51.616-04:00| vthread-4| I125: /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2017-10-11T23:22:51.616-04:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2017-10-11T23:22:51.621-04:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.13.0-kali1-amd64". 2017-10-11T23:22:51.621-04:00| vthread-4| I125: The header path "/lib/modules/4.13.0-kali1-amd64/build/include" for the kernel "4.13.0-kali1-amd64" is valid. Whoohoo! 2017-10-11T23:22:51.733-04:00| vthread-4| I125: found symbol version file /lib/modules/4.13.0-kali1-amd64/build/Module.symvers 2017-10-11T23:22:51.733-04:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.13.0-kali1-amd64/build/Module.symvers. 2017-10-11T23:22:51.748-04:00| vthread-4| I125: Read 19660 symbol versions 2017-10-11T23:22:51.748-04:00| vthread-4| I125: Reading in info for the vmmon module. 2017-10-11T23:22:51.748-04:00| vthread-4| I125: Reading in info for the vmnet module. 2017-10-11T23:22:51.748-04:00| vthread-4| I125: Reading in info for the vmblock module. 2017-10-11T23:22:51.748-04:00| vthread-4| I125: Reading in info for the vmci module. 2017-10-11T23:22:51.748-04:00| vthread-4| I125: Reading in info for the vsock module. 2017-10-11T23:22:51.748-04:00| vthread-4| I125: Setting vsock to depend on vmci. 2017-10-11T23:22:51.748-04:00| vthread-4| I125: Invoking modinfo on "vmmon". 2017-10-11T23:22:51.749-04:00| vthread-4| I125: "/sbin/modinfo" exited with status 0. 2017-10-11T23:22:51.749-04:00| vthread-4| I125: Invoking modinfo on "vmnet". 2017-10-11T23:22:51.750-04:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2017-10-11T23:22:51.750-04:00| vthread-4| I125: Invoking modinfo on "vmblock". 2017-10-11T23:22:51.752-04:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2017-10-11T23:22:51.752-04:00| vthread-4| I125: Invoking modinfo on "vmci". 2017-10-11T23:22:51.753-04:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2017-10-11T23:22:51.753-04:00| vthread-4| I125: Invoking modinfo on "vsock". 2017-10-11T23:22:51.754-04:00| vthread-4| I125: "/sbin/modinfo" exited with status 0. 2017-10-11T23:22:51.762-04:00| vthread-4| I125: to be installed: vmnet status: 0 2017-10-11T23:22:51.869-04:00| vthread-4| I125: Obtaining info using the running kernel. 2017-10-11T23:22:51.869-04:00| vthread-4| I125: Setting header path for 4.13.0-kali1-amd64 to "/lib/modules/4.13.0-kali1-amd64/build/include". 2017-10-11T23:22:51.869-04:00| vthread-4| I125: Validating path "/lib/modules/4.13.0-kali1-amd64/build/include" for kernel release "4.13.0-kali1-amd64". 2017-10-11T23:22:51.869-04:00| vthread-4| I125: Failed to find /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h 2017-10-11T23:22:51.869-04:00| vthread-4| I125: /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2017-10-11T23:22:51.869-04:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2017-10-11T23:22:51.884-04:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.13.0-kali1-amd64". 2017-10-11T23:22:51.884-04:00| vthread-4| I125: The header path "/lib/modules/4.13.0-kali1-amd64/build/include" for the kernel "4.13.0-kali1-amd64" is valid. Whoohoo! 2017-10-11T23:22:52.014-04:00| vthread-4| I125: found symbol version file /lib/modules/4.13.0-kali1-amd64/build/Module.symvers 2017-10-11T23:22:52.014-04:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.13.0-kali1-amd64/build/Module.symvers. 2017-10-11T23:22:52.028-04:00| vthread-4| I125: Read 19660 symbol versions 2017-10-11T23:22:52.028-04:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.13.0-kali1-amd64/build/include 2017-10-11T23:22:52.028-04:00| vthread-4| I125: Update kernel header path to /lib/modules/4.13.0-kali1-amd64/build/include 2017-10-11T23:22:52.028-04:00| vthread-4| I125: Validating path "/lib/modules/4.13.0-kali1-amd64/build/include" for kernel release "4.13.0-kali1-amd64". 2017-10-11T23:22:52.028-04:00| vthread-4| I125: Failed to find /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h 2017-10-11T23:22:52.028-04:00| vthread-4| I125: /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2017-10-11T23:22:52.028-04:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2017-10-11T23:22:52.033-04:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.13.0-kali1-amd64". 2017-10-11T23:22:52.033-04:00| vthread-4| I125: The header path "/lib/modules/4.13.0-kali1-amd64/build/include" for the kernel "4.13.0-kali1-amd64" is valid. Whoohoo! 2017-10-11T23:22:52.034-04:00| vthread-4| I125: Found compiler at "/usr/bin/gcc" 2017-10-11T23:22:52.036-04:00| vthread-4| I125: Got gcc version "7". 2017-10-11T23:22:52.036-04:00| vthread-4| I125: Unable to parse gcc version 2017-10-11T23:22:52.036-04:00| vthread-4| I125: User supplied gcc at "" is not executable. 2017-10-11T23:22:52.037-04:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.13.0-kali1-amd64". 2017-10-11T23:22:52.037-04:00| vthread-4| I125: No matching PBM set was found for kernel "4.13.0-kali1-amd64". 2017-10-11T23:23:48.213-04:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc-6". 2017-10-11T23:23:48.277-04:00| vthread-4| I125: Got gcc version "6.4.0". 2017-10-11T23:23:48.277-04:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2017-10-11T23:23:49.438-04:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2017-10-11T23:23:49.438-04:00| vthread-4| I125: Validating path "/lib/modules/4.13.0-kali1-amd64/build/include" for kernel release "4.13.0-kali1-amd64". 2017-10-11T23:23:49.438-04:00| vthread-4| I125: Failed to find /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h 2017-10-11T23:23:49.438-04:00| vthread-4| I125: /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2017-10-11T23:23:49.439-04:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2017-10-11T23:23:49.451-04:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.13.0-kali1-amd64". 2017-10-11T23:23:49.451-04:00| vthread-4| I125: The header path "/lib/modules/4.13.0-kali1-amd64/build/include" for the kernel "4.13.0-kali1-amd64" is valid. Whoohoo! 2017-10-11T23:23:49.451-04:00| vthread-4| I125: Using temp dir "/tmp". 2017-10-11T23:23:49.452-04:00| vthread-4| I125: Obtaining info using the running kernel. 2017-10-11T23:23:49.452-04:00| vthread-4| I125: Setting header path for 4.13.0-kali1-amd64 to "/lib/modules/4.13.0-kali1-amd64/build/include". 2017-10-11T23:23:49.452-04:00| vthread-4| I125: Validating path "/lib/modules/4.13.0-kali1-amd64/build/include" for kernel release "4.13.0-kali1-amd64". 2017-10-11T23:23:49.452-04:00| vthread-4| I125: Failed to find /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h 2017-10-11T23:23:49.452-04:00| vthread-4| I125: /lib/modules/4.13.0-kali1-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2017-10-11T23:23:49.452-04:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2017-10-11T23:23:49.457-04:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.13.0-kali1-amd64". 2017-10-11T23:23:49.457-04:00| vthread-4| I125: The header path "/lib/modules/4.13.0-kali1-amd64/build/include" for the kernel "4.13.0-kali1-amd64" is valid. Whoohoo! 2017-10-11T23:23:49.571-04:00| vthread-4| I125: found symbol version file /lib/modules/4.13.0-kali1-amd64/build/Module.symvers 2017-10-11T23:23:49.571-04:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.13.0-kali1-amd64/build/Module.symvers. 2017-10-11T23:23:49.587-04:00| vthread-4| I125: Read 19660 symbol versions 2017-10-11T23:23:49.587-04:00| vthread-4| I125: Invoking modinfo on "vmnet". 2017-10-11T23:23:49.588-04:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2017-10-11T23:23:50.289-04:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.13.0-kali1-amd64/misc/vmnet.ko". 2017-10-11T23:23:50.320-04:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar". 2017-10-11T23:23:50.370-04:00| vthread-4| I125: Successfully extracted the vmnet source. 2017-10-11T23:23:50.370-04:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-hWKzWP/vmnet-only auto-build HEADER_DIR=/lib/modules/4.13.0-kali1-amd64/build/include CC=/usr/bin/gcc-6 IS_GCC_3=no" 2017-10-11T23:23:59.356-04:00| vthread-4| W115: Failed to build vmnet. Failed to execute the build command.

[Bob123]

You got a lot there and I'll try to read through it shortly but forgive me is Kali 4.13 the latest?  And workstation 12 came from where?  Right from VMware's site?  Let me see if I can repeat this on my system.  Thanks.

[Exmix]

4 hours ago, Bob123 said:

You got a lot there and I'll try to read through it shortly but forgive me is Kali 4.13 the latest?  And workstation 12 came from where?  Right from VMware's site?  Let me see if I can repeat this on my system.  Thanks.

Yeah, latest Kali version and VMWare 12 came from their site, I'd upgrade to 14 but I don't have a Key for that, the only key I have is for VMWare WOrkstation 12 from my college. xD

Edited October 15, 2017 by Exmix

[Dave-ee Jones]

 

2 hours ago, Exmix said:

the only key I have is for VMWare WOrkstation 12 from my college. xD

VMware WS12 is free though..?

[Exmix]

Just now, Dave-ee Jones said:

 

VMware WS12 is free though..?

It might be now since 14 came out but when I got the key a few months ago it wasn't. But the key isn't the issue. xD Even when using VMWare Player I still get the same errors. I can't install the Virtual Network Device. or it doesn't start. So it fails to start the service.

[Bob123]

Ok so I tried this on a physical machine with the newest (2017.2) of Kali (which ran awful for some reason) and you are correct it barks at gcc. 

To continue testing I tried it on Ubuntu and 12.5.7 of workstation runs just fine without issue.  I did notice that Ubuntu uses gcc 5 where as Kali uses gcc 7.  Maybe we need to install 5?  I'm going to try a few other distros just see if there is something else I'm missing.  I'll even try older versions of Kali and see if they have any better luck.  I'll keep you posted.

[Bob123]

I think I got it.  So you changed your /usr/bin/gcc pointer to point to version 6 rather than version 7?  I can walk you through that if you haven't but then you need to run:

sudo apt-get install build-essential linux-headers-$(uname -r)

Probably without the sudo since it's Kali.  After that VMware workstation installed like a champ and opened up.  Granted I did all of this testing in VMs but I believe it should work on a physical box too.  I can check tonight and let you know of the results.  I had no issues setting up workstation in Ubuntu and all I had to do in Parrot was change the gcc pointer. 

Two websites I used to figure it out:

 

https://askubuntu.com/questions/26498/choose-gcc-and-g-version

https://askubuntu.com/questions/40979/what-is-the-path-to-the-kernel-headers-so-i-can-install-vmware

 

[Exmix]

20 minutes ago, Bob123 said:

I think I got it.  So you changed your /usr/bin/gcc pointer to point to version 6 rather than version 7?  I can walk you through that if you haven't but then you need to run:

sudo apt-get install build-essential linux-headers-$(uname -r)

Probably without the sudo since it's Kali.  After that VMware workstation installed like a champ and opened up.  Granted I did all of this testing in VMs but I believe it should work on a physical box too.  I can check tonight and let you know of the results.  I had no issues setting up workstation in Ubuntu and all I had to do in Parrot was change the gcc pointer. 

Two websites I used to figure it out:

 

https://askubuntu.com/questions/26498/choose-gcc-and-g-version

https://askubuntu.com/questions/40979/what-is-the-path-to-the-kernel-headers-so-i-can-install-vmware

 

I have ran that command before because if I don't it tells asks e for something about the Kernel Firmware I think, I don't remember exactly what it asks for. The only reason I have it point to gcc-6 is because it says it's lookbng for gcc version 6.4.0, I haven tried making it point ti gcc-7, i'll try that here soon and post back with results.

[Bob123]

Maybe there's more to it that I'm missing.  In my virgin Kali vm all I did was change gcc to point to 6.  It points to 7 by default.  Then it complained about missing Linux headers so I ran the command above which grabbed the latest headers.  Then typed 'vmware' again and it took off, installing the four items before opening allowing me to run the software.  And looking at ifconfig it shows the two virtual adapters.  So on my VM it appears to be working fine.  I'll try everything I did above on my physical machine this evening and report back.  Keep in mind everything I'm using is virgin with no changes except for the ones above.  I've found that Linux tends to evolve after a person uses it for a while so sometimes a fix on one machine doesn't necessarily fix it on another.

[digip]

What version of Kali are you running and is VMware for the specific version you are running? Example, if you're on an ARM device, this is more than likely not going to work unless for the i386/AMD64 versions. Not having the proper linux headers could also cause it, as Bob123 pointed out. Not sure a GCC version makes a difference unless libraries it needed were deprecated/removed and not in the latest, which the older should fix if that is the case.

 

[Exmix]

29 minutes ago, Bob123 said:

Maybe there's more to it that I'm missing.  In my virgin Kali vm all I did was change gcc to point to 6.  It points to 7 by default.  Then it complained about missing Linux headers so I ran the command above which grabbed the latest headers.  Then typed 'vmware' again and it took off, installing the four items before opening allowing me to run the software.  And looking at ifconfig it shows the two virtual adapters.  So on my VM it appears to be working fine.  I'll try everything I did above on my physical machine this evening and report back.  Keep in mind everything I'm using is virgin with no changes except for the ones above.  I've found that Linux tends to evolve after a person uses it for a while so sometimes a fix on one machine doesn't necessarily fix it on another.

This is what I use to do when I had issues but now it's not doing it for me. It always fails.

 

9 minutes ago, digip said:

What version of Kali are you running and is VMware for the specific version you are running? Example, if you're on an ARM device, this is more than likely not going to work unless for the i386/AMD64 versions. Not having the proper linux headers could also cause it, as Bob123 pointed out. Not sure a GCC version makes a difference unless libraries it needed were deprecated/removed and not in the latest, which the older should fix if that is the case.

 

I'm running the latest Kali I got from the ISO from their Website. Kali-rolling I think is what it's called, as far I am aware of the VMWare isn't specific. It was running before with no issues then one day after I updated my system with the "apt-get update" and "apt-get upgrade" command, it stopped working. GCC does make a difference since if I poit it to gcc-5 or gcc-7 it tells me it's imcompatable.

[Bob123]

See that's interesting that you got it to work by typing /usr/bin/gcc-6.  It didn't like that when I typed that in.  gcc by itself when doing a "ls -l gcc" says gcc -> gcc-7 which means the pointer /usr/bin/gcc is actually pointing to /usr/bin/gcc-7 which workstation doesn't like. 

If you haven't done this before I would give word of caution that again everything I've done is purely in a virtual environment which I just toss when done.  If this is your main pc then you may mess things up but I typed: 

rm /usr/bin/gcc

then

ln -s /usr/bin/gcc-6 /usr/bin/gcc

then check it again with ls -l gcc to see if it now says gcc -> gcc-6 and it should be green.  If it's red then apt-get install gcc6.

Then when you run VMware and it asks about gcc you can just type /usr/bin/gcc and it knows you mean gcc-6.  As long as you did that, and grabbed the headers then I would think you would be good to go. 

From the screen shots above you have an issue that I haven't run into.  So with that said you have the latest kali iso and all you have done is an update/upgrade?  If so I'll give that a try and report back. (Personally I'm not an updater/upgrader but that's just me.)

[digip]

You can check with "dpkg -l | grep gcc| grep compiler" which will show gcc, gcc-5, gcc-6 and gcc-7, etc

Sounds like the GCC version it wants in Vmware is hard coded for a specific path/version? I could be wrong, but pointing it to the correct path(s) might be the fix.

Make sure it's fully updated too, then reboot and try again. apt update, apt upgrade, apt dist-upgrade, reboot, then try again with the install. If you need GCC-5, it should already be installed as well though, see the grep command above, you should have all of them installed already, so something in the install script might be pointing to the wrong place.

 

[digip]

4 minutes ago, Bob123 said:

See that's interesting that you got it to work by typing /usr/bin/gcc-6.  It didn't like that when I typed that in.  gcc by itself when doing a "ls -l gcc" says gcc -> gcc-7 which means the pointer /usr/bin/gcc is actually pointing to /usr/bin/gcc-7 which workstation doesn't like. 

If you haven't done this before I would give word of caution that again everything I've done is purely in a virtual environment which I just toss when done.  If this is your main pc then you may mess things up but I typed: 

rm /usr/bin/gcc

then

ln -s /usr/bin/gcc-6 /usr/bin/gcc

then check it again with ls -l gcc to see if it now says gcc -> gcc-6 and it should be green.  If it's red then apt-get install gcc6.

Then when you run VMware and it asks about gcc you can just type /usr/bin/gcc and it knows you mean gcc-6.  As long as you did that, and grabbed the headers then I would think you would be good to go. 

From the screen shots above you have an issue that I haven't run into.  So with that said you have the latest kali iso and all you have done is an update/upgrade?  If so I'll give that a try and report back. (Personally I'm not an updater/upgrader but that's just me.)

Um, don't remove gcc. Just use the WHOLE path to the version you want to run against, ie:

/usr/bin/gcc-5 somecode.c

I also wouldn't change the default hard links. you can probably edit the install script to point to the correct GCC version it wants, or, just edit it so it accepts the newer version, if it's just doing a check for the specific version, which might be hard coded in the install script. making sure it gets the libraries it wants should make it work though.

[Exmix]

I'm not sure what the exact path is since when I looked into the gcc error when I very first had it, that's all I had found was that it's in /usr/bin/

Here's the output of "dpkg -l | grep gcc| grep compiler"

EDIT: I just ensured that it was fully updated and did a reboot, same issue.

 

:~# dpkg -l | grep gcc| grep compiler
ii  gcc                                                              4:7.2.0-1d1                          amd64        GNU C compiler
ii  gcc-6                                                            6.4.0-8                              amd64        GNU C compiler
ii  gcc-7                                                            7.2.0-8                              amd64        GNU C compiler
ii  gcc-mingw-w64                                                    6.3.0-14+19.3                        all          GNU C compiler for MinGW-w64
ii  gcc-mingw-w64-i686                                               6.3.0-18+19.3+b3                     amd64        GNU C compiler for MinGW-w64 targeting Win32
ii  gcc-mingw-w64-x86-64                                             6.3.0-18+19.3+b3                     amd64        GNU C compiler for MinGW-w64 targeting Win64
ii  linux-compiler-gcc-6-x86                                         4.13.4-1kali1                        amd64        Compiler for Linux on x86 (meta-package)

I don't have gcc-5, when I try to install it I get:

 

:~# apt-get install gcc-5
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package gcc-5 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'gcc-5' has no installation candidate

 

 

Edited October 16, 2017 by Exmix

[Bob123]

I agree 100% digip!  I don't like the idea of changing the pointer but that's the only way I got it to work.  Plus I'm sure it can be put back to gcc-7 once VMware is installed.  I couldn't get it to work using the whole method although it sounds like Exmix had better luck with that.  Once I replaced the pointer so gcc points to gcc-6 vs -7 then it installed fine.  My latest vm is almost done.  Once it's built I'll try doing an update/upgrade and see if it breaks it.  Digip could you tell me where to look for a change log?  I'm curious what changes from a virgin 2017.2 iso to one that has had the update/upgrade.

Starting to wonder if workstation 14 has the same issues.

[digip]

7 minutes ago, Bob123 said:

I agree 100% digip!  I don't like the idea of changing the pointer but that's the only way I got it to work.  Plus I'm sure it can be put back to gcc-7 once VMware is installed.  I couldn't get it to work using the whole method although it sounds like Exmix had better luck with that.  Once I replaced the pointer so gcc points to gcc-6 vs -7 then it installed fine.  My latest vm is almost done.  Once it's built I'll try doing an update/upgrade and see if it breaks it.  Digip could you tell me where to look for a change log?  I'm curious what changes from a virgin 2017.2 iso to one that has had the update/upgrade.

Starting to wonder if workstation 14 has the same issues.

 

For which changelog?

updatedb

locate changelog.Debian | grep gcc

 

[Bob123]

When you do an apt-get update/upgrade.  Is there a change log for all of the programs that get updated?  Noob question I know.

[Exmix]

Nope, when I did it nothing needed updated, came back with "0 upgraded, 0 newly installed, 0to remove and 0 not upgraded"

[Bob123]

You are right.  I wonder why the ISO is so much different than the vm I downloaded.  I can't even apt-get install gcc-6.  Had no issue doing that in my vm.  It's like something is missing.  Did update/upgrade and it showed 0.  I'm online with it and yet it can't find any packages...

[Exmix]

I was able to install gcc-6 before and when I try now it just say it's already there.

[digip]

2 hours ago, Exmix said:

I was able to install gcc-6 before and when I try now it just say it's already there.

It should of already been installed, but did you also make sure to run the command above he gave for the Linux headers? I have a feeling something is being missed here, or not supplying what it wants in the install script. Once figured out what that is, should go without a hitch.

[Exmix]

39 minutes ago, digip said:

It should of already been installed, but did you also make sure to run the command above he gave for the Linux headers? I have a feeling something is being missed here, or not supplying what it wants in the install script. Once figured out what that is, should go without a hitch.

Yes I have ran the command for the headers as well.

apt-get install linux-headers-$(uname -r)

 

Correct?

[Bob123]

Well I don't know how I did it but I finally was able to repeat exactly what your seeing.  I'm thinking it's because of the 4.13 headers since the 2017.2 ISO has 4.12 headers by default.  Updating the headers and image to 4.13 seems to fix the headers issue but then it crashes on the virtual network adapters.  I'll have to look at the VMs I created earlier today and see what their headers were compared to their images.  My guess is my earlier successful attempt had 4.12.  I'll keep digging. 

[digip]

If you find that there is a bug, pass it on to bugs.kali.org

I don't have a copy of workstation to install for linux, and my Kali, is in a VM already, so won't be of much help, since this should be something you test on bare metal and not a VM within a VM "inception". I'll see if I can get the free VMware player on my laptop which has a full install of Kali, just need to set some time aside to play with it maybe later this week.

If you're trying to setup a home lab, worse case scenario, use "virtualbox" inside Kali, it's on our repo, so should install easy peasy, although I personally like Workstation better, just my experience from the windows side of things.