VirtualBox

Ticket #19642 (new defect)

Opened 18 months ago

Last modified 15 months ago

Virtualbox UI freezes after clicking VM in list and corresponding VM is not properly booting

Reported by: chrizzzt Owned by:
Component: other Version: VirtualBox 6.1.10
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

Observed behaviour:


When I start the VM with "vagrant up" (while having Virtualbox GUI open), the VM is created and booted in Virtualbox. Then vagrant hangs at the point, when it tries to access the VM via SSH in order to configure the VM. At the same time in Virtualbox, when I click on the VM in the list, the GUI of Virtualbox freezes and does not unfreeze anymore. I need to end the Virtualbox Manager Process in Windows Task manager in order to make Virtualbox work again. The Problem occurs with several Vagrant Boxes with recent Ubuntu versions (e.g. ubuntu/focal64, ubuntu/eoan64). It seems to work (at least most of the time) with older Ubuntu versions (e.g. ubuntu/trusty64).

I have the feeling that I experience problems with Virtualbox since upgrading Windows to 2004 (Spring 2020 Update) and/or enabling WSL2, but I cannot prove since I haven't used Virtualbox immediately before the upgrade / WSL 2 enabling.

Expected bahaviour:


The Virtualbox GUI does not freeze when I click on the VM in the list of VMs and Vagrant is able to finish the prozess of configuring the VM.

Additional Information:


  • Windows 10 Pro (2004, Spring 2020 Update)
  • Windows Subsystem for Linux (WSL) 2 enabled
  • Virtualbox 6.1.10 r138449 (Qt5.6.2)
  • Vagrant 2.2.9
  • Vagrant Box: ubuntu/focal64, 20200605.1.0

Attachments

VBox.log Download (74.5 KB) - added by chrizzzt 18 months ago.
Vagrantfile Download (1.1 KB) - added by chrizzzt 18 months ago.
VBox.2.log Download (81.6 KB) - added by twestendorp 18 months ago.
Basic_test_1591866123242_40462.vbox Download (3.3 KB) - added by chrizzzt 18 months ago.

Change History

Changed 18 months ago by chrizzzt

Changed 18 months ago by chrizzzt

Changed 18 months ago by twestendorp

comment:1 follow-up: ↓ 3 Changed 18 months ago by twestendorp

Happens on macOS 10.15.5 as well since VirtualBox 6.1.8.

I attached my log file, but am forced to strip my username and vm name because they contain company sensitive information.

Additional Information:

  • macOS 10.15.5
  • VirtualBox 6.1.10 r138449
  • Vagrant 2.2.9
  • Vagrant Box: ubuntu/xenial64, v20200605.0.0
Last edited 18 months ago by twestendorp (previous) (diff)

comment:2 follow-up: ↓ 4 Changed 18 months ago by gombara

Please try to reproduce the mentioned problem in vanilla VirtualBox, that is, not through Vagrant etc. Or file a bug report to Vagrant team. Vagrant is not developed and maintained by Oracle.

Last edited 18 months ago by gombara (previous) (diff)

comment:3 in reply to: ↑ 1 Changed 18 months ago by fbatschu

Replying to twestendorp:

Happens on macOS 10.15.5 as well since VirtualBox 6.1.8.


Could you please be more specific about what you experience when you say "Happens on macOS 10.15.5 as well"? Thanks.

Last edited 18 months ago by fbatschu (previous) (diff)

comment:4 in reply to: ↑ 2 Changed 18 months ago by chrizzzt

Replying to gombara:

Please try to reproduce the mentioned problem in vanilla VirtualBox, that is, not through Vagrant etc. Or file a bug report to Vagrant team. Vagrant is not developed and maintained by Oracle.

Hi gombara,

thanks for your reply. I just tried to reproduce the problem without involving Vagrant. After the freeze (and possibly failed VM boot), I needed to restart my system (as described above). Then I started Virtualbox again and started the VM (which was created by Vagrant initially, and still listed in the list in Virtualbox). After the VM booted, and some typical command line output appeared on the VM output, the output stopped and the Virtualbox UI freezed again.

This implies that either the VM itself or the configuration created by Vagrant is causing the issue (not Vagrant itself). I added the config file in the attachments.

I'm not sure, how we can enable you to reproduce the problem on your side, without having to send the whole VM (1,2 GB).

My suggestion for further bug analysis would be therefore to

  • analyse the configuration created by Vagrant
  • quickly install vagrant on your system and reproduct the issue
  • Check Virtualbox forum/bug reports for similar observations

Looking forward to your ideas/suggestions!

best,

Christoph

Changed 18 months ago by chrizzzt

comment:5 Changed 16 months ago by twestendorp

Just upgraded to VirtualBox 6.1.12 r139181 and the issue is still present. Tried starting the VM from Vagrant but also from VirtualBox itself, but no difference.

As mentioned before, the command line output produces some output and than stops and completely freezes the UI and booting fails.

Last edited 16 months ago by twestendorp (previous) (diff)

comment:6 Changed 16 months ago by matthewstrasiotto

I'm also encountering this on:

VirtualBox 6.1.12 r139181 Vagrant 2.2.9

Vagrant Box: ubuntu/focal64

I find a "normal" virtualbox install of focal fossa (from iso image) works just fine.

It sounds like my best bet will be to install VirtualBox 6.1.6 and go from there

(The old 6.1 build page is a little tricky to find, so here's a link https://www.virtualbox.org/wiki/Download_Old_Builds_6_1 )

Thus far, I haven't seen this issue documented in vagrant, so I may raise this ticket (And link to here) on there.

Last edited 16 months ago by matthewstrasiotto (previous) (diff)

comment:7 Changed 15 months ago by Cito

The most likely reason for this problem is that you have WSL 2 (WSL plus the "Virtual Machine Platform" feature) installed. According to my experience and reports by others it cannot coexist with VirtualBox - see also  https://github.com/MicrosoftDocs/WSL/issues/798.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use