[Qemu-devel] [Bug 1191326] Re: QNX 4 doesn't boot on qemu = 1.3
Output from valgrind running latest qemu downloaded from git. Qemu crashed of course. If I can check something more, please let me know. ==29109== Memcheck, a memory error detector ==29109== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==29109== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==29109== Command: qemu-system-i386 -no-kvm -hda /home/jq/QNX4.vmdk ==29109== Parent PID: 15280 ==29109== ==29109== Invalid write of size 8 ==29109==at 0x4C2CD8D: memcpy@@GLIBC_2.14 (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==29109==by 0x4DF292: iov_from_buf (iov.c:37) ==29109==by 0x4E01B8: qemu_iovec_from_buf (iov.c:374) ==29109==by 0x1A0CA6: bdrv_aio_bh_cb (block.c:3820) ==29109==by 0x186CEB: aio_bh_poll (async.c:81) ==29109==by 0x18693D: aio_poll (aio-posix.c:188) ==29109==by 0x1870FA: aio_ctx_dispatch (async.c:205) ==29109==by 0x5081AB4: g_main_context_dispatch (gmain.c:2715) ==29109==by 0x3235CE: glib_pollfds_poll (main-loop.c:189) ==29109==by 0x3236C2: os_host_main_loop_wait (main-loop.c:234) ==29109==by 0x32379A: main_loop_wait (main-loop.c:484) ==29109==by 0x3B0776: main_loop (vl.c:2090) ==29109== Address 0x157c8ff8 is not stack'd, malloc'd or (recently) free'd ==29109== ==29109== Invalid read of size 4 ==29109==at 0x3C4B85: ldl_p (bswap.h:262) ==29109==by 0x3C4CC6: ldl_le_p (bswap.h:295) ==29109==by 0x3CAAC2: address_space_rw (exec.c:1953) ==29109==by 0x3CAE0C: address_space_write (exec.c:2021) ==29109==by 0x3CB570: address_space_unmap (exec.c:2230) ==29109==by 0x1EF736: dma_memory_unmap (dma.h:146) ==29109==by 0x1EFCBD: dma_bdrv_unmap (dma-helpers.c:108) ==29109==by 0x1EFE35: dma_bdrv_cb (dma-helpers.c:146) ==29109==by 0x1A0FE0: bdrv_co_em_bh (block.c:3901) ==29109==by 0x186CEB: aio_bh_poll (async.c:81) ==29109==by 0x18693D: aio_poll (aio-posix.c:188) ==29109==by 0x1870FA: aio_ctx_dispatch (async.c:205) ==29109== Address 0x157ba000 is 0 bytes after a block of size 4,096 alloc'd ==29109==at 0x4C29CD5: memalign (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==29109==by 0x4C29D2E: posix_memalign (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==29109==by 0x4DA0AB: qemu_memalign (oslib-posix.c:90) ==29109==by 0x3CB322: address_space_map (exec.c:2162) ==29109==by 0x1EF6BE: dma_memory_map (dma.h:137) ==29109==by 0x1EFEEF: dma_bdrv_cb (dma-helpers.c:156) ==29109==by 0x1F0205: dma_bdrv_io (dma-helpers.c:219) ==29109==by 0x1F027A: dma_bdrv_read (dma-helpers.c:228) ==29109==by 0x2724C4: ide_dma_cb (core.c:676) ==29109==by 0x278AC2: bmdma_cmd_writeb (pci.c:324) ==29109==by 0x2792AA: bmdma_write (piix.c:76) ==29109==by 0x43535C: memory_region_write_accessor (memory.c:440) ==29109== valgrind: m_mallocfree.c:266 (mk_plain_bszB): Assertion 'bszB != 0' failed. valgrind: This is probably caused by your program erroneously writing past the end of a heap block and corrupting heap metadata. If you fix any invalid writes reported by Memcheck, this assertion failure will probably go away. Please try that before reporting this as a bug. ==29109==at 0x3804C6CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==29109==by 0x3804C812: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==29109==by 0x38000883: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==29109==by 0x38057FB1: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==29109==by 0x38058962: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==29109==by 0x380212DC: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==29109==by 0x3802158F: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==29109==by 0x3808F1DB: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==29109==by 0x3809E68C: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==29109==at 0x4C29CD5: memalign (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==29109==by 0x4C29D2E: posix_memalign (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==29109==by 0x4DA0AB: qemu_memalign (oslib-posix.c:90) ==29109==by 0x1A2192: qemu_blockalign (block.c:4375) ==29109==by 0x1A0D92: bdrv_aio_rw_vector (block.c:3842) ==29109==by 0x1A0EB6: bdrv_aio_readv_em (block.c:3861) ==29109==by 0x1A169A: bdrv_co_io_em (block.c:4068) ==29109==by 0x1A172B: bdrv_co_readv_em (block.c:4085) ==29109==by 0x19D921: bdrv_co_do_readv (block.c:2574) ==29109==by 0x1A1091: bdrv_co_do_rw (block.c:3918) ==29109==by 0x1E7776: coroutine_trampoline (coroutine-ucontext.c:118) ==29109==by 0x5F3264F: ??? (in /lib/x86_64-linux-gnu/libc-2.15.so) ==29109==by 0x7FEFFC5CF: ??? Thread 2: status = VgTs_WaitSys ==29109==at 0x5CDB0C1: sem_timedwait (sem_timedwait.S:102) ==29109==by 0x4DAD2A: qemu_sem_timedwait (qemu-thread-posix.c:238) ==29109==by 0x387F22: worker_thread
[Qemu-devel] [Bug 1191326] Re: QNX 4 doesn't boot on qemu = 1.3
KVM doesnt make any difference. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1191326 Title: QNX 4 doesn't boot on qemu = 1.3 Status in QEMU: New Bug description: I am using virtual machine with QNX4 operating system installed on it. I updated my qemu from version to newer and QNX4 doesn't start any more. All is ok on version 1.2 but when I try to use any newer version (1.3, 1.4, 1.5) QNX4 doesn't boot. I tried on windows and linux ubuntu hosts - effects are the same. When virtual machine boots qnx bootloader loads and starts operating system. In the next step qnx starts its ide driver, which detects qemu harddisk and cdrom. Problem starts when operating system tries mount partition - an error occur and qnx stop booting procedure: mount -p No bios signature in partition sector on /dev/hd0 I have tried install qnx from cdrom but it seems that there is the same problem. QNX installer boot from cdrom, detects hard disk and cdrom, but cdrom can't be mounted in the next step of installation procedure. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1191326/+subscriptions
[Qemu-devel] [Bug 1191326] Re: QNX 4 doesn't boot on qemu = 1.3
problem appeared in this commit: commit b90600eed3c0efe5f3260853c873caf51c0677b1 Author: Avi Kivity a...@redhat.com Date: Wed Oct 3 16:42:37 2012 +0200 dma: make dma access its own address space Instead of accessing the cpu address space, use an address space configured by the caller. Eventually all dma functionality will be folded into AddressSpace, but we have to start from something. Reviewed-by: Anthony Liguori aligu...@us.ibm.com Signed-off-by: Avi Kivity a...@redhat.com -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1191326 Title: QNX 4 doesn't boot on qemu = 1.3 Status in QEMU: New Bug description: I am using virtual machine with QNX4 operating system installed on it. I updated my qemu from version to newer and QNX4 doesn't start any more. All is ok on version 1.2 but when I try to use any newer version (1.3, 1.4, 1.5) QNX4 doesn't boot. I tried on windows and linux ubuntu hosts - effects are the same. When virtual machine boots qnx bootloader loads and starts operating system. In the next step qnx starts its ide driver, which detects qemu harddisk and cdrom. Problem starts when operating system tries mount partition - an error occur and qnx stop booting procedure: mount -p No bios signature in partition sector on /dev/hd0 I have tried install qnx from cdrom but it seems that there is the same problem. QNX installer boot from cdrom, detects hard disk and cdrom, but cdrom can't be mounted in the next step of installation procedure. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1191326/+subscriptions
[Qemu-devel] [Bug 1191326] Re: QNX 4 doesn't boot on qemu = 1.3
with qemu 1.6 is even worse - qemu crash every time when QNX detects hard disk -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1191326 Title: QNX 4 doesn't boot on qemu = 1.3 Status in QEMU: New Bug description: I am using virtual machine with QNX4 operating system installed on it. I updated my qemu from version to newer and QNX4 doesn't start any more. All is ok on version 1.2 but when I try to use any newer version (1.3, 1.4, 1.5) QNX4 doesn't boot. I tried on windows and linux ubuntu hosts - effects are the same. When virtual machine boots qnx bootloader loads and starts operating system. In the next step qnx starts its ide driver, which detects qemu harddisk and cdrom. Problem starts when operating system tries mount partition - an error occur and qnx stop booting procedure: mount -p No bios signature in partition sector on /dev/hd0 I have tried install qnx from cdrom but it seems that there is the same problem. QNX installer boot from cdrom, detects hard disk and cdrom, but cdrom can't be mounted in the next step of installation procedure. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1191326/+subscriptions
[Qemu-devel] [Bug 1191326] [NEW] QNX 4 doesn't boot on qemu = 1.3
Public bug reported: I am using virtual machine with QNX4 operating system installed on it. I updated my qemu from version to newer and QNX4 doesn't start any more. All is ok on version 1.2 but when I try to use any newer version (1.3, 1.4, 1.5) QNX4 doesn't boot. I tried on windows and linux ubuntu hosts - effects are the same. When virtual machine boots qnx bootloader loads and starts operating system. In the next step qnx starts its ide driver, which detects qemu harddisk and cdrom. Problem starts when operating system tries mount partition - an error occur and qnx stop booting procedure: mount -p No bios signature in partition sector on /dev/hd0 I have tried install qnx from cdrom but it seems that there is the same problem. QNX installer boot from cdrom, detects hard disk and cdrom, but cdrom can't be mounted in the next step of installation procedure. ** 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/1191326 Title: QNX 4 doesn't boot on qemu = 1.3 Status in QEMU: New Bug description: I am using virtual machine with QNX4 operating system installed on it. I updated my qemu from version to newer and QNX4 doesn't start any more. All is ok on version 1.2 but when I try to use any newer version (1.3, 1.4, 1.5) QNX4 doesn't boot. I tried on windows and linux ubuntu hosts - effects are the same. When virtual machine boots qnx bootloader loads and starts operating system. In the next step qnx starts its ide driver, which detects qemu harddisk and cdrom. Problem starts when operating system tries mount partition - an error occur and qnx stop booting procedure: mount -p No bios signature in partition sector on /dev/hd0 I have tried install qnx from cdrom but it seems that there is the same problem. QNX installer boot from cdrom, detects hard disk and cdrom, but cdrom can't be mounted in the next step of installation procedure. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1191326/+subscriptions
