Tuesday, 2 September 2014

Deploying OVA fails with "Failed to Deploy OVF/OVA package: The operation is not supported on the object"

We recently had an issue deploying either an OVA/OVF file that was created from one of the virtual machines in our environment.  Deploying this OVA failed instantly (after entering cluster locations / datastore) with the following error: "The Operation is not supported on the object".  After much investigation and examining the /var/log/hostd.log file on the ESXi host we were trying to deploy too, we found the line:  "Video Ram size edit is not supported when auto-detect is True."  Editing the Virtual Machine hardware settings and editing the Video Card and changing the setting from Auto-detect to Specify custom settings (This can be anything) and then exporting the virtual machine as an OVA allowed the deployment to work! Very interesting that this setting caused a problem!  Previously we have also encountered this when the Virtual Machine has an ISO mounted when to converting to OVA.
Posted by at
Labels: , ,

15 comments:

  1. ChāWā Kurt23 February 2015 at 13:34

    Beers and peanuts and much appreciation to you. I flipped one of my VMs to 1024x768, exported it to OVA, and deployed it without trouble. If any asks me I'm gonna tell 'em that you da man.

    Thanks for sharing your insight. Cheers

    ReplyDelete
    Replies
    1. Unknown23 February 2015 at 14:27

      Thanks. Good to hear that this blog has helped someone!!

      Delete
  2. Unknown19 October 2015 at 07:56

    Thank you, your post has helped me too :)

    ReplyDelete
  3. Gezmonderschmeedonheedon1 February 2016 at 09:24

    I just had this issue but thought nah it won't be the display driver as I've not done anything special to the display here. It was just a Windows VM that I was using OVF to export over to another vCenter instance. I thought I'd I'll look in hostd.log file for some clues anyway, then what do I see in there? "Video Ram size edit is not supported when auto-detect is True" :o/

    So I changed it to some other setting, re-export my ovf and the import then worked!

    ReplyDelete
  4. Chris12 May 2016 at 17:13

    Was encountering this exact problem migrating VM's from a VMWare workstation environment over to ESXi 5.5 and this solution fixed us up right away. Thanks for the post.

    ReplyDelete
    Replies
    1. Matthew Short12 May 2016 at 17:16

      Glad people still find this blog useful sometimes! I should really put more updates in here

      Delete
    2. Chris12 May 2016 at 17:25

      You're one of the top results when googling some of these VmWare issues. Maybe you should monetize this blog and make some scratch on the side.

      Delete
  5. Unknown3 August 2016 at 15:49

    Still relevant! I had this problem just now. :)

    I didn't want to re-export the whole machine, so I edited the OVF in Notepad, and changed "useAutoDetect" to "false".

    VMware noticed the changed file hash, and interpreted it as corruption, so I deleted the corresponding .mf file. Now VMware is importing it smoothly.

    Thanks - I never would have checked the video memory. :-O

    ReplyDelete
  6. Unknown9 December 2016 at 15:37

    You are THE MAN! I ran into exact issue and your blog post came out very helpful. Cheers!!!

    ReplyDelete
  7. Unknown13 February 2019 at 01:18

    Perfect.. the tip worked..

    ReplyDelete
    Replies
    1. Matthew Short13 February 2019 at 01:36

      Thanks, Glad the page is still useful, even after all this time!

      Delete
  8. Oliver's superblog26 February 2020 at 23:50

    Thnx man!

    ReplyDelete
  9. Ilya30 August 2021 at 05:08

    yeah, it's still useful even now, in 2021 :) VMware seems to be continue to put a shit.... :))))

    ReplyDelete

Subscribe to: Post Comments (Atom)