Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 231085

Re: Vmware Workstation 10.0.1 build-1379776 patch for Linux kernel 3.17

$
0
0

Pavilinux,

 

Thanks for your reply; however, got hung up here:

 

adler@adler-HP-Spectre-XT-Ultrabook-PC ~ $ sudo mkdir /tmp/vmware && cd /tmp/vmware

[sudo] password for adler:

adler@adler-HP-Spectre-XT-Ultrabook-PC /tmp/vmware $ sudo ls /usr/lib/vmware/modules/source/*.tar

/usr/lib/vmware/modules/source/vmblock.tar  /usr/lib/vmware/modules/source/vmmon.tar  /usr/lib/vmware/modules/source/vmsock.tar

/usr/lib/vmware/modules/source/vmci.tar     /usr/lib/vmware/modules/source/vmnet.tar  /usr/lib/vmware/modules/source/vsock.tar

adler@adler-HP-Spectre-XT-Ultrabook-PC /tmp/vmware $ sudo unzip /tmp/vmware-for-3.17.patch.zip

Archive:  /tmp/vmware-for-3.17.patch.zip

  inflating: vmware-for-3.17.patch  

adler@adler-HP-Spectre-XT-Ultrabook-PC /tmp/vmware $ sudo patch -p1 < vmware-for-3.17.patch

can't find file to patch at input line 4

Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

--------------------------

|diff -ur a/vmblock-only/linux/control.c b/vmblock-only/linux/control.c

|--- a/vmblock-only/linux/control.c    2014-04-15 01:41:40.000000000 +0400

|+++ b/vmblock-only/linux/control.c    2014-10-09 05:21:34.094551409 +0400

--------------------------

File to patch:

 

 

I had eliminated all traces of VMWare before I did a fresh install. The original error shows here:

 

Starting VMware services:

   Virtual machine monitor                                             done

   Virtual machine communication interface                     done

   VM communication interface socket family                  done

   Blocking file system                                                   done

   Virtual ethernet                                                           failed

   VMware Authentication Daemon                                  done

 

 

With previous Kernel up-grades I could always patch VMWare. This time around it has become a nightmare. LOL!

 

Any insight here? Thanks in advance for any ideas.


Viewing all articles
Browse latest Browse all 231085

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>