From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ERTXS-0004f7-BD for qemu-devel@nongnu.org; Mon, 17 Oct 2005 07:52:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ERTXM-0004el-Th for qemu-devel@nongnu.org; Mon, 17 Oct 2005 07:52:20 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ERTXM-0004eh-75 for qemu-devel@nongnu.org; Mon, 17 Oct 2005 07:52:16 -0400 Received: from [203.190.192.17] (helo=wasp.net.au) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ERTXM-0000sd-5E for qemu-devel@nongnu.org; Mon, 17 Oct 2005 07:52:16 -0400 Message-ID: <4353909B.3040109@wasp.net.au> Date: Mon, 17 Oct 2005 15:52:59 +0400 From: Brad Campbell MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] "Issue" With non-blocking IO patch Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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