virtualbox.org

I had no problem compiling and installing a loadable module on a physical computer and a VMware VM running CentOS 5.0 and 5.2. I was able to compile the module on a VirtualBox (1.6.4 and 2.0.0) VM with the same OS, compiler and patch level. However, insmod resulted kernel panic. Any suggestion? Many thanks!

Call Trace:
[<c043e459>] sys_init_module+0x18b5/0x1a60
[<c046d5d3>] __kmalloc+0x0/0x72
[<c0471952>] –fput+0x13f/0x167
[<c0488486>] mntput_no_expire+0x11/0x6a
[<c0404eff>] syscall_call+0x7/0xb
[/img]

Do you observe this crash with both versions, VBox 1.6.4 and 2.0.0 or only with 2.0.0?

Frank Mehnert wrote:Do you observe this crash with both versions, VBox 1.6.4 and 2.0.0 or only with 2.0.0?

Please check the PM. Thanks.

After a first look it is possible that sysenter is the cause. We don't support sysenter/sysexit for VMs executed in raw mode but the module is assuming that this feature is present and used. You might want to try if loading this module fails as well if VT-x/AMD-V is enabled for your VM.

Frank Mehnert wrote:After a first look it is possible that sysenter is the cause. We don't support sysenter/sysexit for VMs executed in raw mode but the module is assuming that this feature is present and used. You might want to try if loading this module fails as well if VT-x/AMD-V is enabled for your VM.

I just enabled VT-x on a computer with Xeon 5140 CPU and the module was loaded without any problem. Is it possible sysenter/sysexit will be supported in the future?

Many thanks!

I doubt that sysenter/sysexit will be supported without VT-x/AMD-V for technical reasons.