[Pkg-virtualbox-devel] excessive syslogging

[Joseph Rawson]

I've been waiting for the 1.6.6 version to be built, and I finally got a 
chance to try it today.  Previously, I had been running a self-built 1.6.6 
package that I built from -r 340 in the subversion repository.

I really needed to use the 1.6.6 version as it fixes a VT bug that wouldn't 
let me run multiple VM's with VT enabled.  Apparently this problem only 
affected hosts with AMD processors.  Having VT enabled really improves the 
performance of the VM's dramatically.

I've noticed that certain machines seem to freeze, and the syslog gets filled 
very quickly.  I mentioned this in a previous post, but I didn't want to say 
any more about it, since I was running a self-built package.  Now I'm running 
the package from unstable, and the problem is (not surprisingly) there also.

I have an AMD Turion 64 bit dual core cpu, but all of my OS's are running i386 
(host and all guests).  The OS's (or iso's, rather) that display this 
behavior are the ubuntu-8.04.1-desktop-i386.iso image and some of the recent 
daily builds of the debian-testing-netinst.iso images.  I tried the daily 
build for 23Sept2008, and that one seems to be ok, but the problem exists in 
the 16Sept2008 version of the daily build.  I'm letting you know this in case 
you need something to test with, and don't feel like getting the larger 
ubuntu image.

AFAICT, this problem only appears when VT is enabled.  I really don't want to 
go back to disabling VT.  Now that I'm used to it, going back makes things 
seem like they're moving at a snail's pace.

Also, why is it that I have to disable VT for all machines, when I only need 
to disable it for one?  It seems that if each machine has an option for using 
VT, that each one should run according to that setting.  I think that if VT 
has to be enabled/disabled for all machines, then the configuation option 
should stay with the global preferences, and not be a per machine option.

If I were to file a bug report for this, should I file it with debian, or with 
virtualbox.org?

here is a snipped from /var/log/syslog:

Sep 23 16:31:07 bard kernel: [15242.263109] !!R0-Assertion Failed!!
Sep 23 16:31:07 bard kernel: [15242.263109] Expression: <NULL>
Sep 23 16:31:07 bard kernel: [15242.263109] 
Location  : /home/michael/technik/s\
ources/archive/pkg-virtualbox/build-area/virtualbox-ose-1.6.6-dfsg/src/VBox/VMM\
/VMMAll/PGMAllPool.cpp(2738) void pgmPoolTracDerefGCPhys(PGMPOOL*, 
PGMPOOLPAGE*\
, RTHCPHYS, RTGCPHYS)
Sep 23 16:31:07 bard kernel: [15242.263109]
Sep 23 16:31:07 bard kernel: [15242.263109] !!R0-Assertion Failed!!
Sep 23 16:31:07 bard kernel: [15242.263109] Expression: <NULL>
Sep 23 16:31:07 bard kernel: [15242.263109] 
Location  : /home/michael/technik/s\
ources/archive/pkg-virtualbox/build-area/virtualbox-ose-1.6.6-dfsg/src/VBox/VMM\
/VMMAll/PGMAllPool.cpp(2738) void pgmPoolTracDerefGCPhys(PGMPOOL*, 
PGMPOOLPAGE*\
, RTHCPHYS, RTGCPHYS)
Sep 23 16:31:07 bard kernel: [15242.263109]
Sep 23 16:31:07 bard kernel: [15242.263109] !!R0-Assertion Failed!!
Sep 23 16:31:07 bard kernel: [15242.263109] Expression: <NULL>
Sep 23 16:31:07 bard kernel: [15242.263109] 
Location  : /home/michael/technik/s\
ources/archive/pkg-virtualbox/build-area/virtualbox-ose-1.6.6-dfsg/src/VBox/VMM\
/VMMAll/PGMAllPool.cpp(2738) void pgmPoolTracDerefGCPhys(PGMPOOL*, 
PGMPOOLPAGE*\
, RTHCPHYS, RTGCPHYS)

I'm getting about 1900-2000 entries like this per second.

Hopefully, since the latest debian netinst image didn't give me any problems, 
I won't be having too many problems with this in the near future.  I don't 
really need to use the ubuntu iso, it's just something I play with from time 
to time.

-- 
Thanks:
Joseph Rawson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-virtualbox-devel/attachments/20080923/0e010a5a/attachment.pgp