Opened 8 years ago
Last modified 8 years ago
#15207 new defect
Guest kubuntu freezes just after dektop completes loading (more often if loading while virtualbox is not in focus)
| Reported by: | Grief | Owned by: | |
|---|---|---|---|
| Component: | guest control | Version: | VirtualBox 5.0.16 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Hello there.
Host=Win10 x64 Guest=Kubuntu 16.04 x64 (I had the same issue with 15.10)
It is reproducible on kernel 4.0.X up to 4.4.4 at least.
Sometimes, after SDDM login desktop appears and freezes in second. I can move one window in that time or click a button but nothing more: virtual box freezes and closes after 4 or 5 tries. I mean, after click stop button it hangs completely and stops to respond.
I had this issue in 5.0.14, 5.0.15 and now in 5.0.16. I never had such problems with the OS running outside virtual box (I have raw image targetting whole SSD drive)
I didn't find anything interesting in VBox.log, but attached it though.
Oh! And one more thing - if virtualbox window is not minimized and doesn't lose focus during the whole boot procedure, chances to be frozen are decreased. It hangs in >80% of cases when the window loses focus during the boot and ~20% only when it stays focused.
Attachments (1)
Change History (5)
by , 8 years ago
| Attachment: | rocket-2016-03-05-15-38-57.log added |
|---|
comment:1 by , 8 years ago
Is the whole machine frozen or just the desktop? Setting up port forwarding to an SSH daemon on the guest and logging into that is a good test - if that works then the guest is not frozen. If it is the desktop, then you are probably best asking the KDE/SDDM people for help debugging in the first place (not least because I suspect based on our developer work loads that one of them will find time to help faster than we will.)
comment:2 by , 8 years ago
Hi Michael,
Sorry for the delayed answer. Yes, it is completely frozen, not only UI. But shame on me, I didn't try 'ssh test' before posting the issue, so thanks for the advice. Now I tried and I can say that SSH stops to work as well. However:
- Port accepts connection but there is no a single byte in response.
- VirtualBox.exe starts to consume 25% of CPU (one core) constantly at the moment of a hang. Forgot to mentinon that fact as well.
comment:3 by , 8 years ago
What I would like to add:
- It doesn't interact with network/disk or RAM at all while hung.
- Also, no new threads are spawned and no old ones are killed. I would like to attach screenshot from Process Explorer, But I guess it's useless :(
VBox.log