Mailinglist Archive: opensuse-bugs (4297 mails)

< Previous Next >
[Bug 1027742] virtualbox cannot setup host-only network parameters
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sun, 28 May 2017 02:04:07 +0000
  • Message-id: <>

Larry Finger <Larry.Finger@xxxxxxxxxxxx> changed:

What |Removed |Added

--- Comment #5 from Larry Finger <Larry.Finger@xxxxxxxxxxxx> ---
I finally figured out how to set up this kind of network, although I used the
VirtuaLBox GUI to do the configuration.

In the GUI, from File=>Preferences=>Network=>Host-Only Networks, Add vboxnet0.
Next edit that network and set the IP address for it under the adapter tab. If
you want the VMs to get their addresses via DHCP, then click the DHCP Server
tap, enable the server, and verify that the addresses belong to the network
selected for the adapter.

In all cases, all machines are fully updated.

With this setup, VMs for TW Gnome and TW KDE could ping each other and the host
adapter address when I was running openSUSE Leap 42.2 KDE as the host. Host and
both VMs are running NetworkManager.

When my host was TW KDE, the TW Gnome VM acquired an IP address of and the TW KDE VM got, the same as with the Leap
host. At this point, there is a problem. The KDE VM can ping itself, but not
the Gnome VM, or the adapter. Although the Gnome VM got an IP address, it could
not ping itself, the adapter, nor the other VM. Again NetworkManager was used
on all machines.

Obviously, there is a problem with TW, but I am not sure which component is
involved. Keep in mind that the same Oracle code is used to generate both Leap
42.2 and Factory/TW VB packages, thus my suspicion is that some other
networking component is at fault. The problem is that I have no idea where to
look. I will need to do more research on this issue.

You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >