Difference between revisions of "Talk:VMware"

From ArchWiki
Jump to: navigation, search
(Long term include fix for Linux 3.7?)
m (A question)
 
(62 intermediate revisions by 25 users not shown)
Line 1: Line 1:
== DKMS ==
+
== GUI doesn't show after upgrade ==
Is the section about using DKMS to compile the kernel modules still valid? There is [http://www.archlinux.org/packages/community/i686/open-vm-tools-dkms/ open-vm-tools-dkms] in the community repository which seems to be the same thing. I don't know how to use DKMS yet so it would be nice if someone with experience on using DKMS could update the corresponding section. --[[User:BertiBoeller|BertiBoeller]] ([[User talk:BertiBoeller|talk]]) 11:33, 2 October 2012 (UTC)
+
Is it necessary to copy the missing libraries to /usr/lib/vmware/lib/? I think it will be better to use soft links.
  
== Instability ==
+
[[User:ThomasWFan|ThomasWFan]] ([[User talk:ThomasWFan|talk]]) 00:58, 18 July 2017 (UTC)
  
Anyone else experienced random kernel crashes when shutting down a VM? The stack trace always mentions XFS(which I use), but is never consistent. I'm on 9.0.0. Going to try upgrading to 9.0.1 to see if that helps it. --[[User:Earlz|Earlz]] ([[User talk:Earlz|talk]]) 23:03, 26 December 2012 (UTC)
+
I just wanted to record that the workaround listed here (export LD_LIBRARY_PATH...) does actually resolve the problem for Workstation 11.1.3 (I'm running on a 4.4.1 Kernel)
:So did it? --[[User:Det|Det]] ([[User talk:Det|talk]]) 14:18, 26 February 2013 (UTC)
 
  
==<s> Long term include fix for Linux 3.7? </s>==
+
I agree that the solution is not easily confirmed (I've read /usr/bin/vmware and there's nothing obvious why LD_LIBRARY_PATH is required) - but that's probably an issue to be taken to VMware, rather than reported in depth here.
  
Is there any kind of long term fix for the moved {{ic|version.h}}? It's a pain having to redo that symlink on every kernel upgrade. --[[User:Earlz|Earlz]] ([[User talk:Earlz|talk]]) 15:14, 13 February 2013 (UTC)
+
This workaround is not easily found on the rest of the internet and I have been struggling to get this working for a while (on & off..), so it is definitely a good idea to keep this section here.
:Already taken care of by 9.0.2/5.0.2. --[[User:Det|Det]] ([[User talk:Det|talk]]) 11:25, 14 March 2013 (UTC)
+
 
 +
[[User:RuneArch|RuneArch]] ([[User talk:RuneArch|talk]]) 09:15, 18 February 2016 (UTC)
 +
 
 +
:Hi, I have this same issue with vmware where the GUI won't show, but If I try the trick in this section of the wiki, it tells me modules have to rebuild, but nothing happens after https://wiki.archlinux.org/index.php/VMware#GUI_doesn.27t_show_after_upgrade. I still get this output: http://slexy.org/view/s2lgjglqrN
 +
:[[User:Professorkaos64|Professorkaos64]] ([[User talk:Professorkaos64|talk]]) 20:56, 5 July 2016 (UTC)
 +
 
 +
::I'm using version WS 12.5 with kernel 4.8, searching all pages in many days, then just need add one line: "export VMWARE_USE_SHIPPED_LIBS=force" in /usr/bin/vmware. The solution comes from https://bugzilla.redhat.com/show_bug.cgi?id=1278896#c3. It works for me. Hope this help.
 +
::[[User:pacman]] Oct 23 15:24:53 UTC 2016
 +
 
 +
== Tools Download Link ==
 +
 
 +
If anyone facing an issue with vmware tools, like could not install component, you can manually download tools from vmware.
 +
 
 +
http://softwareupdate.vmware.com/cds/vmw-desktop/ws/
 +
 
 +
Just shared so someone can find it usefull ;-)
 +
 
 +
== Kernel Modules Not Compiling (Again) ==
 +
 
 +
It seems that with the 4.9 kernel vmware is again refusing to compile modules. Just an advisory for anyone currently running testing. I'm sure that there should be another patch / workaround available soon for it. It seems like VMWare is having this issue more often with recent kernels. I think this is the third time in the past six months with only 4.8 not having any new problems. Is this a problem with the kernel changing more stuff lately than normal or is this VMWare's problem? --[[User:TheChickenMan|TheChickenMan]] ([[User talk:TheChickenMan|talk]]) 08:20, 30 December 2016 (UTC)
 +
 
 +
:''Any'' out-of-tree (non-mainline) driver should get out of sync with each major release of the kernel due to the huge churns and thousands of symbol changes (there's no such thing as a stable ABI for the kernel, because you couldn't then change anything).
 +
:
 +
:VMCI and VSOCK have been mainlined since [https://kernelnewbies.org/Linux_3.9 3.9] (April 2013) and get automatic updates/syncs, but VMMON and VMnet remain bundled/maintained in the app (see [https://communities.vmware.com/thread/186572?tstart=0 this] for vagueish expalantions on each).
 +
:
 +
:4.9 should be fixed by this: http://rglinuxtech.com/?p=1863 (RGLinuxTech is always a good go-to-first resource for Nvidia/VMware breakage)
 +
:
 +
:--'''<span style="text-shadow:grey 0.1em 0.1em 0.1em; font-size:110%">[[User:Det|<font color="gold">D</font><font color="orange">e</font><font color="red">t</font>]][[User talk:Det|<sup><font color="white">talk</font></sup>]]</span>''' 07:43, 31 December 2016 (UTC)
 +
 
 +
::Thanks the modules were an easy fix with this and verified working now. I think this should be held off though. No reason to add it to the main wiki until 4.9 leaves testing. I'll bookmark that site for future reference. --[[User:TheChickenMan|TheChickenMan]] ([[User talk:TheChickenMan|talk]]) 18:47, 1 January 2017 (UTC)
 +
 
 +
:::Well no, you can add it. There's not even an official package called "vmware-workstation", it's something you install manually, and {{AUR|vmware-patch}} is also in [[AUR]]. As soon as a new patch is released, it can be added here, so people who use {{AUR|linux-mainline}} also get the benefit.
 +
:::
 +
:::--'''<span style="text-shadow:grey 0.1em 0.1em 0.1em; font-size:110%">[[User:Det|<font color="gold">D</font><font color="orange">e</font><font color="red">t</font>]][[User talk:Det|<sup><font color="white">talk</font></sup>]]</span>''' 18:52, 1 January 2017 (UTC)
 +
 
 +
== VMware Remote Console ==
 +
 
 +
(After <small>successfully</small> installing the [https://my.vmware.com/web/vmware/details?downloadGroup=VMRC90&productId=491 bundle], and [https://aur.archlinux.org/packages/vmware-patch/ vmware-patch]) <code>vmrc</code> does not ouptut anything (quiting silently).
 +
 
 +
[[User:Chinggis6|Chinggis6]] ([[User talk:Chinggis6|talk]]) 11:37, 20 April 2017 (UTC)
 +
 
 +
 
 +
== Cleanup ==
 +
 
 +
The 'Troubleshooting' section is ever expanding. I'd like to suggest pruning issues which definitely apply to old (minor) versions of VMware only (12.5.3 through 12.5.5 seem no longer relevant to me). Any opinions?
 +
--[[User:Thralas|Thralas]] ([[User talk:Thralas|talk]]) 15:10, 25 May 2017 (UTC)
 +
: I agree that it could use some cleanup. On a related note, I was thinking there should be a note somewhere on {{pkg|linux-lts}}, since vmware has tendency to break with every new minor version of {{pkg|linux}}. --[[User:StrayArch|StrayArch]] ([[User talk:StrayArch|talk]]) 15:42, 10 June 2017 (UTC)
 +
:: To further expand on my previous comment --- the troubleshooting subsections for old minor versions should stay. After updating and rebooting, I am still unable to get 12.5.6 to work with {{pkg|linux}} and {{pkg|awesome}}. For now, I am using 12.5.4 with {{pkg|linux-lts}}. tl;dr the subsections regarding old minor versions should be kept since they are relevant to lts. --[[User:StrayArch|StrayArch]] ([[User talk:StrayArch|talk]]) 16:56, 10 June 2017 (UTC)

Latest revision as of 01:01, 18 July 2017

GUI doesn't show after upgrade

Is it necessary to copy the missing libraries to /usr/lib/vmware/lib/? I think it will be better to use soft links.

ThomasWFan (talk) 00:58, 18 July 2017 (UTC)

I just wanted to record that the workaround listed here (export LD_LIBRARY_PATH...) does actually resolve the problem for Workstation 11.1.3 (I'm running on a 4.4.1 Kernel)

I agree that the solution is not easily confirmed (I've read /usr/bin/vmware and there's nothing obvious why LD_LIBRARY_PATH is required) - but that's probably an issue to be taken to VMware, rather than reported in depth here.

This workaround is not easily found on the rest of the internet and I have been struggling to get this working for a while (on & off..), so it is definitely a good idea to keep this section here.

RuneArch (talk) 09:15, 18 February 2016 (UTC)

Hi, I have this same issue with vmware where the GUI won't show, but If I try the trick in this section of the wiki, it tells me modules have to rebuild, but nothing happens after https://wiki.archlinux.org/index.php/VMware#GUI_doesn.27t_show_after_upgrade. I still get this output: http://slexy.org/view/s2lgjglqrN
Professorkaos64 (talk) 20:56, 5 July 2016 (UTC)
I'm using version WS 12.5 with kernel 4.8, searching all pages in many days, then just need add one line: "export VMWARE_USE_SHIPPED_LIBS=force" in /usr/bin/vmware. The solution comes from https://bugzilla.redhat.com/show_bug.cgi?id=1278896#c3. It works for me. Hope this help.
User:pacman Oct 23 15:24:53 UTC 2016

Tools Download Link

If anyone facing an issue with vmware tools, like could not install component, you can manually download tools from vmware.

http://softwareupdate.vmware.com/cds/vmw-desktop/ws/

Just shared so someone can find it usefull ;-)

Kernel Modules Not Compiling (Again)

It seems that with the 4.9 kernel vmware is again refusing to compile modules. Just an advisory for anyone currently running testing. I'm sure that there should be another patch / workaround available soon for it. It seems like VMWare is having this issue more often with recent kernels. I think this is the third time in the past six months with only 4.8 not having any new problems. Is this a problem with the kernel changing more stuff lately than normal or is this VMWare's problem? --TheChickenMan (talk) 08:20, 30 December 2016 (UTC)

Any out-of-tree (non-mainline) driver should get out of sync with each major release of the kernel due to the huge churns and thousands of symbol changes (there's no such thing as a stable ABI for the kernel, because you couldn't then change anything).
VMCI and VSOCK have been mainlined since 3.9 (April 2013) and get automatic updates/syncs, but VMMON and VMnet remain bundled/maintained in the app (see this for vagueish expalantions on each).
4.9 should be fixed by this: http://rglinuxtech.com/?p=1863 (RGLinuxTech is always a good go-to-first resource for Nvidia/VMware breakage)
--Dettalk 07:43, 31 December 2016 (UTC)
Thanks the modules were an easy fix with this and verified working now. I think this should be held off though. No reason to add it to the main wiki until 4.9 leaves testing. I'll bookmark that site for future reference. --TheChickenMan (talk) 18:47, 1 January 2017 (UTC)
Well no, you can add it. There's not even an official package called "vmware-workstation", it's something you install manually, and vmware-patchAUR is also in AUR. As soon as a new patch is released, it can be added here, so people who use linux-mainlineAUR also get the benefit.
--Dettalk 18:52, 1 January 2017 (UTC)

VMware Remote Console

(After successfully installing the bundle, and vmware-patch) vmrc does not ouptut anything (quiting silently).

Chinggis6 (talk) 11:37, 20 April 2017 (UTC)


Cleanup

The 'Troubleshooting' section is ever expanding. I'd like to suggest pruning issues which definitely apply to old (minor) versions of VMware only (12.5.3 through 12.5.5 seem no longer relevant to me). Any opinions? --Thralas (talk) 15:10, 25 May 2017 (UTC)

I agree that it could use some cleanup. On a related note, I was thinking there should be a note somewhere on linux-lts, since vmware has tendency to break with every new minor version of linux. --StrayArch (talk) 15:42, 10 June 2017 (UTC)
To further expand on my previous comment --- the troubleshooting subsections for old minor versions should stay. After updating and rebooting, I am still unable to get 12.5.6 to work with linux and awesome. For now, I am using 12.5.4 with linux-lts. tl;dr the subsections regarding old minor versions should be kept since they are relevant to lts. --StrayArch (talk) 16:56, 10 June 2017 (UTC)