virtualbox.org

Hello,

It seems beta3 has a major regression. I'm not able to boot any Ubuntu 17.04 64 bit VM, not even the installation ISO. The VM crashes.

Guess may be win 10 specific. ubuntu 17.04 and 17.10 vms start fine here, on win 7 64
j

No problem here with 'ubuntu-17.04-desktop-amd64.iso'. Booted and installed just fine. Furthermore, your log does not show a crash, but a normal ACPI shutdown:

00:00:52.993650 ACPI: Entering S5 power state (power down)
00:00:52.993685 Changing the VM state from 'RUNNING' to 'POWERING_OFF'

Edit: Forgot host info, OSX 10.11.6

The VM definitely crashes. I can save the process memory, if required.
It must be sound related, the VM shows that the audio devices are disabled, output and input.

Can you try a couple of things to see if you can further pinpoint the source of the crash?

• Disable the audio in the VM.
• Disable the 3D acceleration.
• Set the Paravirtualization option to None.

With paravirtualization set to None, 3D and audio disabled - it doesn't crash. Re-enabling audio crashes the VM almost every time. There are also two extra options in Audio, Enable Audio Output and Input, which are not selected by default. Selecting both still leads to a crash.
Out of curiosity, does your Ubuntu VM have functional audio output?

mhanor wrote:Re-enabling audio crashes the VM almost every time.

So, it's the audio part that's crashing. I assume you re-enabled 3D acceleration and Paravirtualization set to Default.

mhanor wrote:There are also two extra options in Audio, Enable Audio Output and Input, which are not selected by default.

That's going to be the default for new VMs, the "paranoid" option, where the audio is enabled (as in an audio card will be presented to the guest), but the VM is going to be deaf and mute unless these options are explicitly enabled. For existing VMs, these two options will be enabled when upgrading.

mhanor wrote:Selecting both still leads to a crash.

Try to see further if it's the input or the output that's causing the problem. Also, I see that you have multiple inputs/outputs in your host, namely Realtek and Steam. See if disabling either on the host has any effect.

mhanor wrote:Out of curiosity, does your Ubuntu VM have functional audio output?

Audio output and input work just fine.

Taking a look again at your log, I saw the following:

00:00:30.363966 VMMDev: Guest Log: 00:00:00.000154 main
                Executable: /opt/VBoxGuestAdditions-5.2.0_BETA2/sbin/VBoxService

That tells me that you had this guest running with the beta 2 GAs installed. Can you repeat the tests with the live DVD to take also that factor out of the equation?

The initial VM is gone, take a look at the new VM log.
I don't see why audio would be disabled by default.

Me too.
Crash at shutdown client os KDE Neon.
But beta2 no this problem.

mhanor wrote:The initial VM is gone, take a look at the new VM log.
I don't see why audio would be disabled by default.

Would be really interesting to know that if you re-enabled 3D + Paravirtualization it still doesn't crash *if* audio is disabled.
Do you have a core dump of the crash available?

Please check your PM inbox, I've sent you a link with a core dump and the VM log.
The VM is a newly created VM with default settings, trying to boot the Ubuntu 17.04 64bit installation ISO. I can crash it almost every time. I rarely use 3D acceleration and the thread that's crashing doesn't seem to be related to 3D.

mhanor wrote:Please check your PM inbox, I've sent you a link with a core dump and the VM log.
The VM is a newly created VM with default settings, trying to boot the Ubuntu 17.04 64bit installation ISO. I can crash it almost every time. I rarely use 3D acceleration and the thread that's crashing doesn't seem to be related to 3D.

Cheers, thanks -- I'll have a peek at the dump.

You should be able to reproduce the problem inside a Windows 7 or a Windows 10 x64 VM, using a nested VirtualBox VM, booting the Ubuntu 17.04 32-bit installation ISO. At least, I'm able to do it. Under the Windows 10 guest, booting the installation ISO results in an identical crash dialog. Booting it under the Windows 7 guest, it reaches the GUI without crash, but crashes if I shutdown the VM. The crash dialog looks similar to Keelung's screenshot. At the beginning, I did't think Keelung's crash had anything to do with my crash.

Oh, this happens using a nested VBox installation? What's about running VBox on bare metal?

You misunderstood me. The problem occurs on my bare-metal PC (look at the core dump and the logs). I only attempted to reproduce the crash on a nested VM, which does occur.