Arch Linux User Repository

New package version released: 17.6.3-8

Changelog:

• Fix download links by hardcoding the domain resolution. curl>=7.49.0 is required ( using the --connect-to flag )

After the first installation, please:

1) install the appropriate headers package(s) for your installed kernel(s): linux-headers for default kernel, linux-lts-headers for LTS kernel...

2) reboot or load vmw_vmci and vmmon kernel modules (modprobe -a vmw_vmci vmmon)

3) Enable the services you need (using .service units to activate them during boot or .path units to activate them when a VM is started) :

• vmware-networks: to have network access inside VMs

• vmware-usbarbitrator: to connect USB devices inside VMs

@timofonic: I use linux-zen as default kernel and I don't have your problem.

Firstly, try to uninstall modules (dkms remove -k 4.14.8-1-zen vmware-workstation/14.1.0_7370693) before reinstall them (dkms install -k 4.14.8-1-zen vmware-workstation/14.1.0_7370693).

Now, when you start command "dkms status" on a terminal, do you see the line "vmware-workstation, 14.1.0_7370693, 4.14.8-1-zen, x86_64: installed"? Does the module files exist (/usr/lib/modules/4.14.8-1-zen/kernel/drivers/misc/vmmon.ko and /usr/lib/modules/4.14.8-1-zen/kernel/drivers/net/vmnet.ko)?

If you used bundle installation before trying this package, maybe some modules are still installed and cause conflicts. On /usr/lib/modules/4.14.8-1-zen directory, search and remove following files: vmmon.ko, vmci.ko, vmnet.ko, vmblock.ko and vsock.ko (but don't touch those have extension .gz or .xz). And retry the dkms command to install modules.

=> Patching VMware for macOS guest support Traceback (most recent call last): File "/tmp/yaourt-tmp-vili/aur-vmware-workstation/src/unlocker.py", line 47, in <module> import six ImportError: No module named six ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build vmware-workstation.</module>

@jihem:Thank you for your reply! I still can't open OVA file. This OVA file was made by virtualbox. I clicked File->Open... and it will show a dialog of "Open virtual machines", then I double clicked my OVA file, it does nothing, no warning, no error dialog, just like i didn't double click it. I'm using i3wm, is that OK? Where can I get further info about this problem?

Modules don't get build here. Would you be able to fix that? What about a separate packages for dkms modules? They can be part of the same PKGBUILD.

modprobe -a vmw_vmci vmmon vmnet

modprobe: WARNING: Module vmmon not found in directory /lib/modules/4.14.8-1-zen modprobe: WARNING: Module vmnet not found in directory /lib/modules/4.14.8-1-zen ZZ

Why? Am I doing some more conplex for me modprobe -a vmw_vmci vmmon vmnet even insmod Sat 23 Dec 2017 11:15:52 PM CET modprobe: WARNING: Module vmmon not found in directory /lib/modules/4.14.8-1-zen modprobe: WARNING: Module vmnet not found in directory /lib/modules/4.14.8-1-zen

Modules aren't in /var/lib/dkms directory. Why? anbox-modules-binder/ dkms_dbversion

I used the following commands and the relevant module (vmmon) got built and installed:

dkms install vmware-workstation/14.1.0_7370693/ -k 4.14.8-1-zen

Creating symlink /var/lib/dkms/vmware-workstation/14.1.0_7370693//source -> /usr/src/vmware-workstation-14.1.0_7370693/

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module: make clean rm -rf vmmon vmnet rm -rf vmmon-only vmnet-only rm -f vmmon.ko vmnet.ko rm -f vmmon.o vmnet.o

{ make -j2 KERNELRELEASE=4.14.8-1-zen KVERSION=4.14.8-1-zen SRCDIR=/usr/src/vmware-workstation -14.1.0_7370693; } >> /var/lib/dkms/vmware-workstation/14.1.0_7370693//build/make.log 2>&1

make clean rm -rf vmmon vmnet rm -rf vmmon-only vmnet-only rm -f vmmon.ko vmnet.ko rm -f vmmon.o vmnet.o

Kernel cleanup unnecessary for this kernel. Skipping...

DKMS: build completed.

vmmon.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /usr/lib/modules/4.14.8-1-zen/kernel/drivers/misc/

vmnet.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /usr/lib/modules/4.14.8-1-zen/kernel/drivers/net/

do_depmod 4.14.8-1-zen

sudo dkms install vmware-workstation/14.1.0_7370693/ -k 4.14.8-1-ARCH

Kernel preparation unnecessary for this kernel. Skipping...

Building module: make clean rm -rf vmmon vmnet rm -rf vmmon-only vmnet-only rm -f vmmon.ko vmnet.ko rm -f vmmon.o vmnet.o

{ make -j2 KERNELRELEASE=4.14.8-1-ARCH KVERSION=4.14.8-1-ARCH SRCDIR=/usr/src/vmware-workstati on-14.1.0_7370693; } >> /var/lib/dkms/vmware-workstation/14.1.0_7370693//build/make.log 2>&1

make clean rm -rf vmmon vmnet rm -rf vmmon-only vmnet-only rm -f vmmon.ko vmnet.ko rm -f vmmon.o vmnet.o

Kernel cleanup unnecessary for this kernel. Skipping...

DKMS: build completed.

vmmon.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /usr/lib/modules/4.14.8-1-ARCH/kernel/drivers/misc/

vmnet.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /usr/lib/modules/4.14.8-1-ARCH/kernel/drivers/net/

do_depmod 4.14.8-1-ARCH

DKMS: install completed.

After this process, the modules load sucessfully :D

@hunk: I have just updated the package, can you test with the last version? (the changes I've made are probably not related to your problem, but I didn't test on the older version)

On this version, I can open ova files without problem, I get a message talking about a problem with OVF specification conformance but if I click on "Retry" the VM is imported.

If you still can't import your OVA file, can you tell me more informations: error messages, how the file was created (with VMware or VirtualBox), can you open it with VirtualBox?

I can't open ova file, any solution here?

jihem, worked! Thank you for your help!! I owe you!

Don't follow the wiki, it is useless if you use this package. Kernel modules are automatically compiled with DKMS when you install the package, you don't have to do it manually (just verify that you installed linux-headers before).

Just read instructions in the pinned comment, this is all you have to do (and be careful that services names are slightly different than services names in the wiki).

Appreciate your feedback, jihem. I don't get it. If I follow the wiki I can't compile the machine monitor. If I use this repo I get: [AppLoader] Unable to lookup library directory.

What am I doing wrong?

@avarx: Yes. I maintain this package for linux, linux-zen and linux-lts kernels.