1. 20 7月, 2012 8 次提交
  2. 29 6月, 2012 1 次提交
  3. 15 3月, 2012 1 次提交
  4. 14 1月, 2012 1 次提交
  5. 04 1月, 2012 1 次提交
    • A
      vmstate, memory: decouple vmstate from memory API · c5705a77
      Avi Kivity 提交于
      Currently creating a memory region automatically registers it for
      live migration.  This differs from other state (which is enumerated
      in a VMStateDescription structure) and ties the live migration code
      into the memory core.
      
      Decouple the two by introducing a separate API, vmstate_register_ram(),
      for registering a RAM block for migration.  Currently the same
      implementation is reused, but later it can be moved into a separate list,
      and registrations can be moved to VMStateDescription blocks.
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      c5705a77
  6. 13 12月, 2011 1 次提交
  7. 20 10月, 2011 2 次提交
  8. 10 8月, 2011 1 次提交
  9. 20 7月, 2011 1 次提交
  10. 19 6月, 2011 1 次提交
  11. 23 4月, 2011 1 次提交
  12. 11 3月, 2011 9 次提交
  13. 03 3月, 2011 2 次提交
  14. 25 1月, 2011 1 次提交
    • G
      usb core: add migration support · c1ecb40a
      Gerd Hoffmann 提交于
      Yes, seriously.  There is no migration support at all for usb devices.
      They loose state, especially the device address, and stop responding
      because of that.  Oops.
      
      Luckily there is so much broken usb hardware out there that the guest
      usually just kicks the device hard (via port reset and
      reinitialization), then continues without a hitch.  So we got away with
      that in a surprising high number of cases.
      
      The arrival of remote wakeup (which enables autosuspend support) changes
      that picture though.  The usb devices also forget that it they are
      supposed to wakeup, so they don't do that.  The host also doesn't notice
      the device stopped working in case it suspended the device and thus
      expects it waking up instead of polling it.  Result is that your mouse
      is dead.
      
      Lets start fixing that.  Add a vmstate struct for USBDevice.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      c1ecb40a
  15. 24 1月, 2011 1 次提交
  16. 09 12月, 2010 1 次提交
    • G
      spice: add qxl device · a19cbfb3
      Gerd Hoffmann 提交于
      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: NGerd Hoffmann <kraxel@redhat.com>
      a19cbfb3
  17. 03 12月, 2010 1 次提交
  18. 01 11月, 2010 1 次提交
  19. 11 8月, 2010 1 次提交
  20. 27 7月, 2010 1 次提交
    • J
      vmstate: add subsections code · 811814bd
      Juan Quintela 提交于
      This commit adds subsections for each device section.
      Subsections is the way to handle information that don't need to be sent
      to de destination of a migration because its values are not needed.  It is
      the way to handle optional information.  Notice that only the source can
      decide if the information is optional or not.  The destination needs to
      understand all subsections that it receives to have a sucessful load.
      Signed-off-by: NJuan Quintela <quintela@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      811814bd
  21. 06 7月, 2010 1 次提交
  22. 14 6月, 2010 1 次提交
  23. 13 6月, 2010 1 次提交