Workstation and GSX Server Troubleshooting II. Max Banihani VMware Technical Support Engineer

Size: px

Start display at page:

Download "Workstation and GSX Server Troubleshooting II. Max Banihani VMware Technical Support Engineer"

Jemimah Anthony
6 years ago
Views:

1 Workstation and GSX Server Troubleshooting II Max Banihani VMware Technical Support Engineer

2 Agenda Brief introduction to resources and tools for troubleshooting VMware Workstation 5 and GSX Server 3.2. Examine VMware Workstation 5 and GSX Server 3.2 configuration files. Analysis of virtual machine configuration file (VMX). Migration of virtual machines. An introduction to VMware virtual networks, network services and configuration of GSX and Workstation. Clustering with GSX Server basics

3 Online Resources Product Documentation A documentation library for all VMware products reference materials in one searchable location

4 Online Resources Knowledge Base A database of searchable technical documents authored by VMware technical staff References the User Manuals

5 Online Resources VMware Product Centers Contains links to White papers, technical notes, compatibility guides and other technical information for all currently released VMware products

6 Online Resources Discussion Forums The VMware community is a set of moderated discussion forums hosted on the VMware Web site and is open to users of all VMware products VMware technical staff regularly monitors the forums to learn about your issues, feedback, and help facilitate discussions when appropriate Expertise of those posting responses varies widely

7 Workstation and GSX Server Common Configuration Files Global preferences files location: For Linux Host: /etc/vmware For Windows Host: \Documents and Settings\All Users\Application Data\VMware\VMware Workstation User preferences location: For Linux Host: /<username>/.vmware For Windows Host: \Documents and Settings\<username>\Application Data\VMware\VMware Workstation

8 config.ini Example 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 to the default preferences is made. (Edit > Preferences in the UI).

9 Preferences.ini Example 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"..

10 UI Logs These log file are useful when troubleshooting issues relating to VMware 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)

11 Virtual Machine Log File This log file is very useful when troubleshooting issues relating to running virtual machines. By default, 3 historical logs are maintained in addition to current powered on virtual machine log file. This is the key log file to examine in the event a virtual machine exits abnormally or crashes. On a Windows host, the vmware.log file is in the same directory as the configuration file (.vmx) of the virtual machine that had problems. The path to the log file of the active virtual machine appears in the About dialog box. In a console, choose Help > About VMware GSX Server, OR VMware Workstation. On a Linux host, the <vmname>.log file is in the same directory as the configuration file (.vmx) of the virtual machine that had problems. You may also see core files (core or vmware-core) to submit to VMware Technical Support.

12 Sample Machine Log File Windows Host Sep 13 15:56:19: vmx Log for VMware Workstation pid=2312 version=5.0.0 build=build option=release Sep 13 15:56:19: vmx Command line: "C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe" "pipe=\\.\pipe\vmx7f a4f8a34; vm=7f a4f8a34" "C:\Documents and Settings\mnottage\My Documents\My Virtual Machines\RHEL4\rhel4.vmx" Sep 13 15:56:19: vmx UI Connecting to pipe '\\.\pipe\vmx7f a4f8a34' with user '(null)' Sep 13 15:56:19: vmx CPU #0 TSC = Sep 13 15:56:19: vmx TSC delta 0 Sep 13 15:56:19: vmx VMMon_GetkHzEstimate: Calculated khz Sep 13 15:56:19: vmx pcpu #0 CPUID numentries=3 GenuntelineI Sep 13 15:56:19: vmx pcpu #0 CPUID version=0xf41 id1.edx=0xbfebfbff id1.ecx=0x441d id1.ebx=0x20800 Sep 13 15:56:19: vmx pcpu #0 CPUID id80.eax= id81.edx=0x0 id81.ecx=0x0 Sep 13 15:56:19: vmx CPUID id1.edx: 0xbfebfbff id1.ecx: 0x441d id81.edx: 0 id81.ecx: 0 Sep 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.vmx Sep 13 15:56:19: vmx VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredon without reset Sep 13 15:56:19: vmx PowerOn Sep 13 15:56:19: vmx HOST Windows version 5.0, build 2195, platform 2, "Service Pack 4"

