Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1631214

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

From Paolo Bonzini <pbonzini@redhat.com>
Newsgroups linux.kernel
Subject Re: [BUG] x86: failed to boot a kernel on a Ryzen machine
Date 2017-04-26 09:50 +0200
Message-ID <tApS1-7Eb-11@gated-at.bofh.it> (permalink)
References (1 earlier) <tzK2u-6io-21@gated-at.bofh.it> <tzLrA-6Zn-21@gated-at.bofh.it> <tzLBf-72B-1@gated-at.bofh.it> <tzLUC-7pd-13@gated-at.bofh.it> <tA56V-2RZ-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw



On 25/04/2017 11:36, Borislav Petkov wrote:
> Looking at CR4: 00000000003006f0, it doesn't have OSXSAVE set. I.e., bit
> 18. And when that bit is not set, VMOVDQA raises an #UD.
> 
> And for some reason qemu doesn't like it even if you request that bit with
> +osxsave:
> 
> warning: host doesn't support requested feature: CPUID.01H:ECX.osxsave [bit 27]
> 
> Even though the corresponding bit in CPUID on the host is set:
> 
> 0x00000001: EAX=0x00800f00, EBX=0x40200800, ECX=0x7ed8320b, EDX=0x178bfbff
> 						   ^
> Paolo, any thoughts?

The OSXSAVE CPUID bit is not set by QEMU, it is set by the OS itself
(indirectly) when it sets CR4.OSXSAVE.  QEMU says it's not available
(probably) because the Opteron_G3 CPU model does not have the 0xD CPUID
leaf.

I think you're using libvirt's "host-model" CPU model.  That model needs
QEMU/libvirt support for each host CPU family, and in general it often
gives rise to bugs such as the one you're reporting,

Change it to host-passthrough, and please send us the output of
/proc/cpuinfo so we can add support for Ryzen in "host-model".

Thanks,

Paolo

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Borislav Petkov <bp@alien8.de> - 2017-04-25 11:40 +0200
  Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Paolo Bonzini <pbonzini@redhat.com> - 2017-04-26 09:50 +0200
    Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Borislav Petkov <bp@alien8.de> - 2017-04-26 10:20 +0200
    Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-26 13:50 +0200
      Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Paolo Bonzini <pbonzini@redhat.com> - 2017-04-26 19:00 +0200
        Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-27 02:50 +0200
          Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Paolo Bonzini <pbonzini@redhat.com> - 2017-04-28 15:40 +0200
            Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-29 23:10 +0200

csiph-web