[virt-tools-list] [virt-manager PATCH 3/3] Fix cpuset tests
Martin Kletzander
mkletzan at redhat.com
Mon Apr 8 08:40:00 UTC 2013
In order to fix last tests that fail for me, I had to modify the
output xml, both modified machines will fit in the first numa node, so
the cpus from that node should be mentioned in the xml and that lead
me to the fact that the problem was in the test xml and not the code.
Signed-off-by: Martin Kletzander <mkletzan at redhat.com>
---
tests/cli-test-xml/compare/cpuset-auto.xml | 4 ++--
tests/xmlconfig-xml/boot-cpuset.xml | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/tests/cli-test-xml/compare/cpuset-auto.xml b/tests/cli-test-xml/compare/cpuset-auto.xml
index fde679b..7b95159 100644
--- a/tests/cli-test-xml/compare/cpuset-auto.xml
+++ b/tests/cli-test-xml/compare/cpuset-auto.xml
@@ -3,7 +3,7 @@
<uuid>00000000-1111-2222-3333-444444444444</uuid>
<memory>65536</memory>
<currentMemory>65536</currentMemory>
- <vcpu cpuset='0,2,4,6,8,10,12,14'>2</vcpu>
+ <vcpu cpuset='0,1,2,3,4,5,6,7'>2</vcpu>
<os>
<type arch='i686'>hvm</type>
<boot dev='network'/>
@@ -29,7 +29,7 @@
<uuid>00000000-1111-2222-3333-444444444444</uuid>
<memory>65536</memory>
<currentMemory>65536</currentMemory>
- <vcpu cpuset='0,2,4,6,8,10,12,14'>2</vcpu>
+ <vcpu cpuset='0,1,2,3,4,5,6,7'>2</vcpu>
<os>
<type arch='i686'>hvm</type>
<boot dev='network'/>
diff --git a/tests/xmlconfig-xml/boot-cpuset.xml b/tests/xmlconfig-xml/boot-cpuset.xml
index 3dc173f..64beafe 100644
--- a/tests/xmlconfig-xml/boot-cpuset.xml
+++ b/tests/xmlconfig-xml/boot-cpuset.xml
@@ -3,7 +3,7 @@
<uuid>12345678-1234-1234-1234-123456789012</uuid>
<memory>409600</memory>
<currentMemory>204800</currentMemory>
- <vcpu cpuset='0,2,4,6,8,10,12,14' current='5'>7</vcpu>
+ <vcpu cpuset='0,1,2,3,4,5,6,7' current='5'>7</vcpu>
<os>
<type arch='i686'>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
--
1.8.1.5
More information about the virt-tools-list
mailing list