Bug 1223631 - smbios, sysinfo, idmap, metadata will lose if we set a memory device in the xml
Summary: smbios, sysinfo, idmap, metadata will lose if we set a memory device in the xml
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.2
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: Virtualization Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2015-05-21 05:00 UTC by Luyao Huang
Modified: 2015-11-19 06:31 UTC (History)
6 users (show)

Fixed In Version: libvirt-1.2.16-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-11-19 06:31:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2202 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2015-11-19 08:17:58 UTC

Description Luyao Huang 2015-05-21 05:00:52 UTC
description of problem:
smbios, sysinfo, idmap, metadata will lose if we set a memory device in the xml

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

How reproducible:

Steps to Reproduce:
1. edit a guest xml like this:
# virsh edit test3

  <maxMemory slots='16' unit='KiB'>2560000</maxMemory>
  <memory unit='KiB'>1536000</memory>
  <currentMemory unit='KiB'>1024000</currentMemory>
    <type arch='x86_64' machine='pc-i440fx-rhel7.1.0'>hvm</type>
    <boot dev='hd'/>
    <smbios mode='sysinfo'/>
  <cpu mode='host-model'>
    <model fallback='forbid'/>
      <cell id='0' cpus='0-1' memory='512000' unit='KiB'/>
      <cell id='1' cpus='2-3' memory='512000' unit='KiB'/>
    <memory model='dimm'>
        <size unit='KiB'>512000</size>

Domain test3 XML configuration not changed.

2. recheck the xml:
    <type arch='x86_64' machine='pc-i440fx-rhel7.1.0'>hvm</type>
    <boot dev='hd'/>

Actual results:
smbios, sysinfo, idmap, metadata will lose if we set a memory device in the xml

Expected results:
libvirt can parse smbios, sysinfo, idmap, metadata when set a memory device


Additional info:

Comment 1 Luyao Huang 2015-05-21 05:10:17 UTC
Send a patch to upstream:


Comment 2 Peter Krempa 2015-05-21 09:07:35 UTC
Fixed upstream:

commit aef2a0a26c42efeedd25ad570269f5f1cc9da6b5
Author: Luyao Huang <lhuang@redhat.com>
Date:   Thu May 21 13:08:12 2015 +0800

    conf: Restore the XML parser context in virDomainMemoryDefParseXML
    After parsing the memory device XML the function would not restore the
    XML parser context causing invalid XPath starting point for the rest of
    the elements. This is a regression since 3e4230d2.
    The test case addition uses the <idmap> element that is currently unused
    by qemu, but parsed after the memory device definition and formatted
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1223631
    Signed-off-by: Luyao Huang <lhuang@redhat.com>
    Signed-off-by: Peter Krempa <pkrempa@redhat.com>


Comment 4 Fangge Jin 2015-08-26 11:55:20 UTC
I can reproduce this bug on build libvirt-1.2.15-2.el7.x86_64

Verify this bug on build libvirt-1.2.17-6.el7.x86_64

1.Edit a guest xml like this:
# virsh edit rhel7d1
  <maxMemory slots='16' unit='KiB'>2560000</maxMemory>
  <memory unit='KiB'>1024000</memory>
  <currentMemory unit='KiB'>1024000</currentMemory>
    <type arch='x86_64' machine='pc-i440fx-rhel7.1.0'>hvm</type>
    <boot dev='hd'/>
    <boot dev='cdrom'/>
    <bootmenu enable='yes' timeout='3000'/>
    <bios useserial='yes' rebootTimeout='0'/>
    <smbios mode='sysinfo'/>
  <sysinfo type='smbios'>
      <entry name='vendor'>LENOVO</entry>
    <uid start='0' target='1000' count='10'/>
    <gid start='0' target='1000' count='10'/>
    <memory model='dimm'>
        <size unit='KiB'>512000</size>
Domain rhel7d1 XML configuration edited.

2.Recheck the xml, all the attributes still exist.

Comment 6 errata-xmlrpc 2015-11-19 06:31:22 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.