qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Morris <jmorris@beau.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] two repeatable kqemu-related crashes
Date: Mon, 16 Apr 2007 16:00:50 -0500	[thread overview]
Message-ID: <1176757250.3325.38.camel@mjolnir> (raw)
In-Reply-To: <20070413073110.DE0D21DBE8B@ravel.n2.net>

On Fri, 2007-04-13 at 02:31, Don Kitchen wrote:
> Hi all
> 
> I've found two repeatable (possibly related) ways to crash kqemu with 0.9.0
> and several earlier versions also I think. It's under linux 2.6.9 fully
> updated CentOS 4.4 (clone of RH enterprise linux 4.4)

I'm running in a similar setting without a problem.  Kqemu 1.3.0pre11 +
a locally cooked rpm of qemu 0.9.0 based an earlier dag package of
qemu.  I running WBEL 4 instead of CentOS 4, but I really doubt that is
where your problem is.  I'm running on x86_64 and have to admit I
haven't bothered going to the very latest kernel package, still running
kernel-2.6.9-34.EL.  The guest I have been playing with this past week
is Debian 4.0 i386.  Installed and have been running since with
-kernel-kqemu.

The only reliable way I have to nuke the machine is boot FC5 with
-kernel-kqemu and start OO.o.  Without -kernel-kqemu it only kills the
VM.  It is something with FC5 and GCJ, been reported on the list
before.  Btw, OO.o as supplied with Debian 4.0 starts up without a
lockup, will be throwing some documents at it later to see if it holds
up.

-- 
John M.      http://www.beau.org/~jmorris     This post is 100% M$Free!
Geekcode 3.1:GCS C+++ UL++++$ P++ L+++ W++ w--- Y++ b++ 5+++ R tv- e* r

      reply	other threads:[~2007-04-16 22:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13  7:31 [Qemu-devel] two repeatable kqemu-related crashes Don Kitchen
2007-04-16 21:00 ` John Morris [this message]

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=1176757250.3325.38.camel@mjolnir \
    --to=jmorris@beau.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).