Hi Rod,
I did try to recreate with the qemu version that you have.
$ apt install apache2 qemu-system-x86
$ qemu-img create -f qcow2 /var/www/html/test.img 1G
# local
$ qemu-img check test.img
No errors were found on the image.
# remote
$ qemu-img check http://localhost:80/test.img
No errors were found on the image.
Image end offset: 262144
Hi Rod,
I did try to recreate with the qemu version that you have.
$ apt install apache2 qemu-system-x86 html/test. img 1G localhost: 80/test. img
$ qemu-img create -f qcow2 /var/www/
# local
$ qemu-img check test.img
No errors were found on the image.
# remote
$ qemu-img check http://
No errors were found on the image.
Image end offset: 262144
Local check and remote check both work just fine.
I recognized the image that you have there and then did: /cloud- images. ubuntu. com/bionic/ current/ bionic- server- cloudimg- amd64.img server- cloudimg- amd64.img localhost: 80/bionic- server- cloudimg- amd64.img
$ cd /var/www/html/
$ wget https:/
# local
$ qemu-img check bionic-
No errors were found on the image.
16651/36032 = 46.21% allocated, 98.92% fragmented, 98.49% compressed clusters
Image end offset: 344195072
# remote
$ qemu-img check http://
<hangs>
Therefore I can confirm the behavior you described.