Skip to main content

XSAVE consistency problem for RHEL 8.x VM on ESXi 7.0 with a Skylake CPU

  Symptoms

Booting RHEL 8.x VM on ESXi 7.0 with a Skylake CPU, XSAVE consistency problem error is reported in the dmesg log of the VM. 
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] XSAVE consistency problem, dumping leaves
[ 0.000000] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:614 do_extra_xstate_size_checks+0x2f3/0x3de
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.18.0-193.el8.x86_64 #1
[ 0.000000] RIP: 0010:do_extra_xstate_size_checks+0x2f3/0x3de
[ 0.000000] Code: ff 44 3b 25 e5 93 b8 01 0f 84 d9 00 00 00 80 3d d9 96 39 01 00 75 27 48 c7 c7 f0 d1 47 bb c6 05 c9 96 39 01 01 e8 65 3e 08 00 <0f> 0b eb 10 83 3d a0 50 1f 01 00 74 23 e8 4a fc ff ff eb 1c 83 3d
[ 0.000000] RSP: 0000:ffffffffbb603da8 EFLAGS: 00010086 ORIG_RAX: 0000000000000000
[ 0.000000] RAX: 0000000000000000 RBX: 000000000000000a RCX: 0000000000000029
[ 0.000000] RDX: 0000000000000009 RSI: ffffffffbc01af40 RDI: 0000000000000046
[ 0.000000] RBP: 0000000000000008 R08: 657661656c20676e R09: 73657661656c2067
[ 0.000000] R10: 656c626f72702079 R11: 69706d7564202c6d R12: 0000000000000988
[ 0.000000] R13: ffffffffbb603db0 R14: ffffffffbb603dac R15: ffffffffbb603da8
[ 0.000000] FS: 0000000000000000(0000) GS:ffffffffbbd4b000(0000) knlGS:0000000000000000
[ 0.000000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.000000] CR2: ffff888000094810 CR3: 0000000091dee000 CR4: 00000000000406a0
[ 0.000000] Call Trace:
[ 0.000000] ? do_clear_cpu_cap+0xf4/0x110
[ 0.000000] ? fpu__init_system_xstate+0x179/0x458
[ 0.000000] ? 0xffffffffba400000
[ 0.000000] ? fpu__init_system+0x208/0x234
[ 0.000000] ? early_init_intel+0x150/0x370
[ 0.000000] ? 0xffffffffba400000
[ 0.000000] ? x86_match_cpu+0x5/0xa0
[ 0.000000] ? early_cpu_init+0x2ae/0x2cb
[ 0.000000] ? setup_arch+0xe0/0x101a
[ 0.000000] ? printk+0x58/0x6f
[ 0.000000] ? start_kernel+0x63/0x55b
[ 0.000000] ? x86_family+0x5/0x20
[ 0.000000] ? load_ucode_bsp+0x42/0x12e
[ 0.000000] ? secondary_startup_64+0xb7/0xc0
[ 0.000000] random: get_random_bytes called from print_oops_end_marker+0x26/0x40 with crng_init=0
[ 0.000000] ---[ end trace 009e620edbd0a5f1 ]---
Cause
You can see this message when the set of xsave features exposed to the virtual machine is a subset of the xsave features support by the host. In such cases, the size of the xsave region enumerated in CPUID may be larger than expected.
Resolution
This is a known issue affecting VMware ESXi 7.0. VMware is working to resolve this issue in a future release.
Note: This message is an advisory from the Linux kernel.

Comments

Post a Comment

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...
Post a Comment
Read more

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...
Post a Comment
Read more

Cloning and converting virtual machine disks with vmkfstools

 Purpose This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another. Resolution The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk ( .vmdk ) format into another. Note : The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats. To convert a virtual machine disk from one type to another: Shut down the virtual machine. Virtual machine disk files are locked while in-use by a running virtual machine. Log in to the VMware vSphere Management Assistant (v...
Post a Comment
Read more