Installing VMWare Workstation 10 on Debian 9.6

If none of the more specific forums is the right place to ask

Installing VMWare Workstation 10 on Debian 9.6

Postby FenrisUltra » 2018-12-28 08:16

Hey Everyone,

This is an odd question but let me get started by first saying, I am running the 32 bit version of Deb 9.6 and there is no version of VMWare Workstation that can be installed on a 32 bit system other then version 10 or older. I never had an issue with it using Deb 8 but Deb 9 seems to be doing weird things.

I am having the same problem that this guy is having in Ubuntu but in Deb 9...
https://askubuntu.com/questions/40979/w ... all-vmware
And yes, I have installed those Kernal files with success including the build essential and also did
Code: Select all
 sudo ln -s /usr/src/linux-headers-$(uname -r)/include/generated/uapi/linux/version.h


I have a screen shot to show what the software does when it compiles (VMware Kernal Module Updater), but the forum won't let me upload it. It basically shows you a comping window that firsts says:
-> Success, Sopping VMware Services
Compiling:
-> Fail, Virtual Machine Monitor
-> Fail, Virtual Network Device
-> Success, Running depmod
-> Fail, Starting VMware Services

Here is the log
Code: Select all
2018-12-28T02:49:42.698-06:00| vthread-3| I120: Log for VMware Workstation pid=8363 version=10.0.6 build=build-2700073 option=Release
2018-12-28T02:49:42.698-06:00| vthread-3| I120: The process is 32-bit.
2018-12-28T02:49:42.698-06:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2018-12-28T02:49:42.698-06:00| vthread-3| I120: Host is Linux 4.9.0-8-686 Debian GNU/Linux 9.6 (stretch)
2018-12-28T02:49:42.697-06:00| vthread-3| I120: Msg_Reset:
2018-12-28T02:49:42.697-06:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2018-12-28T02:49:42.697-06:00| vthread-3| I120: ----------------------------------------
2018-12-28T02:49:42.697-06:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2018-12-28T02:49:42.697-06:00| vthread-3| I120: Msg_Reset:
2018-12-28T02:49:42.697-06:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.
2018-12-28T02:49:42.697-06:00| vthread-3| I120: ----------------------------------------
2018-12-28T02:49:42.697-06:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2018-12-28T02:49:42.697-06:00| vthread-3| I120: PREF Unable to check permissions for preferences file.
2018-12-28T02:49:42.697-06:00| vthread-3| I120: Msg_Reset:
2018-12-28T02:49:42.697-06:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.
2018-12-28T02:49:42.697-06:00| vthread-3| I120: ----------------------------------------
2018-12-28T02:49:42.697-06:00| vthread-3| I120: PREF Failed to load user preferences.
2018-12-28T02:49:42.698-06:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-8363.log
2018-12-28T02:49:42.781-06:00| vthread-3| I120: Obtaining info using the running kernel.
2018-12-28T02:49:42.781-06:00| vthread-3| I120: Created new pathsHash.
2018-12-28T02:49:42.782-06:00| vthread-3| I120: Setting header path for 4.9.0-8-686 to "/lib/modules/4.9.0-8-686/build/include".
2018-12-28T02:49:42.782-06:00| vthread-3| I120: Validating path "/lib/modules/4.9.0-8-686/build/include" for kernel release "4.9.0-8-686".
2018-12-28T02:49:42.782-06:00| vthread-3| I120: Failed to find /lib/modules/4.9.0-8-686/build/include/linux/version.h
2018-12-28T02:49:42.782-06:00| vthread-3| I120: /lib/modules/4.9.0-8-686/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-12-28T02:49:42.782-06:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2018-12-28T02:49:42.793-06:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.9.0-8-686".
2018-12-28T02:49:42.793-06:00| vthread-3| I120: The header path "/lib/modules/4.9.0-8-686/build/include" for the kernel "4.9.0-8-686" is valid.  Whoohoo!
2018-12-28T02:49:42.867-06:00| vthread-3| I120: found symbol version file /lib/modules/4.9.0-8-686/build/Module.symvers
2018-12-28T02:49:42.867-06:00| vthread-3| I120: Reading symbol versions from /lib/modules/4.9.0-8-686/build/Module.symvers.
2018-12-28T02:49:42.929-06:00| vthread-3| I120: Read 18762 symbol versions
2018-12-28T02:49:42.930-06:00| vthread-3| I120: Reading in info for the vmmon module.
2018-12-28T02:49:42.930-06:00| vthread-3| I120: Reading in info for the vmnet module.
2018-12-28T02:49:42.930-06:00| vthread-3| I120: Reading in info for the vmblock module.
2018-12-28T02:49:42.930-06:00| vthread-3| I120: Reading in info for the vmci module.
2018-12-28T02:49:42.930-06:00| vthread-3| I120: Reading in info for the vsock module.
2018-12-28T02:49:42.930-06:00| vthread-3| I120: Setting vsock to depend on vmci.
2018-12-28T02:49:42.930-06:00| vthread-3| I120: Invoking modinfo on "vmmon".
2018-12-28T02:49:42.933-06:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2018-12-28T02:49:42.934-06:00| vthread-3| I120: Invoking modinfo on "vmnet".
2018-12-28T02:49:42.941-06:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2018-12-28T02:49:42.941-06:00| vthread-3| I120: Invoking modinfo on "vmblock".
2018-12-28T02:49:42.944-06:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2018-12-28T02:49:42.944-06:00| vthread-3| I120: Invoking modinfo on "vmci".
2018-12-28T02:49:42.946-06:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2018-12-28T02:49:42.946-06:00| vthread-3| I120: Invoking modinfo on "vsock".
2018-12-28T02:49:42.949-06:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2018-12-28T02:49:42.983-06:00| vthread-3| I120: to be installed: vmmon status: 0
2018-12-28T02:49:42.984-06:00| vthread-3| I120: to be installed: vmnet status: 0
2018-12-28T02:49:43.025-06:00| vthread-3| I120: Obtaining info using the running kernel.
2018-12-28T02:49:43.025-06:00| vthread-3| I120: Setting header path for 4.9.0-8-686 to "/lib/modules/4.9.0-8-686/build/include".
2018-12-28T02:49:43.025-06:00| vthread-3| I120: Validating path "/lib/modules/4.9.0-8-686/build/include" for kernel release "4.9.0-8-686".
2018-12-28T02:49:43.025-06:00| vthread-3| I120: Failed to find /lib/modules/4.9.0-8-686/build/include/linux/version.h
2018-12-28T02:49:43.025-06:00| vthread-3| I120: /lib/modules/4.9.0-8-686/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-12-28T02:49:43.025-06:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2018-12-28T02:49:43.037-06:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.9.0-8-686".
2018-12-28T02:49:43.037-06:00| vthread-3| I120: The header path "/lib/modules/4.9.0-8-686/build/include" for the kernel "4.9.0-8-686" is valid.  Whoohoo!
2018-12-28T02:49:43.109-06:00| vthread-3| I120: found symbol version file /lib/modules/4.9.0-8-686/build/Module.symvers
2018-12-28T02:49:43.109-06:00| vthread-3| I120: Reading symbol versions from /lib/modules/4.9.0-8-686/build/Module.symvers.
2018-12-28T02:49:43.167-06:00| vthread-3| I120: Read 18762 symbol versions
2018-12-28T02:49:43.167-06:00| vthread-3| I120: Kernel header path retrieved from FileEntry: /lib/modules/4.9.0-8-686/build/include
2018-12-28T02:49:43.167-06:00| vthread-3| I120: Update kernel header path to /lib/modules/4.9.0-8-686/build/include
2018-12-28T02:49:43.167-06:00| vthread-3| I120: Validating path "/lib/modules/4.9.0-8-686/build/include" for kernel release "4.9.0-8-686".
2018-12-28T02:49:43.168-06:00| vthread-3| I120: Failed to find /lib/modules/4.9.0-8-686/build/include/linux/version.h
2018-12-28T02:49:43.168-06:00| vthread-3| I120: /lib/modules/4.9.0-8-686/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-12-28T02:49:43.168-06:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2018-12-28T02:49:43.181-06:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.9.0-8-686".
2018-12-28T02:49:43.181-06:00| vthread-3| I120: The header path "/lib/modules/4.9.0-8-686/build/include" for the kernel "4.9.0-8-686" is valid.  Whoohoo!
2018-12-28T02:49:43.183-06:00| vthread-3| I120: Found compiler at "/usr/bin/gcc"
2018-12-28T02:49:43.187-06:00| vthread-3| I120: Got gcc version "6.3.0".
2018-12-28T02:49:43.187-06:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2018-12-28T02:49:43.188-06:00| vthread-3| I120: Using user supplied compiler "/usr/bin/gcc".
2018-12-28T02:49:43.192-06:00| vthread-3| I120: Got gcc version "6.3.0".
2018-12-28T02:49:43.192-06:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2018-12-28T02:49:43.200-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel "4.9.0-8-686".
2018-12-28T02:49:43.200-06:00| vthread-3| I120: No matching PBM set was found for kernel "4.9.0-8-686".
2018-12-28T02:49:43.200-06:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2018-12-28T02:49:43.201-06:00| vthread-3| I120: Validating path "/lib/modules/4.9.0-8-686/build/include" for kernel release "4.9.0-8-686".
2018-12-28T02:49:43.201-06:00| vthread-3| I120: Failed to find /lib/modules/4.9.0-8-686/build/include/linux/version.h
2018-12-28T02:49:43.201-06:00| vthread-3| I120: /lib/modules/4.9.0-8-686/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-12-28T02:49:43.201-06:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2018-12-28T02:49:43.213-06:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.9.0-8-686".
2018-12-28T02:49:43.213-06:00| vthread-3| I120: The header path "/lib/modules/4.9.0-8-686/build/include" for the kernel "4.9.0-8-686" is valid.  Whoohoo!
2018-12-28T02:49:43.214-06:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2018-12-28T02:49:43.214-06:00| vthread-3| I120: Validating path "/lib/modules/4.9.0-8-686/build/include" for kernel release "4.9.0-8-686".
2018-12-28T02:49:43.214-06:00| vthread-3| I120: Failed to find /lib/modules/4.9.0-8-686/build/include/linux/version.h
2018-12-28T02:49:43.214-06:00| vthread-3| I120: /lib/modules/4.9.0-8-686/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-12-28T02:49:43.214-06:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2018-12-28T02:49:43.228-06:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.9.0-8-686".
2018-12-28T02:49:43.228-06:00| vthread-3| I120: The header path "/lib/modules/4.9.0-8-686/build/include" for the kernel "4.9.0-8-686" is valid.  Whoohoo!
2018-12-28T02:49:43.228-06:00| vthread-3| I120: Using temp dir "/tmp".
2018-12-28T02:49:43.230-06:00| vthread-3| I120: Obtaining info using the running kernel.
2018-12-28T02:49:43.230-06:00| vthread-3| I120: Setting header path for 4.9.0-8-686 to "/lib/modules/4.9.0-8-686/build/include".
2018-12-28T02:49:43.230-06:00| vthread-3| I120: Validating path "/lib/modules/4.9.0-8-686/build/include" for kernel release "4.9.0-8-686".
2018-12-28T02:49:43.230-06:00| vthread-3| I120: Failed to find /lib/modules/4.9.0-8-686/build/include/linux/version.h
2018-12-28T02:49:43.230-06:00| vthread-3| I120: /lib/modules/4.9.0-8-686/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-12-28T02:49:43.230-06:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2018-12-28T02:49:43.242-06:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.9.0-8-686".
2018-12-28T02:49:43.242-06:00| vthread-3| I120: The header path "/lib/modules/4.9.0-8-686/build/include" for the kernel "4.9.0-8-686" is valid.  Whoohoo!
2018-12-28T02:49:43.316-06:00| vthread-3| I120: found symbol version file /lib/modules/4.9.0-8-686/build/Module.symvers
2018-12-28T02:49:43.316-06:00| vthread-3| I120: Reading symbol versions from /lib/modules/4.9.0-8-686/build/Module.symvers.
2018-12-28T02:49:43.376-06:00| vthread-3| I120: Read 18762 symbol versions
2018-12-28T02:49:43.376-06:00| vthread-3| I120: Invoking modinfo on "vmmon".
2018-12-28T02:49:43.380-06:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2018-12-28T02:49:43.380-06:00| vthread-3| I120: Invoking modinfo on "vmnet".
2018-12-28T02:49:43.383-06:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2018-12-28T02:49:44.001-06:00| vthread-3| I120: Setting destination path for vmmon to "/lib/modules/4.9.0-8-686/misc/vmmon.ko".
2018-12-28T02:49:44.001-06:00| vthread-3| I120: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".
2018-12-28T02:49:44.018-06:00| vthread-3| I120: Successfully extracted the vmmon source.
2018-12-28T02:49:44.018-06:00| vthread-3| I120: Building module with command "/usr/bin/make -j2 -C /tmp/modconfig-4HpdGv/vmmon-only auto-build HEADER_DIR=/lib/modules/4.9.0-8-686/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2018-12-28T02:49:47.392-06:00| vthread-3| W110: Failed to build vmmon.  Failed to execute the build command.
2018-12-28T02:49:47.395-06:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/4.9.0-8-686/misc/vmnet.ko".
2018-12-28T02:49:47.395-06:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2018-12-28T02:49:47.411-06:00| vthread-3| I120: Successfully extracted the vmnet source.
2018-12-28T02:49:47.411-06:00| vthread-3| I120: Building module with command "/usr/bin/make -j2 -C /tmp/modconfig-4HpdGv/vmnet-only auto-build HEADER_DIR=/lib/modules/4.9.0-8-686/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2018-12-28T02:49:52.098-06:00| vthread-3| W110: Failed to build vmnet.  Failed to execute the build command.


I don't know how to go about fixing this problem. Any ideas?
User avatar
FenrisUltra
 
Posts: 65
Joined: 2016-02-19 01:29
Location: Winnipeg, Manitoba (Canada)

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby Segfault » 2018-12-28 15:57

It is year 2018, will be 2019 soon. Computers are 64 bit and run 64 bit operating systems.
Segfault
 
Posts: 850
Joined: 2005-09-24 12:24

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby FenrisUltra » 2018-12-29 05:05

I didn't ask to be trolled nor have I ever treated others on this forum with disrespect. I ask for the same in return. Thank you

If there wasn't a use for a 32 bit operating system anymore, then why are they still being developed?
User avatar
FenrisUltra
 
Posts: 65
Joined: 2016-02-19 01:29
Location: Winnipeg, Manitoba (Canada)

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby millpond » 2018-12-29 06:47

The problem apparently is that the people developing Linux these days give no thought about deprecating older systems, especially 32 bit. I have run into similar problems with video drivers for older machines, which were removed to 'save space'.

Plus the likelihood that the VMWare probably uses older versions of system libs that wont work with Stretch. See if you can convert to VirtualBox format and use that instead.
millpond
 
Posts: 626
Joined: 2014-06-25 04:56

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby FenrisUltra » 2018-12-29 21:00

