[vbox-dev] PDM virtual PCI device bar size

José Massada jose.massada at gmail.com
Wed Apr 24 02:30:29 PDT 2013


Not sure if relevant but I got the following errors on the log (the machine
still loads) when using the ICH9 chipset:

00:00:11.500658 VMSetError:
/home/vbox/vbox-4.2.10/src/VBox/VMM/VMMR3/PGMPhys.cpp(4502) int
pgmPhysFreePage(VM*, GMMFREEPAGESREQ*, uint32_t*, PGMPAGE*, RTGCPHYS);
rc=VERR_PGM_PHYS_NOT_RAM
00:00:11.500676 VMSetError: GCPhys=0000000020001000 type=6
00:00:11.500723 AssertLogRel
/home/vbox/vbox-4.2.10/src/VBox/VMM/VMMR3/PGMPhys.cpp(911) int
pgmR3PhysFreePageRange(VM*, PGMRAMRANGE*, RTGCPHYS, RTGCPHYS, uint8_t):
RT_SUCCESS_NP(rc)
00:00:11.501156 VERR_PGM_PHYS_NOT_RAM (-1639) - Trying to free a page that
isn't RAM.
00:00:11.581464 AssertLogRel
/home/vbox/vbox-4.2.10/src/VBox/VMM/VMMR3/PGMPhys.cpp(2248) int
PGMR3PhysMMIORegister(VM*, RTGCPHYS, RTGCPHYS, int (*)(VM*, RTGCPHYS,
void*, void*, size_t, PGMACCESSTYPE, void*), void*, RTHCUINTPTR, RTR0PTR,
RTRCPTR, RTRCPTR, const char*): RT_SUCCESS_NP(rc)
00:00:11.581495 cbRamRange=2097280


And when using PIIX3, I only get this next one:

00:00:11.926143 AssertLogRel
/home/vbox/vbox-4.2.10/src/VBox/VMM/VMMR3/PGMPhys.cpp(2248) int
PGMR3PhysMMIORegister(VM*, RTGCPHYS, RTGCPHYS, int (*)(VM*, RTGCPHYS,
void*, void*, size_t, PGMACCESSTYPE, void*), void*, RTHCUINTPTR, RTR0PTR,
RTRCPTR, RTRCPTR, const char*): RT_SUCCESS_NP(rc)
00:00:11.926178 cbRamRange=2097280

Jose


On Wed, Apr 24, 2013 at 8:18 AM, José Massada <jose.massada at gmail.com>wrote:

> I tried both but lately I've been testing with ICH9. Same behaviour.
>
> Jose
>
> On 24/04/2013, at 08:08, Nikolay Igotti <igotti at gmail.com> wrote:
>
>  Which chipset you are using? ICH9 generally shall be better suited for
> your needs, due to recent
> PCI features support.
>
>   Nikolay
>
> 23.04.2013 18:25, José Massada пишет:
>
> Hi all,
>
>  I'm working on a PDM virtual PCI device module and I need to have a bar
> size of 512MB.
> This particular PCI device uses bar 0 and 1 for register blocks (64KB
> each) and bar 2 for memory (this one I need to be 512MB or even bigger).
>
>  Registering the memory bar using the MMIO2 functions fails when the size
> is bigger than 256MB (hard coded limit in the allocation function) so I
> tried registering using MMIO. It seems to work but my read and write
> callbacks never get called (bar 0 and 1 also use MMIO and their callbacks
> always get called). I tried decreasing the bar 2 size and the callbacks got
> called.
>
>  Is this even possible without modifying VBox source code? What am I
> missing?
>
>  Thanks,
> Jose
>
>
> _______________________________________________
> vbox-dev mailing listvbox-dev at virtualbox.orghttps://www.virtualbox.org/mailman/listinfo/vbox-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.virtualbox.org/pipermail/vbox-dev/attachments/20130424/e7290b75/attachment-0001.html 


More information about the vbox-dev mailing list