1. 22 Aug, 2013 1 commit
  2. 11 Mar, 2013 3 commits
  3. 20 Dec, 2012 3 commits
  4. 19 Dec, 2012 5 commits
  5. 02 Nov, 2012 4 commits
  6. 23 Oct, 2012 2 commits
    • Paolo Bonzini's avatar
      migration (incoming): add error propagation to fd and exec protocols · 43eaae28
      Paolo Bonzini authored
      And remove the superfluous integer return value.
      Reviewed-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
    • Paolo Bonzini's avatar
      migration (outgoing): add error propagation for all protocols · f37afb5a
      Paolo Bonzini authored
      Error propagation is already there for socket backends.  Add it to other
      protocols, simplifying code that tests for errors that will never happen.
      With all protocols understanding Error, the code can be simplified
      further by removing the return value.
      Unfortunately, the quality of error messages varies depending
      on where the error is detected, because no Error is passed to the
      NonBlockingConnectHandler.  Thus, the exact error message still cannot
      be sent to the user if the OS reports it asynchronously via SO_ERROR.
      If NonBlockingConnectHandler received an Error**, we could for
      example report the error class and/or message via a new field of the
      query-migration command even if it is reported asynchronously.
          (qemu) migrate fd:ffff
          migrate: An undefined error has occurred
          (qemu) info migrate
          (qemu) migrate fd:ffff
          migrate: File descriptor named 'ffff' has not been found
          (qemu) info migrate
          capabilities: xbzrle: off
          Migration status: failed
          total time: 0 milliseconds
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
  7. 26 Sep, 2012 1 commit
  8. 15 Mar, 2012 1 commit
    • 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
      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>
  9. 13 Jan, 2012 1 commit
  10. 01 Nov, 2011 1 commit
    • Gerd Hoffmann's avatar
      migration: flush migration data to disk. · aab22936
      Gerd Hoffmann authored
      This patch increases robustness when migrating to a file with
      two little changes:
       (1) Before closing the migration file handle checks if it happens to be
           a regular file and if so it issues a fsync.  This way the data is
           flushed to disk before qemu sends the migration completed event.
       (2) It adds error checking.  In case either fsync or close syscall
           fails pass up the error (and fail migration).
      [ v2: return -errno instead of -1 ]
      Cc: Juan Quintela <quintela@redhat.com>
      Cc: Jiri Denemark <jdenemar@redhat.com>
      Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
  11. 20 Oct, 2011 5 commits
  12. 20 Aug, 2011 1 commit
  13. 15 Apr, 2011 1 commit
  14. 22 Jun, 2010 1 commit
  15. 19 Mar, 2010 1 commit
  16. 17 Mar, 2010 1 commit
  17. 06 Feb, 2010 1 commit
  18. 03 Dec, 2009 1 commit
  19. 17 Nov, 2009 1 commit
    • lirans@il.ibm.com's avatar
      Block live migration · c163b5ca
      lirans@il.ibm.com authored
      This patch introduces block migration called during live migration. Block
      are being copied to the destination in an async way. First the code will
      transfer the whole disk and then transfer all dirty blocks accumulted during
      the migration.
      Still need to improve transition from the iterative phase of migration to the
      end phase. For now transition will take place when all blocks transfered once,
      all the dirty blocks will be transfered during the end phase (guest is
      Changes from v4:
      - Global variabels moved to a global state structure allocated dynamically.
      - Minor coding style issues.
      - Poll block.c for tracking of dirty blocks instead of manage it here.
      Signed-off-by: default avatarLiran Schour <lirans@il.ibm.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
  20. 27 Aug, 2009 1 commit
  21. 24 Aug, 2009 2 commits
  22. 30 Jul, 2009 1 commit
    • Paolo Bonzini's avatar
      fix migration to obey -S · d399f677
      Paolo Bonzini authored
      Since migration returns right away, starting the VM right
      after calling qemu_start_incoming_migration is wrong even
      if -S is not passed.  We have to do this after migration
      has completed.
      Cc: Glauber Costa  <glommer@redhat.com>
      Cc: Anthony Liguori  <aliguori@us.ibm.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
  23. 16 Jul, 2009 1 commit
    • Paolo Bonzini's avatar
      honor -S on incoming migration · 89befdd1
      Paolo Bonzini authored
      -S is not honored by qemu on incoming migration.  If a domain is migrated
      while paused, thus, it will start running on the remote machine; this
      is wrong.
      Given the trivial patch to fix this, it looks more like a thinko
      than anything else, probably dating back to the qemu-kvm merge.
      The interesting part is that the -S mechanism was in fact *used* when
      migrating (setting autostart = 0) and the incoming migration code was
      starting the VM at the end of the migration.
      Since I was removing the vm_start from there, I also corrected a related
      imprecision.  The code was doing a vm_stop "just in case", but we can
      be sure that the VM is not running---the vm_start call in vl.c has not
      been reached yet.  So the vm_stop is removed together with the vm_start.
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>