Re: [Qemu-block] [Qemu-devel] I/O errors reported to guest for raw-image-file backed /dev/vda - but host sees no I/O errors

On 04/22/2016 03:16 AM, Fam Zheng wrote: On Thu, 04/21 17:54, Lutz Vieweg wrote: Nevertheless, I think qemu could be somewhat more verbose, reporting when and why it stops emulation. Something like a message to the monitor or to standard out would be helpful to start with... QEMU does report a

Re: [Qemu-block] [Qemu-devel] I/O errors reported to guest for raw-image-file backed /dev/vda - but host sees no I/O errors

On Thu, 04/21 17:54, Lutz Vieweg wrote: > Nevertheless, I think qemu could be somewhat more verbose, reporting > when and why it stops emulation. Something like a message to the monitor > or to standard out would be helpful to start with... QEMU does report an error message to connected monitor if

Re: [Qemu-block] [Qemu-devel] I/O errors reported to guest for raw-image-file backed /dev/vda - but host sees no I/O errors

On 04/20/2016 01:50 PM, Kevin Wolf wrote: To catch all possible write failures, I think pwrite, pwritev and possibly fdatasync need to be considered. I've now a strace -f -p 10727 -e trace=pwrite,pwritev,fdatasync,file -t 2>&1 | gzip -1 -c >trace.gz attached to the qemu-process. If the inci

Re: [Qemu-block] [Qemu-devel] I/O errors reported to guest for raw-image-file backed /dev/vda - but host sees no I/O errors

Am 20.04.2016 um 04:11 hat Fam Zheng geschrieben: > On Tue, 04/19 19:47, Lutz Vieweg wrote: > > The guest drive parameters are: > > > -drive > > > "file=image.raw,if=virtio,format=raw,media=disk,cache=unsafe,werror=report,rerror=report" > > Given this implies aio=threads... > > > Can you provide