[WorksForMe] Linux guest that was ok yesterday - unable to connect

Discussions related to using VirtualBox on Linux hosts.
Post Reply
Lus1phur
Posts: 11
Joined: 10. May 2017, 14:25

[WorksForMe] Linux guest that was ok yesterday - unable to connect

Post by Lus1phur »

The host was set up with bridged and hostonly networking.

Code: Select all

VBoxManage modifyvm "Serverapps" --cpus 4 --memory 4096 --boot1 dvd --nic1 bridged --bridgeadapter1 enp0s31f6 --nic2 hostonly --hostonlyadapter2 vboxnet0

ifconfig
enp0s31f6 Link encap:Ethernet  HWaddr 1c:1b:0d:64:1a:8d
          inet addr:192.168.1.130  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::1e1b:dff:fe64:1a8d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22457 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8131 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5969689 (5.9 MB)  TX bytes:1119495 (1.1 MB)
          Interrupt:16 Memory:ef200000-ef220000

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:3344 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3344 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:696855 (696.8 KB)  TX bytes:696855 (696.8 KB)

vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00
          inet addr:192.168.2.130  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::800:27ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:8891 (8.8 KB)

virbr0    Link encap:Ethernet  HWaddr 52:54:00:2c:ec:fc
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

VBoxManage list hostonlyifs
Name:            vboxnet0
GUID:            786f6276-656e-4074-8000-0a0027000000
DHCP:            Disabled
IPAddress:       192.168.2.130
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:0800:27ff:fe00:0000
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-vboxnet0

traceroute 192.168.1.132
traceroute to 192.168.1.132 (192.168.1.132), 30 hops max, 60 byte packets
 1  192.168.1.130 (192.168.1.130)  2998.405 ms !H  2998.389 ms !H  2998.382 ms !
This was working yesterday before a reboot of the host this morning. The guest has a static IP set on it. I have tried
1) Delete and re-create the hostonlyif
2) Changing networking to NAT + hostonlyif
3) Changing networking to bridged only

I just can't get connected. Any other suggestions gratefully received.
Last edited by socratis on 14. Jun 2018, 21:38, edited 1 time in total.
Reason: Marked as [WorksForMe].
Lus1phur
Posts: 11
Joined: 10. May 2017, 14:25

Re: Linux guest that was ok yesterday - unable to connect

Post by Lus1phur »

Just close this. It's a boot issue with the VM itself. It's booting to the grub screen.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Linux guest that was ok yesterday - unable to connect

Post by socratis »

Great, thanks for letting us know. Marking as [WorksForMe].
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply