Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu
切换分支/标签
  1. 03 3月, 2018 2 次提交
  3. 02 3月, 2018 2 次提交
  5. 01 3月, 2018 2 次提交
  7. 19 2月, 2018 2 次提交
  9. 14 2月, 2018 1 次提交
  11. 13 2月, 2018 2 次提交
  13. 09 2月, 2018 2 次提交
  15. 08 2月, 2018 2 次提交
  17. 23 1月, 2018 1 次提交
  19. 22 1月, 2018 1 次提交
  21. 19 1月, 2018 4 次提交
  23. 15 1月, 2018 2 次提交
  25. 12 1月, 2018 1 次提交
  27. 22 12月, 2017 2 次提交
  29. 21 12月, 2017 1 次提交
  31. 19 12月, 2017 1 次提交
  33. 27 11月, 2017 2 次提交
    • K
      QAPI & interop: Clarify events emitted by 'block-job-cancel' · c117bb14
      由 Kashyap Chamarthy 提交于 
      When you cancel an in-progress 'mirror' job (or "active `block-commit`")
with QMP `block-job-cancel`, it emits the event: BLOCK_JOB_CANCELLED.
However, when `block-job-cancel` is issued *after* `drive-mirror` has
indicated (via the event BLOCK_JOB_READY) that the source and
destination have reached synchronization:

    [...] # Snip `drive-mirror` invocation & outputs
    {
      "execute":"block-job-cancel",
      "arguments":{
        "device":"virtio0"
      }
    }

    {"return": {}}

It (`block-job-cancel`) will counterintuitively emit the event
'BLOCK_JOB_COMPLETED':

    {
      "timestamp":{
        "seconds":1510678024,
        "microseconds":526240
      },
      "event":"BLOCK_JOB_COMPLETED",
      "data":{
        "device":"virtio0",
        "len":41126400,
        "offset":41126400,
        "speed":0,
        "type":"mirror"
      }
    }

But this is expected behaviour, where the _COMPLETED event indicates
that synchronization has successfully ended (and the destination now has
a point-in-time copy, which is at the time of cancel).

So add a small note to this effect in 'block-core.json'.  While at it,
also update the "Live disk synchronization -- drive-mirror and
blockdev-mirror" section in 'live-block-operations.rst'.

(Thanks: Max Reitz for reminding me of this caveat on IRC.)
Signed-off-by: NKashyap Chamarthy <kchamart@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      c117bb14
    • F
      docs: Add image locking subsection · b1d1cb27
      由 Fam Zheng 提交于 
      This documents the image locking feature and explains when and how
related options can be used.
Signed-off-by: NFam Zheng <famz@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      b1d1cb27
  35. 21 11月, 2017 2 次提交
    • S
      Use HTTPS for qemu.org and other domains · 70b7fba9
      由 Stefan Hajnoczi 提交于 
      qemu.org enabled HTTPS in 2017 and it should be used instead of HTTP.
There are also URLs to json.org, openvpn.net, and other domains that
support HTTPS.

This patch updates the qemu.org domains everywhere and also third-party
domains that I have checked.
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
Message-id: 20171121120435.28728-3-stefanha@redhat.com
Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      70b7fba9
    • S
      Use qemu.org domain name · 1b3bbc68
      由 Stefan Hajnoczi 提交于 
      The owner of qemu.org has delegated authority to modify DNS records to
the QEMU Project.  This has allowed us to use the domain name without
worries about IP address changes or technical issues disrupting service.
The issues described in commit 85938981
("Use qemu-project.org domain name") have therefore been mitigated.

This patch switches back to consistently using qemu.org instead of
qemu-project.org in documentation, version.rc, and the Windows installer
script.

The git submodules and SeaBIOS still use qemu-project.org for the time
being.  This will be fixed in the QEMU 2.12 release cycle.
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
Message-id: 20171121120435.28728-2-stefanha@redhat.com
Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      1b3bbc68
  37. 15 11月, 2017 1 次提交
  39. 05 11月, 2017 1 次提交
  41. 17 10月, 2017 1 次提交
  43. 15 10月, 2017 2 次提交
  45. 13 10月, 2017 1 次提交
  47. 27 9月, 2017 1 次提交
  49. 26 9月, 2017 1 次提交