new1234.jpg

Archive

Posts Tagged ‘kb’

VMware: Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" for object "ha-datastoresystem" on ESXi "SERVERNAME" failed.

February 27th, 2012 20 comments

After I placed two new 146 GB SAS hard disks to an ESXi 4.1 host, configured a new array, try to add a new datastore with my vSphere Client I received this warning:

Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object “ha-datastoresystem” on ESXi “SERVERNAME” failed.

image

After reading VMwareKB 1008886 and following the instructions I solved the issue..


Solution:

image

Commandline:

dd if=/dev/zero of="/vmfs/devices/disks/vml.0000000000766d686261313a313a30" bs=512 count=34 conv=notrunc

Output:

34+0 records in
34+0 records out

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Creating a snapshot for a virtual machine fails with the error: File is larger than maximum file size supported (1012384)

February 4th, 2010 3 comments

When Creating a snapshot for a virtual machine fails

Or you receive the error:
File is larger than the maximum size supported by datastore

Note: This error does not occur on ESX 3.5 or earlier.

ESX 4.0 is able to detect when a snapshot file at maximum size cannot fit into a datastore. Instead of allowing the file to be created, which may not work correctly if it grows to big, ESX cancels the operation and displays the above error.

To confirm if the snapshot files may be too big, compare the size of the virtual machine’s base disks against the block size of the datastore which contains the virtual machine’s working directory.

Note: If you are using Raw Device Map, you should compare the size of the RDMs instead of the base disks.

Read more…

Categories: VMware Tags: , , , , ,

VMware: Top Ten KB Articles for 2009

January 6th, 2010 No comments

To give you some idea of what our most popular content was in 2009 we have compiled a year end top 10 list. Looks like best practice and how-to articles are used the most. We notice things like this, and are working on many more of the same sort of thing now that we’re in a new year.

 

1003303 VMware Partner Activation Codes (PAC) Explained 1301

1009039 Upgrading to ESX 4.0 and vCenter 4.0 Best Practices

1004588 Best Practices for using and Troubleshooting VMware Converter

1003212 Enhanced VMotion Compatibility (EVC) Processor Support

1003490 Restarting the Management Agents on an ESX or ESXi Server

1007849 Consolidating Snapshots

1003889 Upgrading to ESX 3.5 and VirtualCenter 2.5 Best Practices

1003501 Increasing the Amount of RAM assigned to the ESX Server Service Console

1001596 Troubleshooting VMware High Availability (HA)

1005466 Downloading and Installing VMware Fusion

 

Source: VMware Knowledge Base Blog

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , ,

VMware: VMware KB search on Twitter

September 25th, 2009 1 comment

Today on Twitter user “VMwareKB” has tweeted: Can’t find a KB that you need? Tweet us and we’ll get it written?

image

 

Thats nice 🙂

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , ,

VMware: Upgrading to ESX 4.0 and vCenter 4.0 best practices (1009039)

August 5th, 2009 No comments

This article provides steps which may be useful when upgrading to ESX 4.0 and vCenter 4.0.

Note: This article assumes that you have read the vSphere Upgrade Guide. This upgrade guide contains definitive information. If there is a discrepancy between the guide and this article, assume that the guide is correct.

Note: Read the VMware vSphere 4.0 Release Notes for known installation issues.

Read more…

VMware: Creating snapshots in a different location than default virtual machine directory (1002929)

May 14th, 2009 2 comments

All snapshots are created in the default virtual machine directory. Even if the vmdk disk file is located on different datastore than the virtual machine, the delta files are created in the default virtual machine directory.

This article provides instructions to change the default location.

Changing the location of where the delta files are created is helpful if you need to:

  • Create a snapshot but do not have enough space on the VMFS volume
  • Power on a virtual machine but there is not enough space to create a swap file on the VMFS volume
    To change the default location:
  1. Power off the virtual machine.
  2. Add the following line to the VMX configuration file for the virtual machine:
    workingDir="<new_path_location>"
    For example:
    workingDir="/vmfs/volumes/46f1225f-552b0069-e03b-00145e808070/vm-snapshots"
  3. To reload virtual machine configuration, run the command:
    # vimsh -ne "vmsvc/reload <VmId>"
    When you power on the virtual machine, snapshot files and VSWP files are created in the new location.

