vmfs-undelete utility is not available for ESX/ESXi 4.0
ESX/ESXi 3.5 Update 3 included a utility called vmfs-undelete, which could be used to recover deleted .vmdk files. This utility is not available with ESX/ESXi 4.0.

Workaround: None. Deleted .vmdk files cannot be recovered.

So if you are currently actively using vmfs-undelete and looking into upgrading to vSphere take this in account!

[update: Eric just tweeted 11 - 20 so I added these to the list]

1. Yellow Bricks – Duncan Epping(1) – 102 first place votes – weighted score of 991
2. Scott Lowe’s Blog – Scott Lowe(2) – 39 first place votes – weighted score of 707
3. Virtual Geek – Chad Sakac(10) – 61 first place votes – weighted score of 550
4. NTPro – Eric Sloof(3) – 12 first place votes – weighted score of 412
5. RTFM Education – Mike Laverick(8) – 5 first place votes – weighted score of 232
6. VM/ETC – Rich Brambley(6) – 5 first place votes – weighted score of 196
7. Virtualization Evangelist – Jason Boche(5) – 4 first place votes – weighted score of 190
8. Gabe’s Virtual World(12) – Gabe Van Zanten – 5 first place votes – weighted score of 132
9. Virtualization Pro – Various(4) – 3 first place votes – weighted score of 129
10. Mike D’s blog – Mike DiPetrillo(7) – 3 first place votes – weighted score of 120
11. VMware Tips – Rick Scherer(15)
12. The VM Guy – Dave Lawrence(16)
13. VCritical – Eric Gray(17)
14. Planet VM – Tom Howarth(11)
15. Ken’s Virtual Reality - Ken Cline(20)
16. Professional VMware – Cody Bunch(09)
17. Virtual Future – Sven Huisman (19)
18. Rational Survivability – Christofer Hoff(13)
19. Virtual Black Hole – Steve Beaver(18)
20. Musings of Rodos – Rodney Haywood(14)

Description: Managing VMware Fault Tolerance via the command line.

Params: The following operations are supported: create|enable|disable|stop

Requirement:
vSphere vCenter 4.0
ESX(i) 4.0
Advanced, Enterprise, Enterprise Plus or Eval licensing

Assumption: Your environment is FT capable and is configured properly

I think it speaks for itself. If you are a command line guy this is really useful! Great work William, keep it up! Just head over to the VMTN Communities for the download link and more details on how to use it.

Anyone know if you can change the default VMFS block size in ESX4 during interactive installation?

This is something that I also ran into personally a couple of weeks ago. If you install ESX 4.0 with the defaults a large VMFS volume is created that fills up the disk. This VMFS volume has a default block size of 1MB which means a file size limit of 256GB.

In the setup there’s currently no way of changing the block size. (If I’m wrong please leave a comment.) The only way to avoid this is to create two VMFS volumes. The first one will need to be created during the installation and will be the volume on which the Service Console VMDK resides. The second VMFS volume should be created after the installation and will be hosting the VMs. Although it does sound like an unnecessary step I personally think it is a good approach. This way the chance of filling up(snapshots) your VMFS partition which hosts you Service Console is very slim.

Latest Version: 2.5.5 | June 27, 2009
Download | Documentation

Release notes:
Version 2.5.5 (June 27, 2009)
Changed health check properties are not set at start of the program. The program will use the default values until you start and transmit the properties screen. This problem is now fixed.

Since version 2.5 the vDisk tab displays information that is aggregated from “config.hardware” and “guest” information. That was not a good idea! If there is more than one partition on a virtual disk the displayed information is wrong. To solve this problem I now split this information in a vDisk tab which will show only the information that is provided by the “config.hardware” information and a new vPartition tab that will display the “guest” information.
Better exception handling on filter.

New fields on vHost tab: Number of CPUs, Cores per CPU and virtual CPUs per Core.

For those who are using this awesome tool, there’s a donate button and of course there are other ways to  give Rob some credits . Visit Robware.net

With the release of vSphere VMware introduced a new hardware level for VM’s. De upgrade process to the new hardware level is already described on Scott Lowe’s blog: http://blog.scottlowe.org/2009/06/01/vsphere-virtual-machine-upgrade-process/.

I wanted to see if I could script this process with PowerCLI. My first goal was to upgrade al my templates.

The script does the following:

• Export template names to CSV
• Convert templates back to VM’s
• Check the vHardware version of the VM. If the hardware version is version 4 start the VM
• When the VM is ready check the VMware Tools version. If the VMware Tools are old, the script will install the new version.
• When the VMware Tools are Ok the VM gets a shutdown.
• When the VM is down, the vHardware will be upgraded
• The final step is converting the VM back to a template.

I stripped out the link to his script, please visit the source article and download the script over there.

VI (VSphere) Java API 2.0 was GAed last night. The 2.0 release represents 6 months of continuous (after work) engineering effort since this January. It has packed many features:

New high performance web service engine. When I told people that we replaced AXIS, most of them wanted me to confirm what I said. The new engine is 15X faster in loading, 4+X in de-serialization than AXIS 1.4 with only 1/4 of size.

• vSphere 4 support.
• REST client API.
• Caching framework API.
• Multiple version support with single set of APIs.
• Clean licenses. The API and dependent dom4j are all BSD licenses.

The open source project was sponsored by VMware but not supported by VMware. To download it, visit http://vijava.sf.net


for N_PATHS in 2 4 6 8; do
# These are the LUNs with N_PATHS:
LUN_LIST=`esxcfg-mpath -l | egrep "^Disk.+has $N_PATHS paths" | awk '{print $2}'`
N=1
for LUN in $LUN_LIST; do
echo "LUN: $LUN, Counter: $N, Possible paths:"
esxcfg-mpath -q --lun=$LUN | grep "FC" | awk '{print $4}'
# Take the Nth path for this LUN
LUN_NEWPATH=`esxcfg-mpath -q --lun=$LUN | \
grep "FC" | awk '{print $4}' | head -n $N | tail -n 1`
# Make the Nth path the preferred path
esxcfg-mpath --lun=$LUN --path=$LUN_NEWPATH --preferred
echo ""
# Increase N (within the limit)
N=$(($N+1))
if [ $N -gt $N_PATHS ]; then
N=1
fi
done
done


Thanks for sharing,

Or as VMware puts it:

VMware Studio provides mechanisms for authoring, on-site management, distributing and deployment of production-ready virtual appliances. ISVs, hardware appliance vendors, and developers use VMware Studio to configure and package their solutions in a standards-based Open Virtualization Format (OVF). VMware Studio also enables software providers and developers to leverage the industry’s leading virtualization platform, VMware Infrastructure, and offers built appliances all the great management services that VMware Infrastructure delivers.

New features:

• Windows Support (32 bit and 64 bit) 2003 & 2008 Server
• Create multi-VM vApp and multi-VM VA
• 64 bit support for SLES 10.2, RHEL 5.2 & 5.3, CentOS 5.2 & 5.3
• Extensible in-guest Management Framework
• OVF 1.0 support
• Eclipse Plugin
• Enable ESX, ESXi, VC, Server 2.0 and Workstation as provisioning engine
• Automatic Dependency Resolution (Static)
• Publish OVF to VC
• Infrastructure enhancements – GUI and Builds
• Studio-created VM as Input

VMware Studio 2.0 will be available on Monday! Better make sure to get it while it’s hot… even vStu is excited!

There’s more info to be found here.