From: Christian Hesse <mail@earthworm.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Con Kolivas <kernel@kolivas.org>,
Nick Piggin <npiggin@suse.de>, Mike Galbraith <efault@gmx.de>,
Arjan van de Ven <arjan@infradead.org>,
Peter Williams <pwil3058@bigpond.net.au>,
Thomas Gleixner <tglx@linutronix.de>,
caglar@pardus.org.tr, Willy Tarreau <w@1wt.eu>,
Gene Heskett <gene.heskett@gmail.com>,
kvm-devel@lists.sourceforge.net, Avi Kivity <avi@qumranet.com>
Subject: crash with CFS v4 and qemu/kvm (was: [patch] CFS scheduler, v4)
Date: Mon, 23 Apr 2007 11:28:18 +0200 [thread overview]
Message-ID: <200704231128.23594.mail@earthworm.de> (raw)
In-Reply-To: <20070420140457.GA14017@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
On Friday 20 April 2007, Ingo Molnar wrote:
> i'm pleased to announce release -v4 of the CFS patchset.
Hi Ingo, hi Avi, hi all,
I'm trying to use kvm-20 with cfs v4 and get a crash:
eworm@revo:~$ /usr/local/kvm/bin/qemu -snapshot /mnt/data/virtual/qemu/winxp.img
kvm_run: failed entry, reason 7
kvm_run returned -8
It works (though it is a bit slow) if I start qemu with strace, so for me it
looks like a race condition?
I did not test any earlier versions of cfs and kvm in combination - I can't
say if it happens there as well.
--
Regards,
Chris
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2007-04-23 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070420140457.GA14017@elte.hu>
2007-04-23 9:28 ` Christian Hesse [this message]
[not found] ` <200704231128.23594.mail-8oMOrB1mGocUSW6y5lq3GQ@public.gmane.org>
2007-04-23 10:18 ` crash with CFS v4 and qemu/kvm (was: [patch] CFS scheduler, v4) Ingo Molnar
[not found] ` <20070423101839.GA19599-X9Un+BFzKDI@public.gmane.org>
2007-04-24 10:54 ` Christian Hesse
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=200704231128.23594.mail@earthworm.de \
--to=mail@earthworm.de \
--cc=arjan@infradead.org \
--cc=avi@qumranet.com \
--cc=caglar@pardus.org.tr \
--cc=efault@gmx.de \
--cc=gene.heskett@gmail.com \
--cc=kernel@kolivas.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=pwil3058@bigpond.net.au \
--cc=tglx@linutronix.de \
--cc=w@1wt.eu \
/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