Professional Documents
Culture Documents
Vmwareinterviewqa 1 PDF
Vmwareinterviewqa 1 PDF
10
11
/home
/tmp
ext3
ext3
/vmimages ext3
1600MB
The swap partition is used to supplement RAM if the service console runs out
of physical memory.
512MB
2.0GB
512MB
12
ext3
ext3
2.0GB
260MB /boot stores the files necessary to boot the service console.
vmkcore 100MB
The vmkcore partition temporarily stores log and error information should the
VMkernel crash.
13
14
15
16
17
Resolution
Validate that each troubleshooting step below is true for your environment. The steps will provide instructions
or a link to a document, for validating the step and taking corrective action as necessary. The steps are
ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not
skip a step.
Verify that the reduced performance is unexpected behavior. When a workload is virtualized it is common to
see some performance reduction due to virtualization overhead. Troubleshoot a performance problem if you
experience the following conditions:
18
19
20
21
22
23
24
25
26
27
28
29
30
Resolution
A VMware product may behave unexpectedly if the operating system on which it is installed is experiencing
problems. Follow the section that matches your operating system.
Note: If you perform a corrective action in any of the following steps, determine if the problems initially
encountered are still being experienced.
Common Windows Problems
Verify there are no problems with the filesystem by performing a disk check on your hard drives. For more
information, see Performing a disk check (1004003).
Performing a disk check
Symptoms
VMware Workstation unrecoverable error: (vcpu-0)
Exception 0xc0000006 (disk error while paging) has occurred.
Purpose
This article describes how to perform a disk check. This is required to address problems encountered with an
operating system as a result of file system errors. Problems can include data loss, virtual machine crashes,
slow performance, virtual machine resume and suspend failures, and other unexpected behaviour.
Resolution
Determine if there are problems with your file system by performing a disk check. A disk check can be done
by using a 3rd party application or by using tools native to your operating system.
The method of performing a disk check differs between operating systems. Refer to the section below that
matches your operating system.
Windows
Note: The exact procedure differs between versions of Windows. If one procedure below does not work try
the other. If neither method works, consult the manual for your version of Windows.
To perform a disk check from the user interface:
Double-click the My Computer icon.
Right-click the entry for your local disk.
Click Properties.
Click the Tools tab.
Click Check Now.
Select Scan for and attempt recovery of bad sectors.
Click Start.
To perform a disk check from a command line:
Open a command prompt. For more information, see Opening a command or shell prompt (1003892).
Type chkdsk c: /r and press Enter.
Note: If the local disk being scanned is not c: , replace c: with its drive letter.
31
Defragmenting a disk
Purpose
This article describes how to defragment a disk. Defragmenting a disk is required to address problems
encountered with an operating system as a result of file system fragmentation. Fragmentation problems
result in slow operating system performance.
Resolution
Determine if fragmentation of your file system is causing problems by defragmenting.
Note: Linux file systems do not require disk defragmentation and Mac OS performs disk defragmentation as
required. To manually defragment a disk in either of these operating systems, a 3rd party application is
required.
Defragmenting a disk under Windows
This can be done by using a 3rd party application or by using tools native to Windows. If you have more than
one hard drive, perform the defragmentation on each hard drive.
Note: The exact procedure differs between versions of Windows. If one procedure does not work, try the
other. If both do not work, consult the manual for your version of Windows.
To defragment a disk from the user interface:
Double-click the My Computer icon.
Right-click the entry for your local disk.
Click Properties.
Click the Tools tab.
Click Defragment Now.
Click Defragment.
To defragment a disk from a command line:
Open a command prompt. For more information, see Opening a command or shell prompt (1003892).
Type defrag c: and press Enter.
Note: If the local disk being defragmented is not c: , replace c: with its drive letter.
3. Check if there are sufficient resources in the following areas:
Memory
For more information, see Investigating operating system memory usage (1004014).
Disk
For more information, see Investigating operating system disk space (1004007).
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
Path status
Disk vmhba2:1:4 /dev/sdh (30720MB) has 2 paths and policy of Most Recently Used
FC 10:3.0 210000e08b89a99b<->5006016130221fdd vmhba2:1:4 On active preferred
FC 10:3.0 210000e08b89a99b<->5006016930221fdd vmhba2:3:4 Standby
Path status contains the status of the path.
There are six attributes that comprise the status:
On: This path is active and able process I/O. When queried, it returns a status of READY.
Off: The path has been disabled by the administrator.
59
Click Storage.
Click Properties.
60
From this example, you can see that the canonical name is vmhba2:1:0 and the true paths are vmhba2:1:0
and vmhba2:3:0 .
The active path is vmhba2:1:0 and the policy is Most Recently Used.
61
To change the policy, click Change in the Policy section. The Manage Paths - Selection Policy dialog appears.
62
63
64
65
66
67
68
69
70
71
In ESX 4.0:
Sep 24 05:05:07 system-name vmkernel: 0:00:01:25.953 cpu1:4097)NMP:
nmp_CompleteCommandForPath: Command <###>
(0x4100070dfa40) to NMP device "naa.60060160d56e1b000e696c75b9a8de11"
failed on physical path "vmhba1:C0:T0:L22" H:0x0
D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x1.
The option LVM.DisallowSnapshotLun is set to 1 (the default). Changing it to 0 and performing a rescan does
not return visibility to the content of the LUNs.
For more information, see VMFS Volume Can Be Erroneously Recognized as a Snapshot (6482648) .
The Navisphere manager reports that there are snapshots sessions of a source LUN in place and some of
them are currently inactive.
Those inactive sessions match the UUID of the missing data stores/RDMs.
In ESX 3.5, you can find these at /proc/vmware/scsi/vmhba1/X:Y.
In ESX 4.0, run this command:
esxcfg-scsidevs -l
4.b.2LUN detected as a snapshot because LUN presentation settings were incorrect (1002351) .
LUN detected as a snapshot because LUN presentation settings were incorrect
Details
Unable to see available datastores.
72
4.c
Verify that the data store is not being detected as a snapshot. For more information, see VMFS Volume
Can Be Erroneously Recognized as a Snapshot (6482648) .
VMFS Volume Can Be Erroneously Recognized as a Snapshot
Details
In some configurations, a VMFS-3 volume can be recognized as a snapshot even when it is not.
The problem was tracked to the following scenario:
Server A is presented LUNs 1, 2, and 3
The same LUNs are then presented to server B as LUNs 5, 6, and 7.
When a VMFS-3 volume is created on LUNs 1, 2, and 3 via server A, rescanning the SAN from server B results
in the latter complaining that volumes on LUNs 5, 6, and 7 are snapshots of those on LUNs 1, 2, and 3.
The vmkernel logs on server B show:
Jul 18 10:58:31 ServerB vmkernel: 0:14:17:59.787 cpu13:1046)LVM: 5670: Device vmhba1:0:5:1 is a
snapshot:
Jul 18 10:58:31 ServerB vmkernel: 0:14:17:59.787 cpu13:1046)LVM: 5676: disk ID: <type 2, len 22, lun 5,
devType 0, scsi 5, h(id) 10179760818951437974>
Jul 18 10:58:31 ServerB vmkernel: 0:14:17:59.787 cpu13:1046)LVM: 5678: m/d disk ID: <type 2, len 22,
lun 1, devType 0, scsi 5, h(id) 10179760818951437974>
Jul 18 10:58:31 ServerB vmkernel: 0:14:17:59.790 cpu13:1046)LVM: 5670: Device vmhba1:0:6:1 is a
snapshot:
Jul 18 10:58:31 ServerB vmkernel: 0:14:17:59.790 cpu13:1046)LVM: 5676: disk ID: <type 2, len 22, lun 6,
devType 0, scsi 5, h(id) 11552037668126695191>
Jul 18 10:58:31 ServerB vmkernel: 0:14:17:59.790 cpu13:1046)LVM: 5678: m/d disk ID: <type 2, len 22,
lun 2, devType 0, scsi 5, h(id) 11552037668126695191>
Jul 18 10:58:31 ServerB vmkernel: 0:14:17:59.794 cpu13:1046)LVM: 5670: Device vmhba1:0:7:1 is a
snapshot:
Jul 18 10:58:31 ServerB vmkernel: 0:14:17:59.794 cpu13:1046)LVM: 5676: disk ID: <type 2, len 22, lun 7,
devType 0, scsi 5, h(id) 13372428508588014685>
Jul 18 10:58:31 ServerB vmkernel: 0:14:17:59.794 cpu13:1046)LVM: 5678: m/d disk ID: <type 2, len 22,
lun 3, devType 0, scsi 5, h(id) 13372428508588014685>
If the Storage Processors are not configured as required for use with ESX Server (see corresponding vendor
for detailed configuration documents), it can result in this behavior.
Sample array misconfiguration that could result in this issue include:
Symmetrix:
73
74
75
76
77
Caution: This procedure can be time-consuming, depending on the size of the environment. Ensure that
you budget time for the outage.
Shut down all virtual machines running on the datastores recognized as snapshots.
Note: This step is necessary because those datastores are affected by the resignaturing process and it cannot
be applied to a datastore that is being used (that is, with active I/O).
Unregister all of the virtual machines on the affected datastore(s). This can be done from VI Client by rightclicking on the virtual machine and selecting Remove from Inventory.
Rescan.
Note: The /var/log/vmkernel file contains snapshot messages.
Enable LVM Resignaturing on the first ESX host:
Log in to the ESX host with VI Client.
Click the Configuration tab.
Select the Advanced setting option.
Choose the LVM section.
Set the value of LVM.EnableResignaturing to 1.
Save the change.
Click the storage adapter tab.
78
In this example, the highlighted datastore has 6 ESX hosts connected to it. This datastore is active and must
not be removed.
Perform a remove process in any other view to remove that active datastore.
Click the arrow next to the Inventory menu option and click Hosts & Clusters.
In the Summary tab, you see the list of datastores.
79
80
81
If Disk.MaskLUNs is not blank, this can account for missing LUNs. Removing all text from that field and
clicking OK removes all LUN masking from the ESX Server host side. This does not affect LUN masking
implemented on the array.
4.f
Verify that write caching is not disabled on the array. This is verified using the storage array management
interface. Consult your storage array vendor if you require assistance. Also, see: Write-cache disabled on
storage array causing performance issues or failures (1002282) .
Write-cache disabled on storage array causing performance issues or failures
Details
Poor disk I/O performance to the storage array, causing very slow or even failure of:
Template deployments
Cold migrations
VMotion
VMware Consolidated Backup
82
To correct this issue, change the partition type back to fb on all the LUNs that are supposed to be VMFS
datastores.
Warning: The following step must be performed only after creating backups as the result might lead to
complete data loss.
83
84
Rescan at this point and the volume appears on the ESX as VMFS datastore.
[root@localhost root]# esxcfg-rescan vmhba1
Additional Information
Troubleshooting flow chart:
85
86