Virtualbox fails to start my VM with the new kernel 3.11.0. Apparently my bridged network interface is responsible for that. The error i see: Failed to open/create the internal network 'HostInterfaceNetworking-vboxnet0' (VERR_INTNET_FLT_IF_NOT_FOUND). Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND). Error Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392} Apperently this issue is resolved in 4.2.18: https://www.virtualbox.org/ticket/12001 Reproducible: Always
Created attachment 358132 [details, diff] Fix for 4.2.16 (from upstream SVN commit r47484)
Created attachment 358134 [details, diff] Fix for 4.2.16 (from upstream SVN commit r47484) - app-emulation/virtualbox-modules The only difference between this patch and the one for app-emulation/virtualbox itself is the pathname.
I have been using the patches as provided above since Aug 10; I had been using sys-kernel/git-sources until the official kernel 3.11.0 release. The app-emulation/virtualbox and app-emulation/virtualbox-modules ebuilds do not call epatch_user, so I had to do these patches in a local overlay. I am not affiliated with Oracle or the VirtualBox development team, but the patch is direct from upstream SVN.
A bump to 4.2.18 would be more appropriate than having the svn fixes around
(In reply to Markos Chandras from comment #4) > A bump to 4.2.18 would be more appropriate than having the svn fixes around Agreed; I guess I was offering those patches to save someone else the legwork if they needed a more immediate fix.
or better yet, bump version to 4.2.18 which is out already.
virtualbox-4.2.18 is in the tree.
