Red Hat Bugzilla – Bug 619894
customized settings are not remembered if first attempt fails to create VM
Last modified: 2011-05-19 09:46:39 EDT
Description of problem:
I tried to use virt-manager to create a new VM with storage located on NFS. I also customized the settings (to select vga instead of cirrus for the video adapter). The first attempt failed, because of SELinux, so I backed up a screen, fixed the selinux settings, then went forward again, but my customizations were lost and I had to repeat them.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. as root, run setsebool virt_use_nfs 0
2. Start virt-manager, and connect to a host
3. Start to create a new domain
4. On step 4, select managed storage, and select a disk image on an NFS path
5. On step 5, check Customize before hitting finish
6. Make a customization, such as changing video to vga, and apply, then hit the check mark to start the install
7. The install will fail because the image can't be accessed and kick you back to step 5
8. run setsebool virt_use_nfs 1
9. Again, check customize, and notice that the customization was lost
customization is lost every time that creation fails and you get kicked back to step 5
customization should be remembered - if creation fails, and I correct the root cause of the failure, then continuing from step 5 should remember what I already changed
Not a show-stopper for 6.0.
Fixed upstream now with a combination of virt-manager and virtinst commits, though we should get it all for 'free' with the rebase.
Fixed in virt-manager-0.8.6-1.el6
Now customization can be remembered and installation is going well. So verified with passed in virt-manager-0.8.6-1.el6
# uname -a
Linux dhcp-65-85.nay.redhat.com 2.6.32-99.el6.x86_64 #1 SMP Fri Jan 14 10:46:00
EST 2011 x86_64 x86_64 x86_64 GNU/Linux
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.