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

    ISO Importing Results in .img Files

    Scheduled Pinned Locked Moved Management
    49 Posts 8 Posters 16.4k Views 9 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.
    • olivierlambertO Online
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by olivierlambert

      No, because only ISO SRs are in read only mode (ie when using a CD, you will never write on it). That's why it can be shared between pools, unlike a VM VDI SR, where you need a lock/write access. You can't coordinate locks outside a pool.

      1 Reply Last reply Reply Quote 1
      • planedropP Offline
        planedrop Top contributor
        last edited by

        Just wanted to chime in to say thanks for looking into this and "glad" you can reproduce it. If there's anything I can do to help/test let me know, would be happy to.

        1 Reply Last reply Reply Quote 0
        • DanpD Danp referenced this topic on
        • O Offline
          Octive
          last edited by

          Im experiencing this behavior up loading iso, one post mentions we can safely rename the iso after import.

          Is this the recommended workaround?

          Also i notice the same thing is happening with my vms. Can. I simply rename the vm as well?

          planedropP 1 Reply Last reply Reply Quote 0
          • planedropP Offline
            planedrop Top contributor @Octive
            last edited by

            @Octive For now that is the right solution in terms of ISOs, it's what I've been doing in a production environment without any issues at all.

            What do you mean same thing with VMs though? Importing from where? They aren't ISOs so that is a different story entirely, don't just go renaming VMs that's for sure.

            For clarity, you can rename the ISO files in your ISO SR's just fine and then do a rescan of the SR and they will be found.

            O 1 Reply Last reply Reply Quote 0
            • O Offline
              Octive @planedrop
              last edited by

              @planedrop Good morning,

              Thanks for the input I have renamed my ISO's directly, and now I can easily track each iso on my NAS.

              Here is what I mean when checking my VMs.

              screenshot of XO-CE.png

              Example:

              For my test lab, the display name for XO-CE is XO-CE_urene when creating the VM. However, when viewing the VM on my NAS, the Guid appears:

              screenshot of nas.png

              I was expecting to see (XO-CE_urene) as the .vhd and thought this might be the same thing going on with the ISO files.

              I'm still learning the system and don't know what the expected behavior is. 🙂

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

                I think the issue is that when we upload a raw file to the SR, SMAPIv1 won't take the name but create an UUID directly 😕

                O 1 Reply Last reply Reply Quote 0
                • O Offline
                  Octive @olivierlambert
                  last edited by

                  @olivierlambert said in ISO Importing Results in .img Files:

                  take the name but create an UUID directl

                  I can try a different connection method I'm currently using.

                  NFS v4 and DNS names to connect to backend storage.

                  I can test with a lower NFS version or switch over to ISCSI targets to see if I can replicate it.

                  1 Reply Last reply Reply Quote 0
                  • planedropP Offline
                    planedrop Top contributor @Octive
                    last edited by

                    @Octive Oh gotcha, you can rename the disks as you want within XO itself but don't rename the long UUID.vhd files within the file system, you don't want to mess with those. The UUID is used to track the file itself rather than what you name it in XO. You can't rename the disks to something other than a UUID though (at the file system level).

                    1 Reply Last reply Reply Quote 1
                    • planedropP Offline
                      planedrop Top contributor
                      last edited by

                      Just jumping back to this thread, since as far as I can tell it's still happening, was this supposed to be fixed?

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

                        It's a XAPI/SMAPI thing (not XO related), and we have far more pressing things to deal with ATM. I'm not sure there's an easy solution.

                        planedropP 1 Reply Last reply Reply Quote 1
                        • planedropP Offline
                          planedrop Top contributor @olivierlambert
                          last edited by

                          @olivierlambert Gotcha, totally agree, super low on the list of things to do.

                          I do wonder if maybe a note should be added somewhere saying you'll have to manually rename the files after importing? Maybe hear near the note about ISO importing?

                          84aee289-b7e6-4bcc-a1b8-1edfbe5ba107-image.png

                          1 Reply Last reply Reply Quote 1
                          • P Offline
                            plaidypus
                            last edited by

                            This is still happening for us on our Community Edition instance that I updated today, but the odd thing I noticed is that it doesn't happen immediately. When I upload an iso file, it keeps the name for a while, but when I return the next day, it is renamed to the <uuid>.img file.

                            Maybe there's some maintenance job that runs that does the renaming?

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

                              I don't think so, adding @Team-XAPI-Network in the loop

                              A psafontP 2 Replies Last reply Reply Quote 0
                              • A Offline
                                acebmxer @olivierlambert
                                last edited by acebmxer

                                @olivierlambert

                                I was noticing this myself many commits ago. I have not uploaded an ISO since updating.

                                In my testing i wasnt sure if it was my proxy manager doing it as it didnt see to to do that when i upload vis the ip of xo-ce vs proxy manager.

                                I have since mounted the ISO share on a PC and the ISO did infact have a .img file format but not all ISO's. Also file name had generic a-z 1-0 file name.

                                I have since deleted those ISOs from the share and manually copied over the ISO. XO-CE updated once it saw the new ISO but as of now (Three days) ISO's has remained as ISO's.

                                1 Reply Last reply Reply Quote 0
                                • psafontP Offline
                                  psafont Vates 🪐 XAPI & Network Team @olivierlambert
                                  last edited by

                                  @olivierlambert Just tried it, because I don't know what XO does:

                                  It starts with a vdi create on the ISO SR:

                                  Oct  8 17:10:20 vega xapi: [debug||2506617 HTTPS XO_IP->:::80|VDI.create R:ceff14462188|audit] VDI.create: SR = 'ISOs' UUID'; name label = 'ubuntu-24.04.3-live-server-arm64.iso'
                                  

                                  then it imports the iso into it:

                                  Oct  8 17:10:20 vega xapi: [ info||2411746 HTTPS XO_IP->:::80|task.create D:355d9ec67664|taskhelper] task [XO] Importing content into VDI ubuntu-24.04.3-live-server-arm64.iso on SR ISOs R:0506cfe68373 (uuid:96ba5dea-ffc5-5131-571d-7545277a7083) created (trackid=df64863568c5db04d470bfd2c5872e20) by task D:355d9ec67664
                                  Oct  8 17:10:21 vega xapi: [debug||2506627 HTTPS XO_IP->:::80|[XO] Importing content into VDI ubuntu-24.04.3-live-server-arm64.iso on SR ISOs R:0506cfe68373|import] import_raw_vdi task_id = OpaqueRef:0506cfe6-8373-7b22-505b-fcc07348bb7b vdi = OpaqueRef:81c1154f-17f4-2114-7c7a-bd74604aff6f; chunked = false; format = raw
                                  

                                  I see SM managing a vdi with the name UUID.img, a strange error, but it ends up creating the VDI with the expected name. I'll wait to see if the same thing happens and it's later renamed to the .img. I've refreshed the SR just in case, but I can't reproduce the issue just yet

                                  1 Reply Last reply Reply Quote 0
                                  • A Offline
                                    acebmxer
                                    last edited by acebmxer

                                    I just uploaded xcp-ng-8.3.0.iso and this is what i seee... I changed the file name to xcp-ng-8.3.iso before upload to prevent duplication file.

                                    Screenshot 2025-10-08 124222.png

                                    Screenshot 2025-10-08 124322.png

                                    Edit - I just tried to upload direct to xo-ce and same outcome.

                                    Screenshot 2025-10-08 124738.png

                                    psafontP 1 Reply Last reply Reply Quote 1
                                    • P Offline
                                      plaidypus @plaidypus
                                      last edited by

                                      Another thing I noticed is that if I rename the ISO in the XO UI, it will keep that name in the UI, but I can't seem to use it mount to any VMs using the Console or Disks tab. A rescan of the SR didn't seem to make a difference either.

                                      1 Reply Last reply Reply Quote 0
                                      • psafontP Offline
                                        psafont Vates 🪐 XAPI & Network Team @acebmxer
                                        last edited by

                                        @acebmxer I tried to force it by uploading the same iso twice, and couldn't reproduce the issue. XO shouldn't allow to upload an ISO to an SR with the same name 🙂

                                        1 Reply Last reply Reply Quote 0
                                        • A Offline
                                          acebmxer
                                          last edited by

                                          @psafont thats good to know the system will prevent you from uploading the same ISO.

                                          Since my latest testing i cant seeem to get XO-CE to show the incorrect file name .img of the iso that was uploaded. But know @plaidypus is not alone in this as I have seen it myself and that is why you will see most of the iso in the picture have a date just a few days prior to this recent testing.

                                          I manually deleted the iso that were .img and manually uploaded the ISOs again.

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post