From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: BUG_ON in mmu.c:436
Date: Mon, 24 Sep 2007 09:54:46 +0200 [thread overview]
Message-ID: <46F76D46.7040502@qumranet.com> (raw)
In-Reply-To: <20070923215548.GP7519-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Ryan Harper wrote:
> I've run into a nasty bug while trying to install a Linux guest using
> VMware Server inside a kvm guest (full dmesg attached and recreate
> instructions below bug).
>
>
Can you reproduce this with AUDIT turned on (top of mmu.c)? AUDIT is
very slow, so it's recommended to reduce guest memory as much as possible.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-24 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 21:55 BUG_ON in mmu.c:436 Ryan Harper
[not found] ` <20070923215548.GP7519-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-24 2:39 ` Scott Serr
2007-09-24 7:54 ` Avi Kivity [this message]
[not found] ` <46F76D46.7040502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-24 21:26 ` Ryan Harper
[not found] ` <20070924212649.GS7519-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-24 21:37 ` Anthony Liguori
[not found] ` <46F82E36.7000402-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-09-28 18:19 ` Ryan Harper
[not found] ` <20070928181915.GH7519-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-30 7:32 ` Avi Kivity
2007-09-25 8:00 ` Avi Kivity
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=46F76D46.7040502@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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