From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FYOpL-0000YC-ND
	for qemu-devel@nongnu.org; Tue, 25 Apr 2006 10:47:43 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FYOpK-0000WH-50
	for qemu-devel@nongnu.org; Tue, 25 Apr 2006 10:47:43 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FYOpK-0000WA-1G
	for qemu-devel@nongnu.org; Tue, 25 Apr 2006 10:47:42 -0400
Received: from [64.233.184.238] (helo=wproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FYOrn-0002lj-MJ
	for qemu-devel@nongnu.org; Tue, 25 Apr 2006 10:50:15 -0400
Received: by wproxy.gmail.com with SMTP id 36so1280443wra
	for <qemu-devel@nongnu.org>; Tue, 25 Apr 2006 07:47:41 -0700 (PDT)
Message-ID: <46d6db660604250747l192ccd7die167926243e6b542@mail.gmail.com>
Date: Tue, 25 Apr 2006 16:47:40 +0200
From: "Christian MICHON" <christian.michon@gmail.com>
Subject: Re: [Qemu-devel] Custom floppy image not booting,
	hanging at ramdisk...
In-Reply-To: <444DAE6F.3000805@tusker.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <443DEBFA.7050109@tusker.org> <444DAE6F.3000805@tusker.org>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

just send your kernel .config for cross verification
:)

On 4/25/06, Damien Mascord <tusker@tusker.org> wrote:
> Hi again,
>
> Sorry to top post, just wanted to know if anyone has had similar experien=
ces to this?
>
> If not, can someone help me debug the issue (bug?) with qemu here?
>