description of problem:
numa settings disapear after restart libvirtd

Version-Release number of selected component (if applicable):
libvirt-1.2.13-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
 
1.edit a vm like this:
# virsh edit r6
  <cpu>
    <numa>
      <cell id='0' cpus='0,2,4,6,8' memory='512000' unit='KiB'/>
      <cell id='1' cpus='1,3,5,7,9' memory='512000' unit='KiB'/>
    </numa>
  </cpu>

2.start it and check running vm xml:
# virsh start test3

# virsh dumpxml test3
  <cpu>
    <numa>
      <cell id='0' cpus='0,2,4,6,8' memory='512000' unit='KiB'/>
      <cell id='1' cpus='1,3,5,7,9' memory='512000' unit='KiB'/>
    </numa>
  </cpu>

3. restart libvirtd and recheck

# service libvirtd restart
Redirecting to /bin/systemctl restart  libvirtd.service

# virsh dumpxml test3
...
  <cpu/>
...

Actual results:
numa settings disapear after restart libvirtd

Expected results:
fix it

infomation:

patch was just pushed these days:

commit d75e23bbfb92793ac6828a6eff6d909c5f92cc9b
Author: Luyao Huang <lhuang>
Date:   Thu Mar 19 18:13:04 2015 +0800

    conf: fix parsing of NUMA settings in VM status XML
    
    Commit 5bba61f changed the XPath strings to be absolute when parsing
    the VM NUMA configuration. Unfortunately the <domain> element is not a
    top level element when parsing the domain status XML thus the absolute
    XPath string doesn't match.
    
    Use the relative string so that the <numa> settings are not lost.
    
    Signed-off-by: Luyao Huang <lhuang>