win2012 guest freeze after trying to log in

[scrooge_74]

Hi,

being trying to find answers to this issue. We got a win2012 server running SAP business one as VM on a Debian Jessie host. As long as no one logs into the machine (either through RDP or on the host desktop) all is good. Client machines will work with no issues. Half of the time someone tries to log into the server it will freeze: no pings, no client connections, nothing. All that can be done is a guest poweroff and a restart (which sometimes entitle Windows complaining and that it needs a Save mode start ). After it will work for days with no issues as long as no one logs, but even that is not certain. We logged a couple of times during the weekend no issues, but when I did it this morning it froze.

Usually top will say CPU usage for the host is low and the process for that guest is 30% CPU with 25% of available RAM. When it freezes it will go to 105% of the allotted CPU but it will never come down again, hence the poweroff.

The Linux hosts keeps churning with no issues, in fact there is a Win2008 server also running there (needed to consult old stuff once a week or something) with no issues while the Win2012 freezes.

I have attached the log of one of those occurrences.

The moment of the freeze this is what I can see in the logs:

HyperV: Guest indicates a fatal condition! P0=0x3b P1=0xc0000005 P2=0x82b7920 P3=0x1136b040 P4=0x0

[socratis]

If you have enabled Hyper-V in your Win2012, disable it. Hyper-V requires VT-x, something which is not available for virtual machines. It's funny that it doesn't complain earlier (at boot). Or maybe it does, but you only see it when you log in.

[scrooge_74]

If you have enabled Hyper-V in your Win2012, disable it. Hyper-V requires VT-x, something which is not available for virtual machines. It's funny that it doesn't complain earlier (at boot). Or maybe it does, but you only see it when you log in.

At some point I read about disabling Hyper-V which I did about a week ago, but it did not improve the situation.

So two days ago I decided maybe my problems come from this VM being originally a real physical machine which we converted using the vmware desktop and we moved it back to the same server it came from, but now as a VM running on top of Linux. So I decided to make a fresh VM Win2012 server, and problems started to appear right after install.

Then, being at a lost I went and decided to just type in dmesg and found this:

VirtualBox[22659]: segfault at 20 ip 00007f4b23b285b0 sp 00007ffe1749fd10 error 4 in libxcb-image.so.0.0.0[7f4b23b26000+4000]
[1134262.952835] vboxdrv: ffffffffa0783020 VMMR0.r0
[1134263.203139] vboxdrv: ffffffffa0888020 VBoxDDR0.r0
[1134263.391403] vboxdrv: ffffffffa00f5020 VBoxEhciR0.r0

And this coincides with every instances of a crash.

So further reading told me this some kind of bug a while back and someone else posted about this on another thread viewtopic.php?f=2&t=78834, seems the solution is to downgrade the VirtualBox from 5.1 to 5.0 which is why I did last night.

So far today clients machines are connecting with no issues to the SAP database and I logged into the Win server with no issues (knocks on wood)

[scrooge_74]

Couple of weeks have gone by.

Solution is to use an older version of Virtualbox, so far no more issues. Did the same with another server last night, installed a previous version no issues, this one has a bigger load of users.