Stefan Hajnoczi writes:
> Thanks for trying it out.
>
> Regarding the guest kernel errors, they may be timeouts. The guest
> may consider the IDE controller buggy/dead due to how long requests
> take to complete under severe throttling. There's not much that can
> be done about that, I think.
On Thu, Mar 29, 2012 at 12:30 PM, Chris Webb wrote:
> Stefan Hajnoczi writes:
>
>> Chris and Richard: Please test this to confirm that it fixes the hang you
>> reported.
>
> We've been testing this (v1 against qemu-kvm 1.0) today, and it's looking
> very good. Thanks!
>
> The lock-ups during boot
Stefan Hajnoczi writes:
> Chris and Richard: Please test this to confirm that it fixes the hang you
> reported.
We've been testing this (v1 against qemu-kvm 1.0) today, and it's looking
very good. Thanks!
The lock-ups during boot no longer happen, and if you severely throttle
(1MB/s, 100 req/s)
On Wed, Mar 28, 2012 at 11:43 PM, Stefan Hajnoczi
wrote:
> IDE PIO mode is currently implemented using synchronous I/O functions.
> There's
> no need to do this because the IDE interface is actually designed with polling
> and interrupts in mind - we can do asynchronous I/O and let the guest kno
Il 28/03/2012 17:43, Stefan Hajnoczi ha scritto:
> IDE PIO mode is currently implemented using synchronous I/O functions.
> There's
> no need to do this because the IDE interface is actually designed with polling
> and interrupts in mind - we can do asynchronous I/O and let the guest know
> when
Stefan Hajnoczi writes:
> The second aim of this conversion is to avoid calling bdrv_read()/bdrv_write()
> since they do not work with I/O throttling. This means guests should now boot
> IDE drives successfully when I/O throttling is enabled.
[...]
> Chris and Richard: Please test this to confir
IDE PIO mode is currently implemented using synchronous I/O functions. There's
no need to do this because the IDE interface is actually designed with polling
and interrupts in mind - we can do asynchronous I/O and let the guest know when
the operation has completed. The benefit of asynchronous I/
