Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

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

You need to sign in or sign up before continuing.
切换分支/标签
  1. 13 7月, 2016 1 次提交
  3. 16 6月, 2016 2 次提交
  5. 19 5月, 2016 2 次提交
    • K
      qemu-iotests: Some more write_zeroes tests · 1ef7d010
      由 Kevin Wolf 提交于 
      This covers some more write_zeroes cases which are relevant for the
recent qcow2 optimisations that check the allocation status of the
backing file for partial cluster write_zeroes requests.

This needs to be separate from 034 because we can only support qcow2 in
this test case for multiple reasons: We check the allocation status
after write_zeroes with 'qemu-img map' and the optimised behaviour that
produces zero clusters is only implemented in qcow2; second, the map
command returns offsets that are qcow2 specific; and finally, we also
use 512 byte clusters which aren't supported for formats like qed.
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
      1ef7d010
    • K
      block: Remove bdrv_aio_multiwrite() · 91c6e4b7
      由 Kevin Wolf 提交于 
      Since virtio-blk implements request merging itself these days, the only
remaining users are test cases for the function. That doesn't make the
function exactly useful any more.
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
Reviewed-by: NMax Reitz <mreitz@redhat.com>
Reviewed-by: NEric Blake <eblake@redhat.com>
      91c6e4b7
  7. 20 4月, 2016 1 次提交
  9. 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
  11. 15 3月, 2016 1 次提交
  13. 14 3月, 2016 1 次提交
  15. 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
  17. 03 2月, 2016 5 次提交
  19. 18 12月, 2015 2 次提交
  21. 12 11月, 2015 1 次提交
  23. 11 11月, 2015 2 次提交
  25. 16 10月, 2015 1 次提交
  27. 14 9月, 2015 2 次提交
  29. 27 7月, 2015 1 次提交
  31. 02 7月, 2015 1 次提交
  33. 12 6月, 2015 1 次提交
  35. 22 5月, 2015 2 次提交
  37. 28 4月, 2015 3 次提交
  39. 08 4月, 2015 1 次提交
  41. 17 3月, 2015 2 次提交
  43. 10 3月, 2015 3 次提交
  45. 16 2月, 2015 2 次提交