Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu
切换分支/标签
  1. 19 5月, 2016 1 次提交
  3. 20 4月, 2016 1 次提交
  5. 30 3月, 2016 2 次提交
    • M
      iotests: Test qemu-img convert -S 0 behavior · f4e732a0
      由 Max Reitz 提交于 
      Passing -S 0 to qemu-img convert should result in all source data being
copied to the output, even if that source data is known to be 0. The
output image should therefore have exactly the same size on disk as an
image which we explicitly filled with data.
Signed-off-by: NMax Reitz <mreitz@redhat.com>
Reviewed-by: NFam Zheng <famz@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      f4e732a0
    • D
      block: an interoperability test for luks vs dm-crypt/cryptsetup · 6278ae03
      由 Daniel P. Berrange 提交于 
      It is important that the QEMU luks implementation retains 100%
compatibility with the reference implementation provided by
the combination of the linux kernel dm-crypt module and cryptsetup
userspace tools.

There is a matrix of tests to be performed with different sets
of encryption settings. For each matrix entry, two tests will
be performed. One will create a LUKS image with the cryptsetup
tool and then do I/O with both cryptsetup & qemu-io. The other
will create the image with qemu-img and then again do I/O with
both cryptsetup and qemu-io.

The new I/O test 149 performs interoperability testing between
QEMU and the reference implementation. Such testing inherantly
requires elevated privileges, so to this this the user must have
configured passwordless sudo access. The test will automatically
skip if sudo is not available.

The test has to be run explicitly thus:

    cd tests/qemu-iotests
    ./check -luks 149
Reviewed-by: NEric Blake <eblake@redhat.com>
Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      6278ae03
  7. 15 3月, 2016 1 次提交
  9. 14 3月, 2016 1 次提交
  11. 22 2月, 2016 1 次提交
    • K
      block: Fix -incoming with snapshot=on · 12d5ee3a
      由 Kevin Wolf 提交于 
      The BDRV_O_INACTIVE flag should only be set for images explicitly opened
by the user. snapshot=on needs to create a new qcow2 image and write
some metadata to it. This is not a problem because it can't come from
the source, so there's no reason to mark it as BDRV_O_INACTIVE, even
though it is opened while waiting for the migration to complete.

This fixes an assertion failure when -incoming and snapshot=on are
combined.
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      12d5ee3a
  13. 03 2月, 2016 5 次提交
  15. 18 12月, 2015 2 次提交
  17. 12 11月, 2015 1 次提交
  19. 11 11月, 2015 2 次提交
  21. 16 10月, 2015 1 次提交
  23. 14 9月, 2015 2 次提交
  25. 27 7月, 2015 1 次提交
  27. 02 7月, 2015 1 次提交
  29. 12 6月, 2015 1 次提交
  31. 22 5月, 2015 2 次提交
  33. 28 4月, 2015 3 次提交
  35. 08 4月, 2015 1 次提交
  37. 17 3月, 2015 2 次提交
  39. 10 3月, 2015 3 次提交
  41. 16 2月, 2015 4 次提交
  43. 07 2月, 2015 1 次提交
  45. 13 1月, 2015 1 次提交