On 10.03.2012 05:42, Brandon Gooch wrote:
It's my guess that not many people are running VirtualBox on a
VIMAGE-enabled kernel. However, for those of us who do (just me?),
the attached patch is required to prevent a panic when running
VirtualBox in such an environment. The patch belongs to the
emulators/virtualbox-ose-kmod port.
--- src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c.orig 2011-12-19
07:01:06.000000000 -0600
+++ src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c 2011-12-26
14:54:27.000000000 -0600
@@ -1189,6 +1189,7 @@
int vboxNetAdpInit(void)
{
unsigned i;
+ PVBOXNETADP pVboxnet0;
/*
* Init common members and call OS-specific init.
*/
@@ -1201,7 +1202,8 @@
vboxNetAdpOsInit(&g_aAdapters[i]);
}
- return VINF_SUCCESS;
+ /* Create vboxnet0 */
+ return vboxNetAdpCreate(&pVboxnet0, NULL);
}
/**
If there is a more appropriate fix, please help me find it,
otherwise,
it would be great to have this committed!
Sorry, that I haven't committed the patch until now. Do you agree that
this patch is licensed under MIT License so I can send it upstream?
Current VIMAGE support is only for vboxnetflt and you are touching
vboxnetadp so that is probably why nobody used it before. Have you
tested it with a non VIMAGE kernel?
--
Bernhard Froehlich
http://www.bluelife.at/
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "[email protected]"
