Windows Server 2012R3 guest: BSOD
Hello, oVirt: 3.6.1 qemu: 2.3.0 I installed a Windows Server 2012R2 guest. The install is good, but when the guest boots into Windows, the Server 2012 version of the BSOD comes up,then goes to a "DOS" screen that has an error code '0xc0000001' I have tried using a VirtIO HDD and IDE; both result in the same error. Any ideas what the issue might be? CPU is Sandybridge, if that makes a difference. Regards, Alan
Hi, I will install in the next few days a new host where Windows Server 2012 R2 should run. On my test machine I had run qemu with the cpu "Westmere" to use Window Server 2012 R2, all other CPU's will bring a BSOD, reboot loop or other issues. Maybe this will help. regards gregor On 06/02/16 09:34, Alan Murrell wrote:
Hello,
oVirt: 3.6.1 qemu: 2.3.0
I installed a Windows Server 2012R2 guest. The install is good, but when the guest boots into Windows, the Server 2012 version of the BSOD comes up,then goes to a "DOS" screen that has an error code '0xc0000001'
I have tried using a VirtIO HDD and IDE; both result in the same error.
Any ideas what the issue might be? CPU is Sandybridge, if that makes a difference.
Regards,
Alan _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Gregor, Thank you for the response. On 06/02/2016 2:05 PM, gregor wrote:
On my test machine I had run qemu with the cpu "Westmere"
I changed the CPU for the Windows Server 2012 R2 VM from the default (Sandybridge) to "Westmere", but the same issue occurs :-( Regards, ALan
Hi, I installed oVirt 3.6 with the host CPU "Intel(R) Xeon(R) CPU E5-2603 v3 @ 1.60GHz". Installation and running of Windows Server Essentials 2012 R2 is possible. These settings have to change to use the VM. - Disk: Interface IDE - Network: Type e1000 Here I have no problem with the CPU type, the cluster is set by default to "Intel Haswell-noTSX Family". regards gregor On 08/02/16 17:20, Alan Murrell wrote:
Hi Gregor,
Thank you for the response.
On 06/02/2016 2:05 PM, gregor wrote:
On my test machine I had run qemu with the cpu "Westmere"
I changed the CPU for the Windows Server 2012 R2 VM from the default (Sandybridge) to "Westmere", but the same issue occurs :-(
Regards,
ALan
participants (2)
-
Alan Murrell -
gregor