Re: [Qemu-devel] virtio-blk wierd memcpy

2013-10-18 Thread Christian Borntraeger
On 17/10/13 20:49, Dave Airlie wrote: In my failing attempts to valgrind qemu (how to people live like this?), I spotted this in the logs What are the failures? Do you use emulation or KVM? I know that there seems to be some issues regarding async I/O but otherwise that that it seems to run.

[Qemu-devel] virtio-blk wierd memcpy

2013-10-17 Thread Dave Airlie
In my failing attempts to valgrind qemu (how to people live like this?), I spotted this in the logs ==19521== Source and destination overlap in memcpy(0x31d38938, 0x31d38938, 64) ==19521==at 0x4A0A343: memcpy@@GLIBC_2.14 (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==19521==

Re: [Qemu-devel] virtio-blk wierd memcpy

2013-10-17 Thread Stefan Weil
Am 17.10.2013 20:49, schrieb Dave Airlie: In my failing attempts to valgrind qemu (how to people live like this?), I spotted this in the logs ==19521== Source and destination overlap in memcpy(0x31d38938, 0x31d38938, 64) ==19521==at 0x4A0A343: memcpy@@GLIBC_2.14 (in