Note: If you do not want to redirect the virtual machine’s swap file, add the following line to the VMX configuration file, then reload the configuration:
sched.swap.dir="<path_to_vm_directory>"

When you power on the virtual machine, the swap file is created in the same directory as virtual machine.

Source: 1002929
Categories: VMware Tags: , , , ,

VMware: Sysprep file locations and versions (1005593)

May 14th, 2009 3 comments
  • When attempting to customize the deployment of a virtual machine the radio buttons are disabled (greyed out).
  • When attempting to create a new virtual machine from a Template in ESX v3.5 you receive the following error message:
    Warning: Windows customization resources were not found on this server

The problem is seen when if Micosoft’s sysprep files are not found on the VirtualCenter host, or are not in the location they are expected.

This article guides you through the process of determining the correct version of sysprep to use and the correct locations for these files.

Microsoft has a different version of Sysprep for each release and service pack of Windows. According to Microsoft, "You need to use the version of Sysprep specific to the operating system you are deploying." For more information, see http://www.microsoft.com/technet/community/en-us/management/setupdeply_faq.mspx
Link valid as of May 27, 2008. If you find the link is broken, provide feedback and a VMware employee will update the article as necessary.

The differences are not immediately visible in the packaging and documentation of the service packs, so it is necessary to manually investigate.

Read more…

VMware: How do I change a forgotten root password on my ESX Server Host?

April 6th, 2009 No comments

Occasionally, an administrator will ask about recovering the password to an ESX Server host:

  • I do not know the root user’s password on my ESX Server host. How can I reset the password?
  • I have lost the root password to my ESX host, how can I recover it? This article provides a solution to the problem of having a lost password for the root account on an ESX Server host.

Note: In some cases a defective keyboard can cause problems logging into ESX. You might want to test with a different physical keyboard if you are having difficulties with known login credentials.

If you have forgotten or don’t know the password for the root user on an ESX Server host, you can change it without reinstalling ESX Server. 

Warning: This can be used maliciously and should be safeguarded against through proper physical access to the host, authenticated remote console access, monitoring and protection against reboot procedures (e.g. grub password) and limited access to the management network.

See http://www.vmware.com/resources/techresources/726 for more information on security best practices.

Note: The procedure below performs a password reset, it "blindly" replaces the existing root password with a new one. This is not password recovery, it does not allow you to learn the original root password. VMware does not provide tools or methods to recover the original root password of an ESX host.

To change the password for the root user, you must reboot the ESX Server host into service console only in single-user mode. To do this, follow the steps below appropriate for your version of ESX:

ESX Server 3.x:

  1. Reboot the ESX Server hostimage Read more…
Categories: VMware Tags: , , , ,

VMware: SATA Controller Support in ESX 3.5 (1008673)

April 4th, 2009 4 comments

ESX 3.5 supports multiple SATA controllers. Some of these controllers are supported only in the native Advanced Host Controller Interface (AHCI)/SATA mode with SATA hard-drive, and some are only supported in IDE/ATA mode with SATA Optical Drive. For other controllers, VMware provides support in AHCI/SATA or IDE/ATA mode on both types of drives, but you need to be aware of certain feature limitations and trade-offs associated with each mode. clip_image005

ESX 3.5 Update 3 introduced support for two new SATA Controllers:

  • Broadcom HT1000
  • Intel ICH-7

ESX 3.5 Update 4 added support for the following SATA controllers:

  • Intel ICH-9
  • Intel ICH-10

Controller

Mode support

Support SATA hard drive and SSD Disk

Support SATA Optical Drive (CD or DVD)

Hard drive VMFS Support

Broadcom HT 1000

AHCI/SATA mode only

Yes

No

No

Intel ICH-7

IDE/ATA mode only

No

Yes

N/A since there is no hard drive support

Intel ICH-9

Both

Yes

Yes

Yes, only in AHCI/SATA mode

Intel ICH-10

Both

Yes

Yes

Yes, only in AHCI/SATA mode

Read more…

Categories: VMware Tags: , , , , ,