Alright I will see if I can give that a shot, everything worked with deb 8 so I will also try that if I don't get the results I am looking for. Is deb 8 still supported?
User avatar
FenrisUltra
 
Posts: 65
Joined: 2016-02-19 01:29
Location: Winnipeg, Manitoba (Canada)

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby None1975 » 2018-12-30 13:42

FenrisUltra wrote: Is deb 8 still supported?

Yes. It is supported by LTS team.More info here.
OS: Debian Stretch / WM: FVWM
Debian Wiki | DontBreakDebian, My config files in github
User avatar
None1975
 
Posts: 748
Joined: 2015-11-29 18:23
Location: Lithuania, Vilnius

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby Head_on_a_Stick » 2018-12-30 14:06

VirtualBox is the worst virtualisation solution around, bar none.

Check this: https://github.com/MorteNoir1/virtualbox_e1000_0day

It was removed from the stable release because of security concerns, it really shouldn't be used. By anybody.

QEMU/KVM is fully integrated with the kernel and offers a world-class virtualisation experience, why not try that instead?

https://wiki.debian.org/KVM

It can also be used without libvirt if that is too complicated a framework for your needs.
"French riots get results! U lot are instagram zzzombies" — graffiti over Euston underpass
User avatar
Head_on_a_Stick
 
