Bug 684134 - Unable to create CDROM device for defined guest
Summary: Unable to create CDROM device for defined guest
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 14
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-11 09:02 UTC by Liam Dennehy
Modified: 2011-06-01 09:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-01 09:54:25 UTC
Type: ---


Attachments (Terms of Use)
Incorrect elements on Add device screen (2.98 KB, image/png)
2011-03-11 09:02 UTC, Liam Dennehy
no flags Details
Incorrect elements on Add device screen (74.96 KB, image/png)
2011-03-11 10:53 UTC, Liam Dennehy
no flags Details

Description Liam Dennehy 2011-03-11 09:02:22 UTC
Created attachment 483665 [details]
Incorrect elements on Add device screen

Description of problem:
When trying to add a CDROM (IDE) device to an existing guest, the storage allocation details remain on screen requesting initial size and path, as required for virtual hard drives. Trying to proceed results in an error, either that requested storage size exceeds available space, or, if a smaller size is entered, that storage cannot be allocated to a CDROM device.

Manuall adding the configuration to the XML works, as does creating a new VM from scratch (bypassing the add device dialog).

Version-Release number of selected component (if applicable):
0.8.5-1.fc14

How reproducible:
Always

Steps to Reproduce:
1. Open configuration of an existing VM
2. Add Device, Storage, IDE-CDROM
3.
  
Actual results:
Storage allocation window remains

Expected results:
Only the path to the physical device or image file should remain

Additional info:

Comment 1 Liam Dennehy 2011-03-11 10:53:23 UTC
Created attachment 483682 [details]
Incorrect elements on Add device screen

Comment 2 Liam Dennehy 2011-06-01 09:54:25 UTC
Apepars to be resolved in a following release, and doesn't appear present in F15.


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