Re: [Xen-devel] Xen 4.4 development update: Is PVH a blocker?

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Tuesday, December 17, 2013, 3:35:45 PM, you wrote:

>> > 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?

Nope my problem (at present) is with the rom bar, that is special cased around 
everywhere (hvmloader, seabios, qemu, guest kernel).
And it appears all fine, but in fact in the guest it isn't backed by the actual 
rom data (neither by a copy, neither by passing it through).

Already tried by letting hvmloader load it as a optionrom, but that didn't cut 
it.

When dumping the rom of the devices passed through in the guest,
i was seeing al kinds of romdata from the emulated devices at the address given 
to the passed through devive,
but not the romdata from the passedthrough device.

And that was when i stumbled upon the whole xen_platform_pci problem,
as i was trying to switch of as many emulated devices as possible (in the hope 
it was some interference between those.

After that tried KVM .. to see if it is in any way feasible and possible with 
my system (iommu + gfx card),
that resulted in almost instant succes .. so yes it should be possible ...

>> 
>> 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.
>   
>> 
>> >> 
>> 
>> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel