I/O Analyzer

http://labs.vmware.com/flings/io-analyzer

I/O Analyzer is a virtual appliance solution by VMware that provides a simple and standardized way of measuring storage performance in a VMware vSphere virtualized environments. I/O Analyzer automates the traditional storage performance analysis cycle and reduces the performance diagnosis time from days to hours.

Features

• Integrated framework for storage performance testing
• Readily deployable virtual appliance
• Easily configure and launch I/O tests on multiple hosts
• View integrated performance results at both guest and host levels
• Easily export performance data for off-site analysis

CPU Ready Time

vCPU waits for pCPU

Live port migration

Live port migration means a stand alone dvport can be moved to a dvportgroup and thus acquiring the all the configuration of the dvportgroup and a dvport which is a part of a dvportgroup can be moved out from a dvportgroup, the subsequent config changes to the dvportgroup does not apply to this dvport.

echo -n 'y\ny' | ./shell.sh

This echo will answer two y separated by new line, which is asked by shell.sh. This is even nice than expect

Nice trick from http://www.van-lieshout.com/2009/03/unattended-upgrade-of-hp-management-agents/

Windows on iSeries

http://as400bks.rochester.ibm.com/iseries/v5r2/ic2924/info/rzahq/rzahq.pdf

The Integrated xSeries Server for iSeries is essentially a PC on a card. It contains an Intel processor and
memory. You install it in iSeries much like a memory upgrade. Similarly, the Integrated xSeries Adapter for
iSeries is an HSL bus adapter plugged into a supported Netfinity or xSeries Server. The Netfinity or
xSeries Server appears as an HSL attached expansion unit to the iSeries system.

Virutal Windows disks are provided by iSCSI storage

IBMi ~ i5/OS ~ OS/400 or OS/400 LPAR on iSeries is required for this purpose

Unix Virtualization

http://en.wikipedia.org/wiki/Hypervisor

LPAR  Logical partition:

IBM Mainframe: (Sytem Z , System i)

IBM midrange iSeries and pSeries

IBM PowerVM, Power Hypervisor: provides industrial-strength virtualization for AIX®, IBMi,and Linux environments on IBM POWER®processor-based systems.

Solaris LDOMs virtualization on SPARC: (Oracle VM Server for SPARC, now)

Sun Logical Domains or LDoms is a full virtual machine that runs an independent operating system instance and contains virtualized CPU, memory, storage, console, and cryptographic devices. This technology allows you to allocate a system resources into logical groupings and create multiple, discrete systems, each with their own operating system, resources, and identity within a single computer system.  

Supported Guest OS:

• Solaris 10 11/06 or later
• OpenSolaris 2009.06 release
• Ubuntu Linux Server Edition
• OpenBSD 4.5 or later
• Wind River Platform for Network Equipment, Linux Edition

HP vPAR at VSE (Virtual Server Environment) HPUX on HP9000 and HP Integrity 


vPars are separate operating system instances on the same nPartition or server. This offering lets you dynamically move either CPU or memory resources between partitions as the workload requirements change. They also give you the ability to run multiple copies of HP-UX on the same hardware.


nPar partitions are electrically isolated from other nPar partitions within the same chassis. Cells (a unit of processors/IO/memory) make up nPar partitions. Being electrically isolated means that if a nPar partition were to fail due to hardware failure, then the other nPar partitions would continue to work. This is contrasted with vPar partitions which exist within nPar partitions in which a failure at the hardware level for a nPar would affect all vPars within that nPar.

It's important to note that while nPartitions support HP-UX, Windows®, VMS, and Linux, they only do so on their Itanium processor, not on their HP9000 PA Risc architecture.

Openfiler 2.3 ESX VM version bug

After the openfiler is reboot, the iSCSI targets could not be reachable, and you will need to remap (unmap and map) LUN with LUN path.

This has been reported, and there was a fix for this at the wikipedia.

After rescanning path, the lost datastores might need to be re-added into ESX(i) by keeping the existing volume signature