Opened 11 years ago
Closed 9 years ago
#13296 closed defect (obsolete)
kernel panic in host when using kernel 3.16.x
Reported by: | Potomac | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.14 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description
Hello,
I use archlinux 64 bits in host,
for the guest OS I use archlinux i686 in virtualbox 4.3.14,
I notice if I run virtualbox that I have a kernel panic ( in host ) after a random time, I have this problem since the linux kernel ( for the host ) is updated to 3.16.x,
[code] kernel panic - not syncing: fatal exception in interrupt kernel offset : 0x0 from 0xffffffffff panic occured, switching back to text consolecode
the bug is easily reproducible :
- you must use linux kernel 3.16.x
- your host is archlinux 64 bits
- your guest archlinux i686 ( may work with 64 bits )
- load manually the virtuablox modules : modprobe vboxdrv && modprobe vboxnetadp && modprobe vboxnetflt
- start virtualbox 4.3.14 ( for example an archlinux guest )
- after a random time ( few minutes ) a kernel panic in host, or a freeze or a crash of virtualbox will occur
sometimes I don't have a kernel panic in host, just a freeze of virtualbox,
if I downgrade the linux kernel host to the 3.15.8 version then the bug is gone,
so something between virtualbox 4.3.14 and kernel 3.16.x is not compatible,
my CPU is an intel pentium dual core E6800, 4 Gb ram, I use 1 Gb for the guest, Vt-x option is enabled, my graphic card is an ati radeon HD4650 pcie, guest-addition modules have been installed in guest
Attachments (3)
Change History (7)
by , 11 years ago
by , 11 years ago
Attachment: | trace_kernel_vbox added |
---|
the journal.log of systemd about the kernel panic
comment:1 by , 11 years ago
it seems that the bug occurs only on "linux guest", not on windows guests,
my virtual machines are all only "linux OSes" ( archlinux, debian ) and all can trigger the bug,
on a french forum of archlinux someone told me the same thing, he has the bug with linux guests ( manjaro, kubuntu ),
the bug occurs especially if the virtual machine makes a lot of I/O ( read/write ) on partition
comment:2 by , 11 years ago
in the french forum of archlinux we found that moving the virtual machine to "/home" instead of using a fuse filesystem ( like an usb harddrive NTFS ) can solve the bug,
so it's seems that if the virtual machine is located in a partition mounted like a fuse filesystem then a freeze or a kernel panic can occur with kernel 3.16.x
comment:4 by , 9 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
vbox log