From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ESS62-0002fr-O0 for qemu-devel@nongnu.org; Thu, 20 Oct 2005 00:32:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ESS60-0002dm-W5 for qemu-devel@nongnu.org; Thu, 20 Oct 2005 00:32:06 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ESS60-0002dc-SN for qemu-devel@nongnu.org; Thu, 20 Oct 2005 00:32:04 -0400 Received: from [64.233.162.199] (helo=zproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ESS60-0003JE-VV for qemu-devel@nongnu.org; Thu, 20 Oct 2005 00:32:05 -0400 Received: by zproxy.gmail.com with SMTP id s18so186088nze for ; Wed, 19 Oct 2005 21:32:04 -0700 (PDT) Message-ID: <79bf98480510192132j52eab59dxa2dca9f80adfc25a@mail.gmail.com> Date: Wed, 19 Oct 2005 21:32:04 -0700 From: Mike Swanson In-Reply-To: <79bf98480510192032o39a3180aq785c48f9ce02d11b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <79bf98480510192032o39a3180aq785c48f9ce02d11b@mail.gmail.com> Subject: [Qemu-devel] Re: NetBSD/i386 2.0.2 does not install with KQEMU 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 Yeah, I've got NetBSD installed now, and the hard disk image isn't bootable either unless KQEMU is deactivated. On 10/19/05, Mike Swanson wrote: > NetBSD 2.0.2 does not install with KQEMU loaded. I have not tested > earlier or later (dev) builds. > > I simply invoke QEMU with this command: > qemu -hda nbsd -cdrom i386cd.iso -boot d > > And NetBSD stops doing anything at the message "warning: no > /dev/console". However, the problem does not ocurr when I start > installation with -no-kqemu. > > I'm still installing NetBSD, so I can't say yet weather the hard disk > image will work with KQEMU, but I'm reporting this so far. -- Mike