Bug 1188527

Summary: virt-manager of RHEL 7.1 Snapshot 4 does not allow to select the "Use CDROM or DVD" option while creating a VM.
Product: Red Hat Enterprise Linux 7 Reporter: Vivek Kumar <vivek.kumar>
Component: virt-managerAssignee: virt-mgr-maint
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.1CC: gscrivan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-03 08:52:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
virt-manager CDROM none

Description Vivek Kumar 2015-02-03 06:56:26 UTC
Created attachment 987417 [details]
virt-manager CDROM

Description of problem:

While creating a new VM, if a CDROM or DVD is connected to the Host OS, the virt-manager does not allow the option "Use CDROM or DVD" to be selected by the user [option is grayed out].

Version-Release number of selected component (if applicable):

virt-manager version 1.1.0
RHEL7.1 kernel: 3.10.0-224.el7

How reproducible:

Easily reproducible

Steps to Reproduce:
1. Attach CDROM and DVD to the Host OS [RHEL 7.1 Snapshot 4]
2. Start virt-manager and click on create a new virtual machine.
3. Select 'Local install media' and press Forward.
4. Observe that the option "Use CDROM or DVD" is grayed out even though the OS DVD is detected.

Actual results:

"Use CDROM or DVD" option is grayed out and unusable for the user.

Expected results:

"Use CDROM or DVD" option should not be grayed out and available for the user.

Additional info:

See attached screenshot 'RH71_VMM_CDROM.png'

Comment 2 Giuseppe Scrivano 2015-02-03 08:52:20 UTC
that is because CD/DVD host passthrough has been disabled in RHEL7. See #760885 for more details about it.

*** This bug has been marked as a duplicate of bug 1072610 ***