virtualbox.org

I have started to experience the Windows guest hanging at startup. Sometimes the guest starts fine but more often than not it just hangs around the point prior to the user login screen.

I have tried as many options of screen memory, usb etc. as I can set but cannot seem to figure out teh problem.

I do have other Windows 10 guests that start fine.

I've attached a log - can anyone point me in the right direction as to possible causes or diagnostic steps?

Update:

I set the USB settings for the Guest to USB 1,1 (OHCI) and this seems to have resolved the problem.

Did the log really terminate there, or did you grab the log while the VM was still running? We need complete logs where possible (zip them before attaching).

Despite the truncated log I'm not inclined to believe that VBox locked up, mostly because the last line in the log is "00:00:49.057041 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago". The entry before that comes 10 seconds earlier, so I'm not sure this is a VirtualBox problem at all.

Have you tried a filesystem check on the host? I see the VM is located on drive E, what kind of drive is that?

TJM_UK wrote:I set the USB settings for the Guest to USB 1,1 (OHCI) and this seems to have resolved the problem.

IMHO, better to disable USB altogether rather than ask Win10 to use a USB1 device.

@mpack

The system hangs up so I have to POWER OFF the VM. I then grabbed the log. I assume the VM becomes unresponsive and reports that in the log via the heartbeat message.

I have a number of Windows 10 VM's and they now all seem to experience the issue so I don't know if its part of a recent VB release.

Setting USB to 1.1 seems to have resolved the issue on all VM's. Drive E is just a partition on the same physical drive running the host.

Would it help if I send logs on a start of the VM with USB set to 1.1 and then setting to 2.0 and recording another log?

Unfortunately it has happened again. This time I suspended the guest and uploaded the logfile.

I'm not even convinced there's a problem. You have a Win10 guest running with one core, I've seen Win10 struggle with that kind of limitation before. How long do you give it to see if it's really hung, and what is the host doing during that time? I mean if a Win10 host and Win10 guest are both fighting on the same day to access the same update server through the same wireless connection, then there might well be some slowness.

Another thing that concerns me is this :-

00:02:05.120068 VMMDev: Guest Log: VBoxMP::DriverEntry: 3D is NOT supported by the host, falling back to display-only mode..

Which kind of implies that host graphics capability is very basic. What is the graphics chipset?

Plus, you seem to have bridged to a wireless LAN. VirtualBox allows it, but it's somewhat outside of the wireless spec. Is there a reason you aren't using NAT?

Thank you for the replies and taken time to help.

I have just updated to VB 5.1.10r112026 and thus far all my various VM's (Windows 7 / Win 10 mix) are starting with no issues. I don't know if that is a coincidence or not.

To answer the last questions:

I'm not using NAT because I need to access a share within a VM guest from a laptop on the same network. I'm sure that didn't work unless I set the guest up as a bridged adapter.

The graphics chipset on the host is a GeForce GT 620. I know that's perhaps not wonderful but its more than enough for the office type applications I run.

Tim.