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

@mabod the patch is added (with another patch to make VMware working on Linux 5.19-rc1).

And yes, thanks to mkubecek for his great work (I usually use his patches to make VMware compatible with newer kernel versions)!

I see errors/warnings for vmnet1/vmnet8 in the journal:

Jun 08 10:21:17 rakete kernel: vmnet1: Current addr:  00 50 56 c0 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>
Jun 08 10:21:17 rakete kernel: vmnet1: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>
Jun 08 10:21:17 rakete kernel: ------------[ cut here ]------------
Jun 08 10:21:17 rakete kernel: netdevice: vmnet1: Incorrect netdev->dev_addr
Jun 08 10:21:17 rakete kernel: WARNING: CPU: 2 PID: 4492 at net/core/dev_addr_lists.c:517 dev_addr_check.cold+0x43/0x74
Jun 08 10:21:17 rakete kernel: Modules linked in: qrtr cfg80211 ccm algif_aead des_generic libdes algif_skcipher cmac md4 msr>
Jun 08 10:21:17 rakete kernel:  vmmon(OE) vmw_vmci pkcs8_key_parser dm_multipath dm_mod crct10dif_pclmul ipmi_devintf crc32_p>
Jun 08 10:21:17 rakete kernel: CPU: 2 PID: 4492 Comm: vmware-networks Tainted: P           OE     5.17.13-lqx1-1-lqx #1
Jun 08 10:21:17 rakete kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA/X570 AORUS ULTRA, BIOS F36c 05/1>
Jun 08 10:21:17 rakete kernel: RIP: 0010:dev_addr_check.cold+0x43/0x74
Jun 08 10:21:17 rakete kernel: Code: 01 e8 6d f4 fa ff 0f 0b 48 c7 c5 8b 8b 3b 82 80 3b 00 75 27 48 c7 c6 14 8c 3b 82 48 89 e>
Jun 08 10:21:17 rakete kernel: RSP: 0018:ffffc90001c2bc38 EFLAGS: 00010246
Jun 08 10:21:17 rakete kernel: RAX: 0000000000000000 RBX: ffff88810c9f3000 RCX: 0000000000000000
Jun 08 10:21:17 rakete kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Jun 08 10:21:17 rakete kernel: RBP: ffffffff8232344e R08: 0000000000000000 R09: 0000000000000000
Jun 08 10:21:17 rakete kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffffffa042a020
Jun 08 10:21:17 rakete kernel: R13: ffff88810c9f3278 R14: 0000000000000000 R15: 0000000000000001
Jun 08 10:21:17 rakete kernel: FS:  00007f6eec890240(0000) GS:ffff888ffe880000(0000) knlGS:0000000000000000
Jun 08 10:21:17 rakete kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 08 10:21:17 rakete kernel: CR2: 0000560ffa472568 CR3: 00000001bbf6e000 CR4: 0000000000750ee0
Jun 08 10:21:17 rakete kernel: PKRU: 55555554
Jun 08 10:21:17 rakete kernel: Call Trace:
Jun 08 10:21:17 rakete kernel:  <TASK>
Jun 08 10:21:17 rakete kernel:  __dev_open+0x3f/0x1a0
Jun 08 10:21:17 rakete kernel:  __dev_change_flags+0x1a9/0x220
Jun 08 10:21:17 rakete kernel:  ? netdev_run_todo+0x60/0x360
Jun 08 10:21:17 rakete kernel:  dev_change_flags+0x22/0x60
Jun 08 10:21:17 rakete kernel:  devinet_ioctl+0x39d/0x7d0
Jun 08 10:21:17 rakete kernel:  inet_ioctl+0x185/0x1c0
Jun 08 10:21:17 rakete kernel:  ? netdev_name_node_lookup_rcu+0x59/0x70
Jun 08 10:21:17 rakete kernel:  ? netdev_name_node_lookup_rcu+0x59/0x70
Jun 08 10:21:17 rakete kernel:  ? __check_object_size+0x53/0x160
Jun 08 10:21:17 rakete kernel:  ? _copy_to_user+0x1c/0x50
Jun 08 10:21:17 rakete kernel:  sock_do_ioctl+0x41/0xf0
Jun 08 10:21:17 rakete kernel:  sock_ioctl+0xf4/0x300
Jun 08 10:21:17 rakete kernel:  __x64_sys_ioctl+0x94/0xd0
Jun 08 10:21:17 rakete kernel:  do_syscall_64+0x3a/0x90
Jun 08 10:21:17 rakete kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Jun 08 10:21:17 rakete kernel: RIP: 0033:0x7f6eec9987af
Jun 08 10:21:17 rakete kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 2>
Jun 08 10:21:17 rakete kernel: RSP: 002b:00007ffe9ac79cb0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jun 08 10:21:17 rakete kernel: RAX: ffffffffffffffda RBX: 00007ffe9ac79d60 RCX: 00007f6eec9987af
Jun 08 10:21:17 rakete kernel: RDX: 00007ffe9ac79d60 RSI: 0000000000008914 RDI: 0000000000000005
Jun 08 10:21:17 rakete kernel: RBP: 0000000000000005 R08: 00007ffe9ac79d20 R09: 0000000000000004
Jun 08 10:21:17 rakete kernel: R10: 0000000000000019 R11: 0000000000000246 R12: 00007ffe9ac79d20
Jun 08 10:21:17 rakete kernel: R13: 00007ffe9ac79d30 R14: 00007ffe9ac79d40 R15: 0000000000000000
Jun 08 10:21:17 rakete kernel:  </TASK>
Jun 08 10:21:17 rakete kernel: ---[ end trace 0000000000000000 ]---

