So udev uses persistence rules based on the MAC address of the network card. The OS cannot rely on them just being physically in the same spot each time - you may move them around for example, or some systems do not report their physical connections in the same sequence each boot. This is because when you have multiple nics, you want them to always have the same ethX name, so that your /etc/network/interfaces configuration targets the right nic each boot. One of the things it does by default is to try to maintain persistent names for network interface cards. This is the process that looks at hardware and sets that hardware up in /dev (or whatever else might need to be done). However, a temporary change as in the other answer by Zuul may be best for your purposes, as it will change the MAC without causing too many additional problems - however it will not survive a reboot.Ĭhanging it in VirtualBox will of course survive a reboot, but the issue you are facing is with udev. On that same line, it would be worth checking to make sure none of your private subnets are conflicting with each other either.You are very likely using the "correct" method to change the MAC address, if you are doing this in the advanced network settings in VirtualBox. I am not entirely certain what it looks like in OS X land, but under Windows VirtualBox adds a "VirtualBox Host-Only Network" that if you disable or generally muck with, it causes no end to weird problems. Or even better, add a different network adapter type (Maybe Intel instead of PCNet or vice versa).įourth, try statically assigning an IP address in your guest as to minimize the host networking issues.įifth, make sure the various VirtualBox adapters in your HOST are enabled and configured right. Third, as suggested, remove the existing network adapter in your VM configuration and re-add it. They usually live where the virtual machine XML configuration file lives. Second, have you looked in the log files VirtualBox generates? It will likely give you (or those trying to help) clues as to what is happening. 3.1.2 is out and 3.1.4 is in beta (at the time of this posting). There are probably several things working against you:įirst, upgrade your version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |