@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?
Search Criteria
Package Details: vmware-workstation 17.6.1-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/vmware-workstation.git (read-only, click to copy) |
---|---|
Package Base: | vmware-workstation |
Description: | The industry standard for running multiple operating systems as virtual machines on a single Linux PC. |
Upstream URL: | https://www.vmware.com/products/workstation-for-linux.html |
Keywords: | dkms ovftool player vmplayer vmware workstation |
Licenses: | custom |
Conflicts: | vmware-modules-dkms, vmware-ovftool, vmware-patch, vmware-systemd-services |
Provides: | vmware-ovftool |
Submitter: | synthead |
Maintainer: | jihem |
Last Packager: | jihem |
Votes: | 203 |
Popularity: | 3.30 |
First Submitted: | 2017-02-10 19:04 (UTC) |
Last Updated: | 2024-10-11 05:17 (UTC) |
Dependencies (13)
- dkms (dkms-gitAUR, dkms-fast-zstdAUR)
- fuse2
- gcr
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- gtkmm3
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libaio (libaio-gitAUR)
- libcanberra
- libxcrypt-compat
- pcsclite (pcsclite-gitAUR)
- vmware-keymapsAUR
- sqlite (sqlite-fossilAUR) (make)
- linux-headers (optional) – build modules against Arch kernel
Required by (6)
Sources (22)
- config
- configure-initscript.sh
- dkms.conf.in
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linux-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linuxPreGlibc25-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-netware-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-solaris-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPre2k-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPreVista-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.6.1/24319023/linux/core/VMware-Workstation-17.6.1-24319023.x86_64.bundle.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.6.1/24319023/linux/packages/vmware-tools-windows-12.4.5-23787635.x86_64.component.tar
- Makefile
- vmmon.patch
- vmnet.patch
- vmware-bootstrap
- vmware-environment.sh
- vmware-networks-configuration.service
- vmware-networks.path
- vmware-networks.service
- vmware-usbarbitrator.path
- vmware-usbarbitrator.service
- vmware-vix-bootstrap
Latest Comments
« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 66 Next › Last »
jihem commented on 2022-04-20 16:45 (UTC)
heimodl commented on 2022-04-19 14:56 (UTC) (edited on 2022-04-19 15:15 (UTC) by heimodl)
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
sxe commented on 2022-04-08 17:00 (UTC)
ok thx. Btw, I tried v16.2.1 as well and get the same journal spam. Sadly that's the last version I can try. All the older ones won't allow me to build the kernel modules.
ajgringo619 commented on 2022-04-08 15:26 (UTC)
sxe commented on 2022-04-08 14:13 (UTC)
@ajgringo619 Good to know I am not alone. Could you please link to your post, so I can keep an eye on it? Thx
sxe commented on 2022-04-07 11:52 (UTC) (edited on 2022-04-07 11:54 (UTC) by sxe)
I just noticed, as soon as I enable networking
$ sudo systemctl start vmware-networks.service
my journal gets spammed with these messages, non stop and as far as I can tell it never ends spamming.
Apr 07 13:31:57 main kernel: userif-10: sent link up event.
Apr 07 13:31:58 main vmnet-natd[1736]: RTM_NEWADDR: index:2, addr:192.168.0.15
Couldn't find anything searching for it. Does anyone experience something similar or can give me a pointer how to fix it?
Thanks
yurikoles commented on 2022-04-04 03:26 (UTC) (edited on 2022-04-04 03:27 (UTC) by yurikoles)
@jihem
I accepted uefitool
and in latest update made binary artifacts names lower-case in accordance to other uefitool-*
packages. So please update line 412 of this PKGBUILD accordingly.
Kodehawa commented on 2022-04-02 21:59 (UTC) (edited on 2022-04-02 21:59 (UTC) by Kodehawa)
/var/lib/dkms/vmware-workstation/16.2.3_19376536/build/vmnet-only/bridge.c:956:36: error: passing 'const unsigned char *' to parameter of type 'uint8 *' (aka 'unsigned char *') discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
SMAC_SetMac(bridge->smac, bridge->dev->dev_addr);
^~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vmware-workstation/16.2.3_19376536/build/vmnet-only/./smac.h:75:45: note: passing argument to parameter 'mac' here
SMAC_SetMac(struct SMACState *state, uint8 *mac); // IN: state, and host MAC
^
1 error generated.
Anyone knows how to fix this error on DKMS compilation?
jihem commented on 2022-03-18 08:05 (UTC)
@LevitatingRein This is normal, because contrary to the official VMware installer, this package does not place any file in /etc/init.d
. Daemons are installed as systemd units. And there is no equivalent systemd service for /etc/init.d/vmware
; see https://wiki.archlinux.org/title/VMware#Package_build_for_x86_64 to know which services can be enabled.
Pinned Comments
jihem commented on 2020-02-10 17:29 (UTC) (edited on 2021-06-19 13:19 (UTC) by jihem)
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