Since upgrade to Ubuntu 16.04, VMs won't start

Discussions related to using VirtualBox on Linux hosts.
Post Reply
flip
Posts: 1
Joined: 8. Jul 2017, 12:48

Since upgrade to Ubuntu 16.04, VMs won't start

Post by flip »

Hi
I have been happily using VirtualBox to access my Windows7 and Windows XP VMs with Ubuntu 12.04 for many years. I finally bit the bullet and upgraded to 14.04 a couple of days ago and did some tests of all my apps (I think I recall) vbox worked OK. I then upgraded again to 16.04 yesterday and encountered the following problem when Starting either VM…
I get two :shock: (not one) Start VM dialogs
On one, progress was 0%
Other (Starting virtual machine 2/2) Progress goes to 20%
but both freeze.
Virtual Box Manager also freezes, so I either need to log out, or kill the vbox processes from a terminal.

Repeatable every time.

I am using VirtualBox Graphical User Interface Version 5.0.40_Ubuntu r115130
uname -a
Linux mach-name 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

dmesg |grep vbox
[ 51.244798] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[ 51.253612] vboxdrv: Found 4 processor cores
[ 51.273172] vboxdrv: TSC mode is Invariant, tentative frequency 2527318349 Hz
[ 51.273179] vboxdrv: Successfully loaded version 5.0.40_Ubuntu (interface 0x00240000)
[ 51.492642] vboxpci: IOMMU not found (not registered)
[ 1600.960789] Modules linked in: bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm bluetooth xen_gntdev xen_evtchn xenfs xen_privcmd binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media arc4 ath9k ath9k_common hp_wmi snd_hda_codec_hdmi ath9k_hw sparse_keymap snd_hda_codec_idt ath snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep cfg80211 snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_powerclamp snd_seq joydev snd_seq_device input_leds coretemp snd_timer serio_raw snd hp_accel soundcore mei_me lis3lv02d shpchp mei lpc_ich input_polldev mac_hid cuse parport_pc ppdev lp parport autofs4 dm_mirror dm_region_hash dm_log dm_snapshot dm_bufio hid_generic usbhid hid
[ 1600.962045] [<ffffffffc07543f7>] ? supdrvIOCtl+0x2de7/0x3250 [vboxdrv]
[ 1600.962083] [<ffffffffc074d5b0>] ? VBoxDrvLinuxIOCtl_5_0_40+0x150/0x250 [vboxdrv]

Looking on-line It seems to have something to do with Secure boot, so I created a signature, but to do this mokutil failed because ‘EFI variables are not supported on this system’. I suspect this is to do with LVM. Now the fix to this is to customise the kernel.

But in any case because I would be doing multiple layers of fixes, none of which I am confident will work, I am wondering is there anything else more straight-forward I can try to re-instate access to my Virtual Machines?

Attached is the vbox log.

Any help or advice would be greatly appreciated !

Regards,
Phil
Attachments
Win7_HP_DV6-2017-07-08-20-41-56.log
(1.22 KiB) Downloaded 9 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Since upgrade to Ubuntu 16.04, VMs won't start

Post by Perryg »

Two problems.
  • 1) you are running the ubuntu fork ( OSE ) that we do not support here.
    2) you have two extpacks installed, one is the distro fork that supports VNC and the second that is from VirtualBox that supports all of the features available. Problem is the VirtualBox extpack does not match the running version of VirtualBox.

Code: Select all

00:00:00.899466 Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.925013 Installed Extension Packs:
00:00:00.925044   VNC (Version: 5.0.40 r115130; VRDE Module: VBoxVNC)
00:00:00.925052   Oracle VM VirtualBox Extension Pack (Version: 4.1.34 r95024; VRDE Module: VBoxVRDP unusable because of 'Incompatible extension pack (version '4.1.34'), please update')
Post Reply