1. 08 3月, 2019 1 次提交
  2. 20 11月, 2018 1 次提交
  3. 23 5月, 2018 1 次提交
  4. 02 8月, 2017 1 次提交
    • M
      iotests: Fix test 156 · 645acdc0
      Max Reitz 提交于
      On one hand, the _make_test_img invocation for creating the target image
      was missing a -u because its backing file is not supposed to exist at
      that point.
      
      On the other hand, nobody noticed probably because the backing file is
      created later on and _cleanup failed to remove it: The quotation marks
      were misplaced so bash tried to delete a file literally called
      "$TEST_IMG{,.target}..." instead of performing brace expansion. Thus, the
      files stayed around after the first run and qemu-img create did not
      complain about a missing backing file on any run but the first.
      Signed-off-by: NMax Reitz <mreitz@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NJeff Cody <jcody@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      645acdc0
  5. 18 7月, 2017 1 次提交
    • J
      qemu-img: Check for backing image if specified during create · 6e6e55f5
      John Snow 提交于
      Or, rather, force the open of a backing image if one was specified
      for creation. Using a similar -unsafe option as rebase, allow qemu-img
      to ignore the backing file validation if possible.
      
      It may not always be possible, as in the existing case when a filesize
      for the new image was not specified.
      
      This is accomplished by shifting around the conditionals in
      bdrv_img_create, such that a backing file is always opened unless we
      provide BDRV_O_NO_BACKING. qemu-img is adjusted to pass this new flag
      when -u is provided to create.
      
      Sorry for the heinous looking diffstat, but it's mostly whitespace.
      
      Inspired by: https://bugzilla.redhat.com/show_bug.cgi?id=1213786Signed-off-by: NJohn Snow <jsnow@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      6e6e55f5
  6. 25 4月, 2017 2 次提交
  7. 16 6月, 2016 1 次提交