VMware vsphere FAQ Rollup (17)

the . VMDK the redo log is corrupted problem solving idea

[vmware-] Environment: esxi5.0,vc5.0

Failure problem: After executing storage vmotion, the virtual machine error occurred.

Error message: XSSJ-000003.VMDK is corrupted.power off of the virtual machine. If The problem still persists, discard the redo log.

Jianti ideas:

"Cause of failure"

The VM failed to start because of an exception in the relationship between the snapshots:

vmware-34.log:2013-01-14t08:36:53.885z| Vmx| Disklib-chain: "/vmfs/volumes/50f13506-075ed29b-86b5-5ef3fd359eab/??? È??? 3???? 184/XSSJ-000005.VMDK ": Failed to open (the parent virtual disk have been modified 34.log:2013-01-14t08:36:53.886z| vmx| di sklib-lib:failed to open '/vmfs/volumes/50f13506-075ed29b-86b5-5ef3fd359eab/??? È??? 3???? 184/XSSJ-000006.VMDK ' with flags 0xa the parent virtual disk had been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child (18).

vmware-34.log:2013-01-14t08:36:53.886z| Vmx| Disk:cannot open Disk "/vmfs/volumes/50f13506-075ed29b-86b5-5ef3fd359eab/??? È??? 3???? 184/XSSJ-000006.VMDK ": The parent Virtual disk has been modified since, the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child (18).

vmware-34.log:2013-01-14t08:36:53.886z| Vmx| Msg_post:error

vmware-34.log:2013-01-14t08:36:53.886z| Vmx| [Msg.disk.nobackend] Cannot open the disk '/vmfs/volumes/50f13506-075ed29b-86b5-5ef3fd359eab/??? È??? 3???? 184/XSSJ-000006.VMDK ' or one of the snapshot disks it depends on.

vmware-34.log:2013-01-14t08:36:53.886z| Vmx| [Msg.disk.configurediskerror] reason:the parent virtual disk had been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child.

vmware-34.log:2013-01-14t08:36:53.900z| Vmx| Module Diskearly power on failed.

"Links between snapshots"

Normally, the original disk is associated with the snapshot through the parent content ID, and the parent content ID is also passed between the parents and the child snapshot, but now we look at the relationship between the original disk and the snapshot disk, and find that their CID and parentcid are confusing, The information is as follows:

Xssj.vmdk:cid=ba60eb23

Xssj.vmdk:parentcid=ffffffff

xssj-000001.vmdk:cid=27f8a456

Xssj-000001.vmdk:parentcid=ba60eb23

Xssj-000002.vmdk:cid=11ed1dac

xssj-000002.vmdk:parentcid=27f8a456

xssj-000003.vmdk:cid=2583a010

xssj-000003.vmdk:parentcid=2583a010

xssj-000004.vmdk:cid=2583a010

Xssj-000004.vmdk:parentcid=11ed1dac

Xssj-000005.vmdk:cid=4d38fabf

xssj-000005.vmdk:parentcid=2583a010

Xssj-000006.vmdk:cid=9402bf1a

Xssj-000006.vmdk:parentcid=a30d0e91

You can see that the relationship between this disk relationship from XSSJ.VMDK disk to XSSJ-000002.VMDK is not a problem.

The problem is that the snapshot Disk association after XSSJ-000002.VMDK is confusing.

With the following records, we can know the correct relationship between these disks:

Xssj-000001.vmdk:parentfilenamehint= "XSSJ.VMDK"

Xssj-000002.vmdk:parentfilenamehint= "XSSJ-000001.VMDK"

Xssj-000003.vmdk:parentfilenamehint= "XSSJ-000004.VMDK"

Xssj-000004.vmdk:parentfilenamehint= "XSSJ-000002.VMDK"

Xssj-000005.vmdk:parentfilenamehint= "XSSJ-000003.VMDK"

Xssj-000006.vmdk:parentfilenamehint= "XSSJ-000005.VMDK"

The data relationship between the disks should be:

Xssj.vmdkàxssj-000001.vmdkàxssj-000002.vmdkàxssj-000004.vmdkàxssj-000003.vmdkàxssj-000005.vmdkà Xssj-000006.vmdk

"Solutions"

The first part, confirming that the above data relationship is correct:

1. Connect to vcenter Server or ESXi server using vsphere Client

2. Turn off the virtual machine

If the virtual machine status is off, go to the ESXi Server command line and confirm that the process does not already exist.

A Go to the ESXi Server command line to view tech support mode for emergency support (1003677) or using tech support mode in ESXi 4.1 and ESXi 5.x ( 1017910).

B Enter "Esxtop"

C. Press "C", press "F", press "C" to select "C:lwid = Leader World id", press ENTER

B. In this panel, "Lwid" is listed, locate the VM, and record the "Lwid" number (if the VM is not already shown in this panel, you do not need to perform step E, which indicates that the VM process has ended)

E. Press "K" to enter the Lwid number of the virtual machine

3. Enter the virtual machine directory with the following command:

#cd VMFS/VOLUMES/50F13506-075ED29B-86B5-5EF3FD359EAB/<VM name>

Note: Because this directory uses the Chinese name, so the display is garbled, please copy this garbled, and then add the double quotation mark "<VM name>" can enter the virtual machine directory

4. Enter the following command:

# VI XSSJ.VMX

Find this line of information "Scsi0:1.filename =" XSSJ-000005.VMDK ""

Press "I" to enter edit mode, change this line of information to "Scsi0:1.filename =" XSSJ-000004.VMDK "", press "ESC" to exit the edit mode, press ": wq!" Save exit.

5. On the vsphere client, locate the virtual machine and right-click on "Remove from list". By browsing the data store where the virtual machine resides, locate the virtual machine's XSSJ.VMX file, right-click on "Add to Manifest" and start the virtual machine

The second part, correct the relationship between each snapshot disk:

After confirming the disk relationship, we need to modify the CID and parentcid on the snapshot disk. Here's how:

Note: Before you perform the following operations, back up all files for the VM. It is recommended that you copy these virtual machine files and then manipulate the copied files.

1. Go to the ESXi Server command line and log in using SSH tools or the Dcui interface.

2. Enter the virtual machine directory with the following command:

#cd VMFS/VOLUMES/50F13506-075ED29B-86B5-5EF3FD359EAB/<VM name>

Note: Because this directory uses the Chinese name, so the display is garbled, please copy this garbled, and then add the double quotation mark "<VM name>" can enter the virtual machine directory

3. Modify the CID and parentcid between the snapshot disks.

A. # vi XSSJ-000003.VMDK

The output is similar to the following, press "I" into the edit mode, press "ESC" to exit the edit mode, press ": wq!" Save exit:

# disk Descriptorfile

Version=3

Encoding= "Utf-8"

Cid=2583a010à change this parameter to "1234b123"

B. #vi XSSJ-000005.VMDK

The output is similar to the following, press "I" into the edit mode, press "ESC" to exit the edit mode, press ": wq!" Save exit:

# disk Descriptorfile

version=2

Encoding= "Utf-8"

Cid=4d38fabf

Parentcid=2583a010à change this parameter to "1234b123"

C. #vi XSSJ-000006.VMDK

The output is similar to the following, press "I" into the edit mode, press "ESC" to exit the edit mode, press ": wq!" Save exit:

# disk Descriptorfile

Version=3

Encoding= "Utf-8"

Cid=9402bf1a

Parentcid=a30d0e91à change this parameter to "4D38FABF"

4. After the above steps are completed, the disk that modifies the xssj.vmx file points to:

A. #vi XSSJ.VMX

B. Find Scsi0:1.filename = "XSSJ-000005.VMDK" line, change "XSSJ-000005.VMDK" to "XSSJ-000006.VMDK"

5. Remove the virtual machine from the manifest. Then browse the data store, locate the virtual machine's xssj.vmx file, and right-click on "Add to manifest" to launch the virtual machine.

171 How to change the Vcenter interface in Chinese to English

See the English interface of Vcenter, and then see if Chinese feel a little twist, in fact, the amendment is very simple. Right-click Properties to open vsphere Client, where the default installation location for client is D:\Program Files (x86) \vmware\infrastructure\virtual Infrastructure client\ Launcher, such as:

650) this.width=650; "Style=" border-bottom:0px; border-left:0px; border-top:0px; border-right:0px "title=" clip_image002 "border=" 0 "alt=" clip_image002 "src=" http://img1.51cto.com/attachment/ 201411/3/184463_1415003638toh2.jpg "" 393 "height="/>

