Getting following stop error while creating windows 2016 in KVM based environment, then try mentioned steps.
Stop Error: “System Thread Exception Not Handled” <\/p>\n\n\n\n
Cause: Main cause of above error is unsupported CPU on your KVM node.<\/p>\n\n\n\n
Check VPS\/VM creation and boot logs on node. It should come with similar logs as follows.
<\/p>\n\n\n\n
SMP: Allowing 1 CPUs, 0 hotplug CPUs Try migrating the vm on another node which has better CPU model then this server. <cpu match =’exact’ Model=’host-model’><\/p>\n\n\n\n <model fallback=’allow’>core2duo<\/model> Regards. Getting following stop error while creating windows 2016 in KVM based environment, then try mentioned steps.Stop Error: “System Thread Exception Not Handled” Cause: Main cause of above error is unsupported CPU on your KVM node. Check VPS\/VM creation and boot logs on node. It should come with similar logs as follows. SMP: Allowing 1 CPUs, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[39,37],"tags":[],"class_list":["post-261","post","type-post","status-publish","format-standard","hentry","category-server-management","category-windows"],"jetpack_publicize_connections":[],"yoast_head":"\n
PM: Registered nosave memory: 000000000009d000 – 000000000009e000
PM: Registered nosave memory: 000000000009e000 – 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 – 00000000000f0000
PM: Registered nosave memory: 00000000000f0000 – 0000000000100000
Allocating PCI resources starting at 1f400000 (gap: 1f400000:e0bbc000)
Booting paravirtualized kernel on KVM
Detected CPU family 6 model 94<\/strong>
UNSUPPORTED HARDWARE DEVICE: Intel CPU model<\/strong>
————[ cut here ]————
WARNING: at kernel\/rh_taint.c:13 mark_hardware_unsupported+0x34\/0x40() (Not tainted)
Hardware name: KVM
Your hardware is unsupported. Please do not report bugs, panics, oopses, etc., on this hardware.
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.32-504.el6.x86_64 #1
Call Trace:
[] ? warn_slowpath_common+0x87\/0xc0
[] ? warn_slowpath_fmt+0x46\/0x50
[] ? mark_hardware_unsupported+0x34\/0x40
[] ? setup_arch+0xc46\/0xc69
[] ? printk+0x41\/0x44
[] ? start_kernel+0xdc\/0x430
[] ? x86_64_start_reservations+0x125\/0x129
[] ? x86_64_start_kernel+0x115\/0x124
—[ end trace a7919e7f17c0a725 ]—
NR_CPUS:4096 nr_cpumask_bits:1 nr_cpu_ids:1 nr_node_ids:1
PERCPU: Embedded 31 pages\/cpu @ffff880002200000 s95064 r8192 d23720 u2097152
pcpu-alloc: s95064 r8192 d23720 u2097152 alloc=1*2097152
pcpu-alloc: [0] 0
kvm-clock: cpu 0, msr 0:2216841, primary cpu clock
kvm-stealtime: cpu 0, msr 220e880
Built 1 zonelists in Node order, mobility grouping on. Total pages: 126045
Policy zone: DMA32
Kernel<\/p>\n\n\n\n
You can try to add following to virtual machine’s config file<\/p>\n\n\n\n
Hope that helps yo to fix your issue.<\/p>\n\n\n\n
24x7serversupport
<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"