[Libvirt-cim] [PATCH] [TEST] In addition to setting the current memory, set the max memory as well

[Kaitlin Rupert]

# HG changeset patch
# User Kaitlin Rupert <karupert at us.ibm.com>
# Date 1259951709 28800
# Node ID ab6ca2e33255553d0bddd8e5ab2e6524113dcb3b
# Parent  320b40f37a368cbc801b7e2761e84cf65136e118
[TEST] In addition to setting the current memory, set the max memory as well

Otherwise, you can end up defining a guest with a current memory value that
is much higher than the max memory value.  That type of guest definition
isn't valid with newer versions of Xen.

diff -r a2d8acd05db2 -r 943b21b79a04 suites/libvirt-cim/cimtest/VirtualSystemMan
agementService/11_define_memrasdunits.py

diff -r 320b40f37a36 -r ab6ca2e33255 suites/libvirt-cim/cimtest/VirtualSystemManagementService/11_define_memrasdunits.py
--- a/suites/libvirt-cim/cimtest/VirtualSystemManagementService/11_define_memrasdunits.py	Fri Dec 04 10:03:39 2009 -0800
+++ b/suites/libvirt-cim/cimtest/VirtualSystemManagementService/11_define_memrasdunits.py	Fri Dec 04 10:35:09 2009 -0800
@@ -52,6 +52,7 @@
     for rasd in rasds:
         if rasd.classname == mrasd_cn:
             rasd['VirtualQuantity'] = Uint64(value)
+            rasd['Limit'] = Uint64(value)
             rasd['AllocationUnits'] = units 
             rasd_list[mrasd_cn] = inst_to_mof(rasd)
         else: