After one week of debugging, there might be a bug in vbox that causes Windows MmFlushSection() to behave weirdly. We have a Windows driver working very well on old versions of vbox, but not on v4. The problem was caused by MmFlushSection, which wrongly updates files that are opened for read. In other words, MmFlushSection() causes files to write even if they are opened for read, and thus get ACCESS denined error. It seems somehow the page dirty bit is not set correctly in some case, because MmFlushSection checks dirty pages. I first thought there might be some bugs in our driver's code, but strange thing is that it works fine before with old versions of vbox, so I post this message just in case something wrong with vbox code.
_______________________________________________ vbox-dev mailing list vbox-dev@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-dev
