Page 1 of 1
The CPU has been disabled by the guest operating system
Posted: Mon Jul 23, 2018 1:32 am
by laith7s
Hi ,I installed CHR on ESXi 6 and activate the license unlimited and everything was ok until a week ago ,everyday the CHR stopped working and when i see the event i got message "The CPU has been disable by the guest operating system " so what can I do for that problem ,please help
Re: The CPU has been disabled by the guest operating system
Posted: Mon Jul 23, 2018 12:08 pm
by laith7s
any idea for that problem ?
Re: The CPU has been disabled by the guest operating system
Posted: Mon Jul 23, 2018 4:13 pm
by Chupaka
So, what's in Log after you reboot the machine?
Re: The CPU has been disabled by the guest operating system
Posted: Mon Jul 23, 2018 5:39 pm
by laith7s
well, if u mean log in mikrotik CHR well there's nothing because i reset the CHR and before reset CHR is like freezing !! and on ESXi also nothing say and work again like nothing happend !! its realy confusing !
Re: The CPU has been disabled by the guest operating system
Posted: Mon Jul 23, 2018 7:00 pm
by Chupaka
there's nothing because
Is it what you think or what you saw?
Also, what version do you use?
Re: The CPU has been disabled by the guest operating system
Posted: Mon Jul 23, 2018 7:04 pm
by laith7s
for first time i used 6.39 and still the problem and before 2 days ago upgraded the routerOS to 6.42.6 and still same problem , and saw nothing in log !
Re: The CPU has been disabled by the guest operating system
Posted: Tue Jul 24, 2018 5:32 pm
by laith7s
anyone can help me !?
Re: The CPU has been disabled by the guest operating system
Posted: Sat Jul 28, 2018 1:37 pm
by laith7s
is it CHR not compatible with ESXi 6 ?
Re: The CPU has been disabled by the guest operating system
Posted: Sat Jul 28, 2018 6:10 pm
by Sob
I don't know if it's your case, but I've seen CHR stopping when it didn't have enough memory. I originally had VMs with 128MB, but CHR got a little bit more hungry over the time.
Re: The CPU has been disabled by the guest operating system
Posted: Mon Jul 30, 2018 3:37 pm
by Steveocee
is it CHR not compatible with ESXi 6 ?
CHR is certainly compatible with ESXi 6 and 6.5(u2).
You must surely have some log files purporting to this?
Re: The CPU has been disabled by the guest operating system
Posted: Sun Aug 05, 2018 5:11 pm
by laith7s
I don't know if it's your case, but I've seen CHR stopping when it didn't have enough memory. I originally had VMs with 128MB, but CHR got a little bit more hungry over the time.
well i don't have any problem with memory only cpu and disabled for unknown reason to me !! thanks for your answer
Re: The CPU has been disabled by the guest operating system
Posted: Sun Aug 05, 2018 5:13 pm
by laith7s
is it CHR not compatible with ESXi 6 ?
CHR is certainly compatible with ESXi 6 and 6.5(u2).
You must surely have some log files purporting to this?
that's my real problem only that log the "The CPU has been disabled by the guest operating system" i have so and i don't know why cpu disabled !
Re: The CPU has been disabled by the guest operating system
Posted: Mon Aug 06, 2018 1:21 am
by Kindis
Re: The CPU has been disabled by the guest operating system
Posted: Mon Aug 06, 2018 8:22 am
by Steveocee
When you say you have just installed CHR, do you mean you’ve used the premade OVA from MikroTik or you have used an ISO to install or how have you done it?
Googleing the problem refers you to the VMware help center and the general consensus is it is caused by a kernel panic in the guest.
So how have you deployed it?
Re: The CPU has been disabled by the guest operating system
Posted: Wed Aug 08, 2018 6:43 pm
by laith7s
well thanks ,but no not helping
Re: The CPU has been disabled by the guest operating system
Posted: Wed Aug 08, 2018 6:45 pm
by laith7s
When you say you have just installed CHR, do you mean you’ve used the premade OVA from MikroTik or you have used an ISO to install or how have you done it?
Googleing the problem refers you to the VMware help center and the general consensus is it is caused by a kernel panic in the guest.
So how have you deployed it?
deployed as OVA from mikortik ,is that effect on cpu and may be disable it ?
Re: The CPU has been disabled by the guest operating system
Posted: Wed Aug 08, 2018 10:11 pm
by Steveocee
How many CPU's are you assigning to the CHR installation? What happens if you set just 1?
Re: The CPU has been disabled by the guest operating system
Posted: Thu Aug 09, 2018 3:53 pm
by laith7s
How many CPU's are you assigning to the CHR installation? What happens if you set just 1?
CPU is 32 and ram 8G ,i didn't try 1 CPU cause i have more than 1 Gbps traffic
Re: The CPU has been disabled by the guest operating system
Posted: Thu Aug 09, 2018 7:36 pm
by Steveocee
ESXi on the free license will only allow up to 8 vCPUs, have you paid for ESXi? Usually ESXi would not start the VM and tell you to pay for it but maybe you’re getting a weird behaviour?
How many CPUs are you allocating?
Re: The CPU has been disabled by the guest operating system
Posted: Sat Aug 11, 2018 6:34 pm
by laith7s
ESXi on the free license will only allow up to 8 vCPUs, have you paid for ESXi? Usually ESXi would not start the VM and tell you to pay for it but maybe you’re getting a weird behaviour?
How many CPUs are you allocating?
yes i already paid for ESXi and CHR
Re: The CPU has been disabled by the guest operating system
Posted: Sat Aug 11, 2018 7:52 pm
by Steveocee
If you run maybe 2 cores do any get disabled?
Re: The CPU has been disabled by the guest operating system
Posted: Mon Aug 13, 2018 5:27 pm
by laith7s
If you run maybe 2 cores do any get disabled?
well i didn't try for 2 core ,i used to 32 core and get disabled don't know why and seems mikrotik also didn't have a solutions !
Re: The CPU has been disabled by the guest operating system
Posted: Wed Sep 12, 2018 3:06 pm
by videnov
We are hit with the same problem: The CPU has been disabled by the guest operating system. 4 times in the last week or so.
Is there any way to get the kernel panic message?
Re: The CPU has been disabled by the guest operating system
Posted: Fri Sep 14, 2018 12:01 am
by Kindis
Many do this and send to mikrotik. So they can troubleshoot.
https://kb.vmware.com/articleview?docid=2000542
Re: The CPU has been disabled by the guest operating system
Posted: Mon Sep 24, 2018 1:24 pm
by jarda
I also face this problem for few last days. Chr 6.43.2 in vmware workstation with 1cpu /2cores in virtual host is once per day switched of because of this. At the moment I have removed one core hoping that the ros will not try to disable the last core it has.
Is there a ticket created at mikrotik for this? Has anyone got any response from support?
Re: The CPU has been disabled by the guest operating system
Posted: Mon Dec 03, 2018 7:32 pm
by dmayan
Same problem here on 6.42.9
1 gbps of traffic. ESXI 6.7 with vCenter.
2 Cores and 512mb of RAM
Any words from Mikrotik?
thanks
Re: The CPU has been disabled by the guest operating system
Posted: Mon Dec 03, 2018 10:36 pm
by schadom
We've encountered this particular error message already with other VMs after kernel panics occurred. As a workaround, you could try to edit the CPUID mask settings and check if the CHR-VM might boot again:
https://docs.vmware.com/en/VMware-vSphe ... 78CEA.html
Re: The CPU has been disabled by the guest operating system
Posted: Wed Apr 10, 2019 5:00 pm
by msandon
Hi,
I am facing the same problem.
I set up the CHR router by following this guide:
https://wiki.mikrotik.com/wiki/Manual:CHR .
I have a licensed VMware and a CHR with P1 license. After having used it for 4 days it freezed without showing any log. VMware only displayed "The CPU has been disabled by the guest operating system".
The CHR has 2 CPU, 4GB RAM and 4GB disk storage. 6.43.13 is the version of VMware disk image.
Did someone find any solution to this problem?
Have I set up the machine with wrong parameters?
Thanks
Re: The CPU has been disabled by the guest operating system
Posted: Mon Apr 29, 2019 10:11 pm
by karwos
Guys, disable conn tracking and problem will gone.
It's been known for a long time. It dies once DDOS kicks in. They not fixed that, but I can confirm disabling conntracks not causing CPU to go offline and machine halt.
Re: The CPU has been disabled by the guest operating system
Posted: Thu Jun 13, 2019 10:59 am
by msandon
Guys, disable conn tracking and problem will gone.
It's been known for a long time. It dies once DDOS kicks in. They not fixed that, but I can confirm disabling conntracks not causing CPU to go offline and machine halt.
If disabling conn tracking will disable NAT, what kind of router is it??
Re: The CPU has been disabled by the guest operating system
Posted: Sun Jun 16, 2019 12:58 pm
by Chupaka
If disabling conn tracking will disable NAT, what kind of router is it??
A router without NAT is definitely not a home router
Re: The CPU has been disabled by the guest operating system
Posted: Sun Jun 16, 2019 8:32 pm
by alex_rhys-hurn
Hi,
I recommend taking a look at your vswitch and physical switch architecture. Be clear about your trunks and any spanning tree issues.
Try out the options with promiscuous mode on the vswitches, and esp on the physcial host interfaces.
Make sure to use VMXNET3 interfaces and drivers. Understand clearly about using vlan 4096 in esxi for trunk ports.
I have vsphere 6.5 with 6 CHRs doing BGP, OSPF IP Transit ipv4 and v6 and have NEVER seen this. We have been doing this since 2017.
Our routers are connected via ESXI trunks to external physical switches which we use as port extenders to the CHR, and then connect to Transit providers from there.
And yes, we have conntrack turned on, and we have also had to handle DDOS situations, but never seen the VM crash.
Also the IPArchitechs guys have run some big labs like this with 10g and I am not aware of them seeing the issue (correct me if Im wrong).
Salaams,
Alex
Re: The CPU has been disabled by the guest operating system
Posted: Mon Jun 17, 2019 11:36 am
by msandon
Hi,
I recommend taking a look at your vswitch and physical switch architecture. Be clear about your trunks and any spanning tree issues.
Try out the options with promiscuous mode on the vswitches, and esp on the physcial host interfaces.
Make sure to use VMXNET3 interfaces and drivers. Understand clearly about using vlan 4096 in esxi for trunk ports.
I have vsphere 6.5 with 6 CHRs doing BGP, OSPF IP Transit ipv4 and v6 and have NEVER seen this. We have been doing this since 2017.
Our routers are connected via ESXI trunks to external physical switches which we use as port extenders to the CHR, and then connect to Transit providers from there.
And yes, we have conntrack turned on, and we have also had to handle DDOS situations, but never seen the VM crash.
Also the IPArchitechs guys have run some big labs like this with 10g and I am not aware of them seeing the issue (correct me if Im wrong).
Salaams,
Alex
Hi Alex,
Thank you for your reply. You are the only one that really helps me.
Regards,
Matt