[gnome-boxes] Use NodeInfo::memory as max memory in diagnostics log



commit 26ce4c258b41b0ecf66025f24fcf10aa48ce599e
Author: Christophe Fergeau <cfergeau redhat com>
Date:   Fri Feb 22 11:09:25 2013 +0100

    Use NodeInfo::memory as max memory in diagnostics log
    
    This is what add_ram_property() uses as the maximum for the memory
    slider, so it's better to log that value rather than the unused
    info.maxMem
    
    https://bugzilla.gnome.org/show_bug.cgi?id=694430

 src/libvirt-machine-properties.vala |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/src/libvirt-machine-properties.vala b/src/libvirt-machine-properties.vala
index 740849c..1d18204 100644
--- a/src/libvirt-machine-properties.vala
+++ b/src/libvirt-machine-properties.vala
@@ -65,7 +65,7 @@ private class Boxes.LibvirtMachineProperties: GLib.Object, Boxes.IPropertiesProv
             var info = machine.domain.get_info ();
             builder.append_printf ("Cpu time: %"+uint64.FORMAT_MODIFIER+"d\n", info.cpuTime);
             builder.append_printf ("Memory: %"+uint64.FORMAT_MODIFIER+"d KiB\n", info.memory);
-            builder.append_printf ("Max memory: %"+uint64.FORMAT_MODIFIER+"d KiB\n", info.maxMem);
+            builder.append_printf ("Max memory: %"+uint64.FORMAT_MODIFIER+"d KiB\n", 
machine.connection.get_node_info ().memory);
             builder.append_printf ("CPUs: %d\n", info.nrVirtCpu);
             builder.append_printf ("State: %s\n", info.state.to_string ());
         } catch (GLib.Error e) {


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]