1. 16 Jan, 2013 1 commit
  2. 14 Jan, 2013 11 commits
  3. 10 Jan, 2013 1 commit
    • Dimitris Aragiorgis's avatar
      Add machine version in kvm runtime file · e6ba3320
      Dimitris Aragiorgis authored
      
      
      kvm -M ? returns the supported machines (e.g. pc-1.1).
      Add _GetDefaultMachineVersion() function to get the default value.
      
      Upon kvm runtime file creation (this is in _GenerateKVMRuntime() invoked
      only in StartInstance()) append this info in kvm_cmd. During
      live migration the -incoming kvm process is started based on this file.
      
      In case of different KVM versions between source and target nodes
      there is a possibility (e.g. due to a kvm bug) for migration to fail silently.
      
      This patch forces the target node to emulate the same machine version
      used by running process. If KVM on target node does not support it
      the -incoming kvm process will crash and migration will be aborted.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      e6ba3320
  4. 18 Dec, 2012 1 commit
  5. 17 Dec, 2012 2 commits
  6. 20 Nov, 2012 4 commits
  7. 12 Nov, 2012 1 commit
    • Iustin Pop's avatar
      Fix type error in kvm/GetMigrationStatus · 62457f51
      Iustin Pop authored
      Commit 6a1434d7
      
       (“Make migration RPC non-blocking”) changed from
      raising HypervisorErrors to returning MigrationStatus
      objects. However, these objects don't have an "info" attribute, so
      they can't pass a reason back (which is in itself a bug); but the KVM
      hypervisor code attempts to do so, and fails at runtime with:
      
        Failed to get migration status: 'MigrationStatus' object has no attribute 'info'
      
      instead of the intended:
      
        Migration failed, aborting: too many broken 'info migrate' answers
      
      For now (on stable-2.6), let's just remove the "info" reason, and
      later we can add it back properly once we have a way to correctly
      represent migration status failures in the LU.
      
      This fixes issue 297.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      62457f51
  8. 28 Sep, 2012 1 commit
  9. 21 Sep, 2012 1 commit
  10. 18 Sep, 2012 2 commits
  11. 23 Aug, 2012 1 commit
    • Iustin Pop's avatar
      Bump pep8 version to 1.2 · 5ae4945a
      Iustin Pop authored
      
      
      Debian Wheezy will ship with this version, and it has many improved checks compared to 0.6, so let's:
      
      - bump version in the docs
      - silence some new checks that are wrong due to our indent=2 instead of 4
      - fix lots of errors in the code where the indentation was wrong by 1
        or 2 spaces
      - fix a few cases of == True, False, None and replace with 'is'
      - re-indent some cases where the code is OK, but pep8 complains
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      5ae4945a
  12. 27 Jul, 2012 1 commit
  13. 24 Jul, 2012 2 commits
    • Iustin Pop's avatar
      Fix boot=on flag for CDROMs · 24be50e0
      Iustin Pop authored
      This generalises commit 4304964a
      
       to cdroms too, since they have
      somewhat the same logic. We just abstract the needs_boot_flag into a
      separate variable, and then reuse it in the cdrom section.
      
      Note that the logic of what 'if=' type to pass to KVM was very
      convoluted, and (I think) incorrect; I went and cleaned it to be more
      consistent.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      24be50e0
    • Iustin Pop's avatar
      KVM: only pass boot flag once · 2b846304
      Iustin Pop authored
      This addresses issue 230: passing two methods of booting to KVM can,
      depending on the KVM version, confuse it.
      
      Note that commit 4304964a
      
       introduced a partial fix for this (but only
      for disks, and keyed on KVM versions). However, it didn't fix cdrom
      booting, which still fails with the same error, so let's fix it more
      generically; we still leave the per-disk check since that is about
      -boot c versus -drive …,boot=on rather than two boot methods.
      
      Patch is based on the one submitted by Vladimir Mencl, many thanks!
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      2b846304
  14. 20 Jul, 2012 1 commit
  15. 12 Jun, 2012 2 commits
  16. 11 Jun, 2012 2 commits
  17. 21 Mar, 2012 1 commit
  18. 23 Jan, 2012 1 commit
  19. 20 Jan, 2012 2 commits
  20. 17 Jan, 2012 1 commit
  21. 06 Jan, 2012 1 commit