VMware KB Roll Outs – June 2011 – a few I noticed.

I was reviewing a few KB’s, on VMware’s RSS feed, and thought this stood out.

The following is taken from http://kb.vmware.com

Cannot license a centralized ESX/ESXi 4.x host

KB Article: 2000723


    Cannot license a centralized ESX/ESXi 4.x host
    Licensing an ESX/ESXi host fails with one of these errors:
        Features in use – vMotion/fault tolerance
        The license key entered does not have enough capacity for this entity

Resolution http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2000723

Cisco Nexus 1000v logs contain the message: Dropping received frames from duplicate VSM saddr (0x1010000)

KB Article: 2000074


    Cisco Nexus 1000v logs may contain the error:

    vswews01a %KERN-1-SYSTEM_MSG: Dropping received frames from duplicate VSM saddr (0x1010000)

Resolution http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2000074

The esxtop utility causes high CPU load

KB Article: 2000829


    The esxtop utility is very slow to redraw and display data.
    The console world indicates 100% load.
    ESX console shows the esxtop process generating the high CPU load.
    ESX host is sluggish and unresponsive.
    Stopping the esxtop utility reduces the CPU load to normal.

Resolution http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2000829

The guest operating system is extremely slow or does not boot when connected to the host CD/DVD drive

KB Article: 2000382


    The virtual machine is extremely slow
    The guest operating system fails to boot
    CPU and disk performance charts for the virtual machine show little or no activity
    The virtual CD/DVD drive is connected to a host device
    In the host vmkernel or messages log, you see a log spew similar to:

    May 27 07:42:07 VS2 vmkernel: 21:02:21:57.950 cpu5:4235)ScsiDeviceIO: 1672: Command 0x28 to device “mpx.vmhba1:C0:T0:L0” failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x2 0x0.
    May 27 07:42:13 VS2 vmkernel: 21:02:22:04.455 cpu5:4235)NMP: nmp_CompleteCommandForPath: Command 0x28 (0x41027f3c6640) to NMP device “mpx.vmhba1:C0:T0:L0” failed on physical path “vmhba1:C0:T0:L0” H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x2 0x0.

Resolution http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2000382

vMotion fails at 78% with the error: Could not open change tracking file

KB Article: 2001004


    vMotion fails at 78%
    You see the error:

    A general system error occured. Source detected that destination failed to resume”

    In the vmware.log file, you see errors similar to:

    Jun 09 18:13:13.815: vmx| DISKLIB-LIB   : Resuming change tracking.
    Jun 09 18:13:17.821: vmx| DISKLIB-CTK   : Could not open tracking file. File open returned IO error 4.
    Jun 09 18:13:17.821: vmx| DISKLIB-CTK   : Could not open change tracking file “/vmfs/volumes/4da7419d-76842557-1fe8-001a6468e1ed/erptlbi/erptlbi-ctk.vmdk”: Could not open/create change tracking file.
    Jun 09 18:13:17.825: vmx| DISK: Cannot open disk “/vmfs/volumes/4da7419d-76842557-1fe8-001a6468e1ed/erptlbi/erptlbi.vmdk”: Could not open/create change tracking file (2108).
    Jun 09 18:13:17.825: vmx| Msg_Post: Error

    In the hostd.log file, you see entries similar to:

    [fusion_builder_container hundred_percent=”yes” overflow=”visible”][fusion_builder_row][fusion_builder_column type=”1_1″ background_position=”left top” background_color=”” border_size=”” border_color=”” border_style=”solid” spacing=”yes” background_image=”” background_repeat=”no-repeat” padding=”” margin_top=”0px” margin_bottom=”0px” class=”” id=”” animation_type=”” animation_speed=”0.3″ animation_direction=”left” hide_on_mobile=”no” center_content=”no” min_height=”none”][2011-06-09 13:35:43.602 57781B90 verbose ‘vm:/vmfs/volumes/4da7419d-76842557-1fe8-001a6468e1ed/erptlbi/erptlbi.vmx’] VMotionLastStatusCb: Failed with error 7: Source detected that destination failed to resume.
    [2011-06-09 13:35:43.602 57781B90 verbose ‘vm:/vmfs/volumes/4da7419d-76842557-1fe8-001a6468e1ed/erptlbi/erptlbi.vmx’] VMotionResolveCheck: Operation in progress
    [2011-06-09 13:35:43.603 57740B90 verbose ‘vm:/vmfs/volumes/4da7419d-76842557-1fe8-001a6468e1ed/erptlbi/erptlbi.vmx’] Tools are auto-upgrade capable
    [2011-06-09 13:35:43.604 57740B90 verbose ‘vm:/vmfs/volumes/4da7419d-76842557-1fe8-001a6468e1ed/erptlbi/erptlbi.vmx’] Tools guest daemon status changed to: 1
    [2011-06-09 13:35:43.610 57781B90 verbose ‘vm:/vmfs/volumes/4da7419d-76842557-1fe8-001a6468e1ed/erptlbi/erptlbi.vmx’] VMotionStatusCb: Completed
    [2011-06-09 13:35:43.610 57781B90 verbose ‘vm:/vmfs/volumes/4da7419d-76842557-1fe8-001a6468e1ed/erptlbi/erptlbi.vmx’] VMotionResolveCheck: Firing ResolveCb
    [2011-06-09 13:35:43.611 57781B90 info ‘VMotionSrc (1307644538230054)’] ResolveCb: VMX reports needsUnregister = false for migrateType MIGRATE_TYPE_VMOTION
    [2011-06-09 13:35:43.611 57781B90 info ‘VMotionSrc (1307644538230054)’] ResolveCb: Failed with fault: (vmodl.fault.SystemError) {
       dynamicType = ,
       faultCause = (vmodl.MethodFault) null,
       reason = “Source detected that destination failed to resume.”,
       msg = “”,
    [2011-06-09 13:35:43.611 57781B90 verbose ‘VMotionSrc (1307644538230054)’] Migration changed state from MIGRATING to DONE
    [2011-06-09 13:35:43.611 57781B90 verbose ‘VMotionSrc (1307644538230054)’] Finish called

Resolution http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2001004

Question, do you guy’s/gals want me to the full resolution into the blog? I linked to shorten.


Roger L[/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]

Written by Roger Lund

VMware and Storage crazy man, vExpert, MN VMUG leader