From: Avi Kivity <avi@redhat.com>
To: neal.p.murphy@alum.wpi.edu
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: kvm hangs with 1GB or more memory assigned
Date: Wed, 20 Apr 2011 11:01:25 +0300 [thread overview]
Message-ID: <4DAE92D5.5060706@redhat.com> (raw)
In-Reply-To: <201104150028.03397.neal.p.murphy@alum.wpi.edu>
(re-adding list)
On 04/15/2011 07:28 AM, Neal Murphy wrote:
> On Wednesday 06 April 2011 03:35:27 you wrote:
> > On 04/06/2011 06:22 AM, Neal Murphy wrote:
> > > ENVIRONS:
> > > I'm running
> > >
> > > - Debian Squeeze.
> > > - QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5)
> > > - 2.6.32-5-686-bigmem #1 SMP Tue Mar 8 22:14:55 UTC 2011 i686
> > > GNU/Linux - Quad Phenom II 965, 8GB RAM
> > >
> > > I'm booting generic 2.6.35.11 through syslinux. The command is generated
> > > via a script I wrote. It works fine until I assign more than 1005M RAM
> > > to the VM; it's been working fine (at less than 1GB RAM) for many
> > > months. The system I am booting boots and runs fine on bare metal.
> > >
> > > I got the same results when I DLed and installed ver. 0.14.
>
> > Looks like a guest BIOS issue.
> >
> > Please try qemu-0.14. Also try -cpu qemu64 instead of phenom.
> >
> > If those fail, we can attach with gdb and try to look at what's going
> > on, but let's try the simple tests first.
>
> BTW, is there a preferred 'set' of options to feed ./configure?
No.
> I used
> './configure --prefix=/opt/kvm --enable-kvm' to build.
>
> Finally got my system (Smoothwall/Roadster) stabilized and out the door, so I
> have time to dedicate to this.
>
> OK. I've built 0.14 (installed to /opt/kvm and I deleted Squeeze's older
> package) and am using Squeeze's kvm_amd module. I tried without -cpu and -smp;
> I tried -cpu qemu64. I eliminated the -vga and -serial options to no avail. It
> still chokes on 1005MB RAM.
>
Works for me. Please use -monitor stdio and issue the commands
(qemu) info registers
(qemu) x/50i $eip - 30
> So what's the next ste... ... Wait, just thought of something to try: 'rmmod
> kvm-amd'. ... Oho! Without the accelerator, it runs with at least 1588M RAM,
> but can't allocate 2000M RAM (this may be expected on a 32-bit OS with PAE).
2G limit is expected on i386.
> Does this help? Is it time to submit a debian bug?
If debian fixes the bug, that would be great.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-04-20 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 3:22 kvm hangs with 1GB or more memory assigned Neal Murphy
2011-04-06 7:35 ` Avi Kivity
[not found] ` <201104150028.03397.neal.p.murphy@alum.wpi.edu>
2011-04-20 8:01 ` Avi Kivity [this message]
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=4DAE92D5.5060706@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=neal.p.murphy@alum.wpi.edu \
/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