[Qemu-devel] [Bug 1823152] Re: QEMU not able to boot ubuntu 18.04 as a guest
maybe this is just this issue? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795857 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1823152 Title: QEMU not able to boot ubuntu 18.04 as a guest Status in QEMU: Invalid Status in qemu package in Ubuntu: New Bug description: Host information: sushant@sushant-OptiPlex-7050:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic QEMU version: sushant@sushant-OptiPlex-7050:~$ /usr/bin/qemu-system-x86_64 --version QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.12) Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers I am trying to install xubuntu 18.04 as a qemu guest. The installation process goes smoothly and I reboot. After reboot, the boot process hangs with black screen and a blinking pointer. I used the following steps to install and boot the machine: STEP 1: sudo qemu-img create /var/lib/libvirt/images/xubuntu18_04.qcow2 30G STEP 2: sudo qemu-system-x86_64-spice -enable-kvm -cpu host -boot d -cdrom /home/sushant/Downloads/xubuntu-18.04.2-desktop-amd64.iso /var/lib/libvirt/images/xubuntu18_04.qcow2 -m 8G STEP 3: sudo qemu-system-x86_64-spice -enable-kvm -cpu host /var/lib/libvirt/images/xubuntu18_04.qcow2 -m 8G I tried with ubuntu 18.04(deafult ubuntu) and it also hangs with error "removed slice user slice of gdm" Also, if I install ubuntu 16.04 as guest, it boots smoothly. What should be done? To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1823152/+subscriptions
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug
** Attachment added: "qemu-cmdline" https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240132/+files/qemu-cmdline -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1685242 Title: ovmf hangs at efi with virtio-net memory hotplug Status in QEMU: New Bug description: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug
** Attachment added: "debug-nonworking.log" https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240134/+files/debug-nonworking.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1685242 Title: ovmf hangs at efi with virtio-net memory hotplug Status in QEMU: New Bug description: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug
** Attachment added: "qemu-cmdline" https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240133/+files/qemu-cmdline -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1685242 Title: ovmf hangs at efi with virtio-net memory hotplug Status in QEMU: New Bug description: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug
** Attachment added: "debug-working-222G.log" https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240135/+files/debug-working-222G.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1685242 Title: ovmf hangs at efi with virtio-net memory hotplug Status in QEMU: New Bug description: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug
** Attachment added: "debug-working-novirtio-net.log" https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240137/+files/debug-working-novirtio-net.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1685242 Title: ovmf hangs at efi with virtio-net memory hotplug Status in QEMU: New Bug description: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug
** Attachment added: "debug-working-2.6.log" https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240136/+files/debug-working-2.6.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1685242 Title: ovmf hangs at efi with virtio-net memory hotplug Status in QEMU: New Bug description: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug
i see, but is there a good reason why it did work with an older qemu version/machine type (<= 2.6) also my cpuinfo says physical bits 39 but i cannot use more maxmem than 222G i attached the cpuinfo, cmdline, and debug logs for a nonworking invocation and one for each working, with 222G, with machine type 2.6 and without a virtio-net respectively ** Attachment added: "/proc/cpuinfo" https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240131/+files/cpuinfo -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1685242 Title: ovmf hangs at efi with virtio-net memory hotplug Status in QEMU: New Bug description: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug
i forgot: it also works with -machine pc-i440fx-2.6 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1685242 Title: ovmf hangs at efi with virtio-net memory hotplug Status in QEMU: New Bug description: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
[Qemu-devel] [Bug 1685242] [NEW] ovmf hangs at efi with virtio-net memory hotplug
Public bug reported: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1685242 Title: ovmf hangs at efi with virtio-net memory hotplug Status in QEMU: New Bug description: with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices the ovmf images where compiled from https://github.com/tianocore/edk2 (current master) reproducer: qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G' interestingly, it works when you do the following: - omit the virtio-net-pci device - use seabios - use less maxmem, e.g. 512G qemu was compiled from source (v2.9.0) with following options: ./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable -spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
[Qemu-devel] [Bug 1644754] [NEW] gluster partial reads refusal conflicts with qcow2
Public bug reported: there is an inconsistency in how qemu creates qcow2 files, which causes an error in the gluster (and possibly other block drivers) the problem is that the gluster backend expects the filesize to be 512 byte aligned, which is not the case anymore since 2.7.0 when using the file backend for qcow2 files with a backing file the error is then Could not open 'gluster://gluster01/gv0/bar2.qcow2': Could not read L1 table: Input/output error steps to reproduce: * create a.qcow2 * create b.qcow2 with a.qcow2 as base via filesystem (without gluster) b.qcow2 filesize is not a multiple of 512 bytes * move both files to a gluster share * access to b.qcow2 via gluster block driver fails example: have a gluster server at 'gluster01' with a volume 'gv0' (gluster versions tested: 3.7.15,3.8.5,3.8.5) root@pc:~# mount -t glusterfs gluster01:/gv0 /mnt/gluster root@pc:~# qemu-img create -f qcow2 gluster://gluster01/gv0/foo.qcow2 100M Formatting 'gluster://gluster01/gv0/foo.qcow2', fmt=qcow2 size=104857600 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16 root@pc:~# qemu-img info /mnt/gluster/foo.qcow2 image: /mnt/gluster/foo.qcow2 file format: qcow2 virtual size: 100M (104857600 bytes) disk size: 193K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false root@pc:~# qemu-img info gluster://gluster01/gv0/foo.qcow2 image: gluster://gluster01/gv0/foo.qcow2 file format: qcow2 virtual size: 100M (104857600 bytes) disk size: 193K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false root@pc:~# qemu-img create -f qcow2 -b foo.qcow2 gluster://gluster01/gv0/bar.qcow2 Formatting 'gluster://gluster01/gv0/bar.qcow2', fmt=qcow2 size=104857600 backing_file=foo.qcow2 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16 root@pc:~# qemu-img info /mnt/gluster/bar.qcow2 image: /mnt/gluster/bar.qcow2 file format: qcow2 virtual size: 100M (104857600 bytes) disk size: 193K cluster_size: 65536 backing file: foo.qcow2 (actual path: /mnt/gluster/foo.qcow2) Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false root@pc:~# qemu-img info gluster://gluster01/gv0/bar.qcow2 image: gluster://gluster01/gv0/bar.qcow2 file format: qcow2 virtual size: 100M (104857600 bytes) disk size: 193K cluster_size: 65536 backing file: foo.qcow2 (actual path: gluster://gluster01/gv0/foo.qcow2) Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false root@pc:~# qemu-img create -f qcow2 -b foo.qcow2 /mnt/gluster/bar2.qcow2 Formatting '/mnt/gluster/bar2.qcow2', fmt=qcow2 size=104857600 backing_file=foo.qcow2 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16 root@pc:~# qemu-img info /mnt/gluster/bar2.qcow2 image: /mnt/gluster/bar2.qcow2 file format: qcow2 virtual size: 100M (104857600 bytes) disk size: 193K cluster_size: 65536 backing file: foo.qcow2 (actual path: /mnt/gluster/foo.qcow2) Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false root@pc:~# qemu-img info gluster://gluster01/gv0/bar2.qcow2 qemu-img: Could not open 'gluster://gluster01/gv0/bar2.qcow2': Could not read L1 table: Input/output error root@pc:~# ls -l /mnt/gluster/ total 578 -rw-r--r-- 1 root root 196616 Nov 25 09:07 bar2.qcow2 -rw--- 1 root root 197120 Nov 25 09:07 bar.qcow2 -rw--- 1 root root 197120 Nov 25 09:06 foo.qcow2 drwxr-xr-x 6 root root 46 Nov 24 16:51 images here you can see that the file created with directory path is not 512 byte aligned, while the one created through the gluster api is also, when creating a qcow2 with the nfs block driver, the filesize is also a multiple of 512, but reading a non aligned file with nfs works however ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1644754 Title: gluster partial reads refusal conflicts with qcow2 Status in QEMU: New Bug description: there is an inconsistency in how qemu creates qcow2 files, which causes an error in the gluster (and possibly other block drivers) the problem is that the gluster backend expects the filesize to be 512 byte aligned, which is not the case anymore since 2.7.0 when using the file backend for qcow2 files with a backing file the error is then Could not open 'gluster://gluster01/gv0/bar2.qcow2': Could not read L1 table: Input/output error steps to reproduce: * create a.qcow2 * create b.qcow2 with a.qcow2 as base via filesystem (without gluster) b.qcow2 filesize is not a multiple of 512 bytes * move both files to a gluster share * access to b.qcow2 via gluster block driver fails example:
