new1234.jpg

Archive

Posts Tagged ‘OVF’

VMware: vRealize Operations Manager vApp deployment fails with error: This operation is not supported on the object

December 10th, 2014 2 comments

Today I was installing VMware vCenter Operations 5.8.4.0 in my vSphere 5.5 update 1 homelab, during deployment I received this warning message:
   

The OVF package is invalid and cannot be deployed.

This operation is not supported on the object.

   

VMpros

Cause

vRealize Operations Manager vApp 5.x can only deploy to a host inside a cluster if DRS is enabled.

 

Solution

My homelab is running a VMware vCenter 60 day trial version, after I enabled DRS in my cluster with 2 hosts I was able to deploy vCO 5.8

 

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: Virtual machines created from OVF sources with SCSI LSI Logic disk controller might not start up after conversion to an ESX destination

February 20th, 2009 No comments

I have created some Virtual Appliances with VMware Converter 3.0 that will be imported to ESX. The Virtual Appliances are saved as OVA, it’s a zipped file that contains the vmdk and ovf.

This week VMware released vConverter Standalone 4.0. So I upgraded my version to 4.0. And I started to import my templates. I always import an XP template for testing. First I imported some windows 2k3 templates, then I started with the XP template. I was going through the steps until I got to step 3.Where the VM options can be edited, I noticed that the SCSI controller was changed from LSI Logic to Bus Logic.

This will cause XP to crash. Because of the LSI logic driver that was installed in the OS. To verify that there was no mistake, I opened the ovf file where the vmx options are stored.

<Item>
   <rasd:Caption>SCSI Controller 0</rasd:Caption>
   <rasd:Description>SCSI Controller</rasd:Description>
   <rasd:InstanceId>3</rasd:InstanceId>
   <rasd:ResourceType>6</rasd:ResourceType>
   <rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
   <rasd:BusNumber>0</rasd:BusNumber>
</Item>

Searching for the SCSI controller in the file, will show the type of SCSI controller that was used.Changing the SCSI Controller at this point was not an option, because the LSI Logic controller was not listed as an option in the dropdown list.

As workaround I had to start the VI client after the XP machine was imported. I edited the settings of the imported virtual machine to change the controller type from Bus Logic back to LSI Logic.

This will enable the virtual machine to boot again.

After some research I found that it was a know issue. Read about it after the jump.

Source: http://www.vmware.com/support/converter/doc/releasenotes_conv40.html#knownissues
  https://blog.vmpros.nl/2009/02/16/vmware-released-new-version-vcenter-converter-40/
  http://www.vmware.com/appliances/learn/ovf.html
Categories: Hardware, VMware Tags: , , , ,