As my previous experienced, if you having a disk space full on /var, the host server will hung and all the VMs on the host will stop functioning. I had my test machine setup as default configuration, which the /var/log only allocated for 2GB in place. Prior to move the system to production, I decide to extend the /var/log from 2GB to 10GB as our current standard. Here come to the idea that I try to extend, unmount and remount as I usually did on the Linux.
Read more »
We see the growth in the market to be more aggressive for consolidation in the data center for both physical and virtual server from time to time. There are plenty of solutions in place allow blade to support virtualization today such as virtual connect from HP, pass through module, infiniband integration Xsigo, Cisco UCS and etc. This had significant resolved the I/O interfaces require per blade to host the virtualization host server. CPU and memory per blade and significant increase with the latest release from all the major server vendors, the CPU, memory and disk I/O are no longer the concerns for virutalization.
Read more »
You can easily found “how to reset the root password on ESX” articles on the web for an example VMware KB article 1317898, xtravirt, or Petri.
However, unauthorized entry into single user mode is a risk. For security enhancement, you should enable password protect GRUB and enable root password for single user mode on vSphere 4.
How To Enable Root Password for Single User Mode on vSphere 4
- Login to vSphere server as root
- Edit /etc/inittab file
- # vi /etc/inittab
- Insert “~~:S:wait:/sbin/sulogin” and reboot
What is this mean?
man inittab shows
id:runlevels:action:process
id = is a unique sequence of 1-4 characters which identifies an entry in inittab
runlevels = lists the runlevels for which the specified action should be taken
action = describes which action should be taken.
process = specifies the process to be executed.
S = Single user mode
wait = The process will be started once when the specified runlevel is entered and init will wait for its termination.
- You should be able to see password prompt during single user mode boot up
Read more »
With the recent experience I had on the deployment with vSphere 4 and PowerVault MD3000i, I found there are plenty of room you may able to further fine tune to improve the performance of the storage and virtual infrastructure. Before this, the initial deployment was done by default configuration without any fine tune yet, and I found that the storage performance looks little bit slow. Therefore, I had decided to further research and fine tune everything we had to improve the performance.
Equipment List
- 2 x R710 with Intel 5530
- 2 x PowerConnect 5424
- MD3000i with 15 SATA Disks
- Software ISCSI initiator from vSphere 4
Read more »
Many of you may had noticed the changes in vSphere 4 if you had previously implemented or managed any of the virtual environment running vmware infrastructure. VMware had converted every license file we previously own to a new license key which allow us to apply to the vSphere hosts we had in our environment. If you had sign up the SNS previously, you will be entitled for an upgrade and under the license portal of your official log in ID that previously register with the license you bought, you will notice the new licenses key provided once you log on. Generally, the way of managing the CPU licenses will no longer be the previos method as we did in ESX 3.5.
