From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Kiselev,
Sergey" <sergey.kiselev-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Physical memory read: word crosses page boundary + host kernel oops
Date: Tue, 27 Mar 2007 16:45:12 +0200 [thread overview]
Message-ID: <46092DF8.1020202@qumranet.com> (raw)
In-Reply-To: <C07C4589BE74A34981C3C3525EE1F80101AB0E55-t8eeqVGEwHVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Kiselev, Sergey wrote:
> Hi,
>
> 1. When booting old Linux (RH7.1 based, 2.4.9, 32bit) guest on kvm-18,
> kvm userspace process crashes with 'Bus error' (last output on guest's
> screen is "Uncompressing Linux...").
> I did some debugging and found that kvm_readl() function calls
> ldl_phys() with address 0x9FFFD, so resulting double-word read crosses
> page boundary.
> After looking at qemu/exec.c it seems that ld*_phys and st*_phys
> functions not really care about crossing page boundary (even there is
> a comment sayng "warning: addr must be aligned"). So either
> qemu/exec.c should be updated to check such condition or (more logical
> place) qemu/qemu-kvm.c should take care of it.
>
> gdb backtrace:
> (gdb) bt
> #0 ldl_phys (addr=4093) at ../cpu-all.h:322
> #1 0x000000000047e08d in kvm_readl (opaque=0x9f, addr=159,
> data=0x2b63605a5030) at /srv/src/kvm-18/qemu/qemu-kvm.c:543
This is quite surprising. I agree that hacking kvm_readl() is the best fix.
> 2. After working-around the first issue, I have following problem: at
> some point of guest's Linux boot sequence (after running
> microcode_ctl, before running kudzu) following oops happens:
>
>
> Mar 27 12:10:39 itstl140 kernel: Code: 4c 8b 08 41 0f 18 09 48 8d 70
> d8 31 c0 e9 39 ff ff ff 48 63
> Mar 27 12:10:39 itstl140 kernel: RIP
> <ffffffff88366aa6>{:kvm:mmu_page_remove_parent_pte+225} RSP
> <ffff81014e34f938>
> Mar 27 12:10:39 itstl140 kernel: CR2: 000000030593a563
> I tried to disable both microcode_ctl and kudzu, in this case oops h
Strangely, I've seen this exact oops somewhere booting Windows XP in
safe mode. I haven't been able to reproduce it, though.
If this is reproducible, it may be debugged by turning on audit
(s/#undef AUDIT/#define AUDIT/ in mmu.c). Audit slows the guest down,
but is a little faster if you reduce the amount of guest memory. If
this is reproducible using a publicly available image, I may have a go
at it too.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-27 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 14:28 Physical memory read: word crosses page boundary + host kernel oops Kiselev, Sergey
[not found] ` <C07C4589BE74A34981C3C3525EE1F80101AB0E55-t8eeqVGEwHVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-03-27 14:45 ` Avi Kivity [this message]
[not found] ` <46092DF8.1020202-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-29 13:59 ` Kiselev, Sergey
[not found] ` <C07C4589BE74A34981C3C3525EE1F80101AE2908-t8eeqVGEwHVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-03-29 14:30 ` 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=46092DF8.1020202@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sergey.kiselev-ral2JQCrhuEAvxtiuMwx3w@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