Bug 838049

Summary: [libvirt] Domain's xml is broken after set numa parameters using numatune
Product: Red Hat Enterprise Linux 6 Reporter: hongming <honzhang>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.4CC: acathrow, ajia, dallan, dyasny, dyuan, mzhan, rwu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-06 14:47:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description hongming 2012-07-06 09:05:58 UTC
Description of problem:
Domain's  xml is broken after set numa parameters using numatune  

Version-Release number of selected component (if applicable):
kernel- 2.6.32-276.el6.x86_64
libvirt-0.9.13-2.el6.x86_64
qemu-kvm-0.12.1.2-2.295.el6.x86_64


How reproducible:
100% 

Steps to Reproduce:
1.# virsh list --all
 Id    Name                           State
----------------------------------------------------
 -     rhel6u3                        shut off

2. # virsh numatune rhel6u3 --nodeset 1


3. # virsh numatune rhel6u3
numa_mode      : strict
numa_nodeset   : 1


3.# virsh dumpxml rhel6u3

<domain type='kvm' id='2'>
  ....
  <numatune>
    <memory mode='strict'   </numatune>
 
</domain>


4. # virsh start rhel6u3
error: Failed to start domain rhel6u3
error: (domain_definition):13: error parsing attribute name
    <memory mode='strict'   </numatune>
----------------------------^
  
Actual results:
The domain's xml is broken after set numa parameters using numatune 

Expected results:
It works fine after set numa parameters using numatune.

Additional info:

Comment 2 Alex Jia 2012-07-06 09:35:43 UTC
It's a known bug 828023.

Comment 3 Dave Allan 2012-07-06 14:47:11 UTC
(In reply to comment #2)
> It's a known bug 828023.

Closing as such.

*** This bug has been marked as a duplicate of bug 828023 ***