VirtualBox

Opened 6 years ago

Last modified 6 years ago

#18261 new defect

VM self-terminates during first boot after install (Virtualbox 6.0 MacOS Mojave 10.14.2 Host, Ubuntu 18.04.1 Guest)

Reported by: 0x7766 Owned by:
Component: host support Version: VirtualBox 6.0.0
Keywords: 6.0 crash ubuntu Cc:
Guest type: Linux Host type: Mac OS X

Description

Not long before the ubuntu login screen would be reached, the VM stops with an error alert box showing (not pointing to anything in particular).

Second boot works fine. I observed this twice.

Attachments (1)

VBox.log.1 (138.1 KB ) - added by 0x7766 6 years ago.

Download all attachments as: .zip

Change History (3)

by 0x7766, 6 years ago

Attachment: VBox.log.1 added

in reply to:  description comment:1 by 0x7766, 6 years ago

Replying to 0x7766:

Not long before the ubuntu login screen would be reached, the VM stops with an error alert box showing (not pointing to anything in particular).

Second boot works fine. I observed this twice.

Guest install Settings:

Minimal install

Update while installing on

3rd party graphics wifi etc - install

15gb fixed size vdi

comment:2 by Socratis, 6 years ago

It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help you, me, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

I'm on OSX 10.11.6 on a MacBookPro11,5 and running several Ubuntu VMs, including an 18.04 one. The differences that we have between our VMs are:

  • 1536 MB RAM.
  • 128 MB VRAM, VBoxVGA, 3D enabled.
  • USB3

From all of these my hunch would lead me to point to the RAM as being the culprit; 1024 MB might not be enough for a 64-bit guest, even if it's a low-requirement one. Try changing these settings one-by-one and see if/when your issue gets resolved.

PS. For future reference, you should follow a "start the VM from cold-boot" / "observe problem" / "shutdown the VM" cycle, before grabbing the VBox.log. It's rather incomplete otherwise...

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use