From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JGWSp-0007sE-Kj for qemu-devel@nongnu.org; Sun, 20 Jan 2008 04:27:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JGWSn-0007s1-Gr for qemu-devel@nongnu.org; Sun, 20 Jan 2008 04:27:38 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JGWSn-0007ry-ET for qemu-devel@nongnu.org; Sun, 20 Jan 2008 04:27:37 -0500 Received: from merlin.artenumerica.net ([80.68.90.14]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JGWSn-0002p6-1W for qemu-devel@nongnu.org; Sun, 20 Jan 2008 04:27:37 -0500 Received: from [10.10.1.21] (89-180-126-56.net.novis.pt [89.180.126.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by merlin.artenumerica.net (Postfix) with ESMTP id 47C13501CB for ; Sun, 20 Jan 2008 09:27:35 +0000 (GMT) Message-ID: <47931401.4040203@artenumerica.com> Date: Sun, 20 Jan 2008 09:27:29 +0000 From: J M Cerqueira Esteves MIME-Version: 1.0 References: <44E7032B.9060807@artenumerica.com> <44E70699.2070103@artenumerica.com> <46d6db660608230102g4d24430y700683c8e3f7aedb@mail.gmail.com> In-Reply-To: <46d6db660608230102g4d24430y700683c8e3f7aedb@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] DSC timeout with a CD as ide1 slave / Lost interrupts without -no-acpi 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 Returning to an old topic... Christian MICHON wrote: > On 8/19/06, J M Cerqueira Esteves wrote: >> So the "culprit" of the cdrom timeouts seems to be -hdd ... >> but why? > > I saw the same things few weeks ago. Since then, I do > not use hdd anymore (my qemu host is winXP). My previous issue on this was with QEMU 0.8.2 and kqemu 1.3.0pre9 (in fact the subject was misleading, since I really used -hda .. -hdb .. -hdd .. -cdrom .. -boot d). Now with QEMU 0.9.1 and kqemu 1.3.0pre11 (host: Debian Etch on a Pentium M 1400MHz) I got DSC timeout again when trying to use a cdrom as a slave of ide1 (CD image: Debian netinst CD for i386: debian-40r2-i386-netinst.iso), invoking qemu with vdeq qemu \ -kernel-kqemu -no-acpi \ -m 256 \ -net nic,vlan=0,model=rtl8139,macaddr=$MAC_ADDR_0 \ -net vde,vlan=0,sock=/var/run/vde2/tap-vde-1.ctl \ -drive file=/dev/sda,if=ide,index=2,media=disk \ -drive file=/tmp/debian-40r2-i386-netinst.iso,if=ide,index=3,media=cdrom \ -boot d But if I put the cdrom device as a slave of ide0, file=...,if=ide,index=1,media=cdrom I get no DSC timeouts. By the way, in the few tests I made until now in this Pentium M host (mostly with Debian guest systems) I had to use -no-acpi since otherwise the boot process gets stuck or at least very slow and the guest reports hdc: lost interrupt (or "hda:" or "hdb:" depending on what was the first existing IDE device in the specific guest). This happens also with a Debian virtual machine which was previously running in a P4 host with QEMU 0.8.2 and kqemu 1.3.0pre9 not requiring the -no-acpi option... I'll test a bit more, but apparently I also get *no* such 'lost interrupt' messages with 32-bit guests in a 64-bit host (AMD Athlon 64 3500+, also with Debian Etch and QEMU 0.9.1). Best regards J Esteves