From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Xen 4.4 development update: Is PVH a blocker?
Date: Tue, 17 Dec 2013 09:35:45 -0500
Message-ID: <20131217143545.GA4433@phenom.dumpdata.com>
References: <CAFLBxZZYMU3wJey4tZN9pVrfeTeujLQLBRbiGe-WFevpO2UhvQ@mail.gmail.com>
	<20131213193926.GE28412@phenom.dumpdata.com>
	<10210502196.20131213215514@eikelenboom.it>
	<20131216150906.GA14038@phenom.dumpdata.com>
	<16110253000.20131216182420@eikelenboom.it>
	<20131216174635.GA23286@phenom.dumpdata.com>
	<1195791410.20131216185916@eikelenboom.it>
	<20131216193403.GB25548@phenom.dumpdata.com>
	<402966494.20131216204644@eikelenboom.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <402966494.20131216204644@eikelenboom.it>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

> > rm -Rf tools/firmware/seabios-dir* tools/qemu-xen*
> > rebuilt and had the same issue :-(
> 
> Hmm so taking it forward doesn't cut it .. going back is probably going to be searching for a needle in a haystack.
> Finding many incomptabilities. I tried it with vga passthrough to find back a working config i knew i once had .. but to no avail :-(

Yikes. Do you get a similar error message in QEMU?
> 
> It's at least a good testdevice :-) seems to stretch the limits ...

I also tried it with my GPU:
05:00.0 VGA compatible controller: NVIDIA Corporation GF104GLM [Quadro 4000M] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: Gigabyte Technology Co., Ltd Device 34fc
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at fc000000 (32-bit, non-prefetchable) [disabled] [size=32M]
        Region 1: Memory at d0000000 (64-bit, prefetchable) [disabled] [size=128M]
        Region 3: Memory at d8000000 (64-bit, prefetchable) [disabled] [size=64M]
        Region 5: I/O ports at c000 [disabled] [size=128]
        Expansion ROM at fe000000 [disabled] [size=512K]
        Capabilities: <access denied>
        Kernel driver in use: pciback


But my GPU's BAR (fc000000) is right smack in where the HVMloader stashes the ACPI tables -
so I figured I would try with something less complex, like a NIC.
  
> 
> >> 
> 
>