All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Owen Tuz <qemu.owentuz@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] xsave instruction not passed through correctly on AMD hardware
Date: Mon, 11 Nov 2013 16:25:16 +0100	[thread overview]
Message-ID: <5280F6DC.6080301@redhat.com> (raw)
In-Reply-To: <CAAhzb2bUHRapkOhUubZxjJCmj9152rT0+tgHYnE1RK+415bYOQ@mail.gmail.com>

Il 11/11/2013 15:30, Owen Tuz ha scritto:
> Hi all,
> 
> We've been seeing a problem lately running FreeBSD 9.1 and 9.2 (latest
> stable) which causes the guest to crash during boot when QEMU is run on
> an AMD processor with the 'xsave' flag set. 
> 
> To reproduce this behaviour:
> 
> - Boot a FreeBSD 9.1 or 9.2 guest or even installation CD on an AMD
> processor with xsave enabled. Use '-cpu host'.
> 
> - After the bootloader, the guest will crash almost immediately with the
> message 'kernel trap 12 with interrupts disabled'. This occurs before
> any disks are loaded, so it's not possible to get a memory dump from the
> guest OS for backtrace.
> 
> - Boot again with '-cpu host,-xsave'. The guest should boot successfully.

This is probably cause by the "lightweight profiling" XSAVE extension.
KVM does not support it.  Using "-cpu host" may show problems when the
CPU has features that are not supported by KVM.

It's possible though that this has been recently fixed.  Please try
branch "next" of git://git.kernel.org/pub/scm/virt/kvm/kvm.git and
report back.

Paolo

  reply	other threads:[~2013-11-11 15:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 14:30 [Qemu-devel] xsave instruction not passed through correctly on AMD hardware Owen Tuz
2013-11-11 15:25 ` Paolo Bonzini [this message]
2013-11-11 15:43   ` Owen Tuz
2013-11-11 16:56     ` Paolo Bonzini
2013-11-13 12:11       ` Owen Tuz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5280F6DC.6080301@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu.owentuz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.