Add "-locale en_US" in the "Target" white box ("D:\Program Files (x86) \vmware\infrastructure\virtual Infrastructure Client\launcher\ VpxClient.exe "-locale en_US").

172. about storage Vmotion Unable to rename a virtual machine file (5.0U2)

If you want to change the folder name of the virtual machine, the light change inventory is useless, need to use storage vmotion to complete, the method to solve this problem is as follows:

1. VSphere Client Login to Vcenter Server (note that this is vcenter server);

2. Click Administration > VCenter Server Settings > Advanced Settings;

3. In the Advanced settings option that pops up, add a new parameter and enter it on the left:

Provisioning.relocate.enableRename
Right-type: True, then click the Add button, as shown in:

650) this.width=650; "Style=" border-bottom:0px; border-left:0px; border-top:0px; border-right:0px "title=" clip_image004 "border=" 0 "alt=" clip_image004 "src=" http://img1.51cto.com/attachment/ 201411/3/184463_1415003639uuq9.jpg "" 594 "height=" 481 "/>

4, restart the vcenter server server, done, since then, Storage vmotion can change the name of the VM folder and VM files.

173. Explanation of the virtual machine system log file

In addition to the list of events and alerts, VSphere components generate a variety of logs. These logs contain information about the VSphere ring
Details of activities in the environment.
1. View System log Entries
You can view the system logs generated by the VSphere components.
To access and view system logs:

