OSX 10.9 Mavericks Bridged Network error
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: OSX 10.9 Mavericks Bridged Network error
Yes, as I said it might or might not work. Usually it does. It's not a bug in VBox as far as I know because there is a technical explanation on why this is happening.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 3
- Joined: 21. Jul 2011, 20:32
- Primary OS: Fedora other
- VBox Version: OSE Fedora
- Guest OSses: Windows 7, Debian, CrunchBang, Slitaz
Re: OSX 10.9 Mavericks Bridged Network error
I found the answer here:
viewtopic.php?f=8&t=56013&start=15#p272403
and
http://theengguy.blogspot.ca/2013/08/vi ... -os-x.html
Essentially, what I found was that all the kernel extensions are not loaded:
and that causes the bridged network to fail.
When we run the script, it starts all the kernel extensions and the bridged adapter to work!
However, my setup was a little different from the one proposed in the script and I had to modify the location of the extensions. Also the command line for loading the kernel extensions is a bit different. Here is my script. Hope it works for you!
viewtopic.php?f=8&t=56013&start=15#p272403
and
http://theengguy.blogspot.ca/2013/08/vi ... -os-x.html
Essentially, what I found was that all the kernel extensions are not loaded:
Code: Select all
> kextstat | grep virtualbox
137 0 0xffffff7f8261a000 0x45000 0x45000 org.virtualbox.kext.VBoxDrv (4.3.4) <7 5 4 3 1>
When we run the script, it starts all the kernel extensions and the bridged adapter to work!
Code: Select all
> kextstat | grep virtualbox
137 3 0xffffff7f8261a000 0x45000 0x45000 org.virtualbox.kext.VBoxDrv (4.3.4) <7 5 4 3 1>
141 0 0xffffff7f8265f000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (4.3.4) <137 7 5 4 3 1>
142 0 0xffffff7f82664000 0x8000 0x8000 org.virtualbox.kext.VBoxUSB (4.3.4) <137 41 36 7 5 4 3 1>
143 0 0xffffff7f8266c000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (4.3.4) <137 5 4 1>
Code: Select all
#!/bin/bash
unload() {
# sudo ifconfig bridge0 down
# sudo ifconfig bridge0 unplumb
kextstat | grep "org.virtualbox.kext.VBoxUSB" > /dev/null 2>&1 \
&& sudo kextunload -b org.virtualbox.kext.VBoxUSB
kextstat | grep "org.virtualbox.kext.VBoxNetFlt" > /dev/null 2>&1 \
&& sudo kextunload -b org.virtualbox.kext.VBoxNetFlt
kextstat | grep "org.virtualbox.kext.VBoxNetAdp" > /dev/null 2>&1 \
&& sudo kextunload -b org.virtualbox.kext.VBoxNetAdp
kextstat | grep "org.virtualbox.kext.VBoxDrv" > /dev/null 2>&1 && \
sudo kextunload -b org.virtualbox.kext.VBoxDrv
}
load() {
sudo kextload "/Library/Application Support/VirtualBox/VBoxDrv.kext"
sudo kextload "/Library/Application Support/VirtualBox/VBoxDrv.kext" "/Library/Application Support/VirtualBox/VBoxUSB.kext"
sudo kextload "/Library/Application Support/VirtualBox/VBoxDrv.kext" "/Library/Application Support/VirtualBox/VBoxNetFlt.kext"
sudo kextload "/Library/Application Support/VirtualBox/VBoxDrv.kext" "/Library/Application Support/VirtualBox/VBoxNetAdp.kext"
# sudo ifconfig bridge0 plumb
# sudo ifconfig bridge0 inet 192.168.20.1 netmask 255.255.255.0 broadcast 192.168.20.255 up
}
case "$1" in
unload|remove)
unload
;;
load)
load
;;
*|reload)
unload
load
;;
esac