WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple

Upcoming vSphere.Next Features Hinted in vSphere 4.1 APIs?

08.03.2010 by William Lam // 2 Comments

Back in December, I created a VTMN document - How to browse the internal vSphere APIs which shows you how to access some of the undocumented vSphere API properties and methods. This was done prior to vSphere 4.1 release, but by looking at the python SDK stubs located on an ESX or ESXi host, you can see some of the some of the upcoming features that would eventually be released in vSphere 4.1.

Here is a look at some of these features found in the vSphere 4.0 SDK stubs:

Features known:

API STRING FEATURE
vim.version.drs Distributed Resource Scheduler
vim.version.dvs Distributed Virtual Switch
vim.version.ft Fault Tolerance
vim.version.ipv6 IPv6

Features eventually known:

API STRING FEATURE
vim.version.iorm I/O Resource Management what is now known as Storage I/O Control or SIOC

Features unknown:

API STRING FEATURE
vim.version.fed Unknown - (Federation?)
vim.version.lc Unknown - (Related properties in API referenced Linked Clones)
vim.version.logan Unknown - (Related properties in API referenced MediaAnalysisManager
vim.version.policy Unknown - (Rrelated properties in API referenced PolicyManager
vim.version.svm Unknown - (Rrelated properties in API referenced svmVmxDiskCopy)
vim.version.uber Unknown

Now, looking at vSphere 4.1 SDK stubs, I noticed a slew of new "potential" features that VMware is or maybe working on:

vim.version.cvp - ?unknown? (Client Virtualization Platform? below are properties and methods associated with this feature)

  • SetDisplayTopologyModes
  • VirtualMachinePowerPolicyPowerMode
  • VirtualMachinePowerPolicyCpuMode
  • requestedReplicationCanBeDeferred
  • userAllowedToDeferReplication
  • policyCacheLifetime

vim.version.dev - ?device? (below are properties and methods associated with this feature which seem to be related to FCoE support with vSphere)

  • DiscoverFcoeHbas
  • FcoeConfigFcoeSpecification
  • removeFcoeHba
  • userAllowedToDeferReplication

vim.version.h20 - (unknown, but related properties in API referenced PropertyProviderManager)

  • InternalPropertyProviderManager

vim.version.hbr - ?unknown? (Host Based Replication? below are properties and methods associated with this feature)

  • hostBasedReplicationSupported

vim.version.vcp - ?unknown? (VM Component Protection? below are properties and methods associated with this feature)

  • ClusterVmComponentProtectionSettings
  • ClusterVmComponentProtectionSettingsFtVmReaction

What you see here are not just string text found in the SDK stubs, these features are actually implemented in the current release of vSphere 4.1. Though undocumented, if you can reverse engineer where these methods and properties are located, you can actually execute them.

Here is an example of executing discoverFcoeHbas method via the MOB which is part of the Host's StorageSystem:

I am no fortune teller, but I suspect we may see some of these features much sooner than later 😉

Categories // Uncategorized Tags // cvp, fcoe, vSphere 4.1

vSphere 4.1 Is the Gift That Keeps On Giving

07.23.2010 by William Lam // 3 Comments

While doing some testing on ghettoVCB earlier this week, I noticed a new command line argument to vmkfstools utility called "--fix" in vSphere 4.1. From the man pages for vmkfstool, it states the following:


-x, --fix -[check|repair]
This option will check and/or repair the virtual disk in case of an unclean shutdown.

Here is an example of running the command against a VM's VMDK:

[root@esx4-1 ~]# vmkfstools --fix check /vmfs/volumes/esx4-1-local-storage-1/dummy/dummy.vmdk
Disk is error free

What surprised me next while looking up this new parameter in the man pages, I discovered another new argument called "--miscop":


-J, --miscop [setuuid | getuuid]
´setuuid´ option creates a unique identifier (UUID) for the
virtual disk and stores the UUID in the descriptor file of the
virtual disk. If the descriptor file already contains a UUID,
it will be overwritten with a new one. Please make sure that the
virtual disk does not have a UUID before using this option.
´getuuid´ option displays the UUID of the virtual disk.

The "--miscop" command is listed in the man pages but is not displayed when running "vmkfstools --help".

At this point, I thought there might be more hidden commands that VMware is holding out on us. I decided to use a well known UNIX/Linux utility called "strings" which looks for printable string in files and apply that to the vmkfstools binary. After sifting through the massive output, I found the following additional command line parameters that are not documented:

  • dumpfs
  • numfiles
  • force
  • recursivelock
  • recover
  • vmfsscan
  • physicalmapping
  • logicalmapping
  • allocateblock
  • clearlazyzero
  • parseimage
  • createarro
  • createmirrordisks
  • createmultiextent
  • trackvdisk
  • activehosts

Here are some of the command syntax which I have been able to verify:

dumpfs can be used by specifying either "-D | --dumpfs" and specifying a VMFS volume, file or folder.


[root@esx4-1 ~]# vmkfstools -D /vmfs/volumes/esx4-1-local-storage-1/

Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
Addr <4, 0, 0>, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576

[root@esx4-1 ~]# vmkfstools --dumpfs /vmfs/volumes/esx4-1-local-storage-1/

Lock [type 10c00001 offset 4292608 v 33, hb offset 3440640
gen 11, mode 0, owner 00000000-00000000-0000-000000000000 mtime 2509]
Addr <4, 0, 0>, gen 1, links 4, type dir, flags 0, uid 0, gid 0, mode 1755
len 1260, nb 1 tbz 0, cow 0, zla 1, bs 1048576

activehosts can be used by specifying "--activehosts" and specifying a VMFS volume


[root@esx4-1 ~]# vmkfstools --activehosts /vmfs/volumes/esx4-1-local-storage-1/
Found 1 actively heartbeating hosts on volume '/vmfs/volumes/esx4-1-local-storage-1/'
(1): MAC address 00:50:56:92:3f:86

For the other parameters, I have not been able to figure out the additional arguments to make them work. If anyone or VMware has further insight into these other options, I would love to know what they are used for.

Categories // Uncategorized Tags // vmkfstools, vSphere 4.1

Script: Updated ghettoVCB and ghettoVCBg2 to Support vSphere 4.1

07.22.2010 by William Lam // 21 Comments

Check out the latest update to both ghettoVCB and ghettoVCBg2, which now supports vSphere 4.1! There are no new features introduced with these updates but ghettoVCB does include additional logging and debugging functionality to help identify issues that may arise. Unfortunately, with ghettoVCBg2 I had to perform some additional code changes due to undocumented changes in vMA's vi-fastpass Perl library. This initially caused the script to break and the reason was deprecated methods that were removed in the latest release of vMA 4.1. Luckily the fix was not too bad and I had to spend a few hours looking at the new methods that were implemented.

Hopefully everyone enjoys these two releases and if you run into any troubles, please post in respective script's forum.

Categories // Uncategorized Tags // ghettoVCB, ghettoVCBg2, vSphere 4.1

  • « Previous Page
  • 1
  • …
  • 7
  • 8
  • 9
  • 10
  • 11
  • …
  • 14
  • Next Page »

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025