Revision 521 – Dump-Config for ESX HBAs to Check PHC

In revision 521, I added the ability to dump out the esx hbas as esxhbas.csv, esxhbas.xml, vminventoryraw.csv, or vminventoryraw.xml similar to dumping roving.xml and roving.csv. The outputs are self-documenting in #comments in the CSV, or as XML self-documents already. The benefit of this function is that when the PHC seems to miscalculate the HBA speeds in phc-vm.csv, the raw data can be debugged. Note that the XML has no whitespace, so “xmllint -format esxhbas.xml” is your friend.

For example:

(typically running locally: the MySQL is configured to only accept local connections)

java -jar vict.jar -D esxhbas.csv

or

java -jar vict.jar -D esxhbas.xml

…and in long-options too:

java -jar vict.jar --dump-config esxhbas.xml

…but since the JRE is typically hidden below the VirtualWisdom directory, use vict.bat:

VICT.BAT -D esxhbas.xml

VICT.BAT --dump-config esxhbas.xml

Revision 424 – Dump Current Detected VMs

In revision 424, similar to 423 wherein I added the ability to dump out detected ESXs, I added the ability to dump out the virtualserver table as vm.csv or vm.xml. The outputs are self-documenting in #comments in the CSV, or as XML self-documents already. Note that the XML has no whitespace, so “xmllint -format vm.xml” is your friend.

For example:

(typically running locally: the MySQL is configured to only accept local connections)

java -jar vict.jar -D vm.csv

or

java -jar vict.jar -D vm.xml

…and in long-options too:

java -jar vict.jar --dump-config vm.xml

…but since the JRE is typically hidden below the VirtualWisdom directory, use vict.bat:

VICT.BAT -D vm.xml