Announcement

Collapse
No announcement yet.

Virtual machine will not start

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [SOLVED] Virtual machine will not start

    I have a headless VirtualBox machine on one of my remote servers that has become unable to start. I'm not sure if this is due to any recent updates or if something got borked during a sudo apt-get autoremove. When I try to start up the VM I receive the following output:

    Code:
    [gknbynw@QuickBox]:(0b)~$ VBoxManage startvm "MeGUI" --type headless
    WARNING: The vboxdrv kernel module is not loaded. Either there is no module
           available for the current kernel (4.4.0-146-generic) or it failed to
           load. Please recompile the kernel module and install it by
    
             sudo /sbin/vboxconfig
    
           You will not be able to start VMs until this problem is fixed.
    Waiting for VM "MeGUI" to power on...
    VBoxManage: error: The virtual machine 'MeGUI' has terminated unexpectedly during startup with exit code 1 (0x1)
    VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
    [gknbynw@QuickBox]:(0b)~$
    I don't fully grasp recompiling a kernel module but I did try the vboxconfig command and got this:

    Code:
    [gknbynw@QuickBox]:(0b)~$ sudo /sbin/vboxconfig
    vboxdrv.sh: Stopping VirtualBox services.
    vboxdrv.sh: Building VirtualBox kernel modules.
    vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
    
    There were problems setting up VirtualBox. To re-start the set-up process, run
    /sbin/vboxconfig
    as root.
    [gknbynw@QuickBox]:(0b)~$
    The vbox-install.log is WAY beyond my comprehension but here's a link if anyone's interested:

    Code:
    https://drive.google.com/file/d/1mMBtXwt8k_C6ljKWEndYoZEbGo6ttlvo/view?usp=sharing
    As always, thanks in advance for any guidance or direction anyone can provide. You guys are the reason I come to this site before anywhere else




    Moderator's note:

    This was moved from the now-closed 16.04 Xenial forums
    Last edited by claydoh; May 26, 2019, 01:10 PM.

    #2
    I found this on virutalbox's forum:
    https://forums.virtualbox.org/viewto...27514982e0bf0c

    and sunsequently
    https://bugs.launchpad.net/ubuntu/+s...x/+bug/1818049


    You may need to reboot to a previous kernel version, else try a newer version of virtualbox

    Comment


      #3
      Originally posted by claydoh View Post
      I found this on virutalbox's forum:
      https://forums.virtualbox.org/viewto...27514982e0bf0c

      and sunsequently
      https://bugs.launchpad.net/ubuntu/+s...x/+bug/1818049

      You may need to reboot to a previous kernel version, else try a newer version of virtualbox
      Thanks, claydoh. Rather than take the risk of a VirtualBox upgrade (from v5.1 to v6.x) screwing things up even further, I installed the .deb’s for the 4.4.0-040400 kernel and that has fixed the problem. I’m sure at some point I will have to upgrade VB, but I had a heck of a time getting the virtual machine set up to function properly as a headless server with RDP access & I *REALLY* dread the headache of having to go through all that again if an upgrade borks things.

      EDIT: Thread marked as solved
      Last edited by GKNByNW; May 28, 2019, 08:31 PM.

      Comment

      Working...
      X