<![CDATA[ISO Importing Results in .img Files]]>Wanted to post a dedicated post here, a while back I had an issue where I uploaded a whole bunch of ISO files from the Import > Disk section of XOA, after doing so I noticed that for some reason I could only see them in the drop down for new VMs on one host (the one that I uploaded them from) even though they were files residing on a shared NAS that all 3 of my hosts had access to.

Anyway, after posting about that @olivierlambert had me check file extensions and I realized all of them were uploaded as img instead of .iso. I renamed them all to what I wanted them to be called and .iso at the end and instantly they all showed up when creating new VMs from all hosts.

Do we know why these are being imported as what appears to be a UUID.img file? My understanding is they should all be .iso files and also shouldn't need a UUID assigned to them.

]]>https://xcp-ng.org/forum/topic/7663/iso-importing-results-in-img-filesRSS for NodeMon, 14 Sep 2026 00:28:32 GMTThu, 24 Aug 2023 17:38:11 GMT60<![CDATA[Reply to ISO Importing Results in .img Files on Thu, 09 Oct 2025 22:12:25 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/98338https://xcp-ng.org/forum/post/98338Thu, 09 Oct 2025 22:12:25 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Thu, 09 Oct 2025 17:21:30 GMT]]>@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 🙂

]]>https://xcp-ng.org/forum/post/98321https://xcp-ng.org/forum/post/98321Thu, 09 Oct 2025 17:21:30 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Wed, 08 Oct 2025 16:50:17 GMT]]>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.

]]>https://xcp-ng.org/forum/post/98288https://xcp-ng.org/forum/post/98288Wed, 08 Oct 2025 16:50:17 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Wed, 08 Oct 2025 16:49:00 GMT]]>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

]]>https://xcp-ng.org/forum/post/98287https://xcp-ng.org/forum/post/98287Wed, 08 Oct 2025 16:49:00 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Wed, 08 Oct 2025 16:35:18 GMT]]>@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

]]>https://xcp-ng.org/forum/post/98286https://xcp-ng.org/forum/post/98286Wed, 08 Oct 2025 16:35:18 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Wed, 08 Oct 2025 16:34:18 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/98285https://xcp-ng.org/forum/post/98285Wed, 08 Oct 2025 16:34:18 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Wed, 08 Oct 2025 15:56:50 GMT]]>I don't think so, adding @Team-XAPI-Network in the loop

]]>https://xcp-ng.org/forum/post/98284https://xcp-ng.org/forum/post/98284Wed, 08 Oct 2025 15:56:50 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Wed, 08 Oct 2025 15:55:55 GMT]]>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?

]]>https://xcp-ng.org/forum/post/98283https://xcp-ng.org/forum/post/98283Wed, 08 Oct 2025 15:55:55 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Sat, 09 Mar 2024 03:09:31 GMT]]>@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

]]>https://xcp-ng.org/forum/post/73133https://xcp-ng.org/forum/post/73133Sat, 09 Mar 2024 03:09:31 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Fri, 08 Mar 2024 23:22:21 GMT]]>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.

]]>https://xcp-ng.org/forum/post/73131https://xcp-ng.org/forum/post/73131Fri, 08 Mar 2024 23:22:21 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Fri, 08 Mar 2024 19:20:16 GMT]]>Just jumping back to this thread, since as far as I can tell it's still happening, was this supposed to be fixed?

]]>https://xcp-ng.org/forum/post/73121https://xcp-ng.org/forum/post/73121Fri, 08 Mar 2024 19:20:16 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Tue, 09 Jan 2024 22:22:03 GMT]]>@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).

]]>https://xcp-ng.org/forum/post/69373https://xcp-ng.org/forum/post/69373Tue, 09 Jan 2024 22:22:03 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Tue, 09 Jan 2024 13:58:26 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/69344https://xcp-ng.org/forum/post/69344Tue, 09 Jan 2024 13:58:26 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Tue, 09 Jan 2024 13:47:42 GMT]]>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 😕

]]>https://xcp-ng.org/forum/post/69339https://xcp-ng.org/forum/post/69339Tue, 09 Jan 2024 13:47:42 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Tue, 09 Jan 2024 13:32:03 GMT]]>@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. 🙂

]]>https://xcp-ng.org/forum/post/69335https://xcp-ng.org/forum/post/69335Tue, 09 Jan 2024 13:32:03 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Tue, 09 Jan 2024 02:49:58 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/69292https://xcp-ng.org/forum/post/69292Tue, 09 Jan 2024 02:49:58 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Sat, 06 Jan 2024 16:40:16 GMT]]>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?

]]>https://xcp-ng.org/forum/post/69232https://xcp-ng.org/forum/post/69232Sat, 06 Jan 2024 16:40:16 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Thu, 16 Nov 2023 23:04:56 GMT]]>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.

]]>https://xcp-ng.org/forum/post/67485https://xcp-ng.org/forum/post/67485Thu, 16 Nov 2023 23:04:56 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Mon, 13 Nov 2023 10:56:34 GMT]]>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.

]]>https://xcp-ng.org/forum/post/67357https://xcp-ng.org/forum/post/67357Mon, 13 Nov 2023 10:56:34 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Mon, 13 Nov 2023 10:54:59 GMT]]>@olivierlambert this where it gets fun

after a rescan, the iso is listed in the SR > disks tabs, but since its vdi uuid is the same the link vdi to SR only show one SR.
The fix won't be trivial, I created a task in the backlog for this

Is it possible for non iso SR to be connected to multiple pool ?

]]>https://xcp-ng.org/forum/post/67356https://xcp-ng.org/forum/post/67356Mon, 13 Nov 2023 10:54:59 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Mon, 13 Nov 2023 10:05:52 GMT]]>Even after a rescan?

]]>https://xcp-ng.org/forum/post/67352https://xcp-ng.org/forum/post/67352Mon, 13 Nov 2023 10:05:52 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Mon, 13 Nov 2023 10:03:39 GMT]]>@olivierlambert I don't think we do any filtering, the iso uploaded to another pool doesn't appear in the xapi calls result

]]>https://xcp-ng.org/forum/post/67351https://xcp-ng.org/forum/post/67351Mon, 13 Nov 2023 10:03:39 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Mon, 13 Nov 2023 09:33:50 GMT]]>@olivierlambert Oh yes, that's right the file does not appear in the iso list

only the file really named *.iso of the SR are listed
I am checking where do we filter it

]]>https://xcp-ng.org/forum/post/67348https://xcp-ng.org/forum/post/67348Mon, 13 Nov 2023 09:33:50 GMT<![CDATA[Reply to ISO Importing Results in .img Files on Mon, 13 Nov 2023 09:27:04 GMT]]>Yeah but I can assume the name is correct here, but not from another pool connected to this SR, since the VDI name is only used from the original filename that is unknown outside the pool.

]]>https://xcp-ng.org/forum/post/67347https://xcp-ng.org/forum/post/67347Mon, 13 Nov 2023 09:27:04 GMT