Home News June 2009, New / Updated VMware KB Articles.

June 2009, New / Updated VMware KB Articles.

by Roger Lund

Yes, I  am very behind on reading KB Articles.

Here are a few that I saw, and wanted to link, I have the symptoms here, you’ll have to click the links for resolutions.

Issues when vCenter Server and License Server are installed on ESX 3.x hosted virtual machines
  • KB Article: 1011085
  • Updated: Jun 23, 2009
  • Symptoms

    If you have vCenter Server and License Server installed on a virtual machine on an ESX 3.x host, you may experience the following symptoms:

    • You cannot power on the virtual machine
    • You see the error not enough licenses to perform the operation if you:
      • Try to power on the virtual machine
      • Reboot the virtual machine
      • Try to add new licenses to the server
        Note: This error displays even though you correctly installed a server-based (centralized) license file.
    • You cannot change the ESX status from Unlicensed. All other options are unavailable.
    • You cannot use vCenter features such as VMotion, VMware High Availability, and Distributed Resource Scheduling

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

     

    The tg3 network driver fails to load during ESX boot
  • KB Article: 1006601
  • Updated: Jun 19, 2009
  • Symptoms

    You may experience these symptoms:

    • When migrating a host to a new network, the onboard NICs stop working
    • Broadcomm tg3.0 kernel driver is not loading at boot
    • You can manually load the tg3 driver successfully

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

    Issues when vCenter Server and License Server are installed on ESX 3.x hosted virtual machines
  • KB Article: 1011085
  • Updated: Jun 23, 2009
  • Symptoms

    If you have vCenter Server and License Server installed on a virtual machine on an ESX 3.x host, you may experience the following symptoms:

    • You cannot power on the virtual machine
    • You see the error not enough licenses to perform the operation if you:
      • Try to power on the virtual machine
      • Reboot the virtual machine
      • Try to add new licenses to the server
        Note: This error displays even though you correctly installed a server-based (centralized) license file.
    • You cannot change the ESX status from Unlicensed. All other options are unavailable.
    • You cannot use vCenter features such as VMotion, VMware High Availability, and Distributed Resource Scheduling

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

     

    VirtualCenter Server with multiple IP addresses changes the IP address while the services are running
  • KB Article: 1006437
  • Updated: Jun 19, 2009
  • Symptoms
    • The VirtualCenter Server has multiple IP addresses and changes the IP address on which the services run
    • The ESX hosts disconnect from VirtualCenter
    • You see the message:
      These ESX are currently being managed by another VirtualCenter (VC) and do you want to continue.
      The "other" VirtualCenter (VC) is using the original IP address of the server.

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

     

    Cannot see a line item for add-ons when viewing licenses on the vSphere Client licensing page
  • KB Article: 1011926
  • Updated: Jun 19, 2009
  • Symptoms
    • When you view your purchase on the vSphere Client licensing page, a separate product line item for add-ons is not displayed
    • Only vSphere 4.0 Standard license appears even though you have purchased, for example, a vSphere 4.0 Standard with VMotion license

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

     

    Unable to start vCenter 4 after upgrade from 2.0.2
  • KB Article: 1011670
  • Updated: Jun 18, 2009
  • Symptoms
    • After successful upgrade from VirtualCenter 2.0.2 to vCenter Server, the vCenter service does not start
    • vpxd logs show:
      [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”][VpxUtil] Failed to deserialize object using SOAP deserializer: Invalid argument : version
      [VpxdInvtVm] Failed to load vm summary: Not initialized: boolean disableSnapshotsSupported
      [VpxdMain] Failed to initialize: Not initialized: boolean disableSnapshotsSupported
      Failed to initialize VMware VirtualCenter. Shutting down…
      Forcing shutdown of VMware VirtualCenter now

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

     

    vSphere Host Update Utility not available for download to upgrade standalone ESX Server 3.x to ESX 4
  • KB Article: 1011542
  • Updated: Jun 19, 2009
  • Purpose

    If you do not have access to vCenter 4.0 then the vSphere Host Update Utility cannot be installed. The installer is only available with the installation of vCenter 4.0 and is currently not available for download

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

     

    Cannot deploy a virtual machine from a template after changing the NFS datastore IP address
  • KB Article: 1003477
  • Updated: Jun 17, 2009
  • Details
    • You cannot deploy a virtual machine from a template after changing the IP address of an NFS datastore
    • You see the error:
      unknown device ID.
    • You see the error:  
      Invalid configuration on device 1 . The specified key name identifier already exists.
    • When converting the template to a virtual machine, you see the error:
      host or cluster is not valid.
    • If you delete the NFS datastore from all ESX hosts in the cluster and then add it back using the VirtualCenter Server, a (1) is appended to the original datastore name.

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

     

    Cannot log in to an ESX 4 host with vSphere Web Access
  • KB Article: 1011921
  • Updated: Jun 16, 2009
  • Symptoms
    • You cannot log in to an ESX 4.0 host using vSphere Web Access
    • The vSphere Web Access browser does not open
    • The browser shows the error:
      503 Service unavailable

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

     

    Today, I had a fellow VI admin, tell me that my blog was a #1 hit on Google, regarding a VMware KB.

    Thought I should keep it up.

     

    Roger L.

    [/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]

    You may also like