public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: Can't boot guest with more than 3585MB when using large pages
Date: Tue, 24 Mar 2009 16:57:46 -0500	[thread overview]
Message-ID: <20090324215746.GH27104@us.ibm.com> (raw)
In-Reply-To: <1237928806.6124.39.camel@bling>

* Alex Williamson <alex.williamson@hp.com> [2009-03-24 16:07]:
> 
> On a 2.6.29, x86_64 host/guest, what's special about specifying a guest
> size of -m 3586 when using -mem-path backed by hugetlbfs?  3585 works,
> 3586 hangs here:
> 
> ...
> PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000
> software IO TLB at phys 0x20000000 - 0x24000000
> Memory: 3504832k/4196352k available (2926k kernel code, 524740k absent, 166780k reserved, 1260k data, 496k init)
> 
> I can back -mem-path by tmpfs or disk and it works fine.  Also works
> with no -mem-path, but it would obviously be nice to benefit from large
> pages on big guests.  The system has plenty of huge pages to back the
> request, and booting with -mem-prealloc makes no difference.  Tested on
> latest git as of today.  Thanks,

I've seen this as well, haven't had a chance to dig into the issue yet
either.  Certainly can test patches if anyone has an idea of what's
wrong here.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

  reply	other threads:[~2009-03-24 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 21:06 Can't boot guest with more than 3585MB when using large pages Alex Williamson
2009-03-24 21:57 ` Ryan Harper [this message]
2009-03-25 16:10   ` Marcelo Tosatti
2009-03-25 16:26     ` Alex Williamson
2009-04-03 23:28   ` Marcelo Tosatti
2009-04-04 17:56     ` Alex Williamson
2009-04-05 11:53       ` 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=20090324215746.GH27104@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=alex.williamson@hp.com \
    --cc=kvm@vger.kernel.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