Having problems getting virtualization to work

Asked by Joe Willmann

I am trying to setup a system that replicates my system at work. Linux development environment with Windows 7 running in a VM.

Bought all new parts, built computer, installed Ubuntu. Most everything went smoothly. Unfortunately my wireless adapter isn't yet supported so I have a wired connection for now. I will work the wireless issue later.

Started with VMware. Downloaded VMware-Player-12.1.1-3770994.x86_64.bundle

Followed the instructions at
https://help.ubuntu.com/community/VMware/Player

ran gksudo bash VMware-Player-12.1.1-3770994.x86_64.bundle and everything installed.
Ran Vm player and created the first VM for, Windows 7 Home Premium 64 bit. I am not sure that is the one I am going to settle with but I thought it would be a good first try.

I used defaults to configure the VM.

Then I tried to Play the VM and got the dreaded:
Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded.

Started troubleshooting this. Which led me to this page
http://unix.stackexchange.com/questions/99388/could-not-open-dev-vmmon-no-such-file-or-directory

which had this:
sudo vmware-modconfig --console --install-all

which I ran, which produced:

Stopping VMware services:
   VMware Authentication Daemon done
   VM communication interface socket family done
   Virtual machine communication interface done
   Virtual machine monitor done
   Blocking file system done
make: Entering directory '/tmp/modconfig-9bvFMI/vmmon-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/4.4.0-22-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/linux/driver.o
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/linux/hostif.o
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/common/memtrack.o
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/linux/driverLog.o
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/common/apic.o
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/common/vmx86.o
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/common/cpuid.o
/tmp/modconfig-9bvFMI/vmmon-only/linux/driver.c:1283:1: warning: always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/common/task.o
/tmp/modconfig-9bvFMI/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/modconfig-9bvFMI/vmmon-only/linux/driver.c:1981:1: warning: the frame size of 1168 bytes is larger than 1024 bytes [-Wframe-larger-than=]
 }
 ^
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/common/hashFunc.o
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/common/comport.o
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/common/phystrack.o
  CC [M] /tmp/modconfig-9bvFMI/vmmon-only/vmcore/moduleloop.o
  LD [M] /tmp/modconfig-9bvFMI/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC /tmp/modconfig-9bvFMI/vmmon-only/vmmon.mod.o
  LD [M] /tmp/modconfig-9bvFMI/vmmon-only/vmmon.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-22-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-9bvFMI/vmmon-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-9bvFMI/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory '/tmp/modconfig-9bvFMI/vmmon-only'
make: Entering directory '/tmp/modconfig-9bvFMI/vmnet-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/4.4.0-22-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/driver.o
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/hub.o
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/userif.o
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/netif.o
In file included from include/linux/pci.h:35:0,
                 from /tmp/modconfig-9bvFMI/vmnet-only/compat_netdevice.h:27,
                 from /tmp/modconfig-9bvFMI/vmnet-only/netif.c:43:
include/linux/pci_ids.h:2252:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
 #define PCI_VENDOR_ID_VMWARE 0x15ad
 ^
In file included from /tmp/modconfig-9bvFMI/vmnet-only/net.h:38:0,
                 from /tmp/modconfig-9bvFMI/vmnet-only/vnetInt.h:26,
                 from /tmp/modconfig-9bvFMI/vmnet-only/netif.c:42:
/tmp/modconfig-9bvFMI/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition
 #define PCI_VENDOR_ID_VMWARE 0x15AD
 ^
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/bridge.o
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/procfs.o
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/smac_compat.o
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/smac.o
In file included from /tmp/modconfig-9bvFMI/vmnet-only/net.h:38:0,
                 from /tmp/modconfig-9bvFMI/vmnet-only/vnetInt.h:26,
                 from /tmp/modconfig-9bvFMI/vmnet-only/bridge.c:52:
/tmp/modconfig-9bvFMI/vmnet-only/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
 #define PCI_VENDOR_ID_VMWARE 0x15AD
 ^
In file included from include/linux/pci.h:35:0,
                 from /tmp/modconfig-9bvFMI/vmnet-only/compat_netdevice.h:27,
                 from /tmp/modconfig-9bvFMI/vmnet-only/bridge.c:51:
