Virtualbox - *within* 10.6.8, linux - network issues

[bb_matt]

After a few days of running with no issues, I'm encountering issues when trying to run virtualbox.

On first starting up Virtualbox, my network died - I put it down to router issues and rebooted, network worked again.

Now, obviously, Virtualbox installs network drivers, so I suspect that this is what is causing network failure in my hackintosh.

Exactly why, is so far beyond my skillset, I wouldn't even know where to begin.

Anyone else had issues like this?

 

[bb_matt]

.. to explain further...

Mac is the host, Linux is the guest.

Tried with several different Virtualbox network configurations - NAT is fine, it's only when I switch to Bridged that the network on my Hackintosh dies.

 

[mhmacgre]

I'm having the exact same problem only I'm using VMWare Fusion.
All my VM's run fine in NAT but when switched to Bridged I lose all networking on the machine.

I've tried Lnx2Mac as well as the standard Realtek Driver and get the same results in both.

Any ideas on how to fix this or troubleshoot it further?

UPDATE: just realized that Lnx2Mac never actually installed as I do not think the Realtek chipset RTL8111e is supported by Lnx2Mac yet.... I'm hoping his new upcoming release will add support! this is the only problem I have with my hackintosh... and this is only a problem as I want to run a few Virtual Machines in vmware fusion... in bridged mode.

GigaByte H67MA-USB3-B3
Core i7 2600K
GeForce GT 240
OSX 10.6.8

 

[KenBotwinick]

I have the same problem in Lion when using Parallels. Both drivers. Any one make progress on this yet?

 

[powerpcg5]

I'm having the exact same problem only I'm using VMWare Fusion.
All my VM's run fine in NAT but when switched to Bridged I lose all networking on the machine.

I have both Parallels and VMWare Fusion installed on my Hackintosh.

Using Ethernet(Bridged), the GUEST OS (with it's own IP address) can be seen by the rest of my network with either Parallels or VMWare Fusion. The GUEST in Parallels can also see the GUEST OS in VMWare Fusion and vice versa, all of them having unique IPs.

Host OSX is Lion 10.7.1 (built-in Ethernet on mobo, Intel DG33TL).

I don't have VirtualBox so can't comment on that part. When I get time, I'll try installing it.

 

[hardmantosh]

I also have had issues with this problem in the past,i got around a couple by reassigning
different ip addresses .this can become difficult with different isp providers..here i have included a link which may be of some help;but as far as technicalities go i personally dont have any guests setup at the minute to be of anymore help than this....good luck with it all;sometimes its a pain but thats virtualisation,in my book..
http://www.virtualbox.org/manual/ch06.html

 

[KenBotwinick]

Hardmantosh, thanks but I don't think this problem has anything to do with the configuration of any of the different virtualization software. I think it's caused by the network drivers. My guess is most people with the problem have a motherboard/ethernet controller/driver combination in common.

 

[hardmantosh]

Hardmantosh, thanks but I don't think this problem has anything to do with the configuration of any of the different virtualization software. I think it's caused by the network drivers. My guess is most people with the problem have a motherboard/ethernet controller/driver combination in common.

My comments were not about configuring different virtualisation software,they were about
configuring each guest differently via different ip addresses and using onboard and pci controller with each guest differently..
I may have needed to add more precise info before,so good luck with it all anyway its..

 

[bash721]

Bump, anyone figured out a solution? I'm seeing the same thing on my system with Virtual Box. When I set the network configuration to Bridged in full promiscuous mode, the moment I power on the VM, I get disconnected from screen sharing and have to reboot.

 

[powerpcg5]

Buy a Sonnet NIC card. Supported OOB by Apple kext. You can use Bridged networking in VMs without issues or the network dying suddenly in both the VM and the host.