Bug 593336

Summary: virt-manager: Fix create wizard 'customize' if no storage: xmlParseDoc() failed
Product: Red Hat Enterprise Linux 6 Reporter: Cole Robinson <crobinso>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: dyuan, hbrock, mjenner, mzhan, xen-maint
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: virt-manager-0.8.4-3.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 21:53:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
Straight backport from upstream none

Description Cole Robinson 2010-05-18 14:42:13 UTC
To reproduce:

- Launch New VM wizard
- Choose CDROM install
- Disable all storage for the guest
- On the last page, check the 'Customize before install' option
- An error box will pop up with 'xmlParseDoc() failed' error

Fixed by the following upstream commit:


Comment 1 RHEL Product and Program Management 2010-05-18 14:55:17 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 2 Cole Robinson 2010-05-18 15:02:18 UTC
Created attachment 414885 [details]
Straight backport from upstream

Comment 3 Cole Robinson 2010-05-18 15:37:46 UTC
Fix built in virt-manager-0.8.4-3.el6

Comment 5 dyuan 2010-07-06 04:22:25 UTC
Verified PASSED with virt-manager-0.8.4-6.el6.

Comment 6 min zhan 2010-09-13 06:11:07 UTC
Verified Passed with virt-manager-0.8.4-8.el6.noarch.

Comment 7 releng-rhel@redhat.com 2010-11-10 21:53:50 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.