Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

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

切换分支/标签
  1. 20 10月, 2011 10 次提交
  3. 04 10月, 2011 1 次提交
    • L
      RunState: Rename enum values as generated by the QAPI · 0461d5a6
      由 Luiz Capitulino 提交于 
      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: NLuiz Capitulino <lcapitulino@redhat.com>
      0461d5a6
  5. 16 9月, 2011 4 次提交
  7. 21 8月, 2011 1 次提交
  9. 06 8月, 2011 1 次提交
  11. 24 7月, 2011 1 次提交
  13. 14 2月, 2011 1 次提交
  15. 24 1月, 2011 1 次提交
    • G
      add migration state change notifiers · 99a0db9b
      由 Gerd Hoffmann 提交于 
      This patch adds functions to register and unregister notifiers for
migration state changes and a function to query the migration state.
The notifier is called on every state change.  Once after establishing a
new migration object (which is in active state then) and once when the
state changes from active to completed, canceled or error.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      99a0db9b
  17. 18 1月, 2011 1 次提交
    • A
      savevm: Fix no_migrate · dc912121
      由 Alex Williamson 提交于 
      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: NAlex Williamson <alex.williamson@redhat.com>
Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      dc912121
  19. 09 12月, 2010 1 次提交
  21. 03 12月, 2010 1 次提交
  23. 04 11月, 2010 1 次提交
  25. 19 8月, 2010 1 次提交
  27. 31 7月, 2010 1 次提交
  29. 02 7月, 2010 1 次提交
    • L
      Monitor: handle optional '-' arg as a bool · eb159d13
      由 Luiz Capitulino 提交于 
      Historically, user monitor arguments beginning with '-' (eg. '-f')
were passed as integers down to handlers.

I've maintained this behavior in the new monitor because we didn't
have a boolean type at the very beginning of QMP. Today we have it
and this behavior is causing trouble to QMP's argument checker.

This commit fixes the problem by doing the following changes:

1. User Monitor

   Before: the optional arg was represented as a QInt, we'd pass 1
           down to handlers if the user specified the argument or
           0 otherwise

   This commit: the optional arg is represented as a QBool, we pass
                true down to handlers if the user specified the
                argument, otherwise _nothing_ is passed

2. QMP

   Before: the client was required to pass the arg as QBool, but we'd
           convert it to QInt internally. If the argument wasn't passed,
           we'd pass 0 down

   This commit: still require a QBool, but doesn't do any conversion and
                doesn't pass any default value

3. Convert existing handlers (do_eject()/do_migrate()) to the new way

   Before: Both handlers would expect a QInt value, either 0 or 1

   This commit: Change the handlers to accept a QBool, they handle the
                following cases:

                   A) true is passed: the option is enabled
                   B) false is passed: the option is disabled
                   C) nothing is passed: option not specified, use
                                         default behavior
Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
      eb159d13
  31. 23 6月, 2010 2 次提交
  33. 15 6月, 2010 1 次提交
  35. 04 6月, 2010 1 次提交
  37. 02 6月, 2010 1 次提交
  39. 20 2月, 2010 2 次提交
  41. 11 2月, 2010 1 次提交
  43. 07 2月, 2010 1 次提交
  45. 04 2月, 2010 4 次提交