13 Sample Machine Log File Windows Host Sep 13 15:56:19: vmx DICT config.version = 8 Sep 13 15:56:19: vmx DICT virtualhw.version = 4 Sep 13 15:56:19: vmx DICT scsi0.present = TRUE Sep 13 15:56:19: vmx DICT scsi0.virtualdev = lsilogic Sep 13 15:56:19: vmx DICT memsize = 256 Sep 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 = generated Sep 13 15:56:19: vmx DICT uuid.location = 56 4d 2f b4-e1 d9 af 0e Sep 13 15:56:19: vmx DICT uuid.bios = 56 4d 2f b4-e1 d9 af 0e Sep 13 15:56:19: vmx DICT ethernet0.generatedaddress = 00:0c:29:10:75:05 Sep 13 15:56:19: vmx DICT ethernet0.generatedaddressoffset = 0 Sep 13 15:56:19: vmx DICT workingdir =. Sep 13 15:56:19: vmx DICT checkpoint.vmstate.readonly = FALSE Sep 13 15:56:19: vmx DICT checkpoint.vmstate = Sep 13 15:56:19: vmx DICT snapshot.action = keep Sep 13 15:56:19: vmx DICT ide1:0.startconnected = TRUE Sep 13 15:56:19: vmx DICT tools.synctime = TRUE Sep 13 15:56:19: vmx DICT uuid.action =. Sep 13 15:56:19: vmx MStat: Creating Stat vm.uptime Sep 13 15:56:19: vmx WSSCAN: reserved mem (in MB) min=32 max=896 recommended=896 Sep 13 15:56:19: vmx hostmem=1024 maxallowedall=4096 maxallowedvm=3600 Sep 13 15:56:19: vmx totoverhead=16.. Sep 13 15:56:19: vmx KHZEstimate Sep 13 15:56:19: vmx MHZEstimate 2793 Sep 13 15:56:19: vmx NumVCPUs 1

14 Sample Machine Log File Linux Host Aug 17 08:47:49: vmx Log for VMware Workstation pid=9833 version=5.0.0 build=build option=release Aug 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 GenuntelineI Aug 17 08:47:49: vmx pcpu #0 CPUID version=0xf27 id1.edx=0xbfebfbff id1.ecx=0x400 id1.ebx=0x10809 Aug 17 08:47:49: vmx pcpu #0 CPUID id80.eax= id81.edx=0x0 id81.ecx=0x0 Aug 17 08:47:49: vmx CPUID id1.edx: 0xbfebfbff id1.ecx: 0x400 id81.edx: 0 id81.ecx: 0 Aug 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.vmx Aug 17 08:47:50: vmx VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredon without reset Aug 17 08:47:50: vmx PowerOn Aug 17 08:47:50: vmx HOST sysname Linux, nodename vaio.kana.com, release EL, version #1 Fri Oct 3 18:13:58 EDT 2003, machine

15 Sample Machine Log File Linux Host Aug 17 08:47:50: vmx DICT tools.synctime = FALSE Aug 17 08:47:50: vmx DICT scsi0:1.present = TRUE Aug 17 08:47:50: vmx DICT scsi0:1.filename = /dev/scd0 Aug 17 08:47:50: vmx DICT scsi0:1.devicetype = cdrom-raw Aug 17 08:47:50: vmx DICT floppy0.startconnected = FALSE Aug 17 08:47:50: vmx DICT usb.generic.autoconnect = FALSE Aug 17 08:47:50: vmx DICT sound.startconnected = FALSE Aug 17 08:47:50: vmx DICT sharedfolder.maxnum = 1 Aug 17 08:47:50: vmx DICT sharedfolder0.present = TRUE Aug 17 08:47:50: vmx DICT sharedfolder0.enabled = TRUE. Aug 17 08:47:50: vmx DICT sharedfolder0.hostpath = /tmp Aug 17 08:47:50: vmx DICT sharedfolder0.guestname = Shared Aug 17 08:47:50: vmx DICT ide0:0.present = FALSE Aug 17 08:47:50: vmx DICT ide0:0.filename = /dev/cdrom Aug 17 08:47:50: vmx DICT ide0:0.devicetype = atapi-cdrom Aug 17 08:47:50: vmx DICT ide0:0.startconnected = FALSE Aug 17 08:47:50: vmx DICT scsi0:2.present = TRUE Aug 17 08:47:50: vmx DICT scsi0:2.filename = /dev/cdrom Aug 17 08:47:50: vmx DICT scsi0:2.devicetype = cdrom-raw Aug 17 08:47:50: vmx DICT scsi0:2.startconnected = FALSE Aug 17 08:47:50: vmx DICT checkpoint.vmstate = Windows 2000

16 Additional Logging For GSX Server Only VMware Management Interface Log File The VMware Management Interface keeps a log. On a Windows host, the log is called mui.log and is stored by default 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 File You 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 = TRUE log.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.

17 Virtual Machine Configuration Files Extension.log.nvram.vmdk File Name <vmname>.log or vmware.log <vmname>.nvram or nvram <vmname>.vmdk.vmdk <vmname>.vmdk <diskname>- <###>.vmdk Description 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. This is the file that stores the state of the virtual machine's BIOS. This is a virtual disk file, which stores the contents of the virtual machine's hard disk drive. 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