Posts: 8587
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby stevepusser » 2018-12-30 20:23

Are you saying that VMWare 10 is no longer being maintained, and then asking us why it won't build on a newer kernel than they had when development was stopped?
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, 4.19.13 kernel, wine-staging 4.0~rc4, Stellarium 0.18.3, VLC 3.0.5, Midori 7.0
User avatar
stevepusser
 
Posts: 10429
Joined: 2009-10-06 05:53

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby FenrisUltra » 2019-01-01 20:22

Head_on_a_Stick wrote:VirtualBox is the worst virtualisation solution around, bar none.

Check this: https://github.com/MorteNoir1/virtualbox_e1000_0day

It was removed from the stable release because of security concerns, it really shouldn't be used. By anybody.

QEMU/KVM is fully integrated with the kernel and offers a world-class virtualisation experience, why not try that instead?

https://wiki.debian.org/KVM

It can also be used without libvirt if that is too complicated a framework for your needs.


Oh wow, I never heard of QEMU. The only systems I have heard of is VirtualBox and VMware. I always stayed away from VBox cause I am dependent on linking special hardware though the VM's that don't always seem to be accepted by the VBox software. I have an oscilloscope for instance that won't connect though VBox but VMware software gives me no trouble at all in any OS that I use. Even some of my PIC programming hardware will not work though VBox but will though VMware, I don't know why this happens, I never figured it out. What I do know is, VMware always magically made all my problems disappear and I never questioned it. Since I never heard of QEMU, do I have the ability to forward hardware though it like VMware? I'm not talking about just USB stuff either, I also use Thunderbolt applications to.
User avatar
FenrisUltra
 
