This is for discussing general topics about how to use VirtualBox.
dargaud
Posts: 16 Joined: 10. Jul 2012, 15:26
Post
by dargaud » 27. Sep 2015, 17:18
Hello all,
I had a snafu trying to increase the size of one of my VMs, and now none of them work. Trying from backup fails. Trying importing a working .ova fails. Even erasing them all, creating a new one WITHOUT HD and trying to start it results in:
Code: Select all
Failed to open a session for the virtual machine test.
The virtual machine 'test' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
What is going on ?!? How do I completely clear VirtualBox settings ? I removed ~/.VirtualBox and ~/VirtualBox VMs/ and still it fails launching an empty test VM. Host is Ubuntu 64.
loukingjr
Volunteer
Posts: 8851 Joined: 30. Apr 2009, 09:45
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: just about all that run
Post
by loukingjr » 27. Sep 2015, 17:24
You removed the folder that contains all your VMs??? i.e. ~/VirtualBox VMs
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
dargaud
Posts: 16 Joined: 10. Jul 2012, 15:26
Post
by dargaud » 27. Sep 2015, 17:55
Well I removed the VMs from the interface, so the directory ended up empty; I then created a new empty VM and still that failed.
loukingjr
Volunteer
Posts: 8851 Joined: 30. Apr 2009, 09:45
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: just about all that run
Post
by loukingjr » 27. Sep 2015, 17:58
I have no idea what an "empty VM" is or how it would start seeing it's empty. But that's just me.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
dargaud
Posts: 16 Joined: 10. Jul 2012, 15:26
Post
by dargaud » 27. Sep 2015, 20:36
Create new VM, do not define a HD. At least you should see the pseudo BIOS message. It fails before that.
loukingjr
Volunteer
Posts: 8851 Joined: 30. Apr 2009, 09:45
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: just about all that run
Post
by loukingjr » 27. Sep 2015, 20:49
dargaud wrote: At least you should see the pseudo BIOS message.
Why? You decided this based on…?
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
dargaud
Posts: 16 Joined: 10. Jul 2012, 15:26
Post
by dargaud » 27. Sep 2015, 21:04
Fine. If I attach some simple LiveCD iso, same thing, it fails before it displays anything.
loukingjr
Volunteer
Posts: 8851 Joined: 30. Apr 2009, 09:45
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: just about all that run
Post
by loukingjr » 27. Sep 2015, 21:07
That's actually never happened to me in 6 years.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
dargaud
Posts: 16 Joined: 10. Jul 2012, 15:26
Post
by dargaud » 28. Sep 2015, 08:10
I noticed that the vboxdrv service was dead (even after a reboot), so I started it manually and, surprise, I could start my VMs. As to why it dies...:
Code: Select all
[ 5.412505] systemd-sysv-generator[294]: Overwriting existing symlink /run/systemd/generator.late/vboxdrv.service with real service
[ 89.480926] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 98.327381] VirtualBox[2879]: segfault at 1d0 ip 00007fe7d2ec6b34 sp 00007ffee6f95940 error 4 in VirtualBox.so[7fe7d2d5f000+8a1000]
[ 113.439396] VirtualBox[2909]: segfault at 1d0 ip 00007f45df5d9b34 sp 00007ffc1133d350 error 4 in VirtualBox.so[7f45df472000+8a1000]
[ 152.414578] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[ 152.417345] vboxdrv: Found 8 processor cores
[ 152.433272] vboxdrv: TSC mode is Invariant, tentative frequency 2691679100 Hz
[ 152.433275] vboxdrv: Successfully loaded version 5.0.4 (interface 0x00240000)
[ 152.637686] VBoxNetFlt: Successfully started.
[ 152.638973] VBoxNetAdp: Successfully started.
[ 152.640192] VBoxPciLinuxInit
[ 152.641963] vboxpci: IOMMU not found (not registered)
[ 158.750547] vboxdrv: ffffffffc0ae2020 VMMR0.r0
[ 158.857199] vboxdrv: ffffffffc0000020 VBoxDDR0.r0
[ 158.860199] vboxdrv: ffffffffc001e020 VBoxDD2R0.r0
[ 158.890928] VBoxNetFlt: attached to 'eth0' / f0:1f:af:38:6c:e3