virtualbox.org

Did a recent VB5 update disable Linux guests with NAT networking from looking up LAN hostnames? (Originally posted to the "Linux Guests" group)

Greetings,

Up until I believe this latest update to VB5 (5.0.22) I was able to have the following configuration:

Host machine: Xubuntu 14.04 x64

Guest machine: Xubuntu 14.04 x64
NAT networking

And could successfully look up hostnames on the host machine's local LAN within the guest.

With VB 5.0.22, I need to shift over to bridged mode networking in order to successfully resolved local LAN hostnames in the guest OS.

Was this due to an intended / unhelpful change? Or is it a new regression defect?

I am thankful,

Greetings again,

I validated that also Windows VM's are unable to successfully resolve hostnames of hosts on the Host machine's local LAN.

So this is not just a Linux VM/Guest issue.

Definitely new behavior.

I am thankful,

JF002 wrote:

Old Newbie wrote: The problem was first observed after upgrading to 5.0.18 with the appropriate GAs, and has persisted through 5.0.20 and now 5.0.22.
...
Once these symptoms appear, opening the Task Manger shows VBoxTray.exe using 50% of the CPU. If I leave the guest running, CPU utilization will vary in a range from 45% to 80% and never returns to normal.

I had this kind of issue when drag and drop between the host and the target was enabled. I simply disable that functionality as I don't use it and the issue disappeared.

After more than a week of testing and upgrading to 5.0.24, disabling drag and drop cleared up the problem. I hadn't realized that I had even enabled this feature since I usually only share the clipboard.

My bad.

O.N.