Workstation and GSX Server Troubleshooting I Max Banihani VMware Technical Support Engineer
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Workstation and GSX Server Troubleshooting I
Max BanihaniVMware Technical Support Engineer
AgendaHighlight resources and tools available for troubleshooting VMware Workstation 5 and GSX Server 3.2An introduction to VMware Workstation 5 and GSX Server 3.2 configuration filesAn introduction to virtual machine configuration filesTroubleshooting common errors
Online ResourcesProduct Documentationhttp://www.vmware.com/support/pubs
A documentation library for all VMware products reference materials in one searchable location
Online ResourcesKnowledge Basehttp://www.vmware.com/kb
A database of searchable technical documents authored by VMware technical staffReferences the User Manuals
Online ResourcesVMware Product Centershttp://www.vmware.com/support/resources
Contains links to White papers, technical notes, compatibility guides and other technical information for all currently released VMware products
Online ResourcesDiscussion Forumshttp://www.vmware.com/community
The VMware community is a set of moderateddiscussion forums hosted on the VMware Web siteand is open to users of all VMware products
VMware technical staff regularly monitors theforums to learn about your issues, feedback,and help facilitate discussions when appropriateExpertise of those posting responses varies widely
Workstation and GSX Server Common Configuration Files
Global preferences files location (config and preferences): For Linux Host: /etc/vmwareFor Windows Host: “\Documents and Settings\All Users\ApplicationData\VMware\VMware Workstation”User preferences location:For Linux Host: /<username>/.vmwareFor Windows Host: “\Documents and Settings\<username>\ApplicationData\VMware\VMware Workstation”
config.iniExample entries:prefvmx.useRecommendedLockedMemSize = "TRUE"mainMem.partialLazySave = "FALSE"mainMem.partialLazyRestore = "FALSE“prefvmx.allVMMemoryLimit = "256"
By default, on Windows hosts the config.ini is not created until a change tothe default preferences is made. (Edit > Preferences in the UI).
Preferences.iniExample entries:# DO NOT EDIT THIS FILE.# This file is automatically generated and maintained by vmware.## If you are going to ignore this order, at least first make# sure that no instances of vmware are running.prefvmx.allVMMemoryLimit = "384"prefvmx.priority.grabbed = "normal"prefvmx.priority.ungrabbed = "normal"pref.syncTime = "TRUE"hints.hideAll = "FALSE"pref.noChrome = "FALSE"pref.view.navBar.width = "181"pref.view.homepage = "FALSE"pref.view.navBar = "FALSE"..
UI LogsThese log file are useful when troubleshooting issues relating toVMware Workstation UI or the VMware Virtual Machine Console in GSX Server
On a Windows host, the log is called vmware-<username>-<PID>.log and is stored in the user's TEMP directory; by default, this directory is C:\Documents and Settings\<username>\Local Settings\Temp. The path to this file appears in the About dialog box. On a Linux host, the log is called ui-<PID>.log and is stored in the user's TEMP directory; by default, this directory is /tmp/vmware-<username>.
Note: the PID in UI log name refers to the vmware.exe running the UI.
(It is not the same PID of the vmware-vmx.exe process that runs virtual machines)
Virtual Machine Log FileThis log file is very useful when troubleshooting issues relating to running virtual machines. By default, 3 historical logs are maintained inaddition to current powered on virtual machine log file.This is the key log file to examine in the event a virtual machine exitsabnormally or crashes.
On a Windows host, the vmware.log file is in the same directory as theconfiguration file (.vmx) of the virtual machine that had problems. The path to the log file of the active virtual machine appears in theAbout dialog box. In a console, choose Help > About VMware GSXServer, OR VMware Workstation. On a Linux host, the <vmname>.logfile is in the same directory as the configuration file (.vmx) of the virtualmachine that had problems.
You may also see core files (core or vmware-core) to submit to VMware Technical Support.
Sample Machine Log File Windows HostSep 13 15:56:19: vmx| Log for VMware Workstation pid=2312 version=5.0.0 build=build-13124 option=ReleaseSep 13 15:56:19: vmx| Command line: "C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe" "-
@" "pipe=\\.\pipe\vmx7f8015734a4f8a34; vm=7f8015734a4f8a34" "C:\Documents and Settings\mnottage\My Documents\My Virtual Machines\RHEL4\rhel4.vmx"
Sep 13 15:56:19: vmx| UI Connecting to pipe '\\.\pipe\vmx7f8015734a4f8a34' with user '(null)'Sep 13 15:56:19: vmx| CPU #0 TSC = 1753611031750270Sep 13 15:56:19: vmx| TSC delta 0Sep 13 15:56:19: vmx| VMMon_GetkHzEstimate: Calculated 2793000 kHzSep 13 15:56:19: vmx| pcpu #0 CPUID numEntries=3 GenuntelineISep 13 15:56:19: vmx| pcpu #0 CPUID version=0xf41 id1.edx=0xbfebfbff id1.ecx=0x441d id1.ebx=0x20800Sep 13 15:56:19: vmx| pcpu #0 CPUID id80.eax=80000008 id81.edx=0x0 id81.ecx=0x0Sep 13 15:56:19: vmx| CPUID id1.edx: 0xbfebfbff id1.ecx: 0x441d id81.edx: 0 id81.ecx: 0Sep 13 15:56:19: vmx| changing directory to C:\Documents and Settings\mnottage\My Documents\My Virtual
Machines\RHEL4\.Sep 13 15:56:19: vmx| Config file: C:\Documents and Settings\mnottage\My Documents\My Virtual
Machines\RHEL4\rhel4.vmxSep 13 15:56:19: vmx| VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOn
without resetSep 13 15:56:19: vmx| PowerOnSep 13 15:56:19: vmx| HOST Windows version 5.0, build 2195, platform 2, "Service Pack 4"
Sample Machine VMX File Windows HostSep 13 15:56:19: vmx| DICT config.version = 8Sep 13 15:56:19: vmx| DICT virtualHW.version = 4Sep 13 15:56:19: vmx| DICT scsi0.present = TRUESep 13 15:56:19: vmx| DICT scsi0.virtualDev = lsilogicSep 13 15:56:19: vmx| DICT memsize = 256Sep 13 15:56:19: vmx| DICT scsi0:0.present = TRUE.Sep 13 15:56:19: vmx| DICT scsi0:0.redo = Sep 13 15:56:19: vmx| DICT ethernet0.addressType = generatedSep 13 15:56:19: vmx| DICT uuid.location = 56 4d 2f 23 65 58 09 b4-e1 d9 af 0e 35 10 75 05Sep 13 15:56:19: vmx| DICT uuid.bios = 56 4d 2f 23 65 58 09 b4-e1 d9 af 0e 35 10 75 05Sep 13 15:56:19: vmx| DICT ethernet0.generatedAddress = 00:0c:29:10:75:05Sep 13 15:56:19: vmx| DICT ethernet0.generatedAddressOffset = 0Sep 13 15:56:19: vmx| DICT workingDir = .Sep 13 15:56:19: vmx| DICT checkpoint.vmState.readOnly = FALSESep 13 15:56:19: vmx| DICT checkpoint.vmState = Sep 13 15:56:19: vmx| DICT snapshot.action = keepSep 13 15:56:19: vmx| DICT ide1:0.startConnected = TRUESep 13 15:56:19: vmx| DICT tools.syncTime = TRUESep 13 15:56:19: vmx| DICT uuid.action = .Sep 13 15:56:19: vmx| MStat: Creating Stat vm.uptimeSep 13 15:56:19: vmx| WSSCAN: reserved mem (in MB) min=32 max=896 recommended=896Sep 13 15:56:19: vmx| hostMem=1024 maxAllowedAll=4096 maxAllowedVM=3600Sep 13 15:56:19: vmx| totOverhead=16..Sep 13 15:56:19: vmx| KHZEstimate 2793000Sep 13 15:56:19: vmx| MHZEstimate 2793Sep 13 15:56:19: vmx| NumVCPUs 1
Sample Machine Log File Linux HostAug 17 08:47:49: vmx| Log for VMware Workstation pid=9833 version=5.0.0 build=build-
13124 option=ReleaseAug 17 08:47:49: vmx| Command line: "/usr/lib/vmware/bin/vmware-vmx" "-@"
"pipe=/tmp/vmware-root/vmx2f6caff8bfc4be50;vm=2f6caff8bfc4be50" "/root/vmware/Windows 2000 Professional/Windows 2000 Professional.vmx"
Aug 17 08:47:49: vmx| UI Connecting to pipe '/tmp/vmware-root/vmx2f6caff8bfc4be50' with user '(null)'
Aug 17 08:47:49: vmx| pcpu #0 CPUID numEntries=2 GenuntelineIAug 17 08:47:49: vmx| pcpu #0 CPUID version=0xf27 id1.edx=0xbfebfbff id1.ecx=0x400
id1.ebx=0x10809Aug 17 08:47:49: vmx| pcpu #0 CPUID id80.eax=80000004 id81.edx=0x0 id81.ecx=0x0Aug 17 08:47:49: vmx| CPUID id1.edx: 0xbfebfbff id1.ecx: 0x400 id81.edx: 0 id81.ecx: 0Aug 17 08:47:49: vmx| changing directory to /root/vmware/Windows 2000 Professional/.Aug 17 08:47:49: vmx| Config file: /root/vmware/Windows 2000 Professional/Windows 2000
Professional.vmxAug 17 08:47:50: vmx| VMXVmdbCbVmVmxExecState: Exec state change requested to state
poweredOn without resetAug 17 08:47:50: vmx| PowerOnAug 17 08:47:50: vmx| HOST sysname Linux, nodename vaio.kana.com, release 2.4.21-4.EL,
version #1 Fri Oct 3 18:13:58 EDT 2003, machine
Sample Machine Log File Linux HostAug 17 08:47:50: vmx| DICT tools.syncTime = FALSEAug 17 08:47:50: vmx| DICT scsi0:1.present = TRUEAug 17 08:47:50: vmx| DICT scsi0:1.fileName = /dev/scd0Aug 17 08:47:50: vmx| DICT scsi0:1.deviceType = cdrom-rawAug 17 08:47:50: vmx| DICT floppy0.startConnected = FALSEAug 17 08:47:50: vmx| DICT usb.generic.autoconnect = FALSEAug 17 08:47:50: vmx| DICT sound.startConnected = FALSEAug 17 08:47:50: vmx| DICT sharedFolder.maxNum = 1Aug 17 08:47:50: vmx| DICT sharedFolder0.present = TRUEAug 17 08:47:50: vmx| DICT sharedFolder0.enabled = TRUE.Aug 17 08:47:50: vmx| DICT sharedFolder0.hostPath = /tmpAug 17 08:47:50: vmx| DICT sharedFolder0.guestName = SharedAug 17 08:47:50: vmx| DICT ide0:0.present = FALSEAug 17 08:47:50: vmx| DICT ide0:0.fileName = /dev/cdromAug 17 08:47:50: vmx| DICT ide0:0.deviceType = atapi-cdromAug 17 08:47:50: vmx| DICT ide0:0.startConnected = FALSEAug 17 08:47:50: vmx| DICT scsi0:2.present = TRUEAug 17 08:47:50: vmx| DICT scsi0:2.fileName = /dev/cdromAug 17 08:47:50: vmx| DICT scsi0:2.deviceType = cdrom-rawAug 17 08:47:50: vmx| DICT scsi0:2.startConnected = FALSEAug 17 08:47:50: vmx| DICT checkpoint.vmState = Windows 2000
Additional Logging For GSX Server Only VMware Management Interface Log FileThe VMware Management Interface keeps a log. On a Windows host, the log is called mui.log and is stored bydefault in C:\Program Files\VMware\VMware Management Interface. On a Linux host, the log is called error_log and is stored by default in /var/log/vmware-mui.
VMware Authorization Service Log FileYou can enable logging for the VMware Authorization Service (known as vmware-authd on Linux hosts)
manually. 1. In a text editor, open the following file:
On a Windows host, edit config.ini, located in C:\Documents and Settings\All Users\Application Data\VMware\VMware GSX Server. On a Linux host, edit /etc/vmware/config.
2. Add the following lines to the file: vmauthd.logEnabled = TRUElog.vmauthdFileName = "vmauthd.log" This creates a file called vmauthd.log. On a Windows host, this file appears by default in C:\Windows\system32 or C:\WINNT\system32; on a Linux host, this file appears by default in /var/log/vmware.
3. Save and close the configuration file. The log is enabled on a Linux host. 4. On a Windows host, restart the VMware Authorization Service. Choose Start > Administrative Tools >
Services. Right-click VMware Authorization Service and choose Restart. This enables logging.
VMware Registration Service Log File The VMware Registration Service keeps a log. On a Windows host, the log is called vmware-serverd.log and is stored in C:\Windows\Temp. On a Linux host, the log is called vmware-serverd.log and is stored in /var/log/vmware.
Virtual Machine Configuration Files
This is a redo-log file, created automatically when a virtual machine has one or more snapshots. This file stores changes made to a virtual disk while the virtual machine is running. There may be more than one such file. The ### indicates a unique suffix added automatically by VMware Workstation to avoid duplicate file names
.vmdk<vmname>.vmdk<diskname>-<###>.vmdk
This is a virtual disk file, which stores the contents of the virtual machine's hard disk drive.
<vmname>.vmdk.vmdk
This is the file that stores the state of the virtual machine's BIOS.
<vmname>.nvram or nvram
.nvram
This is the file that keeps a log of key VMware Workstation activity. This file can be useful in troubleshooting if you encounter problems. This file is stored in the directory that holds the configuration (.vmx) file of the virtual machine.
<vmname>.log or vmware.log
.log DescriptionFile NameExtension
Virtual Machine Configuration Files Cont.
This is the configuration file containing team data.
<vmname>.vmtm.vmtm
This is the suspended state file, which stores the state of a suspended virtual machine .Some earlier VMware products used the extension .std for suspended state files.
<vmname>.vmss.vmss
This is the snapshot state file, which stores the running state of a virtual machine at the time you take that snapshot.
<vmname>-Snapshot.vmsn
.vmsn
This is a centralized file for storing information and metadata about snapshots.
<vmname>.vmsd.vmsdDescriptionFile NameExtension
There can be other files in the directory, some of which are present only while a virtual machine is running.
Virtual Machine Configuration File: .vmxconfig.version = "8"virtualHW.version = "4"scsi0.present = "TRUE"memsize = "256"scsi0:0.present = "TRUE"scsi0:0.fileName = "Windows 2000 Professional.vmdk"ide1:0.present = "TRUE"ide1:0.fileName = "auto detect"ide1:0.deviceType = "cdrom-raw"floppy0.fileName = "A:"ethernet0.present = "TRUE"usb.present = "TRUE"sound.present = "TRUE"sound.virtualDev = "es1371"sound.fileName = "-1"sound.autodetect = "TRUE"displayName = "Windows 2000 Professional"guestOS = "win2000pro"
Virtual Machine Configuration File: .vmxnvram = "Windows 2000 Professional.nvram"ide0:0.present = "TRUE"ide0:0.fileName = "Windows 2000 Professional (2).vmdk"ide0:0.mode = "independent-nonpersistent"ide1:0.autodetect = "TRUE"ethernet1.present = "TRUE"ethernet1.connectionType = "nat"serial0.present = "TRUE"serial0.fileName = "COM1"ide0:0.redo = ".\Windows 2000 Professional (2).vmdk.REDO_a02144"scsi0:0.redo = ""ethernet0.addressType = "generated"ethernet1.addressType = "generated"uuid.location = "56 4d 66 ec a4 10 35 ce-40 63 9b e0 fd c9 d7 09"uuid.bios = "56 4d 66 ec a4 10 35 ce-40 63 9b e0 fd c9 d7 09"ethernet0.generatedAddress = "00:0c:29:c9:d7:09"ethernet0.generatedAddressOffset = "0"ethernet1.generatedAddress = "00:0c:29:c9:d7:13"ethernet1.generatedAddressOffset = "10“
Troubleshooting Common Issues Installation on Windows host:VMware creates installer logs in %temp%called vminst.log and vmmsi.logIn addition, VMware provide a stand alone uninstall cleaner utility
available on line to clean corrupted installs. See VMware Knowledgebase article 1308 for Windows hosts
Cleaning Up After Incomplete Uninstallation on a Windows HostAdditionally, VMware Workstation 5 installer for Windows has a built-in
option ( /c) to perform manual clean
See VMware Knowledgebase article 38 for Linux hosts Manual uninstall
Troubleshooting Common Issues Installation on Linux Host: The most common issue occurs when the product is being configured on unsupported Linux Distributions where VMware product installer could not build necessary modules. Most often, failure is occurs when the installed kernel source files on the host, including kernel headers, do not match the currently running kernel. To verify versions, run”uname -r rpm -qa | grep kernel If the version numbers do not match, obtain the source files andheaders from the distribution CD or the vendor and install them.A properly installed version of gcc compiler and the make program before running vmware-config.pl is required.
Troubleshooting Common Issues VMware product License issuesThe license is saved in the Windows registry and in a file in Linux.Each user requires a separate license.
The most common error reported is that serial number doesn't match any ofthe available licenses. This is often due to the key applied to the wrong host OS platform, License keys for Windows hosts can not be used on Linux hosts.
Troubleshooting Common Issues Connecting virtual peripheralsMost common error related to using peripherals such as USB devices, Serial port, Parallel ports is when the host OS has control of such devices. Peripherals in general can not be shared between host and the virtual machine or among virtual machines. Only one system can control such devices.
For Windows: Verify that no tasks or service are in control of problem devices. This can be accomplish by using task manager, services applet and device manager.
For Linux: Check for loaded modules pertaining to problem device. Most common is USB hotplug which can be resolved by disabling the device in the hotplug configuration files in the /etc/hotplug directory or unload the hotplug modules.
Check the virtual machine log file for errors and verify that the virtual machine is configured to enable the correct device/port
Troubleshooting Common Issues Network connectivity
Basic steps are as follows:1. Verify that the host has connectivity2. Verify that the VMware network protocol and network service are installed and
functioning properly on the host Bridge: Verify that the correct host NIC is bound with the VMware bridge protocol.NAT and Host-only: Verify that VMware NAT and DHCP Service (if used) are running
3. Verify that the virtual machine is configure properly with the correct vmnetvirtual adapter
4. Verify that the GOS is configured the correct network driver.5. Verify that no network services on the host such VPN/Firewalls are preventing
network access to VMware services. This is the most common cause of virtual machine network failures.
6. Use VMware vnetsniffer.exe [/e] (/p "pvnID" | VMnet?) to trace the virtual network traffic.
Contacting VMware Technical SupportBest practices to expedite analysis and processing
your support request:Provide a detailed description of the technical issues you are experiencing.Include the output of the VMware support scripts files (vm-support)
Note: The support script runs only on the GSX Server and VMware Workstation host. If you encounter problems on a remote client please supply the log files manually.
Running VMware Support ScriptWindows Host
1.Open a command prompt. 2.Change directory to c:\Program Files\VMware\VMware
Workstation. If you did not install the program in the default directory, use the appropriate drive letter and substitute the appropriate path.
3.Run the support script.cscript vm-support.vbs
4.After the script runs, it displays the name of the directory where it has stored its output. Use a file compression utility such as WinZip or PKZIP to zip that directory and include the zip file with your support request.
VMware Support ScriptLinux Host
1. Open a terminal. 2. Run the support script as the user who is running the
virtual machine.vm-support If you are not running the script as root, the script displaysmessages indicating that it cannot collect some information. This is normal. If the VMware support team needs that information, a support representative will ask you to run the script again as root.
3. The script creates a compressed .tgz file in the current directory. Include that output file with your support request.
Workstation and GSX Server Troubleshooting I
Questions?
Related Documents
