Error Inserting Openafs Cannot Allocate Memory
Opened 8 years ago Last modified 8 years ago Error inserting vboxdrv: Cannot allocate memory Reported by: mondalaci Owned by: Priority: major Component: host support Version: VirtualBox 1.6.0 Keywords: Cc: Guest type: other Host type: Linux Description I've been told on the forum to report this issue as a bug, so I do so: As an Ubuntu user who has recently upgraded to 4G RAM, I had to compile a custom kernel with high memory support because Ubuntu doesn't ship such a kernel with restricted drivers which I happen to use. Next, I've installed virtualbox_1.6.0-30421_Ubuntu_gutsy_i386.deb successfully. root@whisper:~# /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel module * done. * Removing old VirtualBox kernel module * done. * Recompiling VirtualBox kernel module * done. * Starting VirtualBox kernel module * modprobe vboxdrv failed. Please use 'dmesg' to find out why root@whisper:~# dmesg [ 1608.644113] vboxdrv: Trying to deactivate the NMI watchdog permanently... [ 1608.644117] vboxdrv: Successfully done. [ 1608.644119] vboxdrv: Found 2 processor cores. [ 1608.644131] vboxdrv: fAsync=0 u64DiffCores=406. root@whisper:~# lsmod | grep vboxdrv root@whisper:~# modprobe vboxdrv FATAL: Error inserting vboxdrv (/lib/modules/2.6.24-whisper-2008-05-03/misc/vboxdrv.ko): Cannot allocate memory root@whisper:~# free total used free shared buffers cached Mem: 4139832 1190780 2949052 0 55336 735604 -/+ buffers/cache: 399840 3739992 Swap: 0 0 0 Considering the amount of free memory, it's impossible for vboxdrv to not to have enough memory. Attachments config (84.8 KB) - added by mondalaci 8 years ago. The .config file related to the kernel in question Change History Changed 8 years ago by mondalaci attachment config added The .config file related to the kernel in question comment:1 Changed 8 years ago by frank Host type changed from other to Linux comment:2 Changed 8 years ago by frank Component changed from other to host support comment:3 Changed 8 years ago by frank Status changed from new to closed Resoluti
fails because libafs can't be loaded Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Hello guys. I 've already created a Cell for testing purposes, but every time I try to create a new one, I can't because when I run: $ https://www.virtualbox.org/ticket/1485 modprobe libafs It fails with the error message: FATAL: Error inserting libafs (/lib/modules/2.6.24-16-generic/kernel/fs/libafs.ko): Cannot allocate memory Something that didn't happen the first time. When I run dmesg I get the following: allocation failed: out of vmalloc space - use vmalloc=
src:openafs. Reported by: "Loren A. Linden Levy"
in "Cannot allocate memory" From: Russ Allbery Date: Sun, 06 Jul 2008 20:14:35 -0700 Andrew Perrin <[emailprotected]> writes: > Package: openafs-modules-source > Version: 1.4.7.dfsg1-2 > Severity: grave > Justification: renders package unusable I think that's a little strong. I downgraded the bug. > adorno:/etc/openafs# /etc/init.d/openafs-client force-reload > Stopping AFS services:afsd: Shutting down all afs processes and afs state > openafs. > Starting AFS services:FATAL: Error inserting openafs > (/lib/modules/2.6.24/fs/openafs.ko): Cannot allocate memory > > Failed to load AFS kernel module, not starting AFS > adorno:/etc/openafs# modprobe openafs > FATAL: Error inserting openafs (/lib/modules/2.6.24/fs/openafs.ko): Cannot > allocate memory How many times have you unloaded and reloaded the module on that system since the last reboot? I can't duplicate this on any of my systems at the moment, but I have seen this after some period of time of testing various versions without a reboot and the AFS module does tend to leak at least some memory when it's unloaded. I suspect that eventually it fragments the kernel's internal memory allocator. (The Linux kernel interface keeps changing and it's very hard to keep up with the changes in areas like this.) I suspect the system will be fine after a reboot. Unloading and reloading the module *mostly* works but is not the best thing to do when it can be avoided. It's not something that I consider critical to support, although I'll report this upstream and hopefully someone will have a chance to take a look and figure out where we're leaking memory. If you have more useful debugging information (dmesg, for example), that will be helpful; I can provide upstream with the details of the memory leak that I see, but I can reload the module anyway. -- Russ Allbery ([emailprotected])