From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, nox@jelal.kn-bremen.de
Subject: Re: [Qemu-devel] QEMU refusing to die on FreeBSD host
Date: Sun, 06 Apr 2008 10:58:52 -0600 (MDT) [thread overview]
Message-ID: <20080406.105852.-135506270.imp@bsdimp.com> (raw)
In-Reply-To: <20080406163440.GA47504@saturn.kn-bremen.de>
In message: <20080406163440.GA47504@saturn.kn-bremen.de>
Juergen Lock <nox@jelal.kn-bremen.de> writes:
: On Sun, Apr 06, 2008 at 12:55:39AM -0400, Jake Myers wrote:
: > Hello,
: >
: > On FreeBSD 7-STABLE, qemu refuses to exit even after the window is closed.
: > It is stuck so badly that even kill -9 fails to stop it. I looked in top to
: > see what it was doing that would cause it to lock so badly:
: >
: > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
: > 34859 root 1 -8 20 433M 416M devdrn 9:49 0.00% qemu
: >
: > I believe the problem is that qemu for some reason refuses to stop trying
: > to use the kqemu device.
: >
: > I am running the latest qemu (0.9.1). I can provide a backtrace on request
: > (I'm really busy right now with other things, so I didn't have time to
: > attach one).
:
: Yeah this looks like its the same FreeBSD 7.x/SMP issue that I already
: got reports of (refcount problem, similar to what has already been fixed
: once, only this time it seems to be a race...)
:
: If it is, you should be able to work around it by using an uniprocessor
: host kernel until a fix is known.
Well, reboot also works, since qemu that gets stuck will slowly be
paged out to the swap partition... it isn't a huge deal from a
practical perspective... Of course, this is just until the bug is
fixed...
Warner
next prev parent reply other threads:[~2008-04-06 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 4:55 [Qemu-devel] QEMU refusing to die on FreeBSD host Jake Myers
2008-04-06 16:34 ` Juergen Lock
2008-04-06 16:58 ` M. Warner Losh [this message]
2008-04-07 4:14 ` Jake Myers
2008-04-07 19:14 ` Juergen Lock
2008-04-19 15:21 ` Juergen Lock
2008-05-27 3:22 ` Jake Myers
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=20080406.105852.-135506270.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=nox@jelal.kn-bremen.de \
--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.