Archive

Archive for August, 2010

Understanding Storage Device Naming

August 27th, 2010 4 comments
In the vSphere Client, each storage device, or LUN, is identified by several names, including a friendly name, a UUID, and a runtime name.
 
Name
This is a friendly name that the ESXi host assigns to a device based on the storage type and manufacturer. You can modify the name using the vSphere Client. When you modify the name of the device on one host, the change takes affect across all hosts that have access to this device.
 
Identifier
This is a universally unique identifier assigned to a device. Depending on the type of storage, different algorithms are used to create the identifier. The identifier is persistent across reboots and must be the same for all hosts sharing the device.
 
Runtime Name
This is the name of the first path to the device. The runtime name is created by the host, is not a reliable identifier for the device, and is not persistent.
The runtime name has the following format: vmhba#:C#:T#:L#.
vmhba#
The name of the storage adapter. The name refers to the physical adapter on the host, not to the SCSI controller used by the virtual machines.
 
C#
The storage channel number. Software iSCSI initiators use the channel number to show multiple paths to the same target.
 
T#
The target number. Target numbering is decided by the host and might change if there is a change in the mappings of targets visible to the host. Targets that are shared by different ESXi hosts might not have the same target number.
 
L#
The LUN number that shows the position of the LUN within the target. The LUN number is provided by the storage system. If a target has only one LUN, the LUN number is always zero (0).
For example, vmhba1:C0:T3:L1 represents LUN1 on target 3 accessed through the storage adapter vmhba1 and channel 0.
 
Source –  ESXi Configuration Guide
Share
Categories: Storage Tags:

Understanding VMDirectPath I/O

August 26th, 2010 No comments

What is VMDirectPath I/O

VMDirectPath I/O is a VMware technology that can be used with I/O hardware to reduce the CPU impact of high-bandwidth throughput workload's by ‘‘bypassing’’ the hypervisor. It is supported for specific networking adapters in vSphere ESX 4, and it is experimental for specific storage adapters in vSphere ESX 4.

By allowing virtual machines to directly access the underlying hardware devices, VMDirectPath I/O device access enhances CPU efficiency in handling workload's that require constant and frequent access to I/O devices. VMDirectPath I/O for networking I/O devices is fully supported with the Intel 82598 10 Gigabit Ethernet Controller and Broadcom 57710 and 57711 10 Gigabit Ethernet Controller.

Prerequisites

1. To use VMDirectPath, verify that the host has Intel® Virtualization Technology for Directed I/O (VT-d) or AMD I/O Virtualization Technology (IOMMU) enabled in the BIOS. Refer to my earlier post.
2. Verify that the PCI devices are connected to the host and marked as available for passthrough.
3. Verify that the virtual machine is using hardware version 7.

 

Drawbacks

Use of the VMDirectPath disables many advanced VMware functions for the virtual machine, so be careful before you start using VMDirect Path. 
1. VMotion
2. High availability
3. Suspend and resume
4. Record and replay
5. Fault tolerance
6. Memory overcommitment and page sharing
7. Hot add/remove of virtual devices

8. No Snapshot backup

Few Good links about VMDirect Path I/O

1. A video is posted here by chad which will show you step by step instructions. All though this link is for Cisco Unified Computing (UCS) but still     it will help –  Link
2. VMware VMDirect Path I/O by Simon Long
3. To check for device compatibility please visit here
4. Configure VMDirect Path article 1010789
5. Troubleshooting VMDirect Path
6. http://communities.vmware.com/docs/DOC-11089
7. Scott Lowe blog about VMDirect Path

 

Share
Categories: Uncategorized Tags:

Determining if Intel Virtualization Technology or AMD Virtualization is enabled in the BIOS without rebooting

August 25th, 2010 No comments

Without rebooting the server if you need to check whether the server has VT technology enabled in the BIOS you can use the following cmd

esxcfg-info|grep “HV Support”

Refer to kb article –  1011712

 

Tags: ,
Share
Categories: Uncategorized Tags:

Copy and Paste option is disabled in vSphere Client 4.1

August 24th, 2010 No comments

Now that is bad, we cannot copy and paste from the virtual machine remote console to the system in which the vSphere client is installed

KB article –  1026437 

Share
Categories: Uncategorized Tags:

Types of Disks format in VMware Environment

August 24th, 2010 No comments

VMware products have different kinds of disks. Some are compatible with ESX some are not. To make them compatible we have to use tools like converter OR vmkfstools

1) Zeroedthick (default) –  This is the default type of disk format. All the space is allocated at creation time. Any data remaining on the physical device is not erased during creation, but is zeroed out on demand at a later time on first write from the virtual machine. These types of disks are less secure because their disk blocks are not being cleared of previous data. The performance may not be great at first write because the disk needs to be zeroed before the data can be written.

2) Eagerzeroedthick –  Space required for the virtual disk is allocated at creation time.Since the data remaining on the physical device is zeroed out during creation, it takes longer time to create this disk. These disks are the most secure and, because the block has already been cleared of previous data, offer slightly better performance on the first write of data to a disk block.

3) Thick disks –  Space required for the virtual disk is allocated during creation. This type of formatting does not zero out any old data that might be present on this allocated space.

4) Thin Disk –  Space required for the virtual disk is not allocated during creation, but is supplied and zeroed out, on demand at a later time.

5) RDM –  Virtual compatibility mode for raw disk mapping

6) RDMP –  Physical compatibility mode (pass-through) for raw disk mapping

7) RAW –  Raw device

8) 2bgsparse disk –  2bgsparse divides a disk into multiple disks with a maximum size of 2 GB per disk. You can use disks in this format with other VMware products like Workstation, Server. You cannot use this type of disks in ESX server. You will have to import them with the help of converter OR vmkfstools 

9) monosparse – A monolithic sparse disk. You can use disks in this format with other VMware products.

10) monoflat – A monolithic flat disk. You can use disks in this format with other VMware products.

 

The above information is from VMware's kb article 1022242

Share
Categories: Uncategorized Tags:
# this line was added by me, vcpguy to make the Syntaxhighlighter evolved work !!!