On the home page of the VSphere Client that connects the VCenter Server system or the ESX/ESXI host, click
The System log. In the drop-down menu, select the logs and entries you want to view.
Select View > Filter to reference filter options.
Enter text in the data field.
Click Clear to empty the data field.
2. External System Log

VMware Technical Support may request multiple files to help resolve any issues that you experience when you use the product. This
section describes the types and locations of log files found on various ESX 4.0 component systems.
Esx/esxi System log:
Component Location
Syslog Log/var/log/messages
Service Console Availability Report/var/log/vmkernel
VMkernel message/var/log/vmkernel
VMkernel Alerts and Availability reports/var/log/vmkernel
VMkernel Warning/var/log/vmkwarning
Virtual machine log file Vmware.log in the same directory as the. vmx file for the virtual machine
Virtual machine configuration file/.vmx

is located in the data store associated with the managed host. Use the Virtual Machine Summary page in VSphere Client to determine the data store where the file is located.

650) this.width=650; "Style=" border-bottom:0px; border-left:0px; border-top:0px; border-right:0px "title=" clip_image006 "border=" 0 "alt=" clip_image006 "src=" http://img1.51cto.com/attachment/ 201411/3/184463_1415003639vpco.jpg "" 702 "height=" 304 "/>
VSphere Client System logs:
Component Location
VSphere Client Installation

A temporary directory on the VSphere Client computer. For example: C:\Documents and log or C:\Users\\LocalSettings\Temp\vmmsi.log
VSphere Client Service Log

The \VPX directory in the application Data directory on the VSphere Client computer. Example: C:\Documents and settings\\local Settings \applicationdata\vpx\viclient-x.log

or C:\Users\\LocalSettings\ApplicationData\vpx\viclient-x.log x (=0, 1, ...) 9)

Note: You cannot configure the syslog behavior of an ESX host using VSphere Client or Vicfg-syslog. To configure the ESX host
Syslog, you must edit the/etc/syslog.conf file.
Configuration steps:

1 in the VSphere Client directory, select the host.
2 Click the Configuration tab.
3 Click Advanced Settings.
4 Select Syslog in the tree control.
5 Enter the data for the file that Syslog will use to log messages in the Syslog.Local.DatastorePath text box
The storage path. The data storage path should take the [< data storage name;] < file path > form, where path and number of backups
is related to the root directory of the stored volume. For example, the data store path [Storage1] var/log/messages is mapped to the path

/vmfs/volumes/storage1/var/log/messages. If no path is specified, the default path is/var/log/messages.

