Getting things working with Arch Linux

myitcv commented 10 years ago

Notwithstanding #4, can anyone point me towards the steps required to get things working with Arch Linux (fresh install)?

There is this guide but it appears outdated.

Indeed following those steps in combination with using vmware-tools-patches I encounter these issues:

Some of the patches fail but this doesn't appear critical because everything builds fine - namely linux/driver.c, all hunks fail, vmhgfs/inode.c, all hunks fail, shared/compat_mm.h, all hunks fail, mhgfs-d_count-kernel-3.11-tools-9.6.0, 2 hunks fail
Then I get two sh: command not found errors before the first compilation step
I get a message telling me it's using the 2.6.x Kernel build system?
Messages that vmxnet3, pcscsi and vmmemctl are not supported for Kernels > 3.10... that I need to enable those modules in my kernel and might need to enable HYPERVISOR_GUEST
Complaints that I don't have the relevant fuse packages installed (although fuse is installed)

The final error messages are:

VM communication interface socket family fails to start
Guest filesystem driver fails to start
Mounting HGFS shares fails

Can anyone point me in the right direct with any of these before I start digging too far?

Thanks

rasa commented 10 years ago

A lot of the errors you mention can be safely ignored.

For simplicity, all of the patches are applied, even if they aren't needed for a particular file or kernel version. Hence the hunk fail messages you see.

The command not found errors are probably because you are running on arch linux, and the script couldn't find apt-get, so it wasn't able to install a prerequisite.

Perhaps you could add set +vx near the top of the scripts and see exactly where they are failing?

The 2.6.x error can be safely ignored.

And as long as the VMWare installer runs without a compile failure, its warnings can be safely ignored.

I hope that helps,

Ross

myitcv commented 10 years ago

Thanks for the quick response. I'll give this another shot and report back

davispuh commented 10 years ago

For some reason open-vm-tools-modules is removed from Arch repository and so I created open-vm-tools-dkms and added to AUR

It's using latest open-vm-tools-2013.09.16-1328054 [development snapshot from sourceforge](http://sourceforge.net/projects/open-vm-tools/files/open-vm-tools/Development Snapshots/)

I created patch file which fixes everything so it compiles perfectly on 3.13 kernel without any warnings. I plan to submit it upstream.

Once you install open-vm-tools-dkms package then just

dkms add open-vm-tools/2013.09.16
dkms install -m open-vm-tools -v 2013.09.16 -k $(uname -r)

I haven't fully tested it yet, but atleast modules does get loaded and kernel doesn't crash. Here's log, seems there's some problems.

[   43.384134] vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16
[   43.384202] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[   43.384360] vmw_vmci 0000:00:07.7: irq 72 for MSI/MSI-X
[   43.384403] vmw_vmci 0000:00:07.7: irq 73 for MSI/MSI-X
[   43.384787] VMCI host device registered (name=vmci, major=10, minor=59)
[   43.470872] [drm] Initialized vmwgfx 2.4.0 20120209 for 0000:00:0f.0 on minor 0
[   43.471245] VMware vmxnet3 virtual NIC driver - version 1.2.0.0-k-NAPI
[   45.060779] systemd[1]: Detected virtualization 'vmware'.
[   47.758881] vmci: exports duplicate symbol vmci_context_get_priv_flags (owned by vmw_vmci)
[   52.215389] vmci: exports duplicate symbol vmci_context_get_priv_flags (owned by vmw_vmci)
[   52.240572] vmci: exports duplicate symbol vmci_context_get_priv_flags (owned by vmw_vmci)
[   57.110147] vmblock: Unknown symbol putname (err 0)
[   57.111156] vmci: exports duplicate symbol vmci_context_get_priv_flags (owned by vmw_vmci)
[   57.132562] vmhgfs: disagrees about version of symbol vmci_datagram_destroy_handle
[   57.132565] vmhgfs: Unknown symbol vmci_datagram_destroy_handle (err -22)
[   57.132587] vmhgfs: disagrees about version of symbol vmci_datagram_send
[   57.132588] vmhgfs: Unknown symbol vmci_datagram_send (err -22)
[   57.132610] vmhgfs: disagrees about version of symbol vmci_datagram_create_handle
[   57.132611] vmhgfs: Unknown symbol vmci_datagram_create_handle (err -22)
[   57.134455] VMware vmxnet virtual NIC driver
[   87.108297] vmci: exports duplicate symbol vmci_context_get_priv_flags (owned by vmw_vmci)
[   87.125855] vmci: exports duplicate symbol vmci_context_get_priv_flags (owned by vmw_vmci)

