Remember directories

[Richard Laager]

For the ISO and Simple Disk paths, I'd like to see virt-manager remember previous entries. It would chop off the filename component to get a directory component. If the last element of that were the name of the virtual machine (being created), then that component would be replaced by some marker (%s or whatever) that could be replaced later. Then that directory would be saved. In the future, it would be used as the default in the appropriate field. The ISO and Simple Disk directories should be tracked separately.

For example, if I was created a virtual machine named "foo" and changed my disk path to /srv/virtualmachines/foo/foo.img, it would save /srv/virtualmachines/%s as the directory for next time. Then when I went to create bar, it would add bar.img (as it does now) to that saved path, replacing %s with the host name, yielding /srv/virtualmachines/bar/bar.img.

[Richard Laager (rlaager)]

Alternatively, a default directory structure would be fine. If you're creating a number of VMs, it's nice to have some consistency.

[Dustin Kirkland  (kirkland)]

Thanks for the bug report.

Agreed, most annoying!

:-Dustin

[Daniel (daniel-redhat-bugs)]

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4) Gecko/2008111318 Ubuntu/8.10 (intrepid) Firefox/3.0.4

For the ISO and Simple Disk paths, I'd like to see virt-manager remember previous entries. It would chop off the filename component to get a directory component. If the last element of that were the name of the virtual machine (being created), then that component would be replaced by some marker (%s or whatever) that could be replaced later. Then that directory would be saved. In the future, it would be used as the default in the appropriate field. The ISO and Simple Disk directories should be tracked separately.

For example, if I was created a virtual machine named "foo" and changed my disk path to /srv/virtualmachines/foo/foo.img, it would save /srv/virtualmachines/%s as the directory for next time. Then when I went to create bar, it would add bar.img (as it does now) to that saved path, replacing %s with the host name, yielding /srv/virtualmachines/bar/bar.img.

Reproducible: Always

[Marc Deslauriers (mdeslaur)]

In recent virt-manager versions, such as the one currently in Lucid, you can now add storage pools, which solves the issue.

[Cole (cole-redhat-bugs)]

Actually I don't think we will implement this in virt-manager, I don't think it's common that people store disk images in multiple places so it really isn't something worth spending dev resources on facilitating.

If people want to easily use a non default storage path they should use some mechanism to tell virt-manager their preferred storage location (there are other bugs tracking that).