virtualbox.org

Hello all,

I'm not totally thinking this is a Virtualbox issue versus a network configuration problem on the wireless side. But let me throw this out and see if anyone has any ideas how to identify the problem, or maybe what I should look at?

I'm running Mac OS X 10.7.2 (Lion), with VirtualBox 4.1.6 download and installed. I have installed a Debian 6 Linux as a guest. Here is the problem, when trying to Bridge to the wireless adapter (en1: Wi-Fi (AirPort)) on my VM, i can not access the network. I first noticed the problem when trying to use a net install to install Debian when in Bridge Mode. To get around the problem I configured it back to NAT and installed the OS. All other configurations work:

• Using NAT
• Bridging to the Wired Ethernet (en0)
• Tried more then one VM Linux distribution.

If I bridge to the wireless network card (which wireless is working on the host mac without issues) I can not get DHCP, or when I set to static can not ping anything other then the local mac host's IP address. I have looked in the /Users/me/VirtualBox VMs/LinuxBox/Logs/VBox.log and I don't see any errors. I wouldn't even have posted this thread, but why, when setting to a static IP the VM can ping the Mac Host? But on the other hand if I connect to wire, and then bridge to that connection everything works fine.

So in short, If I bridge to the wireless adatper on my Mac, my Guest VM can not access the network. But my Mac host can access the network without issues. What should I look at? OR what am I missing?

Thanks for all your time and help,
Nick

I'm experiencing the same issue with VirtualBox 4.1.6 on Mac OS X 10.7.2. My Debian guest VM cannot get a DHCP lease (or do anything else) if its interface is set to bridge the host's Wi-Fi connection. Asking it to bridge the host's Ethernet connection works fine. I'd love to figure out whether this is something that I'm doing wrong or if it's a bug.

I having the same problem. MacBook Air with Host Mac OS X 10.7.2 and Guest CentOS-6 (64bit).

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.

I've created a bug report:

https://www.virtualbox.org/ticket/10019

I just went through this same pattern with two different Windows 7 VMs on a Mac host (bridging through a wired router to the DSL2 modem) -- anything in the VMs (applications, Internet time settings) could not get DNS, but the Mac host was fine for a couple of hours -- then kernel panic, restart, kernel panic.

I see this a lot in Console: CPUMSetGuestCpuIdFeature: Disabled x2APIC
but it's apparently a very common error message.

No idea how to replicate the DNS problem (or the kernel panics either).