Guest hangs from GUI

Discussions about using Linux guests in VirtualBox.
Post Reply
ctgscott
Posts: 1
Joined: 8. Feb 2019, 22:08

Guest hangs from GUI

Post by ctgscott »

Hi all,

I am trying to boot a Homestead-7 box and am struggling. After identifying that the vagrant boot methods were not working I moved the troubleshooting to vbox gui. Starting it manually, the guest homestead-7 box begins booting and then hangs before showing any output on the virtual screen. Below are the last few lines of the log file and I have attached the full log file. I then created a new box with the same attributes and using the same virtual disk as Homestead and it boots perfectly. I have gone through all the settings (including virtualization, storage, cpu... etc), particularly the ones I thought likely to cause a box to fail at what appears to be the screen or GUI sizing. Starting in 'headless' hangs also.

Any thoughts? My apologies for calling on your expertise. I have worked hard to sort this out myself.

Here is the last bit of log file when starting with a screen

Code: Select all

00:00:06.811552 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0
00:00:06.811613 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=720x400, Sending to async-handler
00:00:06.811680 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=720x400
00:00:06.811688 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=720x400
00:00:06.811704 GUI: UIFrameBufferPrivate::performResize: Size=720x400, Directly using source bitmap content
Attachments
homestead-7-2019-02-08-12-11-04.log
(84.39 KiB) Downloaded 16 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Guest hangs from GUI

Post by socratis »

Vagrant is a program that relies on VirtualBox, but modifies its configuration files in unknown ways to us, and with unknown consequences, especially the networking part. It is not supported on these VirtualBox forums/channels, they have their own Vagrant support channels. If you are having this problem with a standalone version of VirtualBox (after a complete uninstallation of Vagrant), then we can continue this discussion.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply