[Solved] VirtualBox issue after upgrade to Win 10 1709

[davidhay]

My Windows 10 was recently upgraded to vsn 1709 and I had to re-install VirualBox to avoid the network adaptor issues reported on another thread.

My Debian VM is now working but I am unable to open a PuTTY session to the Debian VM as I had previously been able to do, it gives "host does not exist".



Any ideas anyone?

[mpack]

I would start with the assumption that the error message is correct. So find out why it would think that the host doesn't exist. Offhand this doesn't seem likely to be a VirtualBox problem. Probably the network config (machine name etc) of the host has changed.

[socratis]

Did you try with a named or a numeric connection? I.e. did you try "myDebian.local" or did you try "192.168.56.nnn"? Can you ping the VM?

[davidhay]

Before I upgraded to Win 10 1709 I used to be able to connect simply using the name of the VM, in my case Debian. debian.local does not work and I don't know what numeric ip address to try.

Thanks for your help.

[davidhay]

If I open the VM under VirtualBox the hostname is Debian.

[socratis]

I used to be able to connect simply using the name of the VM, in my case Debian.

Then something is not right in your name resolution. You shouldn't be able to connect by using "Debian" unless you set up your "hosts" file to point to that. There should be no "Debian" by default.

I don't know what numeric ip address to try.

Have you tried to find out from within the guest? As in check the output of "ifconfig"?

[davidhay]

The output of ifconfig from the VM is:

Code: Select all

eth0      Link encap:Ethernet  HWaddr 08:00:27:fd:04:6e  
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fefd:46e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:590 (590.0 B)  TX bytes:8118 (7.9 KiB)

eth1      Link encap:Ethernet  HWaddr 08:00:27:b3:90:61  
          inet6 addr: fe80::a00:27ff:feb3:9061/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:83 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:12446 (12.1 KiB)  TX bytes:7830 (7.6 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:480 (480.0 B)  TX bytes:480 (480.0 B)

I have tried all combinations 10.0.x.x. Before the 1709 upgrade the hostname debian was enough for PuTTY to find the connection.

[socratis]

I only see a NAT connection available in your guest (eth0) and the other one (eth1) doesn't seem to get an IPv4 address. What settings do you have in the VM settings for its network adapters? Actually, post a "VBox.log.zip":

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM.
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

BTW, are you sure that it was simply "Debian" in PuTTY and that wasn't simply the name of the profile? Again, this shouldn't be available automatically, you'd have to interfere to make the name resolution happen.

[davidhay]

BTW Since the upgrade to 1709, when I start the VM I get a message "a start job is running for LSB: Raise network interf..." which remains for about a minute.

Log file attached.

Screenshot of Adaptor 2 settings.

Thanks for your help.

[socratis]

00:00:02.406036 Host RAM: 8082MB (7.8GB) total, 3895MB (3.8GB) available
00:00:02.774184 RamSize <integer> = 0x0000000135b00000 (5 195 694 080, 4 955 MB, 4.8 GB)

You are assigning memory to your guest, that you do not have available. Either close some applications on the host, buy more RAM for the host, or reduce the amount of RAM assigned to the guest.

00:00:02.774414 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)

On the other hand, you should take the vRAM up to 32 or 64 MB.

00:00:02.774432 [/Devices/virtio-net/0/LUN#0/] (level 4)
00:00:02.774433   Driver <string>  = "NAT" (cb=4)

00:00:02.774452 [/Devices/virtio-net/1/LUN#0/] (level 4)
00:00:02.774452   Driver <string>  = "IntNet" (cb=7)
00:00:02.774455   Network <string>  = "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2" (cb=65)
00:00:02.774456   Trunk   <string>  = "VirtualBox Host-Only Ethernet Adapter #2" (cb=41)

You seem to have the correct setup. I don't use virtio-net for my setup, but I will assume that it works on Debian 9, since it seems to work with NAT. So, that leads me to think that something is wrong with your HostOnly adapter, aka a botched installation.

You said that you reinstalled VirtualBox. Did you uninstall it first? Did you install it with "Run-As-Administrator", even if you are the administrator? If not, please try again.

And finally, what are the options/parameters that you have enabled in your "Host Network Manager"?

And last, but not least:

when I start the VM I get a message "a start job is running for LSB: Raise network interf..." which remains for about a minute.

Search for that messasge. That's a Debian message and most probably indicates a failure to activate the HostOnly network card.

[davidhay]

You said that you reinstalled VirtualBox. Did you uninstall it first? Did you install it with "Run-As-Administrator", even if you are the administrator? If not, please try again.

Yes and Yes

And finally, what are the options/parameters that you have enabled in your "Host Network Manager"?

Where do I see these please?

Thanks for taking the time to look at this.

PS I am away for two days.

[socratis]

The "Host Network Manager" is available from the top right icon, the "Global Tools". Click on the downwards triangle and select it. Or, go to your "/Users/<you>/.VirtualBox/VirtualBox.xml". ZIP that XML file and attach it.

[davidhay]

Fixed.

DHCP was not enabled in the host only adaptor 2 settings and I also set the ip to be assigned. PuTTY now finds the VM from the hostname. The "Raise network interfaces" job no longer runs.

Strange though that I did not change any of this, just upgraded to Win 10 1709 and removed and re-installed VirtualBox.

Thank you so much!!

[socratis]

Strange though that I did not change any of this, just upgraded to Win 10 1709 and removed and re-installed VirtualBox.

Well it may have to do with the fact that the installer created the #2 host adapter? And that needed to be re-configured? I really can't tell, but that #2 and #n for subsequent installations is getting more and more prominent in the Windows world, with no quick and easy solution unfortunately...

Glad you got it going. Marking as [Solved].