Bug 813972 - libvirt should reject invalid memory values in xml
Summary: libvirt should reject invalid memory values in xml
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.3
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Eric Blake
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 617711 770683 796526
Blocks: 808522
TreeView+ depends on / blocked
 
Reported: 2012-04-18 21:53 UTC by Eric Blake
Modified: 2012-06-20 06:54 UTC (History)
10 users (show)

Fixed In Version: libvirt-0.9.10-14.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 796526
Environment:
Last Closed: 2012-06-20 06:54:31 UTC
Target Upstream Version:


Attachments (Terms of Use)


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

Comment 4 dyuan 2012-04-25 07:36:09 UTC
Verified PASS with libvirt-0.9.10-14.el6.

virsh will reject the following xml:
<memory>1G</memory>
<currentMemory>1G</currentMemory>

# virsh edit xp
error: XML error: could not parse memory element ./currentMemory[1]

# virsh define /tmp/xp.xml 
error: Failed to define domain from /tmp/xp.xml
error: XML error: could not parse memory element ./currentMemory[1]

# virsh create /tmp/xp.xml 
error: Failed to create domain from /tmp/xp.xml
error: XML error: could not parse memory element ./currentMemory[1]

Reproduced this bug with libvirt-0.9.10-12.el6.
libvirt silently use <memory unit='KiB'>1</memory> instead of 1G.

Comment 6 errata-xmlrpc 2012-06-20 06:54:31 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.

http://rhn.redhat.com/errata/RHSA-2012-0748.html


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