ISO Importing Results in .img Files
-
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.
-
@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 -
@olivierlambert I don't think we do any filtering, the iso uploaded to another pool doesn't appear in the xapi calls result
-
Even after a rescan?
-
@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 thisIs it possible for non iso SR to be connected to multiple pool ?
-
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.
-
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.
-
D Danp referenced this topic on
-
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?
-
@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.
-
@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.
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:
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.
-
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
-
@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.
-
@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).
-
Just jumping back to this thread, since as far as I can tell it's still happening, was this supposed to be fixed?
-
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.
-
@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?
