Change History

Summary
changed from R0-Assertion Failed in pgmPoolGetPage to PGMPOOLKIND_FREE Assertion

The interesting thing is that your host processor is quite fast but the log file contains a lot of complaints that ATA commands took a long time to complain. Though this shouldn't be related to the PGMPOOLKIND_FREE assertion...

Yes, we had quite poor hard drives (5400 RPM) that even in RAID 5 of 4 of them were performing bad. The guests were also crashing from time to time complaining about IO errors, FS was remounted r/o ... all kind of crap. We have assumed they were caused by the poor IO so we've replaced the disks recently. If we see the errors again we'll come back with bug reports.

I have added a log file for a similar occurence on a Mac Pro. It happened on the first day of installing VBox, though. Could disabling Nested Paging and/or Hardware Virtualization help to circumvent the problem for now?

Experienced PGMPOOLKIND_FREE Assertions for two Solaris 10u6 guests running concurrently (VBox-vm1.log & VBox-vm2.log attached) running on the same Ubuntu Linux host with Virtualbox 2.2.
One of the Solaris 10u6 guests was performing a code build at the time (VBox-vm2.log) so there would have been a fair amount of I/O and CPU load.

This is the second occurrence of PGMPOOLKIND_FREE causing the two VM's to crash in two days.

EXT3 used as the host file-system.

The two remaining guest VM's (one Solaris 10u6 and the other a Redhat 4 EL guest) are still running fine.