4.3.24, internet issue after upgrade

[genEric]

I updated Virtualbox to 4.3.24 (+ extensions & guestaddtions) a few days ago. Since then, internet in my Fedora guest doesn't load on start.

To get i working again, I have to:

• Start Fedora, (no internet).
• Vbox settings: change NAT to some other option and click ok
• In Fedora re-establish the connection so it fails
• VBox settings, change back to NAT
• In Fedora re-establish the connection (= OK)

- - -

If it helps, the log of the startup:

VBox_startup.log

(82.77 KiB) Downloaded 6 times

At this point there is no internet.

Changing NAT to somthing and then back... adds this to the log:

VBox_startup_xtras.log

(2.99 KiB) Downloaded 7 times

Code: Select all

VBoxManage showvminfo "Fedora21" --details

Vbox_showinfo.txt

(3.99 KiB) Downloaded 5 times

Virtualbox: 4.3.24 r98716 + ext, GA
Host: OS X 10.7.5
Guest: Fedora 21 (32bit)

- - -

Any ideas?

[socratis]

I believe that you might have been hit by a regression bug in 4.3.24. Take a look at https://www.virtualbox.org/ticket/13918 because I believe that they have a testbuild that you can try.

[genEric]

I believe that you might have been hit by a regression bug in 4.3.24. Take a look at https://www.virtualbox.org/ticket/13918 because I believe that they have a testbuild that you can try.

Thanks socratis. Will keep an eye on that ticket. Looks interesting. But it seems like the test build didn't solve it though.

Had to install the new 4.3.25 Vbox Additions. (Mac OSX host, Windows 7 Guest) "NAT Network" works fine. Still no DNS in "NAT" mode.

Perhaps I should downgrade to the version I had, until it's ok again? Not that it is too hard to do the xtra steps, but it also breaks a couple of things in my startup which I additionally have to “redo” (reload my dock/panel etc...).

[socratis]

Perhaps I should downgrade to the version I had, until it's ok again?

Yes, there should be no problem downgrading. Just don't do it while the guest(s) are in saved state. Make sure they're properly shut down. Also, unless you try the new versions that come out, how are you going to know that it's OK?

[genEric]

Yes, there should be no problem downgrading. Just don't do it while the guest(s) are in saved state. Make sure they're properly shut down. Also, unless you try the new versions that come out, how are you going to know that it's OK?

Yes, that's true. I was thinking about perhaps testing the testbuild. How to do with the extensionpack? Didn't see it @ https://www.virtualbox.org/wiki/Testbuilds

Speaking of saved states... I had a lesson learned the other day. Was about to remove a VM and setup a new with the same disk... just that I had 2 snapshots (I forgot about) w. saved states. My “new” machine entered a very early stage, and before I had figured out how get the snapshots back in order, including diff uuid's, misc warnings etc... Many f-words and evil things were said to myself. ^^ *oops*

[loukingjr]

The 4.3.24 extension pack works with the 4.3.25 testbuild.

[genEric]

The 4.3.24 extension pack works with the 4.3.25 testbuild.

Thanks loukingjr... I'll try.

[loukingjr]

yvw.

[genEric]

Ok, it didn't work. (VirtualBox-4.3.25-98862-OSX.dmg + GA, and ext from *.24)

VBox.log.txt

(107.21 KiB) Downloaded 5 times

Just a longshot... I get a few startup errors, mainly about opengl/vboxvideo/dri etc... Could that affect the boot so internet won't kick in?

[loukingjr]

I don't know what the issue is but it's not OpenGL. I've been running a Fedora 21 guest since the end of last year and I had/have no problem connecting to the internet. Not with VB 4.3.20 - 4.3.25 using NAT. Hopefully someone else has an idea.

[genEric]

Same here... It's been working with NAT until I upgraded VB to *.24

[loukingjr]

you could always fall back to 4.3.22. just be sure to uninstall VB using the VirtualBox_Uninstall.tool first.
https://www.virtualbox.org/wiki/Download_Old_Builds_4_3

[genEric]

