From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1ClTNQ-0006E1-Vi
	for qemu-devel@nongnu.org; Mon, 03 Jan 2005 09:40:09 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1ClTNP-0006DT-V8
	for qemu-devel@nongnu.org; Mon, 03 Jan 2005 09:40:08 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1ClTNP-0006DI-Rx
	for qemu-devel@nongnu.org; Mon, 03 Jan 2005 09:40:07 -0500
Received: from [212.238.201.82] (helo=xi.wantstofly.org)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1ClTC9-0002TJ-Sr
	for qemu-devel@nongnu.org; Mon, 03 Jan 2005 09:28:30 -0500
Date: Mon, 3 Jan 2005 15:28:29 +0100
From: Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [Qemu-devel] Re: Re: Firefox crashes inside qemu
Message-ID: <20050103142829.GA30388@xi.wantstofly.org>
References: <cr90kt$h4n$1@sea.gmane.org>
	<20050102145606.GA18712@xi.wantstofly.org>
	<cr94c6$ojc$1@sea.gmane.org>
	<20050102155730.GB18712@xi.wantstofly.org>
	<cr98ce$14f$1@sea.gmane.org> <crarf3$jh0$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <crarf3$jh0$1@sea.gmane.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

On Mon, Jan 03, 2005 at 12:16:47PM +0500, Alexander E. Patrakov wrote:

> >>> >> Firefox will crash. I suppose that there is some bug in the CPU
> >>> >> emulation.
> >>> >> 
> >>> >> How can I help debugging this problem further?
> >>> > 
> >>> > Can you try that disk image on a 'real' machine and see if it crashes
> >>> > then also?
> >>> 
> >>> I instaled win2k from the same CD to a real computer. Firefox downloaded
> >>> from the same URL doesn't crash under the same condition.
> >> 
> >> There are many different factors in both scenarios besides that one of
> >> them uses qemu and the other one does not: disk size, video card, network
> >> card, etc.
> >> 
> >>> But how do I test a qemu image on a real machine?
> >> 
> >> I would just dd it to an old IDE disk, even though that might give issues
> >> with differing head/sector counts.
> >> 
> >> dd if=disk.img of=/dev/hdx bs=1024k
> >> 
> >> (Where /dev/hdx is the old IDE disk.)
> > 
> > I see. The problem is that I don't have any old IDE disk at hand. But I
> > will dd that into VMware tomorrow in order to see if the installation is
> > really bad. As for the geometry, the doc at
> > http://linux-ntfs.sourceforge.net/ntfs/files/boot.html is known sufficient
> > for fixing such issues.
> 
> After changing the IDE driver to "generic dual-channel" (in order to avoid
> "inaccessible boot device" blue screen) and dd'ing the disk image into
> VMware (using Knoppix and ssh to the host), Firefox doesn't crash. So the
> problem is indeed in qemu.

Does VMware use the same virtual ethernet and video card types as qemu
does?  It might still be that qemu triggers a bug in Windows' handling
of some kind of peripheral that doesn't show up when using VMware.

Do you have any Windows debuggers?  Can you hook Firefox up to a debugger
and see where exactly it crashes?


> I hope this information is useful.

Even though I probably won't be able to debug this myself, this is
definitely a useful datapoint.  Thanks!


cheers,
Lennert