1. 20 Jul, 2012 5 commits
  2. 29 Jun, 2012 3 commits
  3. 18 Jun, 2012 1 commit
  4. 15 Jun, 2012 1 commit
  5. 15 Apr, 2012 1 commit
  6. 19 Mar, 2012 1 commit
    • Stefano Stabellini's avatar
      Introduce "xen-save-devices-state" · a7ae8355
      Stefano Stabellini authored
      
      
      - add an "is_ram" flag to SaveStateEntry;
      
      - register_savevm_live sets is_ram for live_savevm devices;
      
      - introduce a "xen-save-devices-state" QAPI command that can be used to save
      the state of all devices, but not the RAM or the block devices of the
      VM.
      
      Changes in v8:
      
      - rename save-devices-state to xen-save-devices-state.
      
      Changes in v7:
      
      - rename save_devices to save-devices-state.
      
      Changes in v6:
      
      - remove the is_ram parameter from register_savevm_live and sets is_ram
      if the device is a live_savevm device;
      
      - introduce save_devices as a QAPI command, write a better description
      for it;
      
      - fix CODING_STYLE;
      
      - introduce a new doc to explain the save format used by save_devices.
      Signed-off-by: default avatarStefano Stabellini <stefano.stabellini@eu.citrix.com>
      Reviewed-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      Acked-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      a7ae8355
  7. 17 Mar, 2012 1 commit
  8. 15 Mar, 2012 2 commits
    • Luiz Capitulino's avatar
      qapi: Convert migrate · e1c37d0e
      Luiz Capitulino authored
      
      
      The migrate command is one of those commands where HMP and QMP completely
      mix up together. This made the conversion to the QAPI (which separates the
      command into QMP and HMP parts) a bit difficult.
      
      The first important change to be noticed is that this commit completes the
      removal of the Monitor object from migration code, started by the previous
      commit.
      
      Another important and tricky change is about supporting the non-detached
      mode. That is, if the user doesn't pass '-d' the migrate command will lock
      the monitor and will only release it when migration is finished.
      
      To support this in the new HMP command (hmp_migrate()), it is necessary
      to create a timer which runs every second and checks if the migration is
      still active. If it is, the timer callback will re-schedule itself to run
      one second in the future. If the migration has already finished, the
      monitor lock is released and the user can use it normally.
      
      All these changes should be transparent to the user.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      e1c37d0e
    • Luiz Capitulino's avatar
      Purge migration of (almost) everything to do with monitors · 539de124
      Luiz Capitulino authored
      
      
      The Monitor object is passed back and forth within the migration/savevm
      code so that it can print errors and progress to the user.
      
      However, that approach assumes a HMP monitor, being completely invalid
      in QMP.
      
      This commit drops almost every single usage of the Monitor object, all
      monitor_printf() calls have been converted into DPRINTF() ones.
      
      There are a few remaining Monitor objects, those are going to be dropped
      by the next commit.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      539de124
  9. 08 Jan, 2012 1 commit
  10. 04 Jan, 2012 1 commit
    • Avi Kivity's avatar
      vmstate, memory: decouple vmstate from memory API · c5705a77
      Avi Kivity authored
      
      
      Currently creating a memory region automatically registers it for
      live migration.  This differs from other state (which is enumerated
      in a VMStateDescription structure) and ties the live migration code
      into the memory core.
      
      Decouple the two by introducing a separate API, vmstate_register_ram(),
      for registering a RAM block for migration.  Currently the same
      implementation is reused, but later it can be moved into a separate list,
      and registrations can be moved to VMStateDescription blocks.
      Signed-off-by: default avatarAvi Kivity <avi@redhat.com>
      c5705a77
  11. 15 Dec, 2011 1 commit
  12. 12 Dec, 2011 4 commits
  13. 05 Dec, 2011 1 commit
  14. 02 Dec, 2011 1 commit
  15. 21 Nov, 2011 1 commit
  16. 01 Nov, 2011 1 commit
  17. 21 Oct, 2011 1 commit
  18. 20 Oct, 2011 11 commits
  19. 19 Oct, 2011 1 commit
  20. 04 Oct, 2011 1 commit
    • Luiz Capitulino's avatar
      RunState: Rename enum values as generated by the QAPI · 0461d5a6
      Luiz Capitulino authored
      
      
      Next commit will convert the query-status command to use the
      RunState type as generated by the QAPI.
      
      In order to "transparently" replace the current enum by the QAPI
      one, we have to make some changes to some enum values.
      
      As the changes are simple renames, I'll do them in one shot. The
      changes are:
      
       - Rename the prefix from RSTATE_ to RUN_STATE_
       - RUN_STATE_SAVEVM to RUN_STATE_SAVE_VM
       - RUN_STATE_IN_MIGRATE to RUN_STATE_INMIGRATE
       - RUN_STATE_PANICKED to RUN_STATE_INTERNAL_ERROR
       - RUN_STATE_POST_MIGRATE to RUN_STATE_POSTMIGRATE
       - RUN_STATE_PRE_LAUNCH to RUN_STATE_PRELAUNCH
       - RUN_STATE_PRE_MIGRATE to RUN_STATE_PREMIGRATE
       - RUN_STATE_RESTORE to RUN_STATE_RESTORE_VM
       - RUN_STATE_PRE_MIGRATE to RUN_STATE_FINISH_MIGRATE
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      0461d5a6