ubuntu 19.04:vboxwebservice.service refuses to start

[Stephen Waines]

I use virtualbox to host serval vms. About a week ago since an update. I lost connectivity to the internet via all my vms.

I just did 6 hours of troubleshooting and I see upon serveral fresh installs of virtualbox on 19.04.That

Failed to start vboxweb-service.service: Unit vboxweb-service.service not found.

dmesg errors say

[ 272.533269] vboxpci: IOMMU not found (not registered)

Virtual machine do not hve access to this service therefore they cannot get an outside connection

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1825598/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Stephen Waines (stevinski)]

Left all my systems and routers unplugged all night.

It seems that upon a fresh install of virtualbox, that it states

vboxweb.service is a disabled or a static unit, not starting it.

though I use Stacer to enable it.

then check
/lib/systemd/system and the service file is there

perhaps its not configured correctly

-Steve

On 2019-04-20 2:56 a.m., Paul White wrote:
> ** Package changed: ubuntu => virtualbox (Ubuntu)
>

[Stephen Waines (stevinski)]

Hello,

I have ubuntu 19.04 on my laptop and my tower pc. I have virtualbox
hosting a virtual machine of ubuntu server 18.04 on my tower and a copy
of it on my laptop. Bot I had set a static ip outside of my dhcp pool on
via netplan. Both vms are set in bridged mode. They were working and
have been for the past year. Until two weeks ago when google did not
update there signatures so updating didnt work.

At that time I lost connectivity to the internet on both vms, but it
fixed itself withing 3 days on my laptop via updates i assume.

The server on my laptop will connect to the internet. But my server on
my tower pc cant, despite it having a copy of my known good .vhd file
from my laptop. To further my troubleshooting I reset my router to
factory defaults and reconfigured it. I got the same result, my laptop
vm can connect to the internet not my tower one with identical settings.
Even after uninstalling virtualbox many times and reinstalling , same
result.

I can conclude that the problem must be how network manager on ubuntu
19.04 handles virtualized connections.

If I run ifconfig on my host os, I can see a virtual network card but
its on network 122. So unfortunatly I can bridge to that one within
virtualbox.

On 2019-04-20 2:56 a.m., Paul White wrote:
> ** Package changed: ubuntu => virtualbox (Ubuntu)
>

[Stephen Waines (stevinski)]

Hi,

Upon further investigation. I have come to the conclusion that my host
OS 19.04 network card

enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.2.11  netmask 255.255.255.0  broadcast 192.168.2.255
         inet6 fe80::97c7:f9c8:79ec:15d6  prefixlen 64  scopeid 0x20<link>
         ether 50:46:5d:aa:2f:a8  txqueuelen 1000  (Ethernet)
         RX packets 310173  bytes 266065656 (266.0 MB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 254883  bytes 39103611 (39.1 MB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Wont allow bridge mode to Virtualbox on enp2s0.

running iproute on my host os shows weirdness:

steve@Desktop-pc:~$ ip route
default via 192.168.2.1 dev enp2s0 proto dhcp metric 100
169.254.0.0/16 dev enp2s0 scope link metric 1000
192.168.2.0/24 dev enp2s0 proto kernel scope link src 192.168.2.11
metric 100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown

Whereas on my working machine ip route shows:

steve@Stevuntutop:~$ ip route
default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.14
metric 600

On Stevuntotop I have a vm set in bridged mode to the adapter that my
host uses. The vm can ping my gateway, thus get the internet.

On my desktop i have a carbon copy of my virtual server on a fresh
install of virtualbox in bridged mode to the nic that my desktop is
using. The vm can ping my other vm but not my gateway. Perhaps my
routing table is in the wrong order. Hence its a bug with network
manager in 19.04.

-Steve

Guess this is a bug that has nothing to do with what i originally thought.

On 2019-04-20 2:56 a.m., Paul White wrote:
> ** Package changed: ubuntu => virtualbox (Ubuntu)
>

[Launchpad Janitor (janitor)]

This bug was fixed in the package virtualbox - 6.1.16-dfsg-4

---------------
virtualbox (6.1.16-dfsg-4) unstable; urgency=medium

  [ Sam Van den Eynde ]
  * Fix vboxweb.service startup script, from Sam Van den Eynde (LP: #1904123, LP: #1825598)
  * Now the script also sources /etc/vbox/vbox.cfg that can contain all the
    required variables.

 -- Gianfranco Costamagna <email address hidden> Mon, 16 Nov 2020 14:12:27 +0100