Failing to start any vms on ubuntu 19.10

[seif]

Hi,

I've had virtualbox running previously on my machine. I've recently updated to ubuntu 19.10 and now I can't start any virtual machines.

running VBoxManage startvm says machine is successfully started but I then get a dialog about an error starting up. I've attached the file with the logs. Any help would be appreciated,.

[ModEdit: HTML based document deleted]

[scottgus1]

That log seems to be an HTML document. Try again?

[socratis]

The way to grab a complete VBox.log, from a complete VM run, where the problem occurs, is:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response.

[seif]

Thanks, attaching correct file this time.

[scottgus1]

A very easy way to get help is to do a search in a web browser, using the CAPITALIZED_UNDERSCORE_SPACED_WORDS, with the text "site:forums.virtualbox.org" added to restrict searching to this forum, like this:

VERR_INVALID_STATE site:forums.virtualbox.org

VERR_INVALID_STATE seems to mean different things, and looking about in the log may help.
Here's what the log says you have installed:

00:00:00.920941 VirtualBox VM 6.0.14_Ubuntu r132055 linux.amd64

The actual downloaded file from http://www.virtualbox.org is called:

virtualbox-6.0_6.0.14-133895_Ubuntu_bionic_amd64

I've been guessing wrong on whether folks have official or distro-forked Virtualbox installed lately, so I'll just ask: Did you install Virtualbox on your host PC or was it there already?

Seems there might be some video glitches?

00:00:01.286545 VMSVGA3d: cap[82]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC4_UNORM}
00:00:01.286546 VMSVGA3d: cap[83]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC5_UNORM}

Try turning off 3D acceleration?

Not the cause of the problem, but Windows 10 will be happier with two cores, and your host can spare them.

00:00:00.976959   NumCPUs           <integer> = 0x0000000000000001 (1)
00:00:01.209456 CPUM: Physical host cores: 4

Maybe an unusual Extension Pack?

00:00:00.926845 Installed Extension Packs:
00:00:00.926857   VNC (Version: 6.0.14 r132055; VRDE Module: VBoxVNC)

Try removing this and see what happens?

[seif]

Thanks scottgus1, didn't find anything useful when searching... Some people suggested too much memory being allocated, tried reducing that and it didn't help.

I tried all the things you suggested, same result.

I had installed virtualbox from the ubuntu multiverse repository. I just removed it and tried installing the package from virtuabox.org, that failed to install with the error:

dpkg: dependency problems prevent configuration of virtualbox-6.0:
 virtualbox-6.0 depends on libvpx5 (>= 1.6.0); however:
  Package libvpx5 is not installed.

ubuntu 19.10 (eoan) has libvpx6

Anything else I can look at? info that could help?

I've attached the log again after the changes made.

[scottgus1]

I'm a Windows guy, not heavy in Linux yet. But I suppose that libvpx5 isn't libvpx6, like Python 2.7 isn't Python 3.5. Maybe?

Try installing libvpx5.

FWIW, the Downloads page lists the latest Ubuntu for VirtualBox to run on as 19.04. Maybe 19.10 is a bit too fresh? Try a test build?

[seif]

Thanks, tried the test build, I managed to install it but it still doesn't work. Same error as when using virtualbox from the ubuntu multiverse package. Tried bothin the 6.0.x test build and development build of 6.1, both error the same way

[scottgus1]

What happens when you try a fresh new guest?

[seif]

The logs i'm putting are from a brand new guest. Same output regardless of what operating system I chose for the guest

[scottgus1]

Only thing I can guess for now is that 19.10 isn't supported yet. It will be soon, though, for sure. Keep trying test builds, and maybe someone else will have a different suggestion.

[gerryg]

Yeah, I suspect it's not yet supported. I came here after first failing to install a ubuntu 19.10 VirtualBox guest on a ubuntu 18.04 host. I then downloaded a VirtualBox prebuilt 19.10, and that also failed. My other VB guests are all working fine.

[socratis]

Ubuntu 19.10 is not supported yet. Your best, your only option at the moment is to install the "All distributions" build, the last one on the list.

I've been guessing wrong on whether folks have official or distro-forked Virtualbox installed lately

The first line of a VBox.log will tell you if it's the fork or not. Example:

Official VirtualBox

00:00:01.392519 VirtualBox VM 6.1.0_BETA2 r134346 linux.amd64 (Oct 30 2019 15:20:04) release log
00:00:02.844667 VirtualBox VM 6.0.12 r133076 linux.amd64 (Sep  3 2019 12:51:52) release log

Forked VirtualBox

00:00:00.920941 VirtualBox VM 6.0.14_Ubuntu r132055 linux.amd64 (Oct 17 2019 07:24:16) release log

As for the filenames in (for example) http://download.virtualbox.org/virtualbox/6.0.14/ they designate the Host distro/version.

[scottgus1]

Thanks, Socratis! I'll keep these examples in mind. The index site should help me as well.

[richp]

upgrading my linux kernal to 5.3 (inline with ubuntu) did the trick