[vbox-dev] vbox bug causing Windows system cache problems?

Huihong Luo huisinro at yahoo.com
Thu Sep 29 02:19:29 GMT 2011


After last few days' buiding different OSE revisions, the bug exists between
 
r36100 - r36222 (Feb 28, 11 - Mar-09, 11)
 
if you have some wild guess on which code change may have caused that, let me know, to save some time.
 
Otherwise I will continue the brutal force way of narrowing down the code set that caused the bug.


--- On Tue, 9/27/11, Huihong Luo <huisinro at yahoo.com> wrote:


From: Huihong Luo <huisinro at yahoo.com>
Subject: Re: [vbox-dev] vbox bug causing Windows system cache problems?
To: vbox-dev at virtualbox.org
Date: Tuesday, September 27, 2011, 12:33 PM







After some backing tracing, this error occurs from vbox 4.1.0 r73009, and works well with 4.0.12 and before.
 
The windows cache manager displays an error message as attached from our driver.
 
We run exactly the same guest (same disk, same configure) using different versions of vbox downloaded from virtualbox.org.
 
so very likely there is a bug in vbox between 4.0.12 and 4.1.0

--- On Mon, 9/26/11, Huihong Luo <huisinro at yahoo.com> wrote:


From: Huihong Luo <huisinro at yahoo.com>
Subject: [vbox-dev] vbox bug causing Windows system cache problems?
To: vbox-dev at virtualbox.org
Date: Monday, September 26, 2011, 6:47 PM







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.
 
-----Inline Attachment Follows-----


_______________________________________________
vbox-dev mailing list
vbox-dev at virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-dev

-----Inline Attachment Follows-----


_______________________________________________
vbox-dev mailing list
vbox-dev at www.virtualbox.org
https://www.virtualbox.org/mailman/listinfo/vbox-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20110928/0d4d68e9/attachment.html>


More information about the vbox-dev mailing list