virtualbox.org

Hi,

I have Windows and Ubuntu (Backtrack) Installed as guests under Virtualbox 4.1.6r74713
And used them for a year or so in bridged network mode (ethernet and wifi) without any problems.

Today I tried to use Windows guest in bridged mode -- but no IP address was assigned (my network has a DHCP server).
It is working however in the NAT mode.
I tried with Ubuntu and the results are the same -- bridging doesn't work, NAT is OK.
WTF?

I suspect latest OS X updates (installed them over the weekend).

Anyone have any ideas how to fix this?
Anyone have the same problem?

I'm also having this problem. Has anyone found a solution?

Same problem, quite suddenly, but not connected to any OSX update except a iTunes change.

Suddenly, after kernel crashes started, got no connect with bridged setting, which worked quite reliably for most of a year.

Seemed to begin with a series of kernel crashes with VBox 4.1.4 -- that day, I lost all ability for the VMs to get DNS for about three hours, then it came back (although the Mac host never lost DNS). Stuff like changing network time server failed in the VMs, update wouldn't, browsers didn't connect.

After a few restarts the problem went away overnight, then came back with more kernel crashes.

Reinstalled 4.1.4; no improvement; uninstalled and installed with 4.1.2; no improvement, more kernel crashes.

After a visit to Apple to check (no hardware problems found), I downgraded again to 4.0.16, haven't had a kernel crash since, but still have no VMs that will connect with bridged -- all require NAT.

No clue. Same problem with seven different Windows VMs (XP and Win7/86 and Win7/64-bit).

These kinds of problems that are reproducible should be reported to bugtracker. You will need to setup an account there as it is on a different system.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.

> reproducible

I have no idea how to reproduce this problem.

Is the reply here that I've seen the same problem appropriate?

I thought that might be useful information to someone, or that someone might suggest what to look for, or how to try to reproduce this.

It's a generic reply hank. From what you and the others state the problem is beyond the ability to fix here and that is why I suggested to report this to the DEVs (bugtracker)

> These kinds of problems that are reproducible should be reported

If I could reproduce it I would, but I don't know how to reproduce it.

Is there a way of reproducing this 'bridged guest stops working' problem?
(All I've seen is, it developed intermittently, and seems to be permanent, but no idea how it was produced or could be reproduced or where to look for such info).

I'll eventually move up from 4.0.14 and try the recent release, and -- if the kernel panics don't happen-- see if the bridged guest problem persists.