Page 1 of 1

VB locks up in Ubuntu 15.10

Posted: 13. Dec 2015, 19:10
by xen82
I am in a Windows 10 system.

I have had AMD-V enabled in my BIOS and installed Ubuntu x64 guest (15.10).

System runs correctly and I can install Guest Additions.

And then usually within 10 minutes of actually using the system -- I am in fullscreen mode the two times this has happened now -- my system locks up; the guest doesn't respond anymore but I *also* cannot get back to Windows, so VirtualBox in its entirety locks up.

I am on a Six-core FX 6300 and I had 3 cores available to the VM at 90% max. I am going to try to install a 32-bit Ubuntu with no AMD-V to see if that changes things.

But is this something people recognise? I cannot use the system in this way. I was hoping to do some.... well whatever, but right now it is failing. The first time it happened I was able to get into the Process Manager and kill the VB process. The second time I wasn't so "lucky". The "bar" at the bottom of the screen that usually pops up with options (for the virtual machine) also doesn't pop up anymore. The entire thing just freezes.

It's not that my Windows system is actually frozen (for real) but I cannot get back to it because the VB process apparently still claims the foreground window.

This is the final content of my log file, I don't know what else:
00:26:53.350629 VMMDev: SetVideoModeHint: Got a video mode hint (1920x1080x32)@(0x0),(1;0) at 0
00:26:53.356876 VBVA: InfoScreen: [0] @0,0 1920x1080, line 0x1e00, BPP 32, flags 0x1
00:26:53.356982 Display::handleDisplayResize: uScreenId=0 pvVRAM=000000000c2f0000 w=1920 h=1080 bpp=32 cbLine=0x1E00 flags=0x1
00:26:53.357161 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1920x1080, Sending to async-handler
00:26:53.364201 VBVA: InfoScreen: [0] @0,0 1920x1080, line 0x1e00, BPP 32, flags 0x1
00:26:53.372070 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=800x600
00:26:53.372113 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=800x600
00:26:53.372145 GUI: UIFrameBufferPrivate::performResize: Size=800x600, Directly using source bitmap content
00:26:53.375740 VBVA: InfoScreen: [0] @0,0 1920x1080, line 0x1e00, BPP 32, flags 0x1
00:26:53.618844 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1920x1080
00:26:53.619729 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1920x1080
00:26:53.619743 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1920x1080
00:34:48.870755 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
00:34:49.025852 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
Regards, X.

Re: VB locks up in Ubuntu 15.10

Posted: 13. Dec 2015, 20:01
by loukingjr
It's best to post the entire vbox.log as an attachment.

With the VM fully shut down, right click its icon in the VirtualBox Manager, select "Show Log" and save "VBox.log" to a zip file. Attach the zip here.

Re: VB locks up in Ubuntu 15.10

Posted: 13. Dec 2015, 21:19
by xen82
This is from the same attempt as last time.

Ubuntu 32-bit won't show me the desktop right, not sure what is going on. But this is from Ubuntu 64-bit:

<file>

Re: VB locks up in Ubuntu 15.10

Posted: 14. Dec 2015, 02:07
by xen82
So what should I do? I want to do some Linux programming, but.

I have an AMD software RAID that is supported by Linux but not by Grub, apparently; and I can't boot from it.

I was hoping to use Virtual Machines ONLY but if they don't work, that strategy suddenly goes to the wastebin.

I must say Windows XP 32-bit as guest did run without problems. Windows 98SE gave problems but certainly no locking up of the program itself, nor the guest.

Normally you can (with VirtualBox) I believe install a system (Linux) on real partitions and then run that as a VM from the host, but in this case that either won't make a difference, and I won't be able to boot from it.

I don't even know why Linux fails to boot off the RAID, maybe Grub does function, but the process freezes somewhere; obviously I won't have logs. I shall ask on the AMD forums.

I could, without issue, probably, turn my 4 disk RAID 10 into a 2 disk RAID 0, then I will have 2 disks leftover. But that's not really what I want, JUST to run Linux.

Maybe Windows 10 is to blame, it's not like the system actually functions well.

Sigh.

Re: VB locks up in Ubuntu 15.10

Posted: 14. Dec 2015, 02:23
by Perryg
Is this log from a session that actually locked up?

Re: VB locks up in Ubuntu 15.10

Posted: 14. Dec 2015, 10:55
by xen82
Yes, but obviously if the entire program freezes there might not be anything worthwhile in it.

Re: VB locks up in Ubuntu 15.10

Posted: 14. Dec 2015, 15:14
by Perryg
I can't see a reason why the host raid would come into play here and might be taking you down the wrong road as far as diagnosing the problem.
00:00:03.587096 NumCPUs <integer> = 0x0000000000000003 (3)

00:00:04.194926 CPUM: Logical host processors: 6 present, 6 max, 6 online, online mask: 000000000000003f
00:00:04.195103 CPUM: Physical host cores: 3
I do see something that could be an issue though. Try using 2 CPUs instead of 3 and see if it becomes more stable,

VirtualBox only deals with true cores and you only have three so assigning all of them to the guest could cause your issue.

Note: AMD claims that you have 6, I know but they are already in trouble for this claim and even has a class act against them to properly identify the cores/threads.

Re: VB locks up in Ubuntu 15.10

Posted: 14. Dec 2015, 15:18
by loukingjr
Just to add, I just read yesterday from one side of their (AMD's) mouth they say six cores, and from the other they say it has multi-threading. Bad AMD.

Re: VB locks up in Ubuntu 15.10

Posted: 14. Dec 2015, 18:33
by xen82
I guess there are three groups of people, those that can count, and those that cannot.

I will try to run it with 2 cores but I won't run it fullscreen for a while to see if the same thing happens; I might be able to escape from it.

I'll update this post later to relate. Thus far no lock-up, but I'm running it maximized, not Host-F fullscreen. I hesitate to put it to the full test, so I will keep it running in the background and maybe perform some duties in this maximized condition. I will report back later what it does in Fullscreen condition when I have nothing to lose.

Well the thing has been running for quite some time without me doing much in it. I haven't run it Fullscreen much but there also hasn't been a problem. I guess the 3 to 2 core thing solved it? Amazing? I'll report later after I've done my fullscreen stuff.