VirtualBox

Opened 14 years ago

Closed 13 years ago

#6896 closed defect (fixed)

Kernel panic, panic() called by vboxguest in VBoxGuestCommonIOCtl()

Reported by: nicmp Owned by:
Component: guest additions Version: VirtualBox 3.2.6
Keywords: Cc:
Guest type: Linux Host type: Linux

Description

Hello,

One of my Linux guests has paniced yesterday, the attached kernel log excerpt shows the reason.

Would be happy to supply any information which may be needed.

Attachments (5)

panic.txt (983 bytes ) - added by nicmp 14 years ago.
VBox.log (58.2 KB ) - added by nicmp 14 years ago.
panicnew.txt (1.7 KB ) - added by nicmp 14 years ago.
vboxsf.ko (51.3 KB ) - added by nicmp 14 years ago.
panic-3.2.6.txt (2.6 KB ) - added by nicmp 14 years ago.

Download all attachments as: .zip

Change History (23)

by nicmp, 14 years ago

Attachment: panic.txt added

by nicmp, 14 years ago

Attachment: VBox.log added

in reply to:  description comment:1 by nicmp, 14 years ago

I should add that I still did not upgrade to 3.2.2 to reduce downtime, but can do so if necessary.

Replying to nicmp:

Hello,

One of my Linux guests has paniced yesterday, the attached kernel log excerpt shows the reason.

Would be happy to supply any information which may be needed.

comment:2 by Frank Mehnert, 14 years ago

Did you do anything special with that guest, for instance some heavy shared folder usage or something like that?

comment:3 by nicmp, 14 years ago

I am using the shared folder for log writes, instead of writing them inside the VM image.

I wouldn't call it heavy usage, but its definitely active.

comment:4 by Frank Mehnert, 14 years ago

Version: VirtualBox 3.2.0VirtualBox 3.2.4

comment:5 by Frank Mehnert, 14 years ago

#7062 marked as duplicate though #7062 contains a better stack trace.

comment:6 by Frank Mehnert, 14 years ago

So far I have no idea why this happens. For some reason the guest kernel stack is scrambled. As there were no related changes in VBox 3.2.6 I assume that you will experience such guest Oopses with 3.2.6 too. Do you have any special guest kernel configuration?

comment:7 by nicmp, 14 years ago

Nothing I would consider special at all. I have the /var/log writing to a shared folder, that's it.

comment:8 by nicmp, 14 years ago

This problem could also be related to the fact that our VMs only grow and grow in resident memory size, way beyond the specified amount of RAM per VM.

We have a VM which is set to 2GB physical, yet the process uses 3.6GB, at which point we must restart it to prevent the machine from swapping.

All our VMs use shared folders in exactly the same way, logs written to /var/log get written to the shared folder.

by nicmp, 14 years ago

Attachment: panicnew.txt added

comment:9 by nicmp, 14 years ago

I just attached a more complete trace of a panic which happened just 20 minutes ago.

comment:10 by Frank Mehnert, 14 years ago

VBox 3.2.6 fixed several potential memory leaks so updating might fix the leak issue. But I doubt think that the memory leak is related to your guest kernel oops.

comment:11 by Frank Mehnert, 14 years ago

Version: VirtualBox 3.2.4VirtualBox 3.2.6

comment:12 by Frank Mehnert, 14 years ago

Just to be sure: You updated your guest additions to 3.2.6, right?

comment:13 by nicmp, 14 years ago

Yes, everything is 3.2.6.

comment:14 by Frank Mehnert, 14 years ago

Please could you attach the compiled vboxsf.ko module from your guest to this ticket? Thank you.

by nicmp, 14 years ago

Attachment: vboxsf.ko added

comment:15 by nicmp, 14 years ago

Attached, but please note that this is the new one, 3.2.6, compiled just today so it's not likely to match any traces I attached so far.

comment:16 by nicmp, 14 years ago

Attaching a new trace, which should fit the compiled module I attached a few days ago.

by nicmp, 14 years ago

Attachment: panic-3.2.6.txt added

comment:17 by nicmp, 14 years ago

It'd be probably good to add that my VM panics this way 2-3 times a week.

comment:18 by Frank Mehnert, 13 years ago

Resolution: fixed
Status: newclosed

Please reopen if still relevant with VBox 4.0.4.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use