Bug 859012 - Unable to choose a different storage pool to store new vm's that are being created
Summary: Unable to choose a different storage pool to store new vm's that are being cr...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-20 11:09 UTC by Jóhann B. Guðmundsson
Modified: 2012-10-14 01:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-14 01:15:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jóhann B. Guðmundsson 2012-09-20 11:09:48 UTC
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):

0.9.4

How reproducible:

Always

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.

Actual results:

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


Expected results:

Being able to choose which storage pool the vm being create should be stored on

Additional info:

Comment 1 Cole Robinson 2012-10-14 01:15:23 UTC
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...'
- Browse
- 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.


Note You need to log in before you can comment on or make changes to this bug.