6 Enter the name of the destination remote host that forwards the Syslog data in the Syslog.Remote.Hostname text box.
If no value is specified, no data is forwarded.

7 Enter the destination remote host port of the forwarding Syslog data in the Syslog.Remote.Port text box. Default situation
mode, this option is set to 514, which is the default UDP port used by the syslog. Changes to this option will not take effect until Syslog.Remote.Hostname is configured.

8 Click OK. Changes to the Syslog option take effect immediately.
4. Export Diagnostic data

You can export all or part of the log file data. When you export log file data, the Vm-support script creates a file of the selected data and stores it in the specified location. If no other extension is specified, the default file type is. txt. The file contains the type, time, and description.
Operation Steps:

1 from the VSphere Client that connects the VCenter Server system or the ESX/ESXI host, select System Management
> Export Diagnostic data.

2 if VSphere Client connects to the VCenter Server system, specify the host for which you want to export the log and the storage day
Location of the log file.

3 if VSphere Client connects to the Esx/esxi host, specify the location of the log file.
4 Click OK.
5. Collect log files

A. Set up verbose logging with the following steps:
The setup steps are as follows:
1 Select System Administration > VCenter Server settings.
2 Select the logging option.
3 Select details in the pop-up menu.
4 Click OK.
B. Collecting vsphere log files: You can collect vsphere log files into one location.
The implementation steps are as follows:
N to view the Viclient-*.log file, change to the directory%temp%.
n If you are running a vSphere Client that is connected to the VCenter Server system, download the log package. Log

Baoseng becomes a. zip file. By default, the Vpxd log in the bundle is compressed into a. gz file. Have to
Use Gunzip to decompress these files.
N from the vcenter server system, select Start > Programs > VMware > Generate vcenter Server logs

Package. Even if you cannot connect to VCenter Server by using VSphere Client, you can build this way
VCenter Server Log package. Log Baoseng become a. zip file. By default, the Vpxd day in the bundle
Log compressed to a. gz file. You must use Gunzip to decompress these files.
C. Collecting ESX log files using the service console
All relevant ESX system and configuration information and ESX log files can be collected and packaged. This information can be used to

D. Turning off compression of vpxd log files
By default, the VCenter Server vpxd log files are rolled up and compressed into a. gz file. You can turn off this setting
To keep the vpxd log in a non-compressed state.
Setup steps:

1 log in to VCenter Server via VSphere Client.
2 Select System Administration > VCenter Server settings.
3 in the Key text box, type Log.compressonroll.
4 in the Value text box, type false.
5 Click Add, and then click OK.
E. esx/esxi VMkernel file
If the VMkernel fails, an error message is displayed, and then the virtual opportunity is rebooted. If you are in a
VMware Core dump partition is specified on the virtual machine, VMkernel also generates core dumps and error days
Log

VMkernel a more serious problem in freezing the computer, and there is no error message or core dump.

New version of vcenter log location:

In the default settings for Windows 2003, log files are stored in the

C:\Documents and Settings\All Users\Application Data\vmware\vmware Virtualcenter\logs

Directory, in Windows 2008, the log files are stored by default in the C:\ProgramData\VMware\VMware virtualcenter\logs directory.

It is conceivable that the C: \ partition is not the ideal place to store log files. I personally recommend using a separate hard drive to store log files so that the logs are stacked on a running program's hard disk. Depending on your situation, you can decide how much hard disk to use, and adjust the number and size of log file storage as needed.

Changing the log file storage path is straightforward. Open the Vpxd.cfg file and add the following line configuration between <log> and </log>:

<directory>D:\VMware\Logs</directory> changing the amount and size of log file storage is simple. The following setting defines 10 log files with a size of 10MB per log file:

<maxFileSize>10485760</maxFileSize> <maxFileNum>10</maxFileNum> After changing settings, restart Vcenter Service can take effect.

174. How to reset the vsphere Data protection password Problem (5.1)

As an alternative to VDR's VDP, the origin of Avamar, it is much more reliable than its predecessor VDR, and its deployment documentation we have written, here is the introduction if its password has been changed, but then forget the question of what to do:

1. First, restart the Vapp under VDP.

2, when the boot to enter as grub boot Select, and then enter the letter e into the editing mode, and then go to the next step;

