Vitali, No problem, I've been doing that. Now narrowed down to r36210 - r36190, where r36210 has the bug, but r36190 works. I will go further. Most likely a bug in vmm. - huihong
--- On Thu, 9/29/11, Vitali Pelenjow <[email protected]> wrote: From: Vitali Pelenjow <[email protected]> Subject: Re: [vbox-dev] vbox bug causing Windows system cache problems? To: "Huihong Luo" <[email protected]> Cc: [email protected] Date: Thursday, September 29, 2011, 1:58 AM Hi Huihong, we would appreciate, if you could narrow down the changeset, which introduced the regression. This would be a great help. The changeset range is still too wide to have a guess. Thanks, Vitali. Huihong Luo wrote: > 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 /<[email protected]>/* wrote: > > > From: Huihong Luo <[email protected]> > Subject: Re: [vbox-dev] vbox bug causing Windows system cache > problems? > To: [email protected] > 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 /<[email protected]>/* wrote: > > > From: Huihong Luo <[email protected]> > Subject: [vbox-dev] vbox bug causing Windows system cache > problems? > To: [email protected] > 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 > [email protected] > ><http://us.mc1603.mail.yahoo.com/mc/[email protected]> > http://vbox.innotek.de/mailman/listinfo/vbox-dev > > > -----Inline Attachment Follows----- > > _______________________________________________ > vbox-dev mailing list > [email protected] > ><http://us.mc1603.mail.yahoo.com/mc/[email protected]> > https://www.virtualbox.org/mailman/listinfo/vbox-dev > > > > _______________________________________________ > vbox-dev mailing list > [email protected] > https://www.virtualbox.org/mailman/listinfo/vbox-dev
_______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
