From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gordan Bobic Subject: Re: AMD GPU passthrough in Xen Date: Mon, 22 Sep 2014 16:05:41 +0100 Message-ID: <54203AC5.2050102@bobich.net> References: <1696208142.20140922143828@eikelenboom.it> <2d24af6e-f1ec-4407-8f62-1493f9b49891@email.android.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2d24af6e-f1ec-4407-8f62-1493f9b49891@email.android.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Peter Kay Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 09/22/2014 03:31 PM, Peter Kay wrote: > > > On 22 September 2014 13:38:28 BST, Sander Eikelenboom wrote: > >> Another interesting question/aspect would be qemu-traditional (with >> rombios) or >> "upstream" (with seabios) ? > Point, although I didn't think this was generally an option in 4.2? > > Certainly I've found upstream to be functional (using a Quadro), but a less stable domU overall Do you happen to know if the recent KVM/QEMU provides a feature to limit the amount of memory below 4GB to assign to the guest? Or provide a custom e820 map? To work around a hardware bug I have to somehow make sure that everything between 2.5GB and 4GB is reserved and untouchable. Gordan