Posts: 65
Joined: 2016-02-19 01:29
Location: Winnipeg, Manitoba (Canada)

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby Head_on_a_Stick » 2019-01-01 20:39

FenrisUltra wrote:do I have the ability to forward hardware though it

Yes: https://wiki.debian.org/VGAPassthrough

For example, Windows runs faster under QEMU than it does on bare metal and a PCI passthrough allows discrete GPUs to be used for the games.

https://www.youtube.com/watch?v=6FI31QDtyy4
"French riots get results! U lot are instagram zzzombies" — graffiti over Euston underpass
User avatar
Head_on_a_Stick
 
Posts: 8587
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Installing VMWare Workstation 10 on Debian 9.6

Postby CwF » 2019-01-01 23:43

I use qemu/kvm for the exact ability to pass things other than, or in addition to a video card. Learn about 'vfio' and use it to pass pci-e cards, usb chips, and I'm sure thunderbolt chips, anything that the guest OS has drivers for. USB can be handed off in an easy way to a vm, but some devices will require 'vfio' to hand over the pci usb device and not just the port. Older serial port things can be attached also. Works well.
CwF
 
Posts: 191
Joined: 2018-06-20 15:16


Return to General Questions

Who is online

Users browsing this forum: No registered users and 3 guests

fashionable