Please consider for 2.1. It needs git-am -3 by now; if you need a
respin, let me know.
Markus Armbruster arm...@redhat.com writes:
When a device model's I/O operation fails, we execute the error
action. This lets layers above QEMU implement thin provisioning, or
attempt to correct errors
On Thu, Jun 05, 2014 at 02:15:33PM +0200, Markus Armbruster wrote:
When a device model's I/O operation fails, we execute the error
action. This lets layers above QEMU implement thin provisioning, or
attempt to correct errors before they reach the guest. But when the
I/O operation fails
Ping?
Markus Armbruster arm...@redhat.com writes:
When a device model's I/O operation fails, we execute the error
action. This lets layers above QEMU implement thin provisioning, or
attempt to correct errors before they reach the guest. But when the
I/O operation fails because its invalid,
Il 05/06/2014 14:15, Markus Armbruster ha scritto:
When a device model's I/O operation fails, we execute the error
action. This lets layers above QEMU implement thin provisioning, or
attempt to correct errors before they reach the guest. But when the
I/O operation fails because its invalid,
Paolo Bonzini pbonz...@redhat.com writes:
Il 05/06/2014 14:15, Markus Armbruster ha scritto:
When a device model's I/O operation fails, we execute the error
action. This lets layers above QEMU implement thin provisioning, or
attempt to correct errors before they reach the guest. But when
When a device model's I/O operation fails, we execute the error
action. This lets layers above QEMU implement thin provisioning, or
attempt to correct errors before they reach the guest. But when the
I/O operation fails because its invalid, reporting the error to the
guest is the only sensible