davispuh commented 10 years ago

those errors are because kernel already have built in vmci module and so it's not needed. Now when I included only needed modules (vmblock, vmhgfs, vmsync) it works perfectly :)

log now:

[   39.097075] vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16
[   39.097115] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[   39.097222] vmw_vmci 0000:00:07.7: irq 72 for MSI/MSI-X
[   39.097247] vmw_vmci 0000:00:07.7: irq 73 for MSI/MSI-X
[   39.097552] VMCI host device registered (name=vmci, major=10, minor=59)
[   39.142958] [drm] Initialized vmwgfx 2.4.0 20120209 for 0000:00:0f.0 on minor 0
[   39.143427] VMware vmxnet3 virtual NIC driver - version 1.2.0.0-k-NAPI
[   40.725842] systemd[1]: Detected virtualization 'vmware'.

and loaded modules:

vmsync                  3745  0 
vmhgfs                 46271  0 
vmblock                11048  0 
vmw_vsock_vmci_transport    20368  0 
vsock                  24519  1 vmw_vsock_vmci_transport
vmw_balloon             6066  0 
vmxnet3                42237  0 
vmwgfx                122457  2 
ttm                    65027  1 vmwgfx
drm                   239102  3 ttm,vmwgfx
vmw_vmci               52304  2 vmw_vsock_vmci_transport,vmhgfs

I've updated my open-vm-tools-dkms package and now there's newest version in AUR. I suggest to checkout out :)

liayn commented 10 years ago

So does the hgfs also work (not only load)?

davispuh commented 10 years ago

Actually I haven't really used file sharing for linux guest, but it seems to be almost working. I think it could be VMware version incompatibility or bug in their part as my patch fixes just differences between kernels so if it doesn't work I bet it didn't worked even for older kernels. And by almost, I mean that when I try to mount share, it kinda mounts it but you can't open it.

$ vmware-hgfsclient
test
$ mount -t vmhgfs .host:/test /mnt/test
Could not add entry to mtab, continuing
$ cat /etc/mtab | grep host
.host:/test /mnt/test vmhgfs rw,relatime 0 0
$ mount | grep host
.host:/test on /mnt/test type vmhgfs (rw,relatime)
$ cd /mnt/test
bash: cd: /mnt/test: Not a directory

But there are no any other errors. Also drag-drop "works" similarly that it seems to be working and there are no errors, but file doesn't get copied.

rasa commented 10 years ago

The

cd: /mnt/test: Not a directory

is the error. It's due to the 3.13 kernel. See #4 for details.

davispuh commented 10 years ago

for which kernel version it did worked? I just never have used this...

liayn commented 10 years ago

Worked for all versions before 3.13

myitcv commented 10 years ago

Given #4 is waiting on some work from VMWare is it worth people adding their voices to this thread?

mod commented 9 years ago

Failure on Archlinux.

After calling ./compile.sh Just before running vmhgfs filesystem shares, VMWare CPU stops

dragon788 commented 8 years ago

On my fork I've got a working script that works with Arch Linux. I'd like to clean it up before I pull request it in, but folks can give it a try to see if it also works for them.

https://github.com/dragon788/vmware-tools-patches

rasa / vmware-tools-patches

Getting things working with Arch Linux #5