Install VMware workstation 11 on Fedora 21 with kernel 3.17

-
Here is some solutions which might be able to help you during your VMware workstation 11 installation on Fedora 21 with kernel 3.17.

1. When you try to power on a virtual guest, you received error : "Unable to change virtual machine power state internal error".

Change the option mks.enable3d in the .vmx file from TRUE to FALSE.

mks.enable3d = FALSE

2. When you try to power on a virtual guest, you received error: "Version mismatch with vmmon module: expecting xxx.x, got yyy.y. You have an incorrect version of the 'vmmon' kernel module.

Try command below, these steps will help to patch vmnet source code:

# curl http://pastie.org/pastes/9934018/download -o /tmp/vmnet-3.19.patch
# cd /usr/lib/vmware/modules/source
# tar -xf vmnet.tar
# patch -p0 -i /tmp/vmnet-3.19.patch
# tar -cf vmnet.tar vmnet-only
# rm -rf *-only
# vmware-modconfig --console --install-all

3.  When you try to power on a virtual guest, you received error: "Failed to open device "/dev/vmci" : No such file or directory. Please make sure that the kernel module 'vmci' is loaded."


Execute the following command to build and install vmci module:

#vmware-modconfig --console --build-mod vmci
# vmware-modconfig --console --install-all

4. When you issue command "vmware-modconfig --console --install-status" at the command prompt and you found that vsock status is not installed.

If you try to use command "vmware-modconfig --console --build vsock" to build vsock module at the command prompt, you see some error like:

error: too many arguments to function ‘sk->sk_data_ready’
sk->sk_data_ready(sk, 0);

Try the steps below to patch the vsock source code:

# curl https://raw.githubusercontent.com/rasa/vmware-tools-patches/master/patches/vsock/01-vsock-sk_data_ready-kernel-3.15-tools-9.6.2.patch -o /tmp/vsock.patch
# cd /usr/lib/vmware/modules/source
# tar -xf vsock.tar
# patch -p0 -i /tmp/vsock.patch
# tar -cf vsock.tar vsock-only
# rm -rf *-only
# vmware-modconfig --console --build vsock
# vmware-modconfig --console --install-all

After you try steps above, when you issue command "vmware-modconfig --console --install-status", you should the result should be like the below: 

vmmon: installed
vmnet: installed
vmblock: unknown
vmci: installed
vsock: installed

 This is the result after I fix all the error that I get.

VMware Workstation Running on Fedora 21 with Kernel 3.17.8
Wish this solution will be able to help you on your VMware Workstation 11 installation.



---

Comments

Post a Comment

Feel free to leave your question or comment here, we will reply you as soon as possible.

Popular posts from this blog

Setup mail server with ldap authentication in docker

-
Getting an email server to run in docker is easy but getting an email server with ldap authentication to run in docker spend me a week to get up and running. Here are the steps that I taken. I will assume you already know how to install docker. Install LDAP. docker run \              --detach \              --restart unless-stopped \              --name openldap \              -e LDAP_ORGANISATION=domain \              -e LDAP_DOMAIN=domain.com \              -e LDAP_ADMIN_PASSWORD=complex-password \              -e LDAP_RFC2307BIS_SCHEMA=true \              -e LDAP_REMOVE_CONFIG_AFTER_SETUP=true \              -e LDAP_TLS=false \             ...
Read more

How to allow non root user to execute hping command ?

-
If you run hping command without root permission or without sudo and you receive this error : [open_sockraw] socket(): Operation not permitted [main] can't open raw socket This command might be able to help you. sudo setcap cap_net_raw+ep /usr/bin/hping3 (or any location of the hping command) setcap command is to set file capabilities. What are filesystem capabilities?    For the purpose of performing permission checks, traditional Unix implementations distinguish two categories of processes: privileged processes (whose effective user ID is 0, referred to as superuser or root), and unprivileged processes (whose effective UID is non-zero). Privileged processes bypass all kernel permission checks, while unprivileged processes are subject to full permission checking based on the process's credentials (usually: effective UID, effective GID, and supplementary group list).  Starting with kernel 2.2, Linux divides the privileges traditionally associated...
Read more

Fedora 19 with kernel 3.10 fail to install vmplayer module.

-
If you are having problem start up vmware player on Fedora 19 after upgrade kernel to 3.10, here is the solution. Basically it is due to the procfs interface and vmnet not able to compiles. First download the procfs patch from http://communities.vmware.com/thread/446113?start=0&tstart=0 .If you don't have time to read the forum, here is the link of the procfs patch. Or you can use the following command: # tar xf /usr/lib/vmware/modules/source/vmnet.tar # cd vmnet-only # wget  http://communities.vmware.com/servlet/JiveServlet/download/2239207-108590/procfs.patch # patch -p1 < procfs.patch # cd .. # tar -cvf vmnet.tar vmnet-only/ # cp vmnet.tar /usr/lib/vmware/modules/source/ This will patch the procfs interface. Secondly download the vmnet patch from http://mysticalzero.blogspot.com/2013/07/vmblock-patch-for-linux-310-vmware.html . The link of the patch is here . Or you can use the following command: # tar xf /usr/lib/vmware/modules/source/vmblock.tar...
Read more