Virtual NIC device naming; VBox moved from Linux to Mac OS X

[AlphaGJohn]

Hi Folks,

I don't know if anything anyone's going to be able to offer suggestions on this (I'm kind of flying blind here because the MAC is at a remote site I do not have access to--but I could get someone there to check the config, if that's useful). But, here's the problem:

Created an Ubuntu guest VBox VM on a Linux Red Hat host.
Exported it.
Transferred the exported files to the end user.
He imported the guest VM onto his Mac.
We can't make the VBox guest's networking function.

The naming conventions for NIC devices are different in Linux than in Mac OS X (eth0 on Linux, en0 on Mac), but it just would not let us even drop and recreate the NICs so they'd work on the Mac. (This was all done via a web conference and I can't get back on the Mac easily so I'm just going by the notes I made at the time):

When we tried to fire it up after the initial import of the VBox VM, we get this error from the guest's dmesg log as it tries to start the networking:

"Malformed host interface networking name 'eth0'"

So, we shut it down and set all the NICs to inactive. The guest's networking would not start (which was expected). Deleted the /etc/udev/rules.d/70=persistent-net.rules file (so it would re-generate with the right NICs when things came up next time).

Enabled a Bridged virtual NIC and associated it with en0. Same error with the complaint about eth0. Huh?

We tried using NAT style virtual NICs also and had no success.

Anyone know how to work around this?

Thanks!

John