ISO Importing Results in .img Files
-
@olivierlambert I will try with a URL on this ISO in specific later, but I tried the vyOS one you linked and got this (it's from my TrueNAS CLI but also is what the XCP-ng host sees):
The vyOS one got imported as the long UUID.img and doing a file command ont hat shows it's that ISO.
-
That's very weird, I can't reproduce here
-
@olivierlambert Interesting, so it just shows up as the filename.iso for you?
I can say this is happening in 2 different environments and 3 different XO installs, 1 is a full enterprise supported XOA, another is the free version of XOA, and the 3rd is a built from the sources XOCE.
I'll see if I can think of anything else to test, definitely an odd one.
-
Yes, "filename.iso"
-
@olivierlambert Hmmm odd, I'll keep testing to see if I can find a pattern, but so far I've never had it do a .ISO file.
Maybe a bug of some kind?
It shouldn't have anything to do with XCP-ng itself right, this is all handled by XO? Either way I'm on fully patched 8.2
-
I can't tell as long I can't reproduce it. Anyone else having the same behavior?
-
@olivierlambert So far I haven't seen anyone else running across this, but maybe people aren't using the feature a ton? Normally I just move my ISOs to the SMB share manually but decided to use this feature for it instead and then noticed it created all the .img files.
It may be worth noting that whatever host that manages the SR I select, can indeed use the .img files to boot, but other hosts using the same ISO SR won't see them until I rename the files to .iso of some sort.
-
I will try to use this option as well, although I don't like that the files are stored as UUID.iso, I prefer to have them as names.
I prefer to have RockyLinux.9.2.iso than to have 89c425b6-42b7-11ee-be56-0242ac120002.iso.
If I can no longer recover the metadata, these UUIDs are of no use. You must identify them first. -
@Gheppy Yeah I agree, and I think what @olivierlambert is saying is that they should import as raw so in theory the name shouldn't change right?
Thanks for helping test this out!
-
I can confirm that the file *.iso importing is converted to *.img
Importing
File on share is
File on XOCE, commit 3baa37846e6dbe775a8891f51f7eaebbbb28bea6
-
@Gheppy This is good to know, thank you!
So at least I know I'm not just super unlucky haha.
So far I haven't been able to get it to do a .iso properly, but I will keep trying various things.
-
O olivierlambert moved this topic from Xen Orchestra on
-
Looks like this is still happening on the latest XO version, any ideas/updates @olivierlambert ?
@Gheppy you still seeing this as well?
Fix is easy enough for me for now, just rename to .iso and everything is good, just a bit odd.
-
Can you check if there's a diff between a local ISO SR and a shared NFS ISO SR?
-
The problem is the same with all form of ISO SR: local, cifs (smb), nfs. On all I have *.img
-
I've only tested local and SMB so far but both did the same thing.
-
@florent can you reproduce this?
-
@olivierlambert yep
upload are renamed as uuid.img , I will check if it is on XO or XCP side
-
And what is displayed in the SR VDI names? It might be the right name but if you are connecting the same ISO SR via another pool, it won't (since it's only local metadata I assume).
-
@olivierlambert
the displayed size is ok on XO :
the file created is
/run/sr-mount/acf947c6-5204-a149-ad41-a5981cc6a3db/0144fd11-d5e6-4915-a153-40548c9d0a60.imgin our lab and the extension choice seems to be made on the host sizethis iso is available on VM creation
-
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.