include/linux/pci_ids.h:2252:0: note: this is the location of the previous definition
 #define PCI_VENDOR_ID_VMWARE 0x15ad
 ^
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/vnetEvent.o
  CC [M] /tmp/modconfig-9bvFMI/vmnet-only/vnetUserListener.o
  LD [M] /tmp/modconfig-9bvFMI/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC /tmp/modconfig-9bvFMI/vmnet-only/vmnet.mod.o
  LD [M] /tmp/modconfig-9bvFMI/vmnet-only/vmnet.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-22-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-9bvFMI/vmnet-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-9bvFMI/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory '/tmp/modconfig-9bvFMI/vmnet-only'
Starting VMware services:
   Virtual machine monitor failed
   Virtual machine communication interface done
   VM communication interface socket family done
   Blocking file system done
   Virtual ethernet failed
   VMware Authentication Daemon done

I have spend a few days, un-installing, re-installing, reformatting hard disk ans starting the system build again, LOTS of google searches, I keep comming back to this basic error.
Ripped everything out, restarted and this time followed

http://tutorialforlinux.com/2016/02/15/how-to-install-vmware-workstation-player-12-on-ubuntu-16-04-xenial-64bit-linux-visual-guide/

So then I went down the route of VirtualBox. Followed the instructions as best I could, got a VM setup and the tried to start it.

Got this error
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please install virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

So I did a sudo modprobe vboxdrv

and got this:
joe@joe-desktop:~/Downloads$ sudo modprobe vboxdrv
[sudo] password for joe:
modprobe: ERROR: could not insert 'vboxdrv': Required key not available

I am stuck.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Manfred Hampl
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Vboxdrv is for Virtualbox. Is there no scope to use Virtualbox instead of VMware?

Revision history for this message
Joe Willmann (jo2eph) said :
#2

Thanks for your response.

I tried to use VirtualBox instead of VmWare but I could not start the Virtual machine. I received the error listed here:;

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please install virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

That is when I did the
joe@joe-desktop:~$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available

All of the reading I did on this error had to do with secure linux, getting a keyring (public and private) setup and generating a lot of signed modules.

This just seemed like it was wrong for a basic Ubuntu install running Windows in a VM.

So I figure I had messed up something else earlier in the process and was off chacing unicorns and other false leads.

As far as you question: Vboxdrv is for Virtualbox. Is there no scope to use Virtualbox instead of VMware? I gave up on VmWare and started trying to get VirtualBox working instead and both paths led me to failure.

So asking for help.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Did you add your user to the vboxusers group then log off and on

Revision history for this message
Joe Willmann (jo2eph) said :
#4

Not there yet.

looked up vboxusers and found
http://askubuntu.com/questions/377778/how-to-add-users-to-vboxusers

Did an id
uid=1000(joe) gid=1000(joe) groups=1000(joe),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare)

No vboxuser group listed

So I ran
sudo usermod -a -G vboxusers $USER

logged out, rebooted, logged back in
ran

joe@joe-desktop:~$ id
uid=1000(joe) gid=1000(joe) groups=1000(joe),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare),129(vboxusers)

So now I am member of vboxusers

started VirtualBox, selected the Win 7 VM, hit start. Same error as before
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please install virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

Again tried joe@joe-desktop:~$ sudo modprobe vboxdrv
[sudo] password for joe:
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
joe@joe-desktop:~$

Same error as before.

Revision history for this message
Best Manfred Hampl (m-hampl) said :
#5

The problem probably is with the 'secure boot' feature of your BIOS, see also https://www.virtualbox.org/ticket/11577 or http://gorka.eguileor.com/vbox-vmware-in-secureboot-linux/

Revision history for this message
Joe Willmann (jo2eph) said :
#6

I wanted to confirm the hypothesis so I looked up how to disable the secure boot function of the BIOS. did the research and went to http://www.technorms.com/45538/disable-enable-secure-boot-asus-motherboard-uefi-bios-utility

Followed the instruction to save the keys and then delete them. I saved them because I want to try to turn secure boot back on but I thought that disabling it completely would be the simplest way to verify the theory.

After disabling and rebooting, ran VmWare and everything worked as it should!

Good job and thanks.

I'll make a separate test of Virtualbox after the WmWare windows install is complete.