new1234.jpg

Archive

Posts Tagged ‘vCenter Server 4.0’

VMware: EVC – Method not found: ‘Vmomi.HostSystemArray EVCState.get_BadSoftwareHostsBlockingEVC()’

January 7th, 2011 3 comments

Today I got an error when selecting the “VMware EVC” option in the Cluster Settings at my vCenter 4.0 host with multiple HP Blades with same CPU. Error message:

Method not found: ‘Vmomi.HostSystemArray EVCState.get_BadSoftwareHostsBlockingEVC()’

VMpros.nl

 

Solution:

This issue occurs when a system installed with vSphere 4.1 and you use vSphere 4.0 Client on that system to access vCenter Server 4.0.

To workaround this issue, install a vSphere 4.0 Client on a system on which you have not installed vSphere4.1 Client earlier and then update the EVC cluster using the vSphere 4.0 Client.

 

Source: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Unable “Add to Invetory” option is greyed out

June 22nd, 2010 9 comments

Today I got some trouble with my Exchange production VM, my VMware Data Recovery 1.2 created many snapshots.. and removed the VM from the vCenter inventory… ok not a big issue, but on the datastore I can’t Add it to the inventory again, the option “Add to Inventory” is greyed out.

VMpros.nl

Solution:

On the console I added the VM again in vCenter with the vmware-cmd option:

image

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Data Recovery – Failed to create snapshot for <server>, (vcb api exeption)

June 21st, 2010 2 comments

Last week we upgraded VMware Data Recovery from version 1.1 to 1.2. After rerun the backup schedule I received this error:

Failed to create snapshot for <server>. error –3948 ( vcb api exeption)

 

My backup starts > Create a new snapshot > Few seconds later… the snapshot is removed and get this warning..

image

  Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Active snapshots but can’t see them in Snapshot Manager

June 2nd, 2010 14 comments

Today I got some problems with backing up one of my VM’s using VMware Data Recovery. I was looking what was going wrong after a few failures.. And yes..  hanging snapshots

Trying to remove the snapshots was a little bit different. When I went into the “Snapshot Manager” there were no active snapshots and I couldn’t delete the files. But while browsing the Datastore I saw many active snapshots.

Current situation:

image

– You can “Revert to Current Snapshot” via menu..

image

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Import Appliance > Device ‘VirtualCdrom’ uses a controller that is not supported

April 19th, 2010 No comments

Today tried to import the ESX Deployment Appliance (EDA) in vCenter 4, but after File > Deploy OVF template > selecting destination host I received this error message:

Device ‘VirtualCdrom’ uses a controller that is not supported. This is a general limitation to the virtual machine’s virtual hardware version on the selected host

To modify the VMware Hardware Version from default version 7 to 4 you can use the VMware vCenter Converter Standalone 4.0.1 Now I was able to import the EDA Appliance in my vCenter.

image

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: How to downgrade VM hardware level 7 to 4

April 9th, 2010 5 comments

After some problems with my ESX 4.0 host I want to move some critical VM’s to my ESX 3.5 u4 host.. but my upgraded hardware level (7) is not compatible with my ESX 3.5 u5 host. The following is a step-by-step guide on how to perform this downgrade:

I want to downgrade my Windows 2008 64-bit with XenApp 6 with hardware level 7 to hardware level 4.

image 

Time to downgrade:

Download and start: VMware vCenter Converter Standalone 4.0.1

VMpros.nl

– Click: Convert Machine
Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: ESX 4.0 down after update: fsck.ext3: unable to resolve ‘uuid

March 29th, 2010 7 comments

After upgrading the VMware ESX 4.0 host with VMware Update Manager I received in the boot loader a few errors:

fsc.ext3: Unable to resolve ‘UUID=xxxxx-xxxx-xxxx-xxxxxxxxxxxx’
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.

To resolve this issue:

image

– Login with Root credentials

Error warnings:

fsck.ext3: Unable to resolve ‘UUID=7d6111a3-d848-4e18-88e3-46a66912f8e6’

fsck.ext3: Unable to resolve ‘UUID=b07fd5a0-4a19-445d-adae-3b3679b5be3b’

fsck.ext3: Unable to resolve ‘UUID=b2ac1406-2dc1-4d4a-8649-0072389978ab’

Edit file /var/fstab/ by using VI of NANO
Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Failed to create http proxy: Resource is already in use: 0.0.0.0:80

December 3rd, 2009 No comments

After rebooting my vCenter server I can’t connect my vCenter 4.0, error:

Windows could not start the VMware VirtualCenter Service on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.

image

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Virtual Machine Monitor Execution Modes in vSphere 4.0

August 19th, 2009 No comments

Recently we published a whitepaper describing the VMware Virtual Machine Monitor (VMM) execution modes in vSphere 4.0. The VMM may choose hardware support for virtualization whenever it’s available or may choose software techniques for virtualization when hardware support is unavailable or not enabled on the underlying platform. The method chosen by the VMM for virtualizing the x86 CPU and MMU is known as the "monitor mode".

This paper attempts to familiarize our customers with default monitor modes chosen by the VMware VMM for many popular guests running on modern x86 CPUs. Most workloads perform well under these default settings. In some cases the user may want to override the default monitor mode. We provide a few examples in which the user may observe performance benefits in overriding the default monitor modes and two ways by which the user can override the defaults.

The default monitor mode chosen by the VMM for a particular guest depends on the available (or enabled) hardware features on the underlying platform and the guest OS performance in that mode. The difference in the availability of virtualization support on modern x86 CPUs and the guest OS performance when using those features (or when using software techniques when those features are unavailable) leads to a complex problem of choosing the appropriate monitor mode for a given guest on a given x86 CPU.  For more details please download and read our full paper from here.

Source: VMware VROOM!
  VMware white paper

Twitter Poster plugin : Earn money on the web