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: [Qemu-devel] KQEMU bus errors
Date: Fri, 11 Feb 2005 14:48:42 +1300	[thread overview]
Message-ID: <1108086522.5629.11.camel@localhost.localdomain> (raw)

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

Hi Fabrice,

    WinXP SP2 guest generates random bus errors during the login process
with kqemu module:
[dixond@localhost machine]$ sudo /opt/src/machine/winxp_boot.sh
Connected to host network interface: tun0
QEMU 0.6.2 monitor - type 'help' for more information
(qemu) /opt/src/machine/winxp_boot.sh: line 2:  6633 Bus error
qemu -hda winxp_hda.img -boot c -enable-audio -nics 1 -m 368 -n qemu-
ifup -monitor stdio -localtime

     Let me know if there is anything I can do to help debug this.

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

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

             reply	other threads:[~2005-02-11  2:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11  1:48 Darryl Dixon [this message]
2005-02-13  1:49 ` [Qemu-devel] KQEMU bus errors Julian Chesterfield
2005-02-13  2:17   ` Hetz Ben Hamo
2005-02-13  5:14     ` Brad Campbell
2005-02-13  9:42       ` Darryl Dixon
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=1108086522.5629.11.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.