Gns3-gui: Qemu image is copied to local directory even if not needed

Created on 9 May 2016  路  4Comments  路  Source: GNS3/gns3-gui

Qemu images are added to the local /home/_user_/GNS3/images/QEMU directory even if I import the .gns3a appliance to a remote server, like this:
add_appliance-remote

Obviously everything works fine if I delete those files from the local directory because nothing references them.

PS: This is not a high prio issue, just wanted to let you know.
PS2: I wasn't sure if I should open the issue here or in the gns3-registry, hope I made the right choice. :)

Bug

All 4 comments

For me it's work as designed.

The image is copied at this place to allow futur usage for example the first time you use the appliance.

Changing that require to push image on the remote server in the wiazard. We could do that but this add a lot of complexity in the import appliance code.

I was thinking pushing the image from its original location when the appliance is used for the first time, not changing the wizard. However what you say is a safer way, the image will be available even if the user removes it from its original directory.

I think both ways are acceptable, it shouldn't cause a problem during everyday usage. In fact I wouldn't have noticed it if I haven't tested all those appliances for gns3-registry (my SSD is only 240G, a directory with 20G of qemu images was noticeable :)).

It's your call if you'll change this behavior later or keep the current one and close this issue.

I don't know if we should not garbage collect images on the remote server when not used to save space in the VM. Not sure about the best strategy.

Will be solved by #1590

Was this page helpful?
0 / 5 - 0 ratings