Page 1 of 1
[Solved] Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 05:59
by jwythe@epicor.com
I just installed Windows 10 yesterday in a VirtualBox VM. Everything went fine, and I was able to install and boot windows 10 afterwords.
Today the VM won't start I get the VBox splash Screen, and then the Guru Mediation Window. Even If I try to create a new VM and boot of the ISO same thing happens now. Although takes a few seconds (get a few dots) before the Windows pops up.
Things I have done since it was running. Update CentOS with yum (including kernel) connected a new display and mouse.
I was running VirtualBox 5.1.22 with 5.1.18 Enhancements. have since tried 5.1.22 with 5.1.22 Enh. 5.1.30 with 5.1.30 Enh. and 5.2 with 5.2 Enh.
Changed the mouse and display back to what it was.
Have rebooted with the old kernel I was using (2.6.32-696.1.1.el6.x86_64) going to try going back to 2.6.32-696 as that was also on the system before.
Have tried going to USB 2.0 instead of 3.0
played with the ParaVirtualization settings, the EFI and PAE settings. nothing seems to make any difference.
I have a good Vbox.log of when it booted under 5.1.22. I am going to go back to 5.1.22/5.1.18 enh if going back to an earler kernel does not work.
If anyone can help and needs the .vbox/.log files I can upload.
Re: Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 06:10
by jwythe@epicor.com
P.S. Windows XP and Windows 7 VM's do not have an issue.
Re: Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 06:40
by socratis
- Follow a "start the VM from cold-boot" / "observe error" / "shutdown the VM" cycle.
- With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).
Re: Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 07:55
by jwythe@epicor.com
I found where The Good and The Dad logs differ, Now to find The Ulgy reason why. lol! Full log attached. Also noticed difference in the NX setting.
The Good
Code: Select all
00:00:03.927301 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f8df8000000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0
00:00:03.927418 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1024x768, Sending to async-handler
00:00:03.927495 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1024x768
00:00:03.927506 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1024x768
00:00:03.927522 GUI: UIFrameBufferPrivate::performResize: Size=1024x768, Directly using source bitmap content
00:00:11.634000 GIM: HyperV: Guest OS reported ID 0x1040a0000271b
00:00:11.634035 GIM: HyperV: Open-source=false Vendor=0x1 OS=0x4 (Windows NT or derivative) Major=10 Minor=0 ServicePack=0 Build=10011
00:00:11.634088 GIM: HyperV: Enabled hypercall page at 0x00000000002cd000
00:00:11.698618 GIM: HyperV: Enabled TSC page at 0x000000000000a000 - u64TscScale=0xda721300000000 u64TscKHz=0x2dc72a (3 000 106) Seq=1
00:00:11.698663 TM: Switching TSC mode from 'Dynamic' to 'RealTscOffset'
The Bad
Code: Select all
00:00:03.527160 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f2bc8ed9000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0
00:00:03.527277 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1024x768, Sending to async-handler
00:00:03.527369 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1024x768
00:00:03.527380 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1024x768
00:00:03.527397 GUI: UIFrameBufferPrivate::performResize: Size=1024x768, Directly using source bitmap content
00:00:03.708180 IEM: wrmsr(0xc0000080,0x0`00000d00) -> #GP(0)
00:00:03.711491 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:03.711513 Console: Machine state changed to 'GuruMeditation'
00:00:03.712169 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Re: Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 07:58
by jwythe@epicor.com
The Bad log file.
Re: Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 08:19
by jwythe@epicor.com
One other thing, I updated was the BIOS on the Physical system an IBM x3650 from version 1.1 to 1.9
I have run into an issue before with the Auto ReSize for the Display. Not sure if this is the same issue. If I remember correctly the previous issue was with the Display resizing on it's own once the system was up and running for a while.
Re: Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 08:28
by jwythe@epicor.com
I found this entry in the Bad. I wonder if updating the BIOS reset a setting for Virtulization
CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it!
Re: Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 08:33
by jwythe@epicor.com
This seems to provide some additional info.
I am going to check the BIOS.
Re: Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 08:56
by jwythe@epicor.com
Oh, This was the link.
https://www.virtualbox.org/ticket/14650
That was it. The Execute Disable Bit was disabled in the Advanced CPU Settings in the BIOS. Enabled it and all is good. Yahoo!
Re: Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 3. Dec 2017, 10:25
by socratis
Great, thanks for the feedback. Marking as [Solved].
Re: [Solved] Windows 10 Guru Medication CentOS 6 5.1.22/5.1.30/5.2
Posted: 7. Dec 2017, 10:37
by michaln
For unknown reasons, Intel made the NX feature optional and many BIOSes offer a way to disable it. It's not known what problem disabling NX solves, it's only known which problems disabling NX causes.