qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] "Issue" With non-blocking IO patch
@ 2005-10-17 11:52 Brad Campbell
  2005-10-17 12:31 ` John Coiner
  0 siblings, 1 reply; 3+ messages in thread
From: Brad Campbell @ 2005-10-17 11:52 UTC (permalink / raw)
  To: qemu-devel

G'day all,

Have discovered a minor hitch with the non-blocking IO patch.
when changing cdrom devices in the console it dies with

qemu: /home/brad/src/qemu/block.c:425: bdrv_cancel_nonblock_io: Assertion `nbst->state == 
STATE_READ_DONE' failed.
Aborted

I start qemu with qemu -hda test.img -cdrom test.iso
ctrl-alt 2 to change to virtual console
issue a "change cdrom /dev/sr0"
and the above happens. It does not seem to matter from<->to what I am changing the device.

I'm using a latest CVS version with the dma/nonblocking IO patch added only.

Other than that, it seems to tick along quite fine. I have been using it for days on end now and the 
other bonus the non-blocking patch seems to have is qemu when running windows seems to keep better 
time. Prior to this patch the clock drift was horrid. I had to install an ntp daemon in windows to 
keep it synced to the host, now it's nowhere near as bad.
It would also appear that the non-blocking patch helps the "stalling" problem, where long installs 
or tasks would appear to stall until I moved the mouse or sent a packet over the network. But this 
is hard to prove, just feels better.


Regards,
Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-10-17 12:52 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-17 11:52 [Qemu-devel] "Issue" With non-blocking IO patch Brad Campbell
2005-10-17 12:31 ` John Coiner
2005-10-17 12:52   ` Brad Campbell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).