From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Guest memory backed by PCI BAR (x86) Date: Thu, 26 Mar 2015 15:02:43 +0100 Message-ID: <55141183.9000304@redhat.com> References: <1790936111.88330.1427298998015.JavaMail.zimbra@xes-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit To: Nate Case , kvm@vger.kernel.org Return-path: Received: from mail-wg0-f45.google.com ([74.125.82.45]:32959 "EHLO mail-wg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751928AbbCZOCt (ORCPT ); Thu, 26 Mar 2015 10:02:49 -0400 Received: by wgbcc7 with SMTP id cc7so64808656wgb.0 for ; Thu, 26 Mar 2015 07:02:47 -0700 (PDT) In-Reply-To: <1790936111.88330.1427298998015.JavaMail.zimbra@xes-inc.com> Sender: kvm-owner@vger.kernel.org List-ID: On 25/03/2015 16:56, Nate Case wrote: > I was hoping I could then use a PCI sysfs resource file instead of a > tmpfs file (i.e., /sys/bus/pci/devices/dddd:bb:ss.f/resourceN) to > achieve the desired effect. But I haven't been able to get Linux or > memtest86+ to boot with this arrangement. It only boots when KVM > acceleration is disabled. > > When KVM acceleration is enabled, SeaBIOS seems to function fine > running out of PCI memory space, but booting the OS resets. > Specifically, the following happens (I'll stick with the memtest86+ > 5.01 test case for simplicity): Hi, please include a trace file of the failure, obtained using "trace-cmd record -e kvm/* -e kvmmmu/*". Thanks, Paolo