1. 08 3月, 2019 1 次提交
  2. 20 11月, 2018 1 次提交
  3. 23 1月, 2018 1 次提交
    • M
      qemu-iotests: Fix locking issue in 102 · 6bfc907d
      Max Reitz 提交于
      102 truncates a qcow2 file (the raw file) on purpose while a VM is
      running.  However, image locking will usually prevent exactly this.
      
      The fact that most people have not noticed until now (I suppose you may
      have seen sporadic failures, but not taken them too seriously, like me)
      further shows that this truncation is actually not really done
      concurrently, but that the VM is still starting up by this point and has
      not yet opened the image.  Remedy this by waiting for the monitor shell
      to appear before the qemu-img invocation so we know the VM is up.
      Signed-off-by: NMax Reitz <mreitz@redhat.com>
      Message-id: 20171129185102.29390-1-mreitz@redhat.com
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Signed-off-by: NMax Reitz <mreitz@redhat.com>
      6bfc907d
  4. 26 9月, 2017 1 次提交
  5. 25 4月, 2017 1 次提交
  6. 15 4月, 2016 1 次提交
  7. 03 11月, 2014 1 次提交
  8. 23 10月, 2014 2 次提交
  9. 29 4月, 2014 1 次提交
  10. 09 2月, 2014 1 次提交
  11. 27 9月, 2013 1 次提交
  12. 24 5月, 2013 1 次提交
  13. 23 2月, 2012 1 次提交
  14. 22 2月, 2012 3 次提交