3. Enter Init=/bin/bash, as shown in the screen:

4, and then restart the system, will not require a password, at this time, enter: passwd root, you can change the password, as shown:

5. After entering, follow the prompts to save, as shown, enter the letter y:

6, then, restart the VDP vapp can be done;

175. How to solve the problem of vcop5.6 on the Web (vcops5.6)

Fault Status:

In the Vcops Web interface, after a period of inactivity, you will be prompted to time out, after the refresh need to enter the account and password again.

Workaround:

1. Enter the UI VM virtual machine, enter the account root and password,

Open With VI

Standard Edition:/usr/lib/vmware-vcops/tomcat/webapps/vcops-vsphere/web-inf/web.xml

Enterprise Edition/usr/lib/vmware-vcops/tomcat-enterprise/webapps/vcops-custom/web-inf/web.xml
Find <session-timeout>30</session-timeout>, default is 30 minutes, as long as the value is changed to 1 (minus 1) can solve the problem of time-out

176. about Ova-vcenter Unable to log on with AD account

After using the vcenter server of OVA, the discovery "Permissions", add "user", but the user cannot display the ad domain, in the configuration VC interface https://yourip:5480/Enter the login interface, the default username is the root password is VMware, has been successfully validated with AD domain integration;

1, Login Web interface, add "identity source", Manage---configuration---identity source, select "Password", enter ad account number for example: [email protected] Domain name, and account password authentication, through;

http://jacksuper.blog.51cto.com/2724857/1061597 How to add an identity source, see the connection, page 40th. Additional Instructions:
1. This error occurs when accessing the Web "VPXD must is stopped to perform this operation"
Please login VC Configuration interface: For example Https://VC IP address: 5480/, restart the VC service can, again found "VPXD must be stopped to perform this operation" the error has not been;
2, such as the landing on the Web error: please follow the following 4 steps to resolve;

Failed to connect to VMware Lookup Service –ssl Certificate verification Failed;

1. Log in the VCSA itself via https://<vcsa-name>:5480

2. Navigate to the ' Admin ' tab

3. Turn 'Certificate regeneration enabled' to 'Yes' by using the 'Toggle Certificate setting' B Utton

4. Reboot the VCenter Server Appliance

177.vCenter " the page cannot be displayed" appears in the "Performance" screen

Failure phenomena:

After logging in to the Vcenter interface, select the host and click "Performance" in the Right Interface "The page cannot be displayed"

Fault Analysis:

The "performance" interface needs to invoke the browser and host name (IP) of the Web page address, such as the hostname or IP error page cannot be displayed.

Workaround:

1. Check the vsphere client to see if the browser is too low.

2. Click "System Management"-"Vcenter Server Settings"-"Runtime Settings", view the VCenter server name, then select "Advanced Settings" to find the value with "HTTP", the IP or host name is the same as the vcenter server name.

178 . Unable to open virtual machine due to storage lock

Failure phenomena:

Open virtual machine appears failed to add disk scsi0:1. Failed to power on Scsi0:1 error

In the log display

? Unable to open Swap File

? Unable to access a file since it is locked

? Unable to access a file <filename> since it is locked

? Unable to access Virtual machine configuration

Fault Analysis:

This problem is caused by a storage lock

Workaround:

A Shut down the entire environment, shutdown sequence:

Turn off virtual machine apps-shut down virtual machines-turn off esxi-shutdown Storage array-turn off fibre switching-turn off total power

Boot order:

Contrary to shutdown order

B Please refer to the kb:http://kb.vmware.com/kb/10051

179 . VMware partial Compatibility List query (1)

First, how to query the compatibility List of the server compatibility:

1. Login to http://www.vmware.com/resources/compatibility/search.php

2. System (SERVER)

3.keyword Search Enter the server model you are using now

Second, how to query the compatibility List of storage compatibility:

1. Login to http://www.vmware.com/resources/compatibility/search.php

2. Storage/san

3. Keyword search Enter the storage model you are using now

Third, how to query the compatibility List of network device compatibility:

1. Login to http://www.vmware.com/resources/compatibility/search.php

2. Io/devices

3. Keyword search enter the type of network device you are using now

VMware vsphere FAQ Rollup (17)