Highlighted
dbgallo1 Absent Member.
Absent Member.
1831 views

OES on VMWARE issue, disabled CPU

This has happened twice in as many weeks. We have a 4 node OES Cluster doing file shares. The server goes offline and the only mention in the VMWARE side is an event that states "The CPU has been disabled by the guest operating system" . If you reboot the machine, it acts like it has a 386 processor and no ram until you reboot it again. Then it functions normally. The only thing is /var/log/messages is normal traffic until the start up messages start to show.

anyone else run into this?

thanks
dave g.
Labels (2)
Tags (3)
0 Likes
4 Replies
Knowledge Partner
Knowledge Partner

Re: OES on VMWARE issue, disabled CPU

On 29/04/2015 15:06, dbgallo wrote:

> This has happened twice in as many weeks. We have a 4 node OES Cluster
> doing file shares. The server goes offline and the only mention in the
> VMWARE side is an event that states "The CPU has been disabled by the
> guest operating system" . If you reboot the machine, it acts like it
> has a 386 processor and no ram until you reboot it again. Then it
> functions normally. The only thing is /var/log/messages is normal
> traffic until the start up messages start to show.
>
> anyone else run into this?


Versions and patch levels? Novell OES, VMware product, etc.

HTH.
--
Simon
Novell/NetIQ Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------
0 Likes
dbgallo1 Absent Member.
Absent Member.

Re: OES on VMWARE issue, disabled CPU

OES11 SP2 patched to March 2015, with the PTF for the 128 character limit issue
VMWare Esx 5.1
OS and NSS disk is Fiber Attached SAN

as stated, nothing in /var/log/messages indicating anything is wrong
Host was showing >50% cpu and ram available when issue happened

smflood;2392487 wrote:
On 29/04/2015 15:06, dbgallo wrote:

> This has happened twice in as many weeks. We have a 4 node OES Cluster
> doing file shares. The server goes offline and the only mention in the
> VMWARE side is an event that states "The CPU has been disabled by the
> guest operating system" . If you reboot the machine, it acts like it
> has a 386 processor and no ram until you reboot it again. Then it
> functions normally. The only thing is /var/log/messages is normal
> traffic until the start up messages start to show.
>
> anyone else run into this?


Versions and patch levels? Novell OES, VMware product, etc.

HTH.
--
Simon
Novell/NetIQ Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES on VMWARE issue, disabled CPU

dbgallo;2392501 wrote:
OES11 SP2 patched to March 2015, with the PTF for the 128 character limit issue
VMWare Esx 5.1
OS and NSS disk is Fiber Attached SAN

as stated, nothing in /var/log/messages indicating anything is wrong
Host was showing >50% cpu and ram available when issue happened


I wonder if it's poison-pilling the node, although not sure that would explain why, upon reboot, it detects the wrong CPU. I would think the BIOS RAM/CPU detection would be 100% VMware.

I know there's some major issues/caveats with running NCS in VMware due to sensitivities with network/disk and I vaguely recall (like 3 years ago?) at Brainshare there was a session on the special things you had to do, but I don't recall exactly what they were.

But I'd be inclined to patch VMware to the latest 5.1 patch as that'll be required if you have to call VMware for support as to why, upon initial restart, it's mis-reporting the CPU/RAM.

Unless you mean that the BIOS is reporting correctly but SLES is not.
0 Likes
dbgallo1 Absent Member.
Absent Member.

Re: OES on VMWARE issue, disabled CPU

we're going to the latest VMWare patch to fix a RDM issue, so we'll see. Though these incidents did drop off after the April patches, and the following Patch to fix the 128 chracter limit issue
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.