Do take a look. Like this video
Friday, February 13, 2015
Wednesday, February 11, 2015
Virtual Machine 3D Support Option is Greyed Out for Windows 2008 and 2012 on VMware
The solution is taken from Enable 3D Support option is greyed out in virtual machine video card settings (2092210)
Modify the VMX file of the Virtual Machine
1. Take backup of the virtual machines VMX file
2. Open the VMX file, using text editor and add this line in the end
3. Check the VMID of the Guest OS you are reloading
4. Reload the virtual machines configuration file by running this command:
1. Take backup of the virtual machines VMX file
2. Open the VMX file, using text editor and add this line in the end
mks.enable3d = TRUE*You can use the vi to edit the VMX file
3. Check the VMID of the Guest OS you are reloading
# vim-cmd "vmsvc/getallvms" Vmid Name ......... 2
4. Reload the virtual machines configuration file by running this command:
# vim-cmd vmsvc/reload VMID
Monday, February 9, 2015
Relooking at usage of /home directory in Linux
File System in /home can be clustered very quickly nowadays where the
amount of data are massive. Residing all the users in one /home
directory will cause the administrator to quickly reach the limits of
the File System especially if the File System is not a Parallel File
System......
For more information, do take a look at Relooking at usage of /home directory in Linux on Linux Cluster
For more information, do take a look at Relooking at usage of /home directory in Linux on Linux Cluster
Linker returns error: /usr/bin/ld: cannot find –llapack
When I do
I resume you have installed the package already. If not, do a check,
The error can be solved by doing a soft-link
When you do a linker again
$ ld –llapack —verbose
attempt to open /usr/x86_64-redhat-linux/lib64/liblapack.so failed attempt to open /usr/x86_64-redhat-linux/lib64/liblapack.a failed attempt to open /usr/local/lib64/liblapack.so failed attempt to open /usr/local/lib64/liblapack.a failed attempt to open /lib64/liblapack.so failed attempt to open /lib64/liblapack.a failed attempt to open /usr/lib64/liblapack.so failed attempt to open /usr/lib64/liblapack.a failed attempt to open /usr/x86_64-redhat-linux/lib/liblapack.so failed attempt to open /usr/x86_64-redhat-linux/lib/liblapack.a failed attempt to open /usr/lib64/liblapack.so failed attempt to open /usr/lib64/liblapack.a failed attempt to open /usr/local/lib/liblapack.so failed attempt to open /usr/local/lib/liblapack.a failed attempt to open /lib/liblapack.so failed attempt to open /lib/liblapack.a failed attempt to open /usr/lib/liblapack.so failed attempt to open /usr/lib/liblapack.a failed ld: cannot find -llapack
I resume you have installed the package already. If not, do a check,
# yum info lapack
The error can be solved by doing a soft-link
# ln -s /usr/lib64/liblapack.so.3.2.1 /usr/lib64/liblapack.so
When you do a linker again
# ld –llapack —verbose
.... .... .... attempt to open /usr/lib64/liblapack.so succeeded .... .... ....
Thursday, February 5, 2015
NetApp Visual Storage Console (VSC)5.0 Plugin for VCentre 5.5
VSC 5.0 is a major change that includes a new look and seamless integration with the VMware vSphere Web Client. New features in this release include support for the following:
- The VMware vSphere Web Client
- VASA Provider for clustered Data ONTAP®
- SnapVault integration as a backup job option for clustered Data ONTAP
- Adding a virtual machine or datastore to an existing backup job
- Numerous bug fixes
- vCenter 5.1 and earlier
- VMware Desktop client
- 32-bit Windows installations
- mbralign
- Single File Restore
- Datastore Remote Replication
- Flash Accel
Subscribe to:
Posts (Atom)
