1. 15 Mar, 2012 2 commits
    • 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
      commit.
      
      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>
      e1c37d0e
    • Luiz Capitulino's avatar
      Purge migration of (almost) everything to do with monitors · 539de124
      Luiz Capitulino authored
      The Monitor object is passed back and forth within the migration/savevm
      code so that it can print errors and progress to the user.
      
      However, that approach assumes a HMP monitor, being completely invalid
      in QMP.
      
      This commit drops almost every single usage of the Monitor object, all
      monitor_printf() calls have been converted into DPRINTF() ones.
      
      There are a few remaining Monitor objects, those are going to be dropped
      by the next commit.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      539de124
  2. 24 Feb, 2012 3 commits
  3. 01 Feb, 2012 1 commit
  4. 19 Jan, 2012 1 commit
  5. 03 Jan, 2012 1 commit
    • Alexander Graf's avatar
      Add generic drive hotplugging · dd97aa8a
      Alexander Graf authored
      The monitor command for hotplugging is in i386 specific code. This is just
      plain wrong, as S390 just learned how to do hotplugging too and needs to
      get drives for that.
      
      So let's add a generic copy to generic code that handles drive_add in a
      way that doesn't have pci dependencies. All pci specific code can then
      be handled in a pci specific function.
      Signed-off-by: default avatarAlexander Graf <agraf@suse.de>
      
      ---
      
      v1 -> v2:
      
        - align generic drive_add to pci specific one
        - rework to split between generic and pci code
      
      v2 -> v3:
      
        - remove comment
      dd97aa8a
  6. 06 Dec, 2011 1 commit
  7. 21 Oct, 2011 1 commit
  8. 19 Oct, 2011 1 commit
    • Luiz Capitulino's avatar
      runstate: Allow user to migrate twice · 8a9236f1
      Luiz Capitulino authored
      It should be a matter of allowing the transition POSTMIGRATE ->
      FINISH_MIGRATE, but it turns out that the VM won't do the
      transition the second time because it's already stopped.
      
      So this commit also adds vm_stop_force_state() which performs
      the transition even if the VM is already stopped.
      
      While there also allow other states to migrate.
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      8a9236f1
  9. 04 Oct, 2011 3 commits
    • Luiz Capitulino's avatar
      qapi: Convert query-status · 1fa9a5e4
      Luiz Capitulino authored
      Please, note that the RunState type as defined in sysemu.h and its
      runstate_as_string() function are being dropped in favor of the
      RunState type generated by the QAPI.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      1fa9a5e4
    • Luiz Capitulino's avatar
      RunState: Rename enum values as generated by the QAPI · 0461d5a6
      Luiz Capitulino authored
      Next commit will convert the query-status command to use the
      RunState type as generated by the QAPI.
      
      In order to "transparently" replace the current enum by the QAPI
      one, we have to make some changes to some enum values.
      
      As the changes are simple renames, I'll do them in one shot. The
      changes are:
      
       - Rename the prefix from RSTATE_ to RUN_STATE_
       - RUN_STATE_SAVEVM to RUN_STATE_SAVE_VM
       - RUN_STATE_IN_MIGRATE to RUN_STATE_INMIGRATE
       - RUN_STATE_PANICKED to RUN_STATE_INTERNAL_ERROR
       - RUN_STATE_POST_MIGRATE to RUN_STATE_POSTMIGRATE
       - RUN_STATE_PRE_LAUNCH to RUN_STATE_PRELAUNCH
       - RUN_STATE_PRE_MIGRATE to RUN_STATE_PREMIGRATE
       - RUN_STATE_RESTORE to RUN_STATE_RESTORE_VM
       - RUN_STATE_PRE_MIGRATE to RUN_STATE_FINISH_MIGRATE
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      0461d5a6
    • Luiz Capitulino's avatar
      RunState: Drop the RSTATE_NO_STATE value · c4d11e38
      Luiz Capitulino authored
      The QAPI framework won't generate it, so we need to get rid of it.
      
      In order to do that, this commit makes RSTATE_PRE_LAUNCH the initial
      state and change qemu_vmstop_requested() to use RSTATE_MAX.
      Signed-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
      c4d11e38
  10. 15 Sep, 2011 6 commits
  11. 22 Aug, 2011 1 commit
  12. 29 Jul, 2011 1 commit
    • wayne's avatar
      showing a splash picture when start · 3d3b8303
      wayne authored
          Added options to let qemu transfer two configuration files to bios:
      "bootsplash.bmp" and "etc/boot-menu-wait", which could be specified by command
          -boot splash=P,splash-time=T
      P is jpg/bmp file name or an absolute path, T have a max value of 0xffff, unit
      is ms. With these two options, if user invoke qemu with menu=on option, then
      a splash picture would be showed in a given time. For example:
          qemu -boot menu=on,splash=/root/boot.bmp,splash-time=5000
      would make boot.bmp shown as a brand with 5 seconds in the booting up process.
      This feature need the new seabios's support, which could be got from git.
      Signed-off-by: default avatarWayne Xia <xiawenc@linux.vnet.ibm.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      3d3b8303
  13. 16 Jun, 2011 1 commit
  14. 08 May, 2011 1 commit
  15. 15 Apr, 2011 4 commits
  16. 26 Mar, 2011 1 commit
  17. 22 Mar, 2011 1 commit
  18. 14 Feb, 2011 2 commits
  19. 25 Jan, 2011 1 commit
  20. 17 Jan, 2011 1 commit
    • Alex Williamson's avatar
      savevm: Fix no_migrate · dc912121
      Alex Williamson authored
      The no_migrate save state flag is currently only checked in the
      last phase of migration.  This means that we potentially waste
      a lot of time and bandwidth with the live state handlers before
      we ever check the no_migrate flags.  The error message printed
      when we catch a non-migratable device doesn't get printed for
      a detached migration.  And, no_migrate does nothing to prevent
      an incoming migration to a target that includes a non-migratable
      device.  This attempts to fix all of these.
      
      One notable difference in behavior is that an outgoing migration
      now checks for non-migratable devices before ever connecting to
      the target system.  This means the target will remain listening
      rather than exit from failure.
      Signed-off-by: default avatarAlex Williamson <alex.williamson@redhat.com>
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
      dc912121
  21. 24 Dec, 2010 1 commit
  22. 11 Dec, 2010 4 commits
  23. 09 Dec, 2010 1 commit
    • Gerd Hoffmann's avatar
      spice: add qxl device · a19cbfb3
      Gerd Hoffmann authored
      qxl is a paravirtual graphics card.  The qxl device is the bridge
      between the guest and the spice server (aka libspice-server).  The
      spice server will send the rendering commands to the spice client, which
      will actually render them.
      
      The spice server is also able to render locally, which is done in case
      the guest wants read something from video memory.  Local rendering is
      also used to support display over vnc and sdl.
      
      qxl is activated using "-vga qxl".  qxl supports multihead, additional
      cards can be added via '-device qxl".
      
      [ v2: add copyright to files                     ]
      [ v2: use qemu-common.h for standard includes    ]
      [ v2: create separate qxl-vga device for primary ]
      Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
      a19cbfb3