Re: [Qemu-block] [Qemu-devel] [PATCH v9 0/8] Optimize VMDK I/O by allocating multiple clusters

[John Snow]

On 10/20/2017 02:53 AM, Ashijeet Acharya wrote:
> 
> On Fri, Oct 20, 2017 at 11:58 Fam Zheng <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     On Mon, 10/09 22:12, Fam Zheng wrote:
>     > On Mon, 10/09 18:29, Ashijeet Acharya wrote:
>     > > Optimization test results:
>     > >
>     > > This patch series improves 128 KB sequential write performance to an
>     > > empty VMDK file by 54%
>     > >
>     > > Benchmark command: ./qemu-img bench -w -c 1024 -s 128K -d 1 -t
>     none -f
>     > > vmdk test.vmdk
>     > >
>     > > Changes in v9:
>     > > - rebase the series
>     >
>     > Thanks, looks good to me, applied:
>     >
>     > https://github.com/famz/qemu/tree/staging
> 
>     Ashijeet: I've been testing my branch and it seems installing
>     Fedora/CentOS to a
>     VMDK image is broken with your patches applied. Both guest and QEMU are
>     responsive, but the installing of packages stops to make any
>     progress at some
>     point:
> 
>     Installing rootfiles.noarch (317/318)
>     Installing langpacks-en.noarch (318/318)
>     Performing post-installation setup tasks
>     Configuring fedora-release.noarch
>     Configuring filesystem.x86_64
>     Configuring GeoIP-GeoLite-data.noarch
>     Configuring python3.x86_64
>     Configuring fedora-logos.x86_64
>     Configuring kernel-core.x86_64
> 
>     # hang here
> 
>     Can you reproduce this on your machine?
> 
>     My command line is something like this:
> 
>     qemu-system-x86_64 -enable-kvm -cpu host -m 1G -qmp
>     unix:/home/fam/.q/qemu-8DOC9EF4/qmp,server,nowait -name 8DOC9EF4
>     -netdev user,id=vnet,hostfwd=:0.0.0.0 <http://0.0.0.0>:10022-:22
>     -device virtio-net-pci,netdev=vnet -drive
>     file=/var/tmp/test2.vmdk,if=none,id=drive-1,cache=none,aio=native
>     -device virtio-blk-pci,drive=drive-1 -cdrom
>     /stor/iso/CentOS-6.9-x86_64-minimal.iso -pidfile
>     /home/fam/.q/qemu-8DOC9EF4/pid
> 
>     qemu.git master doesn't have this problem. So I'll drop this series
>     from the
>     pull request until it is resolved.
> 
> 
> Fam: Alright, I will look into this but I cannot give you a deadline
> unfortunately. I will try my best to resolve this as soon as though.
> 
> Ashijeet
> 
> 
> 
>     Fam
> 

Do we need to temporarily roll this back for the 2.11 release if it
cannot be addressed in time?