1. 22 Aug, 2013 1 commit
  2. 11 Mar, 2013 5 commits
  3. 20 Dec, 2012 2 commits
  4. 19 Dec, 2012 4 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>
      43eaae28
    • 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.
      
      Before:
      
          (qemu) migrate fd:ffff
          migrate: An undefined error has occurred
          (qemu) info migrate
          (qemu)
      
      After:
      
          (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>
      f37afb5a
  7. 13 Jan, 2012 1 commit
  8. 12 Dec, 2011 2 commits
  9. 20 Oct, 2011 5 commits
  10. 21 Aug, 2011 1 commit
  11. 15 Apr, 2011 1 commit
  12. 22 Jun, 2010 1 commit
  13. 04 Jun, 2010 1 commit
    • Blue Swirl's avatar
      migration-exec: fix OpenBSD build warning · 0ffbba35
      Blue Swirl authored
      Add include directives to get WIFEXITED() and WEXITSTATUS() macros defined.
      
      Fixes warnings:
        CC    migration-exec.o
      /src/qemu/migration-exec.c: In function `exec_close':
      /src/qemu/migration-exec.c:53: warning: implicit declaration of function `WIFEXITED'
      /src/qemu/migration-exec.c:54: warning: implicit declaration of function `WEXITSTATUS'
      Signed-off-by: default avatarBlue Swirl <blauwirbel@gmail.com>
      0ffbba35
  14. 03 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
      suspended).
      
      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>
      c163b5ca
  20. 24 Aug, 2009 2 commits
  21. 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>
      d399f677
  22. 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>
      89befdd1