Ubuntu
virtualbox package

Virtualbox install via apt install has errors

Bug #1875271 reported by Sonny Rajagopalan
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have a new Ubuntu 20.04 x_64 install on my server and I installed virtualbox via apt. I am able to run VMs and use vboxmanage, but everytime I run vboxheadless to start a VM, I get the following error:

machine@user: $ vboxheadless -s vmname
Oracle VM VirtualBox Headless Interface 6.1.6_Ubuntu
(C) 2008-2020 Oracle Corporation
All rights reserved.

VBoxHeadless: supR3HardenedVerifyFileFollowSymlinks: Failed to resolve the real path '/usr/lib/virtualbox/components/VBoxREM.so': No such file or directory (2)

machine@user: $ lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04

machine@user: $ apt-cache policy virtualbox
virtualbox:
  Installed: 6.1.6-dfsg-1
  Candidate: 6.1.6-dfsg-1
  Version table:
 *** 6.1.6-dfsg-1 500
        500 http://us.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages
        100 /var/lib/dpkg/status

Expected result: vboxheadless works without error, and VBoxREM.so is found in /usr/lib/virtualbox/VBoxREM.so.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu):
status: New → Confirmed
Revision history for this message
Lukas svärdkvist (sleepyo) wrote :

I have usually used VboxHeadless to start vm's via systemd unit files, But I guess some use it for some vrdp functionality.

Anyway, VboxManage can do almost the same thing. For me the only change was adding RemainAfterExit=yes in my unit file and changing VboxHeadless --startvm debian to VboxManage command instead. Just wanted to add this in. I briefly looked into Oracle's documentation and also found an old post on there forums mentioning VboxHeadless is the preferred way to start vm's this way. Anyway, works for now.

""This is the recommended way, because when starting the headless interface through VBoxManage, you will not be able to view or log messages that VBoxHeadless may have output on the console. Especially in case of startup errors, such output might be desirable for problem diagnosis.""

Requires=systemd-modules-load.service
After=systemd-modules-load.service

[Service]
Type=simple
User=sleepy
Group=vboxusers
ExecStart=/usr/bin/vboxmanage startvm debian --type headless
RemainAfterExit=yes
ExecStop=/usr/bin/VBoxManage controlvm "debian" poweroff

[Install]
WantedBy=multi-user.target [/code]

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

please test proposed pocket

Changed in virtualbox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]

Changed in virtualbox (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Timuridze (aimin) wrote :

I have a similar problem. I am using Virtualbox on the server in conjunction with phpVirtualbox and have problems with VRDP. When I started to find out why remote access does not work, I came across an error at startup.

VBoxHeadless: supR3HardenedVerifyFileFollowSymlinks: Failed to resolve the real path '/usr/lib/virtualbox/components/VBoxREM.so': No such file or directory (2)

If you look at / usr / lib / virtualbox / components /, you can see an erroneous symlink leading to ../VboxREM.so

Changed in virtualbox (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

This might be now fixed in proposed pocket

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.