From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:34036) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QQPln-0000EL-4W for qemu-devel@nongnu.org; Sat, 28 May 2011 16:05:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QQPlm-0007Vx-6L for qemu-devel@nongnu.org; Sat, 28 May 2011 16:05:59 -0400 Received: from seketeli.net ([91.121.166.71]:52332 helo=ms.seketeli.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QQPlm-0007UO-2G for qemu-devel@nongnu.org; Sat, 28 May 2011 16:05:58 -0400 Date: Sat, 28 May 2011 22:05:33 +0200 From: Apelete Seketeli Message-ID: <20110528200532.GB2849@hermes> References: <20110526195900.GE2849@hermes> <20110527125557.GB30093@amit-x200.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110527125557.GB30093@amit-x200.redhat.com> Subject: Re: [Qemu-devel] Booting custom kernel in qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Amit Shah Cc: qemu-devel@nongnu.org On 27-May-11, Amit Shah wrote: > On (Thu) 26 May 2011 [21:59:01], Apelete Seketeli wrote: > > Hello, > > > > I'm trying to boot a custom linux kernel in qemu, and I plan to > > contribute the necessary work to make it work (this is the first step > > I'm taking to add OS support in qemu). I'm totally new to qemu, and I > > haven't found enough information to know how to start debugging the > > thing, so I thought of asking here. > > > > I wanted to launch the kernel in a terminal for practical purposes, so > > I tried: > > > > qemu -kernel bzImage -append console=ttyS0 > > Add -serial stdio to get those logs. Well, qemu -kernel bzImage -append console=ttyS0 -serial stdio does not give me any output, I guess it's because the thing get stuck early during the boot process. For the time being I'm using qemu -kernel bzImage -append console=ttyS0 -S -nographic in order to launch gdbserver in the monitor and attach a gdb in the host; I hope I'll be able to follow the boot process in the debugger and understand qemu inner workings. I have a question though: $ qemu -S -kernel arch/x86/boot/bzImage -append console=ttyS0 -nographic -serial stdio chardev: opening backend "stdio" failed qemu: could not open serial device 'stdio': No such file or directory Why do I get an error since stdio is (according to the manual) the standard device in non graphical mode ? -- Apelete