1. 27 7月, 2009 1 次提交
    • M
      Add machine type aliases · 3f6599e6
      Mark McLoughlin 提交于
      Add an 'alias' field to QEMUMachine and display it in the output of
      'qemu -M ?' with an '(aliased to foo)' suffix.
      
      Aliases can change targets in newer versions of qemu, so management tools
      may choose canonicalize machine types to ensure that if a user chooses an
      alias, that the actual machine type used will remain compatible in
      future.
      
      This is intended to mimic a symlink to a machine description file.
      Signed-off-by: NMark McLoughlin <markmc@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      3f6599e6
  2. 17 7月, 2009 3 次提交
    • B
      Fix OpenBSD build · 96555a96
      Blue Swirl 提交于
      The header sys-queue.h must be #included early, otherwise at some point OS
      queue macros will be used. On OpenBSD, those don't define TAILQ_FOREACH_SAFE.
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      96555a96
    • G
      qdev/compat: compat property infrastructure. · b6b61144
      Gerd Hoffmann 提交于
      This add support for switching devices into a compatibility mode
      using device properties.  Machine types can have a list of properties
      for specific devices attached to allow the easy creation of machine
      types compatible to older qemu versions.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      b6b61144
    • P
      honor -S on incoming migration · 89befdd1
      Paolo Bonzini 提交于
      -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: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      89befdd1
  3. 16 7月, 2009 6 次提交
  4. 10 7月, 2009 4 次提交
  5. 30 6月, 2009 3 次提交
  6. 29 6月, 2009 4 次提交
  7. 24 6月, 2009 1 次提交
  8. 22 6月, 2009 4 次提交
  9. 17 6月, 2009 2 次提交
    • G
      add non-arbitrary migration stop condition · a0a3fd60
      Glauber Costa 提交于
      Currently, we're entering migration's stage 3 when
      a treshold of 10 pages remain to be transferred in the system.
      
      This has hurt some users. However, any proposed threshold is
      arbitrary by nature, and would only shift the annoyance.
      
      The proposal of this patch is to define a max_downtime variable,
      which represents the maximum downtime a migration user is willing
      to suffer. Then, based on the bandwidth of last iteration, we
      calculate how much data we can transfer in such a window of time.
      
      Whenever we reach that value (or lower), we know is safe to enter
      stage3.
      
      This has largely improved the situation for me.
      On localhost migrations, where one would expect things to go as
      quickly as me running away from the duty of writting software for
      windows, a kernel compile was enough to get the migration stuck.
      
      It takes 20 ~ 30 iterations now.
      Signed-off-by: NGlauber Costa <glommer@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      a0a3fd60
    • A
      Remove dead code · 3fe5c14e
      Amit Shah 提交于
      vl.c contains some dead code that initialises a 'label' string with the name
      of the char device being initialised. This is unused.
      Signed-off-by: NAmit Shah <amit.shah@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      3fe5c14e
  10. 14 6月, 2009 2 次提交
  11. 11 6月, 2009 1 次提交
    • L
      Fix "defined but not used" warning · b319820d
      Luiz Capitulino 提交于
      The function qemu_calculate_timeout() is only used when CONFIG_IOTHREAD
      is not defined. When CONFIG_IOTHREAD is defined, we have the following
      warning:
      
      vl.c:4389: warning: ‘qemu_calculate_timeout’ defined but not used
      
      This change fixes that by moving the #ifdef/#endif from main_loop()
      into qemu_calculate_timeout(). This encapsulates the logic and allow
      us to use qemu_calculate_timeout() when CONFIG_IOTHREAD is defined
      or not (suggested by Glauber Costa).
      Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      b319820d
  12. 10 6月, 2009 2 次提交
  13. 09 6月, 2009 4 次提交
  14. 30 5月, 2009 1 次提交
  15. 28 5月, 2009 1 次提交
  16. 27 5月, 2009 1 次提交