18 Virtual Machine Configuration Files Extension.vmsd.vmsn.vmss.vmtm File Name <vmname>.vmsd <vmname>- Snapshot.vmsn <vmname>.vmss <vmname>.vmtm Description This is a centralized file for storing information and metadata about snapshots. This is the snapshot state file, which stores the running state of a virtual machine at the time you take that snapshot. 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. This is the configuration file containing team data. There can be other files in the directory, some of which are present only while a virtual machine is running.

19 Virtual Machine Configuration File:.vmx config.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"

20 Virtual Machine Configuration File:.vmx nvram = "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 a ce b e0 fd c9 d7 09" uuid.bios = "56 4d 66 ec a ce b 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

21 Troubleshooting Common Issues Network connectivity Basic steps are as follows: 1. Verify that the host has connectivity 2. 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 (if used) Service are running 3. Verify that the virtual machine is configure properly with the correct vmnet virtual 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.

22 Migrating virtual machine between VMware hosted products. Migrating virtual machines from VMware GSX 3.2 to VMware Workstation 5.0 is supported. Migrating virtual machines from VMware Workstation 5.0 to VMware GSX 3.2 is not supported unless the virtual machine was created in legacy mode. The virtual machine configuration and hardware versions can be determined by examining the VMX file and looking for value of config.version and virtualhw.version For example config.version = 3 VMware Workstation 4.x or GSX version 3.x config.version = 4 VMware Workstation 5.x virtualhw.version = 7 is a VMware Workstation 4.x virtual machine virtualhw.version = 8 is a VMware Workstation 5.x virtual machine

23 Preparing virtual machines for migration Shut down the guest operating system and power off the virtual machine. If the virtual machine is suspended, resume it, then shut down the guest. If you have snapshots in powered on state, commit or remove. If you move a virtual machine to a host with significant hardware differences, the guest operating system may no longer work correctly. Moving Between 64-bit and 32-bit Hosts may require that you recompile the kernel in your Linux guest operating system.

24 Cluster in a Box with VMware GSX Server

25 Troubleshooting Cluster in a Box with VMware GSX Server check list. SCSI reservation: Sharing the SCSI bus: scsi<x>.sharedbus = "virtual" Sharing a SCSI virtual disk: scsix:x.shared = "true" Disk locking: (permits multiple virtual machines to access a disk concurrently.) disk.locking = "false" Preallocated SCSI virtual disks. Two virtual network adapters: The virtual machines configuration must all be located on the same GSX Server host.

26 Issues to consider when sharing disks Do not share a disk on SCSI bus 0. This bus is usually used for the boot disk. If you share the boot disk, you run the risk of corrupting it, as the boot program is not aware that the disk is being shared and can write to the disk regardless of whether or not it is being shared. If one virtual machine does not have SCSI reservation enabled for its virtual disk, but another virtual machine does have SCSI reservation enabled for the same virtual disk, GSX Server does allow the disk to be shared. However, any virtual machine not configured for SCSI reservation that tries to access this disk concurrently can cause corruption or data loss on the shared disk. VMware recommends you take care when sharing disks. To disable SCSI reservation for all SCSI disks in a virtual machine, open the configuration file and comment out or remove the scsi<x>.sharedbus = "virtual" line and make sure the disk.locking line is set to "true". If you want to disable SCSI reservation for only a specific SCSI disk on a shared bus, change the scsi<x>:<y>.shared = "true" line in the configuration file to scsi<x>:<y>.shared = "false"; you can also comment out the line. In a Windows virtual machine, some disk errors are recorded in the Windows event log in normal operation. These error messages have a format similar to "The driver detected a controller error on \Device\Scsi\BusLogic3 This errors should appear in the log periodically only on the passive node of the cluster and should also appear when the passive node is taking over during a failover. The errors are logged because the active node of the cluster has reserved the shared virtual disk. The passive node periodically probes the shared disk and receives a SCSI reservation conflict error.

27 Contacting VMware Technical Support Best 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 host. If you encounter problems on a remote client please supply the log files manually.

28 Running VMware Support Script Windows 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.

29 VMware Support Script Linux 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 displays messages 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.

30 Workstation and GSX Server Troubleshooting II Questions?

VERSION 3.0. Administration Guide

VERSION 3.0. Administration Guide VERSION 3.0 TM Administration Guide Please note that you will always find the most up-to-date technical documentation on our Web site at http://www.vmware.com/support/. VMware, Inc. The VMware Web site