#12068 closed defect (duplicate)
4.2.16 and Kernel 3.11.0
| 回報者: | mastacontrola | 負責人: | |
|---|---|---|---|
| 元件: | network | 版本: | VirtualBox 4.2.16 |
| 關鍵字: | 副本: | ||
| Guest type: | all | Host type: | other |
描述
Hello all, I sure wish I could give you more information, but if I do, I no longer have a Virtualized system.
I upgraded my systems to Kernel 3.11 and restarted. I performed /etc/init.d/vboxdrv setup as none of my systems would start automatically. I usually do this any time I upgrade my kernels as well just to ensure I have good module support throughout. However, when I upgraded to linux-3.11, none of my Virtual Boxes would start. I Booted to linux-3.10.10 and all worked perfectly fine.
It seems that with linux-3.11, the systems interfaces are not recognized, though the system still see's them as normal.
From my VBox.log for one of my VM's this is what was causing the failure. 00:00:00.408464 Chipset cannot do MSI: VERR_NOT_IMPLEMENTED 00:00:00.418100 VMSetError: /home/vbox/vbox-4.2.16/src/VBox/Devices/Network/DrvIntNet.cpp(1718) int drvR3IntNetConstruct(PDMDRVINS*, CFGMNODE*, uint32_t); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:00.418194 VMSetError: /home/vbox/vbox-4.2.16/src/VBox/Devices/Network/DevE1000.cpp(7680) int e1kConstruct(PDMDEVINS*, int, CFGMNODE*); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:00.424019 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found. 00:00:00.434457 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-br0' (VERR_INTNET_FLT_IF_NOT_FOUND). 00:00:00.434475 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false 00:00:00.445971 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=NS_ERROR_FAILURE (0X80004005))
I tried vboxmanage modifyvm <vmname> --nic1 bridged --bridgeadapter br<0-6> and nothing would work. I verified my system did have the adapters available and it did. I then rebooted to 3.10.10 and reran /etc/init.d/vboxdrv setup and all VMS started automatically and perfectly fine.
Just thought you should be aware.
Thank you,
Duplicate of #12001.