Red Hat Bugzilla – Bug 859012
Unable to choose a different storage pool to store new vm's that are being created
Last modified: 2012-10-13 21:15:23 EDT
Description of problem:
Cant choose a different storage pool to store vm's being created in the "New" vm's wizard
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Start Virtual Machine Manager
Go to Edit -> Connection details
Select storage and add another storage pool ( like /home/$user/.libvirt/images/)
Now create a new VM
Enter the name choose Local install media and go Forward
Choose use ISO Image and select available ISO ( in my case F17 )
Set OS Type to Linux,Version to Fedora17 ( note this option lacks F18 and Rawhide ) go Forward
Accept the default and go Forward
We are now at step 4 of 5 which lacks the option to allow the user to select the newly created storage pool to store the vm which is being created.
No option to select the newly created storage pool to store the new vm image on Thus the vm that is being created gets stored in the default storage pool
Being able to choose which storage pool the vm being create should be stored on
Giving an up front option to create the storage in a different pool is something we deliberately avoided.
If you want to do a one off:
- New VM
- Go to page 4
- Select 'use managed or existing...'
- Select your pool
- New volume
- Follow that wizard
- Select the volume
- Exit dialog
If you want to have a pool be the new default for all your storage, remove the old pool, and change the name of your new pool to 'default' and virt-manager will use it. I do want to make this easier though, see #673025
Maybe we could find a way to make that browse dialog enable just choosing a pool, but I think it would be kinda awkward.
Closing as WONTFIX, but please reopen if I've missed something.