On the VMTN forum I read a cool solution for clearing your update cache when you use a web repository for patching your ESX hosts: “yum clean all”. Never thought of that cause I hardly use a web repository, always use a VMFS volume and the vmprofessional script.
When looking for the “maximum number of allowed console connections, I stumbled upon another handy option in VirtualCenter, “Edit -> Client Settings”.
- Set the maximum number of allowed console connections (0 to 100) to all virtual machines.
- Close all “Getting Started” tabs at once.
I’ve been looking for the lockdown option in ESX 3.5 for a few of hours these last couple of days and can’t seem to find it. In ESX 3i you can easily put it in lockdown mode when you add the host to the Cluster or afterwards here in the configuration/security section:
After a search on the internet is seemed I wasn’t the only that could not find the lockdown mode for 3.5. Viktor van den Berg opened a topic about it on the Dutch VMUG forum and decided to phone VMware about it… There answer was short, it’s not in 3.5 and it should have been. I guess it got lost in cyberspace.
For those who never heard of the lockdown mode:
VirtualCenter 2.5 provides administrators with the option to disable direct remote access to ESX Server 3 hosts as a root user after VirtualCenter 2.5 has taken control of a given host. This is called “lockdown mode.” Enabling this mode ensures that the host is managed only through VirtualCenter 2.5. Certain limited management tasks can still be performed while in lockdown mode by logging in to the local console on the host as a non-root user.
I guess we just have to wait for the upcoming patches.
As most of you know, when VMware Consolidated Backup dumps image level backups VCB only dumps used diskspace. Unfortunately for us VCB does this by checking at block level if it contains only zero’s or not. If it contains only zero’s the block is considered empty, but an Operating System doesn’t zero out the disk space that contained the files when a file is deleted. An Operating System only clears the pointers to these files. This is why you could have a disk with only 4GB of used space and a 6GB VCB dump. As of ESX 3.0.2 update 1 VMware reintroduced the shrink option in VMware Tools. Kind of a weird name “shrink” cause the vmdk doesn’t actually shrink, the unused space is just zeroed out.
I’m not the only one who thinks that the Storage VMotion interface is a burden. A couple of scripting wizards started creating a decent interface for the Storage VMotion script, which definitely come in handy. Check them out:
- Dominic of VMProfessional created an additional perl script to make storage vmotion a bit easier. It works very simple just edit the script to include your VC url, username, password, cluster and Datacenter, then you will be prompted with a list of VMs to choose from, and a list of target datastore to choose from. Check it out at his website, VMProfessional.
- ASP24 created a PHP website with some easy to use dropdown boxes. It’s hosted on the VMware VMTN forum. I did not had the opportunity to test it by the way.