Description of the problem: An then there is the name used for the virtual disk file. Previously, the name of the virtual system was used and it was pretty easy to determine what image was associate with what virtual system. Now, the type and version of the installed OS is being used as the base name for the image file. Now, I have to use the storage connection details to figure out usage. Response by Cole Robinson: Hmm. The disk image name is supposed to match the name of the VM, and the defualt VM name was changed to match the chosen OS. There might be a bug here where we don't change the generated disk image name if the user changes the VM name from the default. Please file a virt-manager bug, with full steps to reproduce, and virt-manager --debug output when reproducing. I set the severity to urgent because virt-manager is now getting confused about the virt disk file names and reusing names it should not. Version-Release number of selected component (if applicable): virt-manager-1.1.0-4.git310f6527.fc20.noarch How reproducible: everytime Steps to Reproduce: 1.create a new Fedora 21 virtual system 2.change the name of the system from Fedora21 to test21 3.do the install Actual results: virtual disk file is named some variation of fedora21.img Expected results: virtual disk file is named some variation of test21.img Additional info:
Fixed upstream now: commit 4a678f05439da9f17c8cd89f22a59df1b27eddd6 Author: Cole Robinson <crobinso> Date: Wed Dec 3 13:08:18 2014 -0500 create: Fix default storage path when VM name is changed (bz 1169141)
OK, it looks like you have a lot of updates in the git repository after that which is in Fedora 21 or the fedora-virt-preview ... perhaps too many for a day-zero or day-one update. So, if I want to see this fixed anyh time soon, it means that I will need to build my own rpms. What do you recommend? 1) current plus just the two updates commit 4a678f05439da9f17c8cd89f22a59df1b27eddd6 and commit 01d6541f69fca943b2b13717187eae709396567c or 2) "go for it" and apply them all as of today?
The two commits should be simple backports so I'd recommend that Though I'm hoping to cut a new virt-manager release within the next two weeks and push that to f21
virt-manager-1.1.0-5.git310f6527.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/virt-manager-1.1.0-5.git310f6527.fc21
Package virt-manager-1.1.0-5.git310f6527.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing virt-manager-1.1.0-5.git310f6527.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4962/virt-manager-1.1.0-5.git310f6527.fc21 then log in and leave karma (feedback).
virt-manager-1.1.0-5.git310f6527.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.