This service will be undergoing non-disruptive maintenance at 07:20 UTC, 2018-12-14. It is expected to last approximately 30 minutes
Bug 708735 - [RFE] Show column and line on XML parsing error
Summary: [RFE] Show column and line on XML parsing error
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
(Show other bugs)
Version: 6.3
Hardware: Unspecified Unspecified
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: Virtualization Bugs
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2011-05-29 08:42 UTC by Saggi Mizrahi
Modified: 2015-03-02 05:22 UTC (History)
8 users (show)

Fixed In Version: libvirt-0.9.9-1.el6
Doc Type: Enhancement
Doc Text:
No Documentation needed
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 06:28:04 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0748 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2012-06-19 19:31:38 UTC

Description Saggi Mizrahi 2011-05-29 08:42:26 UTC
Description of problem:
I would like to be able to see a context output similar to what a compiler gives on XML parsing errors

example output

Parsing error too many >
Line 435, Column 35:
     <element>Funky Text</elemnt>> <thingy/>

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 2 Peter Krempa 2011-09-06 10:15:21 UTC
Fixed in upstream:

commit 9fd3bb7a88bd41a5cf4830529b3b3c87260be62e
Author: Peter Krempa <>
Date:   Tue Sep 6 15:48:22 2011 +0800

    XML: Improve XML parsing error messages
    This patch modifies error handling function for the XML parser provided
    by libxml2.
    Originaly only a line number and error message were logged. With this
    new error handler function, the user is provided with a more complex
    description of the parsing error.
    Context of the error is printed in libXML2 style and filename of the
    file, that caused the error is printed. Example of an parse error:
    13:41:36.262: 16032: error : catchXMLError:706 :
    /etc/libvirt/qemu/rh_bad.xml:58: Opening and ending tag mismatch: name
    line 2 and domain
    Context of the error gives the user hints that may help to quickly
    locate a corrupt xml file.

Comment 4 yuping zhang 2012-01-10 03:21:32 UTC
Verified this issue with:


1.# virsh edit 2
error: (domain_definition):5: StartTag: invalid element name

2012-01-10 03:07:45.056+0000: 1812: error : catchXMLError:711 : (domain_definition):5: StartTag: invalid element name

So change the status to VERIFIED.

Comment 5 Peter Krempa 2012-05-02 13:04:11 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    New Contents:
No Documentation needed

Comment 7 errata-xmlrpc 2012-06-20 06:28:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

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