All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KQEMU bus errors
Date: Sun, 13 Feb 2005 22:42:37 +1300	[thread overview]
Message-ID: <1108287757.7619.7.camel@localhost.localdomain> (raw)
In-Reply-To: <420EE242.2080908@wasp.net.au>

[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]

Hi,

    I'm not convinced that this is actually the case.  I have tested
this on several machines now with several guest OSes and get the same
result on all of them (which all previously worked).  With the snapshot
from 2005-02-09 all works correctly.  With CVS from 2005-02-11 onwards I
get the error ('Bus error' on host for WinXP guest and 'Protection
Fault' inside guest for Win98 guest).  I think that perhaps with smaller
guest RAM size you are simply hiding the bug.  On one machine at least I
have 756MB physical RAM and 3GB swap allocated and get the same problem.
Most of the references that I can find for a Linux 'Bus error' talk
about unaligned memory accesses.  I did a diff of the 2005-02-09 tree
and the 2005-02-11 tree and noted that most of the *changes* (rather
than additions and new things) were relating to the way that memory is
handled and marked inside qemu.  I think that there is a chance that one
of these has introduced the problem.

Regards,
D

On Sun, 2005-02-13 at 09:14 +0400, Brad Campbell wrote:

> Hetz Ben Hamo wrote:
> > Yes, found the reason...
> > 
> > Test with different ram size - you'll be surprised...
> > 
> I second this one.
> I found I had to make sure my tmpfs "partition" was larger than my requested ram size. Problem went 
> away.
> 
> Brad

-- 
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>

[-- Attachment #2: Type: text/html, Size: 2172 bytes --]

  reply	other threads:[~2005-02-13 10:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11  1:48 [Qemu-devel] KQEMU bus errors Darryl Dixon
2005-02-13  1:49 ` Julian Chesterfield
2005-02-13  2:17   ` Hetz Ben Hamo
2005-02-13  5:14     ` Brad Campbell
2005-02-13  9:42       ` Darryl Dixon [this message]
2005-02-13 11:13         ` Jonas Maebe
2005-02-13 14:10           ` Julian Seward
2005-02-13 14:51             ` Grzegorz Kulewski
2005-02-13 20:19               ` [Qemu-devel] Bus errors and /dev/shm -- was: " Darryl Dixon
2005-02-13 22:00                 ` Filip Navara
2005-02-13 12:24         ` [Qemu-devel] " Phil Krylov
2005-02-13  2:37   ` Darryl Dixon
2005-02-13  2:44   ` Grzegorz Kulewski
2005-02-21 22:24   ` [Qemu-devel] " bri3d
2005-02-21 23:04     ` Hetz Ben Hamo
2005-02-21 23:30       ` Darryl Dixon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1108287757.7619.7.camel@localhost.localdomain \
    --to=esrever_otua@pythonhacker.is-a-geek.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.