Description of problem: VM_MEMORY in condor_config is set to "128" as default. This value is in bytes not megabytes. Jobs with anything under 128000 will results in 128M because of libvirtd. Also when creating jobs you must specify the amount of memory in bytes. Version-Release number of selected component (if applicable): condor-7.2.2-0.9.el5 How reproducible: Every time. Steps to Reproduce: 1. Set VM_MEMORY to 8192 in condor_config 2. Create a VM job with VM_MEMORY at 4096 3. Start VM job and notice the virtual machine was started with 128M 4. Repeat steps 1 & 2 by adding 000 to the end of the numbers. 5. Watch them start up with the desired memory. Actual results: Machines are created with the wrong amount of memory because the documentation says to create memory with size in Megabytes. Expected results: Jobs and memory utilization is recorded in bytes not megabytes. Additional info:
Even StartLog reads everything as MB instead of B. That information log should be changed as well. 4/13 16:29:25 The maximum available memory for vm universe is set to 64000000 MB
This needs to be verified in MRG and UW documentation. It is possible this is the result of differences between VMware and libvirt support - if so it must be resolved upstream, likely by converting for libvirt. Also, it seems for libvirt the memory parameter is in kilobytes, not bytes.
When you are ready for documentation changes, please change the component to Grid_User_Guide and assign the bug to me. Thanks, LKB
This has been resolved upstream. Should be available in 7.3.1-0.4. The issue was VMware and xm use MiB units and libvirt uses KiB, but conversion to KiB was not done.
*** Bug 498346 has been marked as a duplicate of this bug. ***
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Corrected problem with VM_MEMORY parameter conversion to KiB when invoking libvirt (495588)
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,3 @@ +Grid bug fix + Corrected problem with VM_MEMORY parameter conversion to KiB when invoking libvirt (495588)
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,3 +1,8 @@ Grid bug fix -Corrected problem with VM_MEMORY parameter conversion to KiB when invoking libvirt (495588)+C: The VM_MEMORY setting in condor_config is set to 128 bytes by default, not 128000 bytes (128MB) +C: Virtual machines are created with the wrong amount of memory +F: The setting is now converted to the correct measurements +R: Memory is now set as expected + +The default setting for VM_MEMORY in condor_config was creating virtual machines with the wrong amount of memory. The setting now converts the amount correctly, and virtual machine memory is now set correctly.
The amount of memory is converted to the right unit. Tested on RHEL 5.4 on i386 Xen, x86_64 Xen and x86_64 KVM. condor-7.4.1-0.4 condor-vm-gahp-7.4.1-0.4 Changing the status to VERIFIED.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1633.html