SRM version 4 had officially released and ready to download from VMware Official Website. Before this, users with SRM will not able to upgrade to vSphere 4 due to the SRM compatible. Now you will be excited to upgrade your existing ESX 3.5 to vSphere 4 with SRM 4. You can read more about SRM 4 from here. You can download the latest copy of SRM 4 from here.
Most of us may had previously experienced a VM which hung in the ESX hosts. Usually we will use the command vmware-cmd utilities to kill or stop the virtual machine. Sometimes we even need to use the vm-support command to force the VM to be stop hardly if vmware-cmd was not worked. Today I found some interesting issue with 1 of the virtual machine. I had executed the instruction to power off from vCenter 4. This virtual machine is running on vsphere 4. After 2 minutes, the virtual machine still showed power on from the vCenter, and I executed again the 2nd command to power off, the system prompted that another process was in progress, and access was denied.
As my previous experienced, if you having a disk space full on /var, the host server will getting an error message such as “A general error occured : Failed to create journal File provider” when creating a new virtual machine. 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.
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.
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
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.
Copyright © 2009 Malaysia VMware Communities | Subscribe RSS Feed
