From: Alexander Graf <agraf@suse.de>
To: kvm@vger.kernel.org
Cc: Avi Kivity <avi@qumranet.com>, mtosatti@redhat.com
Subject: commit 641fb03992b20aa640781a245f6b7136f0b845e4 broke MMU
Date: Wed, 15 Oct 2008 16:07:24 +0200 [thread overview]
Message-ID: <48F5F91C.8060104@suse.de> (raw)
Hi,
while trying to run the current openSUSE on git KVM I found that the
installation doesn't even boot properly. I bisected the problem down to
commit 641fb03992b20aa640781a245f6b7136f0b845e4, as of which udev shows
strange errors.
I reproduced the incorrect behavior reliably on an AMD machine with
npt=0, but since the mmu code is generic I assume that everyone suffers
from this.
To reproduce the problem, do the following:
wget
http://download.opensuse.org/factory/repo/oss/boot/x86_64/loader/{linux,initrd}
qemu-system-x86_64 -m 512 /dev/null -kernel linux -initrd initrd
Since I'm not too much into mmu code, I hope someone else will take a
deeper look at this.
Alex
next reply other threads:[~2008-10-15 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 14:07 Alexander Graf [this message]
[not found] <48F5ECE4.5080804@suse.de>
2008-10-16 8:58 ` commit 641fb03992b20aa640781a245f6b7136f0b845e4 broke MMU Avi Kivity
2008-10-16 10:51 ` Alexander Graf
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=48F5F91C.8060104@suse.de \
--to=agraf@suse.de \
--cc=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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