The solution is another patch https://github.com/mkubecek/vmware-host-modules/commit/4af1a7197896

Thanks to user @mkubecek on the vmware forum for telling me that. https://communities.vmware.com/t5/VMware-Workstation-Pro/kernel-trace-for-vmnet1-8-netdevice-vmnet1-Incorrect-netdev-gt/m-p/2913237/highlight/true#M176135

@Aleksana This error happens when the gcc version used to build the linux*-header package is different than the gcc version installed on your system. It should not happen if you use an official linux package (linux, linux-lts, linux-zen) but if you build a kernel from AUR, you need to recompile it with the updated gcc.

@PC2022: I had a similar experience. In my case all those freezes matched with very high CPU activity on the host from kcompactd0. Disabling transparent hugepages as suggested in the Arch Wiki did not solve the issue, but apparently kcompactd0 can be disabled and did solve my issue: https://communities.vmware.com/t5/VMware-Workstation-Pro/VMWare-workstation-in-a-fistfight-with-Linux-Memory-Compactor/td-p/2876992

Recently archlinux official changed gcc build version of linux kernel,leading to Error：incompatible gcc/plugin versions

Recently archlinux official changed gcc build version of linux kernel,leading to Error：incompatible gcc/plugin versions

Using the MS-Edge Win10 VM image, as supplied by MS.

Performance using vmware-worksation (16.2.3-2) seems to be horrible. It's responsive for a few seconds, then stalls for 10 seconds, rinse and repeat. Task manager shows Win10 is not CPU bound or RAM starved, so it's not clear what's causing the unresponsiveness

VMWare tools is installed, nVidia GeForce RTX 3080 Ti, AMD Ryzen 9 5900X, should be more than capable. Anyone else seeing similar issues?

@jihem Thanks for your advice.I change "export VMWARE_USE_SHIPPED_LIBS=yes" then reboot my system, and problem fixed.

@heimodl The export to ovf works for me (at least with VMware Workstation, not tested with VMware Player). Maybe this is a problem with dependencies. Can you try to decomment the line export VMWARE_USE_SHIPPED_LIBS=yes in /etc/conf.d/vmware, restart VMware and retry to export your virtual machine, and tell me if that works?

Hey guys, I just find that exprort vm to ovf failed in the latest versionn(16.2.3-2) Here the error message:

        Export failed: Unknown error, please try again. If the problem 
        persists, please contact VMware Technical Support and provide 
        /tmp/vmware-darklord/ovftool.log

BUT /tmp/vmware-darklord/ovftool.log is null. So i had to change the version to vmware-workstation15 15.5.7-8, then the error disappeared....

Does anybody know the solution? Thanks