Arch Linux User Repository

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

I already had workstation installed bz .budle package from vmware. I wanted to install vmware-workstation package, but pacman warned me about files already exist in filesystem (obviously). So I used --force (yeah!). Now pacman warns me, that some files are owned by two packages: error: file owned by 'vmware-horizon-virtual-printing' and 'vmware-workstation': 'etc/thnuclnt/.thnumod' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/be101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/be104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/chde101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/chde104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/chfr101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/chfr104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/de101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/de104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/dk101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/dk104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/es101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/es104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/fi101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/fi104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/fr101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/fr104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/gb101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/gb104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/is101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/is104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/it101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/it104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/jp106' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/jp109' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/no101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/no104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/pt101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/pt104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/se101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/se104' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/us101' error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/us104' I am not having a problem, just reporting this, because there appears to be package conflict between vmware-horizon-* and vmware-workstation.

@jihem: Ok, cool! Sounds like a solid plan! Cheers!

Hello, I keep receiving the following error when I attempt to install this pacakge: Extracting VMware Installer...done. /home/[username]/vmware-workstation/VMware-Workstation-Full-12.5.7-5813279.x86_64.bundle: line 302: /tmp/vmis.NauOUt/install/vmware-installer/vmware-installer: Permission denied ==> ERROR: A failure occurred in prepare(). I tried commenting out that line in the bundle, but then I run into other errors. How do I fix this?

Thanks Synthead! I will try to continue maintaining this package as long as possible, that was a great idea to create it. I think I will keep the vmware.conf file because it's the behaviour that the most part of people want. And if you don't want that, you can simply create a void file in /etc/modules-load.d/vmware.conf. In addition, virtualbox-host-dkms contains an equivalent file, so it's also the choice of Arch maintainers.

I love seeing this package kept up to date! Thanks to all the hard work! We probably shouldn't include /usr/lib/modules-load.d/vmware.conf into this package. If a user wants to configure their system to modprobe vmware modules at boot, it should be their choice to do so with whatever modules they want. As of now, the only way to disable probing the modules at boot would be to modify tracked files, which is a Bad Idea (tm).

@dummys: Sorry for the late answer. Unfortunetely I have no idea how to solve your problem. But you can test these workarounds: - use command "VMWARE_USE_SHIPPED_LIBS=yes vmare" - test on another kernel (for example linux-lts) - stop all vmware services before start vmware (to verify if the problem comes from the program itself or the services)

Hi, when using your package I get an error when launching "vmware": -> $ vmware Loop on signal 11. Seems to be a kernel panic, in /tmp/vmware-ui.logs: 2017-08-08T16:32:37+02:00[+0.013]| vmui| W115: Caught signal 11 -- tid 16859 (addr 1430) 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: rip 0x1430 rsp 0x7ffdf7353b48 rbp 0x1 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: rax 0x0 rbx 0x7f4f084cfdd0 rcx 0xcdf6c65740 rdx 0xcdf6c65740 rsi 0x7ffdf7354ae8 rdi 0x1 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: r8 0xcdf787dc50 r9 0x2f r10 0xcdf7876cd0 r11 0x206 r12 0x7ffdf7354ae8 r13 0xcdf6c65740 r14 0x7f4f084cfdd8 r15 0x0 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B48 : 0x00007f4f1853d37a 0x000000000000000b 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B58 : 0x0000000000000001 0x00007ffdf7354ae8 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B68 : 0x000000cdf6c65740 0x000000cdf7876cd0 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B78 : 0x00007f4f1853d486 0x00007f4f1871bea0 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B88 : 0x0000000000000006 0x00007ffdf7353c60 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B98 : 0x000000000000001d 0x0000000000000001 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353BA8 : 0x000000cdf7876cd0 0x000000000000001d 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353BB8 : 0x00007f4f1854193e 0x000000cdf7876cd0 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace: 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[0] 00007ffdf73532b0 rip=00007f4f1051d8fe rbx=00007f4f1051d6d0 rbp=0000000000000000 r12=00007f4f18719b00 r13=00007ffdf7353bc8 r14=00007ffdf73535c0 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[1] 00007ffdf73532e0 rip=00007f4f1048de68 rbx=00007ffdf7353bc8 rbp=000000000000000b r12=00007f4f18719b00 r13=00007ffdf7353bc8 r14=00007ffdf73535c0 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[2] 00007ffdf7353570 rip=00007f4f1048e19d rbx=000000000000000b rbp=0000000000000004 r12=00007f4f18719b00 r13=00007ffdf73536f0 r14=00007ffdf73535c0 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[3] 00007ffdf73535c0 rip=00007f4f1811d7e0 rbx=00007f4f084cfdd0 rbp=0000000000000001 r12=00007ffdf7354ae8 r13=000000cdf6c65740 r14=00007f4f084cfdd8 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: PANIC: Loop on signal 11. 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace: 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[0] 00007ffdf7352160 rip=00007f4f1051d8fe rbx=00007f4f1051d6d0 rbp=0000000000000000 r12=00007ffdf73525c0 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[1] 00007ffdf7352190 rip=00007f4f10261e9a rbx=00007ffdf7352980 rbp=00007f4f17ef0660 r12=00007ffdf73525c0 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[2] 00007ffdf73525c0 rip=00007f4f1026204d rbx=00007ffdf7352980 rbp=000000000000000b r12=00007f4f18719b00 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[3] 00007ffdf73526a0 rip=00007f4f1048dd60 rbx=00007ffdf7352980 rbp=000000000000000b r12=00007f4f18719b00 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[4] 00007ffdf7352930 rip=00007f4f1048e19d rbx=000000000000000b rbp=0000000000000004 r12=00007f4f18719b00 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[5] 00007ffdf7352980 rip=00007f4f1811d7e0 rbx=0000000000000000 rbp=00007ffdf7353250 r12=00007ffdf73530a0 r13=00007ffdf7352fb0 r14=0000000000000000 r15=00007f4f1051db00 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[6] 00007ffdf7352f40 rip=00007f4f17f03e07 rbx=0000000000000000 rbp=00007ffdf7353250 r12=00007ffdf73530a0 r13=00007ffdf7352fb0 r14=0000000000000000 r15=00007f4f1051db00 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[7] 00007ffdf7352fb0 rip=00007f4f17f059b8 rbx=0000000000000000 rbp=00007ffdf7353250 r12=00007ffdf7352fb0 r13=00007ffdf73530a0 r14=00007ffdf7353260 r15=00007f4f1051db00 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[8] 00007ffdf7353260 rip=00007f4f1051d86e rbx=00007f4f1051d6d0 rbp=00007ffdf73532ac r12=00007f4f18719b00 r13=0000000000000000 r14=00007ffdf73535c0 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[9] 00007ffdf73532b0 rip=00007f4f1051d8fe rbx=00007f4f1051d6d0 rbp=0000000000000000 r12=00007f4f18719b00 r13=00007ffdf7353bc8 r14=00007ffdf73535c0 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[10] 00007ffdf73532e0 rip=00007f4f1048de68 rbx=00007ffdf7353bc8 rbp=000000000000000b r12=00007f4f18719b00 r13=00007ffdf7353bc8 r14=00007ffdf73535c0 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[11] 00007ffdf7353570 rip=00007f4f1048e19d rbx=000000000000000b rbp=0000000000000004 r12=00007f4f18719b00 r13=00007ffdf73536f0 r14=00007ffdf73535c0 r15=0000000000000000 2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[12] 00007ffdf73535c0 rip=00007f4f1811d7e0 rbx=00007f4f084cfdd0 rbp=0000000000000001 r12=00007ffdf7354ae8 r13=000000cdf6c65740 r14=00007f4f084cfdd8 r15=0000000000000000

To solve the following problem... " Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded. " ... restart your machine or try the following... Create the file... " /etc/systemd/system/vmware.service " ... with the following content... " [Unit] Description=VMware daemon Requires=vmware-usbarbitrator.service Before=vmware-usbarbitrator.service After=network.target [Service] ExecStart=/etc/init.d/vmware start ExecStop=/etc/init.d/vmware stop PIDFile=/var/lock/subsys/vmware RemainAfterExit=yes [Install] WantedBy=multi-user.target " Create the file... " /etc/systemd/system/vmware-usbarbitrator.service " ... with the following content... " [Unit] Description=VMware USB Arbitrator Requires=vmware.service After=vmware.service [Service] ExecStart=/usr/bin/vmware-usbarbitrator ExecStop=/usr/bin/vmware-usbarbitrator --kill RemainAfterExit=yes [Install] WantedBy=multi-user.target " Add the following service as well, if you want to connect to your VMware Workstation installation from another Workstation Server Console... Create the file... " /etc/systemd/system/vmware-workstation-server.service " ... with the following content... " [Unit] Description=VMware Workstation Server Requires=vmware.service After=vmware.service [Service] ExecStart=/etc/init.d/vmware-workstation-server start ExecStop=/etc/init.d/vmware-workstation-server stop PIDFile=/var/lock/subsys/vmware-workstation-server [Install] WantedBy=multi-user.target " Start and enable the services... " sudo systemctl start vmware.service sudo systemctl enable vmware.service sudo systemctl start vmware-usbarbitrator.service sudo systemctl enable vmware-usbarbitrator.service sudo systemctl start vmware-workstation-server.service sudo systemctl enable vmware-workstation-server.service " Restart your machine! That's all folks! =D

Después de instalado, no se actualizan los complementos