Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 24 10月, 2012 1 次提交
    • P
      block: add block-job-complete · aeae883b
      由 Paolo Bonzini 提交于 
      While streaming can be dropped as soon as it progressed through the whole
image, mirroring needs to be completed manually for two reasons: 1) so that
management knows exactly when the VM switches to the target; 2) because
for other use cases such as replication, we may leave the operation running
for the whole life of the virtual machine.

Add a new block job command that manually completes background operations.
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      aeae883b
  3. 18 10月, 2012 3 次提交
  5. 29 9月, 2012 2 次提交
  7. 27 9月, 2012 2 次提交
    • L
      qmp: qmp_send_key(): accept key codes in hex · 9f328977
      由 Luiz Capitulino 提交于 
      Before the qapi conversion, the sendkey command could be used to
send key codes in hex directly to the guest. In HMP, this would
be like:

 (qemu) sendkey 0xdc

However, the qapi conversion broke this, as it only supports sending
QKeyCode values to the guest. That's a regression.

This commit fixes the problem by adding hex value support down
the QMP interface, qmp_send_key().

In more detail, this commit:

 1. Adds the KeyValue union. This can represent an hex value or
    a QKeyCode value

 2. *Changes* the QMP send-key command to take an KeyValue argument
    instead of a QKeyCode one

 3. Adapt hmp_send_key() to the QMP interface changes

Item 2 is an incompatible change, but as we're in development phase
(and this command has been merged a few weeks ago) this shouldn't be
a problem.

Finally, it's not possible to split this commit without breaking the
build.
Reported-by: NAvi Kivity <avi@redhat.com>
Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      9f328977
    • L
      hmp: dump-guest-memory: hardcode protocol argument to "file:" · 75363769
      由 Luiz Capitulino 提交于 
      Today, it's necessary to specify the protocol you want to use
when dumping the guest memory, for example:

 (qemu) dump-guest-memory file:/tmp/guest-memory

This has a few issues:

 1. It's cumbersome to type
 2. We loose file path autocompletion
 3. Being able to specify fd:X in HMP makes little sense for humans

Because of these reasons, hardcode the 'protocol' argument to
'file:' in HMP.
Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      75363769
  9. 06 9月, 2012 2 次提交
  11. 05 9月, 2012 1 次提交
  13. 22 8月, 2012 1 次提交
  15. 14 8月, 2012 3 次提交
  17. 08 8月, 2012 5 次提交
  19. 03 8月, 2012 1 次提交
  21. 14 7月, 2012 1 次提交
  23. 29 6月, 2012 1 次提交
    • J
      Add spent time for migration · d5f8a570
      由 Juan Quintela 提交于 
      We add time spent for migration to the output of "info migrate"
command.  'total_time' means time since the start fo migration if
migration is 'active', and total time of migration if migration is
completed.  As we are also interested in transferred ram when
migration completes, adding all ram statistics
Signed-off-by: NJuan Quintela <quintela@redhat.com>
      d5f8a570
  25. 15 6月, 2012 1 次提交
  27. 05 6月, 2012 3 次提交
  29. 10 5月, 2012 1 次提交
  31. 03 5月, 2012 1 次提交
  33. 27 4月, 2012 1 次提交
  35. 10 4月, 2012 1 次提交
  37. 15 3月, 2012 1 次提交
    • L
      qapi: Convert migrate · e1c37d0e
      由 Luiz Capitulino 提交于 
      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: NAnthony Liguori <aliguori@us.ibm.com>
Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      e1c37d0e
  39. 12 3月, 2012 1 次提交
  41. 25 2月, 2012 1 次提交
  43. 26 1月, 2012 4 次提交
  45. 18 1月, 2012 2 次提交