[email protected] wrote: > Hi people > > I fixed my problem with my Linux guest network after upgrading from VBOX > 2.0.6 to 2.1.0 that stopped working. This message is more informative than > help required. > > My Linux Slackware guest network (Slackware host too) got damaged after > the upgrade (vbox and guest tools) eth0 did not appear anymore although > PCNET32 module/driver was loaded automatically. Checking the dmesg there > was a 'udev' kind of error that eth0 was renamed to eth1 and none > eth0/eth1 appear after completion boot process. > > There was not solution, reinstalled my Slackware guest to test if it was > that new version of VBOX that would not support it anymore, but after NEW > installation on a new virtual disk it worked, so my linux guest could not > be upgraded transparently like with past versions, had to reinstall. > > Any comment? anybody else experimented the same? could it be fixed or had > to reinstall guest?
Most likely deleting the "persistent network name" rule in /etc/udev/rules.d for the guest would have fixed the problem. That file controls the renaming of network interfaces. Perhaps 2.1.0 presents a different MAC address than did 2.0.6, or the driver is different. _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
