Running VMPlayer on CS Linux Machine
By Hanz Makmur Jan 2020 • Modified Oct 05, 2021
To run vmplayer, user needs to use GUI based desktop. This can be done by sitting in front of the machine, run X2Go or Microsoft Remote Desktop client to connect to any iLab Desktop machines from home. Once connected, open a terminal window and type :
Creating a New Virtual Machine.
In the same iso folder, there is also more recent Ubuntu 20.04 LTS
/common/system/iso/netboot.xyz.iso file which allows you todo different OS and download on the fly. See details about what OS available in url: netboot.xyz/faq
After ISO selection, click Next until you see Customize Hardware. Click on this button to adjust memory, cpu. disk size etc.
We recommend a maximum of 8GB of memory, 25GB of disk which should give you about 16GB of space to play with and 2 CPUs for your VM. Click Close and Finish button when done.
On Installation, skip the VMware Tool by clicking Remind Me Later button. When the installation is done, your VM will automatically run. Don’t forget to edit the VM and remove the ISO image once you no longer need it.
Note: If you are installing a VM, Vmplayer will ask you to install VMWare tools. Skip this. This is not required and may failure on your VM Installation.
Moving your Existing VMs to Local Disk
This section is for existing users who already stored VMs on his/her home directory. Skip this if you never run vmplayer before.
There is a compatibility issues that are crashing machines during/after using vmplayer. We have narrowed this down to an issue related to NFS mounted home directory. To avoid this, make sure your store your VM on local disk. Each iLab machines has fast local SSD based storage
/freespace/local/your_netid disk every one can use.
Note: you must use the same machine to do your work and local disk is not backed up. Data stored in local disk does not count against your quota.
If you already have your VMs stored in your home directory, here is how you move it to local disk.
#make a directory in /freespace/local under your netid mkdir /freespace/local/$USER
#move your existing vmware folder to /freespace/local mv ~/vmware /freespace/local/$USER
#create a softlink (alias) for vmware folder so vmplayer knows where vmware folder is moved to. ln -s /freespace/local/$USER/vmware
- Key mapping has been a long time issues with VMPlayer. A solution recommended by VMWare is to create and add a line in
~/.vmware/configfile that says:
xkeymap.nokeycodeMap = "TRUE"This can be also done by typing the following in terminal window:
echo 'xkeymap.nokeycodeMap = "TRUE"' >> ~/.vmware/config
- If you have weirdness with ‘<‘ character when you use it with Right but not with Left , map Right key to Left key by adding this line in
xkeymap.keycode.62 = 0xffe1
This can be also done by typing the following in terminal window:
echo 'xkeymap.keycode.62 = 0xffe1'
Please note that keysym ‘
0xffe1‘ may be different for your keyboard. You can get this keysym when pressing Left key when running
xevin a terminal.
- If you continue to have issues with other keys, please see VMWare and the fubar keyboard effect blog for more other options.
Reminder: Please SHUTDOWN the VM when you are not using it. All iLab machines are subject to enforced limitations.