From: Marcelo Tosatti <marcelo@kvack.org>
To: kvm-devel@lists.sourceforge.net,
Alexey Eremenko <alexey.eremenko@qumranet.com>
Subject: Re: [ kvm-Bugs-1900829 ] KVM crashes with AMD NPT
Date: Mon, 25 Feb 2008 20:10:57 -0300 [thread overview]
Message-ID: <20080225231057.GA22897@dmt> (raw)
In-Reply-To: <E1JTG9J-0004IS-Me@sc8-sf-web24.sourceforge.net>
On Sun, Feb 24, 2008 at 04:40:09AM -0800, SourceForge.net wrote:
> Bugs item #1900829, was opened at 2008-02-24 14:40
> Message generated for change (Tracker Item Submitted) made by Item Submitter
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1900829&group_id=180599
>
> Please note that this message will contain a full copy of the comment thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: None
> Group: None
> Status: Open
> Resolution: None
> Priority: 5
> Private: No
> Submitted By: Technologov (technologov)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: KVM crashes with AMD NPT
>
> Initial Comment:
> KVM-61 guest crashes, when NPT=on, and when VM is accessed via VNC.
>
> It is 100% reproducible.
>
> Loading kvm-amd module without NPT, works fine.
> like:
> # modprobe kvm-amd npt=0
>
> Host: AMD Barcelona, F7/x64, KVM-61.
>
> Guest: Debian 4/x86.
>
> The Command sent to Qemu/KVM: /usr/local/bin/qemu-system-x86_64 -hda /vm/debian4
> -test32.qcow2 -m 256 -monitor tcp:localhost:4517,server,nowait -cdrom /isos/linu
> x/debian-40r0-i386-DVD-1.iso -boot d -name Debian4 -vnc :10 &
>
> ======================================================
>
> *** glibc detected *** /usr/local/bin/qemu-system-x86_64: realloc(): invalid old
> size: 0x00002aaabbde1010 ***
> ======= Backtrace: =========
> /lib64/libc.so.6[0x3dd0271fbb]
> /lib64/libc.so.6(realloc+0x124)[0x3dd0273d94]
> /usr/local/bin/qemu-system-x86_64[0x471c02]
> /usr/local/bin/qemu-system-x86_64[0x47229b]
> /usr/local/bin/qemu-system-x86_64[0x471583]
> /usr/local/bin/qemu-system-x86_64[0x40de98]
> /usr/local/bin/qemu-system-x86_64[0x4fd81d]
> /usr/local/bin/qemu-system-x86_64[0x4fd859]
> /usr/local/bin/qemu-system-x86_64[0x4fe0a6]
> /usr/local/bin/qemu-system-x86_64[0x410e3d]
> /lib64/libc.so.6(__libc_start_main+0xf4)[0x3dd021daa4]
> /usr/local/bin/qemu-system-x86_64[0x406219]
> ======= Memory map: ========
> 00400000-0057f000 r-xp 00000000 fd:00 1952887 /usr/lo
> cal/bin/qemu-system-x86_64
> 0077e000-007b2000 rw-p 0017e000 fd:00 1952887 /usr/lo
> cal/bin/qemu-system-x86_64
> 007b2000-01a85000 rw-p 007b2000 00:00 0
> 01a85000-02a86000 rwxp 01a85000 00:00 0
> 02a86000-02e12000 rw-p 02a86000 00:00 0 [heap]
Alexey,
Running the test with MMU_DEBUG defined in arch/x86/kvm/mmu.c can
probably shed some light into the issue.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-25 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 12:40 [ kvm-Bugs-1900829 ] KVM crashes with AMD NPT SourceForge.net
2008-02-25 23:10 ` Marcelo Tosatti [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-27 12:03 SourceForge.net
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=20080225231057.GA22897@dmt \
--to=marcelo@kvack.org \
--cc=alexey.eremenko@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
/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.