qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] "Issue" With non-blocking IO patch
Date: Mon, 17 Oct 2005 15:52:59 +0400	[thread overview]
Message-ID: <4353909B.3040109@wasp.net.au> (raw)

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

             reply	other threads:[~2005-10-17 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 11:52 Brad Campbell [this message]
2005-10-17 12:31 ` [Qemu-devel] "Issue" With non-blocking IO patch John Coiner
2005-10-17 12:52   ` Brad Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4353909B.3040109@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).