1. 22 6月, 2009 2 次提交
  2. 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
  3. 14 6月, 2009 2 次提交
  4. 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
  5. 10 6月, 2009 2 次提交
  6. 09 6月, 2009 4 次提交
  7. 30 5月, 2009 1 次提交
  8. 28 5月, 2009 1 次提交
  9. 27 5月, 2009 3 次提交
    • A
      User Networking: Enable removal of redirections · c1261d8d
      Alexander Graf 提交于
      Using the new host_net_redir command you can easily create redirections
      on the fly while your VM is running.
      
      While that's great, it's missing the removal of redirections, in case you
      want to have a port closed again at a later point in time.
      
      This patch adds support for removal of redirections.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      c1261d8d
    • C
      fully split aio_pool from BlockDriver · c16b5a2c
      Christoph Hellwig 提交于
      Now that we have a separate aio pool structure we can remove those
      aio pool details from BlockDriver.
      
      Every driver supporting AIO now needs to declare a static AIOPool
      with the aiocb size and the cancellation method.  This cleans up the
      current code considerably and will make it cleaner and more obvious
      to support two different aio implementations behind a single
      BlockDriver.
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      c16b5a2c
    • K
      Fix output of uninitialized strings · 8cf07dcb
      Kevin Wolf 提交于
      Commit ffad4116 removed the "scratch buffer"
      from check_params, but didn't care for the error messages which actually
      included this string to tell the user which option was wrong. Now this string
      is uninitialized, so this patch removes it from the message.
      
      This means that the user is only told the whole parameter string and has to
      pick the wrong option by himself as the callers of check_params can't know this
      value any more. An alternative approach would be to revert that commit and do
      whatever is needed to fix the original problem without changing check_params.
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      8cf07dcb
  10. 22 5月, 2009 7 次提交
  11. 21 5月, 2009 2 次提交
    • A
      Convert machine registration to use module init functions · f80f9ec9
      Anthony Liguori 提交于
      This cleans up quite a lot of #ifdefs, extern variables, and other ugliness.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      f80f9ec9
    • A
      Eliminate --disable-gfx-check and make VNC default when SDL not available · f92f8afe
      Anthony Liguori 提交于
       --disable-gfx-check predates VNC server support.  It made sense back then
      because the only thing you could do without SDL was use -nographic mode or
      similar tricks.  Since this is a very advanced mode of operation, gfx-check
      provided a good safety net for casual users.
      
      A casual user is very likely to use VNC to interact with a guest.  In fact, it's
      often frustrating to install QEMU on a server and have to specify
      disable-gfx-check when you only want to use VNC.
      
      This patch eliminates disable-gfx-check and makes SDL behave like every other
      optional dependency.  If SDL is not available, instead of failing ungracefully
      if no special options are specified, we default to -vnc localhost:0,to=99.
      When we do default to VNC, we also print a message to tell the user that we've
      done this include which port we're currently listening on.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      f92f8afe
  12. 20 5月, 2009 2 次提交
    • J
      initialize struct sigevent before timer_create · 9ed415b2
      Jean-Christophe Dubois 提交于
      When qemu is run under valgrind, valgrind shows the following output
      on exit:
      
      ==3648== 1 errors in context 2 of 2:
      ==3648== Syscall param timer_create(evp) points to uninitialised byte(s)
      ==3648==    at 0x54E936A: timer_create (in /lib/librt-2.9.so)
      ==3648==    by 0x405DCF: dynticks_start_timer (vl.c:1549)
      ==3648==    by 0x40A966: main (vl.c:1726)
      ==3648==  Address 0x7fefffb34 is on thread 1's stack
      ==3648==  Uninitialised value was created by a stack allocation
      ==3648==    at 0x405D60: dynticks_start_timer (vl.c:1534)
      
      This patch is a simple fix to remove this potential problem.
      Signed-off-by: NJean-Christophe DUBOIS <jcd@tribudubois.net>
      9ed415b2
    • J
      Fix NULL alarm_timer pointer at exit · e332340a
      Jean-Christophe Dubois 提交于
      This fixes a SIGSEGV error on qemu exit.
      
      Here is the valgrind output related to this error
      
      ==3648== Process terminating with default action of signal 11 (SIGSEGV)
      ==3648==  Access not within mapped region at address 0x8
      ==3648==    at 0x40636B: host_alarm_handler (vl.c:1345)
      ==3648==    by 0x52D807F: (within /lib/libpthread-2.9.so)
      ==3648==    by 0x5C0A12E: tcsetattr (in /lib/libc-2.9.so)
      ==3648==    by 0x4DD601: term_exit (qemu-char.c:700)
      ==3648==    by 0x5B636EC: exit (in /lib/libc-2.9.so)
      ==3648==    by 0x5B4B5AC: (below main) (in /lib/libc-2.9.so)
      
      This simple fix check for a valid pointer as host_alarm_handler is
      also called after alarm_timer is released in the exit path.
      Signed-off-by: NJean-Christophe DUBOIS <jcd@tribudubois.net>
      e332340a
  13. 15 5月, 2009 1 次提交
  14. 14 5月, 2009 2 次提交
  15. 10 5月, 2009 1 次提交
  16. 08 5月, 2009 1 次提交
    • J
      Drop CONFIG_GDBSTUB · 322f9d01
      Jan Kiszka 提交于
      This is no user-flippable switch, and no arch makes use of disabling
      gdbstub support. So it's pointless to keep the related #ifdefs and
      configure hunks around - and risking breakages like 711c410fdd again.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      322f9d01
  17. 01 5月, 2009 4 次提交
  18. 30 4月, 2009 1 次提交
  19. 25 4月, 2009 1 次提交