Category Archives: Virtualization

VMware Installation Bundle

VMware uses a file package called a VIB (VMware Installation Bundle) as the mechanism for installing or upgrading software packages, drivers on an ESX server.

The file may be installed directly on an ESX server from the command line or we can deploy using VMware update manager. Here I am going to mention about the command line method of doing the upgrade.

Install or update a patch/driver on the host using these esxcli commands:

COMMAND LINE INSTALLATION

New Installation

For new installs, you should perform the following steps, Issue the following command (full path to the file must be specified):

esxcli software vib install -v {VIBFILE} or esxcli software vib install -d {OFFLINE_BUNDLE}

Upgrade Installation

The upgrade process is similar to a new install, except the command that should be issued is the following:

esxcli software vib update –v {VIBFILE} or esxcli software vib update -d {OFFLINE_BUNDLE}

Notes:

To install or update a .zip file, use the -d option. To install or update a .vib file use the -v option.
The install method has the possibility of overwriting existing drivers. If you are using 3rd party ESXi images, VMware recommends using the update method to prevent an unbootable state.
Depending on the certificate used to sign the VIB, you may need to change the host acceptance level. To do this, use the following command: esxcli software acceptance:
esxcli software acceptance set –level=

esxcli commands

Show ESXi version and build:
esxcli system version get
vmware -v

Enter Maintenance Mode:
esxcli system maintenanceMode set –enable yes

Exit maintenance Mode:
esxcli system maintenanceMode set –enable no

List only advanced settings that have been changed from the system defaults:
esxcli system settings advanced list –d

List only kernel settings that have been changed from the system defaults:
esxcli system settings kernel list –d

List / Change / Test SNMP:
esxcli system snmp get | hash | set | test

List VMs on the ESXi server with the World ID
esxcli vm process list

Kill a VM
esxcli vm process kill –t soft -w WorldID

Install updates and drivers on a ESXi host (make sure the ESXI host is MaintenanceMode)
esxcli software vib install -d /vmfs/volumes/VMFS01/patches/nameoftheupdate.zip

List physical NICs and connection state
esxcli network nic list

List network information for the VM
esxcli network vm list

List the devices currently controlled by the VMware NMP Multipath Plugin and show the SATP and PSP information associated with that device
esxcli storage nmp device list

List VAAI properties for devices currently registered with the PSA.
esxcli storage core device vaai status get

Change the default pathing policy to Round Robin
esxcli storage nmp satp set –default-psp VMW_PSP_RR –satp youre_satp_policy

about Dom0

Dom0, or domain zero to expand the abbreviation, is the initial domain started by the Xen hypervisor on boot. The Xen hypervisor is not usable without Domain-0 (“dom0”).
The dom0 is essentially the “host” operating system (or a “service console”, if you prefer). As a result, it runs the Xen management toolstack, and has special privileges, like being able to access the hardware directly.
It also has drivers for hardware, and it provides Xen virtual disks and network access for guests each referred to as a domU (unprivileged domains). For hardware that is made available to other domains, like network interfaces and disks, it will run the BackendDriver, which multiplexes and forwards to the hardware requests from the FrontendDriver in each DomU.

tc limit incoming bandwidth openvz

DEV=venet0
tc qdisc del dev $DEV root
tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 100mbit
tc class add dev $DEV parent 1: classid 1:1 cbq rate 256kbit allot 1500 prio 5 bounded isolated
tc filter add dev $DEV parent 1: protocol ip prio 16 u32 match ip dst X.X.X.X flowid 1:1
tc qdisc add dev $DEV parent 1:1 sfq perturb 10