XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    ova export not functional

    Scheduled Pinned Locked Moved Solved Advanced features
    xcp-ngxenorchestraova export
    31 Posts 4 Posters 3.1k Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • florentF Offline
      florent Vates 🪐 XO Team @Gheppy
      last edited by

      @Gheppy could you get us an ovf file generated by vmware ?
      it would help us find the right fields to use

      1 Reply Last reply Reply Quote 0
      • GheppyG Offline
        Gheppy
        last edited by

        I don't use VMWare but if you give me some time ( one day ) I will install a server with ESXI and I will do an export.

        florentF 1 Reply Last reply Reply Quote 0
        • florentF Offline
          florent Vates 🪐 XO Team @Gheppy
          last edited by

          @Gheppy said in ova export not functional:

          I don't use VMWare but if you give me some time ( one day ) I will install a server with ESXI and I will do an export.

          no worries I 've got one in my lab, I will just have to create the VM

          florentF 1 Reply Last reply Reply Quote 0
          • florentF Offline
            florent Vates 🪐 XO Team @florent
            last edited by olivierlambert

            @Gheppy
            found it , it's the keys for UEFI

                  <vmw:Config ovf:required="false" vmw:key="firmware" vmw:value="efi"/>
                  <vmw:Config ovf:required="false" vmw:key="powerOpInfo.standbyAction" vmw:value="checkpoint"/>
            

            and there is for the video card

                  <Item ovf:required="false">
                            <rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>
                            <rasd:ElementName>VirtualVideoCard</rasd:ElementName>
                            <rasd:InstanceID>8</rasd:InstanceID>
                            <rasd:ResourceType>24</rasd:ResourceType>
                            <vmw:Config ovf:required="false" vmw:key="useAutoDetect" vmw:value="true"/>
                            <vmw:Config ovf:required="false" vmw:key="videoRamSizeInKB" vmw:value="16384"/>
                            <vmw:Config ovf:required="false" vmw:key="enable3DSupport" vmw:value="false"/>
                            <vmw:Config ovf:required="false" vmw:key="use3dRenderer" vmw:value="automatic"/>
                            <vmw:Config ovf:required="false" vmw:key="graphicsMemorySizeInKB" vmw:value="262144"/>
                            <vmw:CoresPerSocket ovf:required="false">1</vmw:CoresPerSocket>
                          </Item>
            

            we should be able to parse them ( from a virtual box/ esxi export) and add them in XO export

            1 Reply Last reply Reply Quote 0
            • GheppyG Offline
              Gheppy
              last edited by

              I am glad for this.
              Is it published in git?
              I will want to test it 😄 .

              florentF 1 Reply Last reply Reply Quote 0
              • G Offline
                gasky
                last edited by

                I'm sorry this is a bit over my head but I'm glad to see that you have found the issue. I assume that it will become available in a Xen Orchestra update in the near future? I'm keen to try it out when it does. Thanks

                florentF 1 Reply Last reply Reply Quote 0
                • florentF Offline
                  florent Vates 🪐 XO Team @Gheppy
                  last edited by

                  @Gheppy I only identfied the data , I didn't write any code for now

                  1 Reply Last reply Reply Quote 0
                  • florentF Offline
                    florent Vates 🪐 XO Team @gasky
                    last edited by

                    @gasky thank you for signaling this and helping us identifying the cause

                    G 1 Reply Last reply Reply Quote 0
                    • G Offline
                      gasky
                      last edited by

                      Thank you for responding and helping. Please let me know when there is a solution to test out as I will be eager to try it. Thanks

                      1 Reply Last reply Reply Quote 0
                      • G Offline
                        gasky @florent
                        last edited by

                        @florent I was recently able to test the .ova export again and I was pleased to find that it worked without the errors we had been experiencing. I'm not sure if this is something that I should be putting in a new topic but the only thing now stopping me is that for some reason I cannot get the network drivers to work on a brand new Win10 VM. I exported a working Win10 VM from my local VMware workstation. I then imported it into XCP-ng using the latest version of Xen Orchestra and it worked as expected. I then tried exporting as .ova from Xen orchestra without installing Citrix drivers (and then tried a test with the Cirtrix drivers installed), but after importing back into VMware I couldn't get any network options to work except a 3rd party USB to Ethernet adaptor.

                        Thanks in advance if you have any advice.

                        1 Reply Last reply Reply Quote 0
                        • olivierlambertO Offline
                          olivierlambert Vates 🪐 Co-Founder CEO
                          last edited by

                          That's on VMware side then, double check you have all the emulated NICs setup in VMware 🙂

                          1 Reply Last reply Reply Quote 0
                          • olivierlambertO olivierlambert marked this topic as a question on
                          • olivierlambertO olivierlambert has marked this topic as solved on
                          • First post
                            Last post