From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NB6sl-0000NO-EN for qemu-devel@nongnu.org; Thu, 19 Nov 2009 08:17:07 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NB6sg-0000Id-Hp for qemu-devel@nongnu.org; Thu, 19 Nov 2009 08:17:06 -0500 Received: from [199.232.76.173] (port=38672 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NB6sg-0000IO-8W for qemu-devel@nongnu.org; Thu, 19 Nov 2009 08:17:02 -0500 Received: from mail-fx0-f222.google.com ([209.85.220.222]:52976) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NB6sf-0002mB-H1 for qemu-devel@nongnu.org; Thu, 19 Nov 2009 08:17:01 -0500 Received: by fxm22 with SMTP id 22so2683498fxm.2 for ; Thu, 19 Nov 2009 05:16:59 -0800 (PST) MIME-Version: 1.0 Date: Thu, 19 Nov 2009 11:16:59 -0200 Message-ID: <69e11d1f0911190516y28cdb487scdf03f9346bf5220@mail.gmail.com> From: Gustavo Alves Content-Type: multipart/alternative; boundary=0015174784f0942b220478b92c17 Subject: [Qemu-devel] Interactive Unix 4 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --0015174784f0942b220478b92c17 Content-Type: text/plain; charset=ISO-8859-1 I'm trying to install Interactive Unix 4 with qemu 0.10.6, but there is some problems when accessing the IDE disk. Everything appears to hang when the system try to format the fs and all I can see on gdb is some interrupts being executed. The fdisk utility works correctly. As I never had experience before with qemu, how this problem can the debugged? Someone had previous experience with this issue? Anyone can give-me some directions? Thanks Gustavo --0015174784f0942b220478b92c17 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'm trying to install Interactive Unix 4 with qemu 0.10.6, but there is= some problems when accessing the IDE disk. Everything appears to hang when= the system try to format the fs and all I can see on gdb is some interrupt= s being executed. The fdisk utility works correctly.

As I never had experience before with qemu, how this problem can the de= bugged? Someone had previous experience with this issue? Anyone can give-me= some directions?

Thanks

Gustavo

--0015174784f0942b220478b92c17--