1 2 3 4 Previous Next 49 Replies Latest reply on May 9, 2019 11:12 PM by Nash191

    OVF deplyment - cancled by user

    eravn Enthusiast

      Hi

      I have export a ESXi 5.1 server and tried to Deploy this to a new server. The ny server is upgraded fra ESXi 4.0xxx to ESXi 5.1 - after upgrade serveres on this server runs fine.

      I try to make a OVF deploy of export server to this server but get this error Task cancled by user and OVF deplyment stops.

       

      HOW to FIX this.

       

      PLEASE need fast help

        • 1. Re: OVF deplyment - cancled by user
          a.p. Guru
          Community WarriorsvExpertUser Moderators

          Please attach the .ovf file to your next reply post to see whether there's an issue with this file.

           

          André

          • 2. Re: OVF deplyment - cancled by user
            eravn Enthusiast

            Hi, I have attach the file

            • 3. Re: OVF deplyment - cancled by user
              a.p. Guru
              Community WarriorsvExpertUser Moderators

              Does the new server have the same CPU vendor/type and BIOS settings (e.g. VT-x, Execute Disable Bit)?

              What you may try is to remove the following lines from the .ovf file and then try to import the VM again.

                  <vmw:CpuCompatibilitySection>
                    <Info>CPU compatibility constraints</Info>
                    <vmw:Level vmw:eax="----:----:----:----:----:----:----:----" vmw:ebx="----:----:----:----:----:----:----:----" vmw:ecx="----:----:----:----:----:----:----:----" vmw:edx="----:----:---H:----:----:----:----:----" vmw:level="-2147483647" />
                    <vmw:Level vmw:eax="----:----:----:----:----:----:----:----" vmw:ebx="----:----:----:----:----:----:----:----" vmw:ecx="----:----:----:----:----:----:----:----" vmw:edx="----:----:---H:----:----:----:----:----" vmw:level="-2147483647" vmw:vendor="amd" />
                  </vmw:CpuCompatibilitySection>

              André

              • 4. Re: OVF deplyment - cancled by user
                eravn Enthusiast

                I have copy the file and renamed the dal-bo.ovf fil til dal-bo-server.ovf and deletet the intries. Do not work same error.

                I have tried to use ovftools and get this error.

                C:\Program Files\vmware\VMware OVF Tool>ovftool --datastore="DATA2" f:\dalbo\dal
                -bo\dal-bo.ovf vi://root:PwaD4dalbo@192.168.130.9
                Opening OVF source: //:@ERA-ITGV-IBM.it-globalview.dk:80\dalbo\dal-bo\dal-bo.ovf

                The manifest validates
                Opening VI target: vi://root@192.168.130.9:443/
                Error:
                - The task was canceled by a user.
                Warning:
                - No manifest entry found for: 'dal-bo.ovf'.
                - File is missing from the manifest: 'dal-bo.ovf'.
                Completed with errors

                C:\Program Files\vmware\VMware OVF Tool>

                • 5. Re: OVF deplyment - cancled by user
                  a.p. Guru
                  Community WarriorsUser ModeratorsvExpert

                  Which files do you have for this VM?

                  Can you workaround the error message by adding the relax option "--lax" to the ovftool command?

                   

                  In case it's an OVF signing issue, see http://www.virtuallyghetto.com/2012/01/how-to-create-manifest-file-for-ovf.html

                   

                  André

                  • 6. Re: OVF deplyment - cancled by user
                    eravn Enthusiast

                    I have FIX IT with

                     

                    Deleted *.mf file and change settings en OCF file

                     

                    Failed to deploy OVF package: The task was canceled by a user.

                    How misleading. I, or any other user, certainly didn’t cancel the task. So what happened? I took a look through the (horrendous) hostd.log on the ESXi box and found absolutely nothing of any value.

                    Frustrated by the inability to redeploy a template I spent so long preparing, I broke open the OVA template and took a look inside. There were three files with different extensions,

                    • .ova - OVF descriptor, written in XML, which describes the hardware requirements
                    • .mf – contains SHA1 checksums of the .OVA and .VMDK
                    • .vmdk – the virtual hard disk for the virtual machine.

                    I immediately discarded the .mf. If you modify the .ova and don’t update the .mf, it’ll complain that the checksum is invalid. Removing this file seems to prevent vSphere from checking the checksums, which is useful, seeing as we want to poke around the .ova. After fiddling around inside the .ova, I stumbled across the following line…

                    <rasd:ResourceSubType>vmware.cdrom.iso</rasd:ResourceSubType>

                    Changing the above line, to read…

                    <rasd:ResourceSubType>vmware.cdrom.atapi</rasd:ResourceSubType>

                    …appears to have fixed my deployment issues. Perhaps changing the ‘CD Drive Device type’ in the virtual machine’s settings would’ve fixed it. But by that point, I had already exported the OVA and deleted the source virtual machine.

                    Hopefully someone will stumble across this one day, and it’ll save them a few hours!

                    3 people found this helpful
                    • 7. Re: OVF deplyment - cancled by user
                      hwyhobo Novice

                      Before creating an OVA file, in vSphere right click on the VM, open Settings, click on CD/DVD drive, check if Device Type is selected as Datastore ISO. If so, select Client Device. Save settings by clicking OK. Export OVA file, and then deploy.

                      1 person found this helpful
                      • 8. Re: OVF deplyment - cancled by user
                        Jettyz Lurker

                        eravn wrote:

                        Hopefully someone will stumble across this one day, and it’ll save them a few hours!

                        That's exactly what happened! Thank you so much

                        • 9. Re: OVF deplyment - cancled by user
                          Paulus_Koning Lurker

                          You're the greatest. Stumbled upon this error and thanks to your post I solved it within 10 minutes! Thanks so much!

                          • 10. Re: OVF deplyment - cancled by user
                            VIMSupport Lurker

                            Hi,

                                 I got the same problem, enable to import OVA in vSphere 5.1 but was ok on my Workstation 10. After the import completed, . i change the CD-DVD ISO path to local device and export again in OVA format. After the Import was OK in vSphere 5.1.

                            • 11. Re: OVF deplyment - cancled by user
                              radams360 Lurker

                              This too help me. Changed the .iso to atapi.

                              • 12. Re: OVF deplyment - cancled by user
                                Cadstar Lurker

                                Helped me as well, thanks very much for this!!

                                • 13. Re: OVF deplyment - cancled by user
                                  brianhlarose Lurker
                                  VMware Employees

                                  UPDATED INFORMATION:  I HAD A CORRUPTED OVF FILE BUT THE ERROR MESSAGE DIDN'T TELL ME THAT. It looked normal until this "cancelled by user" stuff.  Update at bottom of this post. 

                                   

                                  ------

                                  I had this same exact problem today and i did the following from my mac.

                                   

                                  #  tar xvf THE_NAME_OF_THE_PACKAGE.ova

                                  (it will extract 4 files, a VMDK, a CERT, a OVF and an MF file)

                                  # rm THE_NAME_OF_THE_PACKAGE.mf

                                   

                                  go back into vCenter and redeploy, but this time select the OVF file that was extracted in step 1 above.

                                   

                                  from reading above, it was obviously a checksum problem, but since I downloaded directly from VMware, via the VM Corporate VPN, i'm sure it's genuine.

                                   

                                  VIOLA!  It worked.  Thanks easter bunny!!  Bonk Bonk..

                                   

                                  Turns out that the original file was corrupted at the very end of it.  So it deployed but the VM started up with a corrupted and incomplete filesystem.   This is now explaining the fact that the checksum didn't sync, but of course the error message didn't tell me that.  I finally ended up getting onto a reliable (ie non-DSL) network and downloading a new payload.  Worked like a champ right out of the box, no issues at all.

                                   

                                  SO, moral of this story is "Double Check the size and checksum of your appliances, they might be corrupt images giving you this error"

                                  • 14. Re: OVF deplyment - cancled by user
                                    obogdanov Novice

                                    18 months later and still the most helpful post on the topic.  As suggested, changed the cdrom line from "iso" to "atapi" and now have a happy template.  (And deleted the .mf file) Thanks.

                                    1 2 3 4 Previous Next