[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] iotest 194 fails on vhdx
From: |
Alexey Kardashevskiy |
Subject: |
Re: [Qemu-devel] iotest 194 fails on vhdx |
Date: |
Wed, 25 Oct 2017 17:06:37 +1100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 |
On 25/10/17 15:29, Alexey Kardashevskiy wrote:
> Hi!
>
> The latest QEMU fails on:
> tests/qemu-iotests/check -vhdx 194
Bit more details:
1. the assert started appearing from
https://git.qemu.org/?p=qemu.git;a=commit;h=09e0c771e47 - this one just
added the assert;
2. if removed, then another assert alerts:
qemu-system-ppc64: /home/aik/p/qemu/block/io.c:1423: bdrv_aligned_pwritev:
Assertion `child->perm & BLK_PERM_WRITE' failed.
child->perm == 1 when this happens.
Any clues?
>
>
> /home/aik/pbuild/qemu-aikhostos2-ppc64-softmmu-debug-build/ppc64-softmmu/qemu-system-ppc64
> \
> -chardev socket,id=mon,path=/home/aik/qemudest-monitor.sock \
> -mon chardev=mon,mode=control \
> -display none \
> -vga none \
> -machine accel=qtest \
> -nodefaults \
> -incoming unix:/home/aik/qemu-migration.sock \
> -drive
> if=virtio,id=drive0,file=/home/aik/dest.img,format=vhdx,cache=writeback
>
>
> GDB says it is assert(!(bs->open_flags & BDRV_O_INACTIVE)). The very same
> test passes with a qcow2 image. Does it look any familiar to anyone? Where
> to start digging from? Thanks.
>
>
>
> (gdb) r
> Starting program:
> /home/aik/pbuild/qemu-aikhostos2-ppc64-softmmu-debug-build/ppc64-softmmu/qemu-system-ppc64
> -chardev socket,id=mon,path=/home/a
> ik/qemudest-monitor.sock -mon chardev=mon,mode=control -display none -vga
> none -machine accel=qtest -nodefaults -incoming unix:/home/aik/qemu-mi
> gration.sock -drive
> if=virtio,id=drive0,file=/home/aik/dest.img,format=vhdx,cache=writeback
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> [New Thread 0x7ffff698eb80 (LWP 70705)]
> [New Thread 0x7ffff607eb80 (LWP 70706)]
> qemu-system-ppc64: /home/aik/p/qemu/block/io.c:1601: bdrv_co_pwritev:
> Assertion `!(bs->open_flags & 0x0800)' failed.
>
> Program received signal SIGABRT, Aborted.
> 0x00007ffff77deff0 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x00007ffff77deff0 in raise () from /lib64/libc.so.6
> #1 0x00007ffff77e136c in abort () from /lib64/libc.so.6
> #2 0x00007ffff77d4c44 in __assert_fail_base () from /lib64/libc.so.6
> #3 0x00007ffff77d4d34 in __assert_fail () from /lib64/libc.so.6
> #4 0x000000001074ce44 in bdrv_co_pwritev (child=0x111c6160, offset=65536,
> bytes=80, qiov=0x7fffffffe090, flags=0)
> at /home/aik/p/qemu/block/io.c:1601
> #5 0x0000000010749408 in bdrv_rw_co_entry (opaque=0x7fffffffdfa0) at
> /home/aik/p/qemu/block/io.c:620
> #6 0x0000000010857188 in coroutine_trampoline (i0=287156048, i1=0) at
> /home/aik/p/qemu/util/coroutine-ucontext.c:79
> #7 0x00007ffff77f2b9c in makecontext () from /lib64/libc.so.6
> #8 0x0000000000000000 in ?? ()
> (gdb) p bs->open_flags
> No symbol "bs" in current context.
> (gdb) up
> #1 0x00007ffff77e136c in abort () from /lib64/libc.so.6
> (gdb)
> #2 0x00007ffff77d4c44 in __assert_fail_base () from /lib64/libc.so.6
> (gdb)
> #3 0x00007ffff77d4d34 in __assert_fail () from /lib64/libc.so.6
> (gdb)
> #4 0x000000001074ce44 in bdrv_co_pwritev (child=0x111c6160, offset=65536,
> bytes=80, qiov=0x7fffffffe090, flags=0)
> at /home/aik/p/qemu/block/io.c:1601
> 1601 assert(!(bs->open_flags & BDRV_O_INACTIVE));
> (gdb) p/x bs->open_flags
> $2 = 0xe802
> (gdb)
>
>
--
Alexey