qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH v4 1/6] vl.c: do not save the RAM state when Xen


From: Anthony Liguori
Subject: Re: [Qemu-devel] [PATCH v4 1/6] vl.c: do not save the RAM state when Xen is enabled
Date: Mon, 23 Jan 2012 09:58:51 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15

On 01/20/2012 11:21 AM, Stefano Stabellini wrote:
From: Anthony PERARD<address@hidden>

In the Xen case, the guest RAM is not handle by QEMU, and it is saved by
Xen tools.
So, we just avoid to register the RAM save state handler.

Signed-off-by: Anthony PERARD<address@hidden>
Signed-off-by: Stefano Stabellini<address@hidden>
---
  vl.c |    6 ++++--
  1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/vl.c b/vl.c
index ba55b35..6f0435b 100644
--- a/vl.c
+++ b/vl.c
@@ -3270,8 +3270,10 @@ int main(int argc, char **argv, char **envp)
      default_drive(default_sdcard, snapshot, machine->use_scsi,
                    IF_SD, 0, SD_OPTS);

-    register_savevm_live(NULL, "ram", 0, 4, NULL, ram_save_live, NULL,
-                         ram_load, NULL);
+    if (!xen_enabled()) {
+        register_savevm_live(NULL, "ram", 0, 4, NULL, ram_save_live, NULL,
+                             ram_load, NULL);
+    }


Why not introduce new Xen specific commands like I suggested on IRC?

This sort of change is extremely non-intuitive. We should do as much as we can to avoid magic #ifdefs like this.

Regards,

Anthony Liguori


      if (nb_numa_nodes>  0) {
          int i;




reply via email to

[Prev in Thread] Current Thread [Next in Thread]