Bug 1419464

Summary:	make a better documentation for the installation process in virt-manager
Product:	[Community] Virtualization Tools	Reporter:	Xiaodai Wang <xiaodwan>
Component:	virt-manager	Assignee:	virt-mgr-maint
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	berrange, crobinso, gscrivan, juzhou, kuwei, mxie, mzhan, phrdina, rbalakri, tzheng
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-05 18:27:05 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:

Description Xiaodai Wang 2017-02-06 09:02:11 UTC

Description of problem:
The ISO file is not listed in source path of CDROM disk of custom configuration installation dialog 

Version-Release number of selected component (if applicable):
virt-manager-1.4.0-2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a new vm by "Local install media (ISO image or CDROM).    
2. Select an ISO file in step 2 of 5.
3. Click "Forward" until step 5 of 5, then click "Customize configuration before install".
4. Click "Finish"
5. Check the CDROM disk in custom configuration dialog.

Actual results:
The source path of CDROM disk is null.

Expected results:
The selected ISO file should be list in Source path of the CDROM disk.

Additional info:
1. I usually like to double check my configurations before begin installation, and now from the custom installation dialog, i don't know if the ISO file is the correct one, so it's better to reflect the selected ISO file in customize configuration dialog.
2. This problem won't affect the installation, so it's very low priority.

Comment 1 Pavel Hrdina 2017-02-06 11:38:44 UTC

Well, this is by design.  Virt-manager/virt-install during installation generates two XML, one that is used to install the guest and second one that is used to define the guest after installation is complete.  The install XML contains also the source for installation, ISO image or path to kernel and initrd or PXE boot as the primary boot.  Only exception is import installation where the install XML is not created at all.

Basically it works like this: the custom configuration modifies the resulting XML for the guest after the installation is completed and the install XML is created from the final XML by adding things required for installation.  This is intentional and I don't think that we should change it.  However, this could be probably documented better.

Comment 2 Cole Robinson 2017-03-05 18:27:05 UTC


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