Unable to get bridged adapter to work on a ubuntu 32-bit os

[anwaya]

Hi All,

I have a ubuntu desktop host o/s which is 64-bit. On this ubuntu desktop i installed virtualbox 5.0.10 from the virtualbox website. Then I installed the 32-bit version of the ubuntu server(14.04.3). I had to install 32-bit only as I was unable to see the 64 bit options for any of the guests o/ses. Anyway, so the install went OK. However my main intent to install the server is because i want to use this as a production web server so that i can develop code on my local machine and push it to the guest o/s so that i can test and run my code on the server via virtualbox. For this I need to have a bridged adapter in my virtualbox ubuntu server. This simply refuses to work and I am at a complete loss of what to do. On my host I connect through a wireless NIC to a router which in turn connects to the modem. I tried this on 3 different laptops, some with windows as the host and now with ubuntu as the host. But I am just not able to get the bridged adapter to work. NAT connection works fine but not bridged. Your help is most appreciated!!!

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

Also from the host terminal post the results of the following:

• VBoxManage list bridgedifs

[anwaya]

Thanks PerryG. I have attached the log file as well as the bridged interface list here.

[Perryg]

1) the reason you had to install a 32-bit guest is because your processor does not support VT-x/AMD-v
2) Bridged to a wlan adapter is iffy at best. Some don't support multiple MAC addressing. You say you tried three different laptops so that would justify looking at the router (access point) as the real issue. I would seek assistance from the AP company to see if there is anything that you can do.
You could actually try the wired connection if it has one and see for sure, but I feel contact with the AP company is your next best choice.

[anwaya]

Thanks PerryG. Thing is this happened even at another place that was not home where I was also connected via WiFi from the host. Yes I realize now that due to no support for virtualization in the CPU/BIOS, I'm forced to use 32 bit . So I'm not sure if the AP could be the only issue as some others with me were able to bridge to their host wlans at the same location on their windows and macbooks the only difference being that they all used 64 bit guest Ubuntu servers due to newer CPUs and I was using 32 but. Could that be the issue? 32-bit Ubuntu server guest o/s?

[Perryg]

Last thing to check:
From the hosts terminal type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

[anwaya]

Hi PerryG,

An update from my side. So I realized that the only variable here was the Ubuntu 32 bit image vs the Ubuntu 64 bit image. I also realized that even my newest corei5 laptop on which I had failed had an untouched BIOS. So I got into the BIOS of my Lenovo yoga system and enabled virtual technology(somehow I missed doing this earlier or assumed that I had already done it). After this, I was able to see the 64 bit options for the guest O/Ses too. After this I downloaded Ubuntu server trusty 14.04 LTS and was then very smoothly able to use the bridged adapter without any issues whatsoever. So the red flag was the Ubuntu 32 bit server image for version 14.04. Thanks a lot for your help and feedback in root causing this!