you could always fall back to 4.3.22. just be sure to uninstall VB using the VirtualBox_Uninstall.tool first.
https://www.virtualbox.org/wiki/Download_Old_Builds_4_3

Thanks for the link. Yes, I'll probably do that later. I hade *.20 before, so back to that one (have the dmg). Also, I saw in Yum Extender: kmod-VirtualBox-* ...which is 4.3.20 incl all different kernels. So, perhaps one should go with those instead?

- - -

I thought for a while I had it solved. Tired of this I went online, ran an update and there was a lot of this to update including a new(er) kernel. Ran the update and reinstalled GA. When I restarted, I had internet. *wohoo*, and it survived a few reboots. But, the software rendering mode had kicked in and I noticed in the boot log that vbox-add service failed (vboxadd-service[1766]: Starting VirtualBox Guest Addition service VirtualBox Additions module not loaded!). Reinstalled GA once again. Graphics good (but w gl errs), and no internet. So, I guess it's the GA that's causing this.

[loukingjr]

well as I said, I've had a Fedora 21 guest since it became available. I have the GAs installed and have no connection issues so I suspect it's something else. I suppose it could be a quirk of OSX 10.7.5 but I don't know that.

It's not good to mix the official VirtualBox versions with the fedora versions btw.

[genEric]

I believe that you might have been hit by a regression bug in 4.3.24. Take a look at https://www.virtualbox.org/ticket/13918 because I believe that they have a testbuild that you can try.

I noticed today in the ticket there was a new build they had working. Upgraded, but it didn't help.

well as I said, I've had a Fedora 21 guest since it became available. I have the GAs installed and have no connection issues so I suspect it's something else. I suppose it could be a quirk of OSX 10.7.5 but I don't know that.

Of cource it could be something in my 10.7.5 that is an issue now with the new VB-version. Still it falls back on something in VB that was changed. I didn't change anything.

Anyway... As mentioned above I tested the lastest test build, though it didn't solve it, but... I have found what's causing it - and a way around.

Looking at my connection in the host net worksettings. When I do the fix so internet work I noticed the DNS server came up as 10.0.2.3. When it loads, it defaults to 127.0.0.54 which is the DNS server I have(/get with DNScrypt from OpenDNS). So I tried to change from automatic DNS to manually set 10.0.2.3. Restarted and it did't work. So I guess it's some about how it gets picked up when it starts.

Started an older backup (10.7.4) I have and installed 4.3.20, just to see how the default files where configured, and to see if there where any differences.

The main difference I saw regarding DNS was in: VBoxSCV.log

Before:

Code: Select all

VirtualBox XPCOM Server 4.3.20 r96996 darwin.amd64 (Nov 21 2014 15:07:51) release log
// ... //
00:00:00.108292 nspr-2   Loading settings file "/Users/MYUSERNAME/Library/VirtualBox/VirtualBox.xml" with version "1.12-macosx"
00:00:00.142831 nspr-2   HostDnsMonitorProxy: Host's DNS information updated:
00:00:00.142845 nspr-2   DNS server 1: 127.0.0.54
00:00:00.145198 nspr-2   VDInit finished

Now:

Code: Select all

VirtualBox XPCOM Server 4.3.25 r98882 darwin.amd64 (Mar 11 2015 17:18:00) release log
// ... //
00:00:00.125539 nspr-2   Loading settings file "/Users/MYUSERNAME/Library/VirtualBox/VirtualBox.xml" with version "1.14-macosx"
00:00:00.185740 nspr-2   HostDnsMonitorProxy::notify
00:00:00.185766 nspr-2   HostDnsMonitorProxy: Host's DNS information updated:
00:00:00.185772 nspr-2     server 1: 127.0.0.54
00:00:00.185778 nspr-2     no search string entries
00:00:00.185782 nspr-2     no domain set
00:00:00.204472 nspr-2   VDInit finished

A new “formatting” of the DNS output, and more options that are being checked (what it looks like).

Also, “notify”? If that is something related/connected to the NotificationCenter (new in 10.8+), I don't know...

- - -

If I manually set the OpenDNS servers in networksettings (on the host), and not automatic DNS, then it works. Just that it worked before, without changes.