All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris J Arges <1285708@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1285708] Re: FreeBSD Guest crash on boot due to xsave instruction issue
Date: Wed, 06 Aug 2014 16:56:57 -0000	[thread overview]
Message-ID: <20140806165657.21032.5777.malone@soybean.canonical.com> (raw)
In-Reply-To: 20140227150100.32637.87688.malonedeb@gac.canonical.com

Testing with the identified patch doesn't solve the issue, in addition
looking at the cpu flags (core2duo +xsave) this may not be a valid
configuration since xsave assumes additional features will be there
(instead of creating an older cpu model with xsave.) Therefore I believe
this is a configuration issue.

The comment above in #4 assumes your host has the correct cpu features, you can always run something like:
kvm -cpu host,+xsave,check   to check if are issues with the host plus additional features settings. In addition I've been able to use '-cpu SandyBridge,+xsave' and this also works.

Marking this 'Won't Fix' as there is a clear workaround (use another CPU
model), and this configuration may not be valid.

Thanks

** Changed in: linux (Ubuntu Trusty)
       Status: In Progress => Won't Fix

** Changed in: linux (Ubuntu)
       Status: Fix Released => Invalid

** Changed in: linux (Ubuntu Precise)
   Importance: Medium => Undecided

** Changed in: linux (Ubuntu Trusty)
   Importance: Medium => Undecided

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1285708

Title:
  FreeBSD Guest crash on boot due to xsave instruction issue

Status in QEMU:
  Invalid
Status in qemu-kvm:
  New
Status in “linux” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Won't Fix
Status in “linux” source package in Trusty:
  Won't Fix

Bug description:
  When trying to boot a working FreeBSD 9.1/9.2 guest on a kvm/qemu host
  with the following command:

  kvm -m 256 -cdrom FreeBSD-9.2-RELEASE-amd64-disc1.iso -drive
  file=FreeBSD-9.2-RELEASE-amd64.qcow2,if=virtio -net nic,model=virtio
  -net user -nographic -vnc :10 -enable-kvm -balloon virtio -cpu
  core2duo,+xsave

  The FreeBSD Guest will kernel crash on boot with the following error:

  panic: CPU0 does not support X87 or SSE: 0

  When launching the guest without the cpu flags, it works just fine.

  This bug has been resolved in source:
  https://lkml.org/lkml/2014/2/22/58

  Can this fix be included in Precise ASAP!

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1285708/+subscriptions

  parent reply	other threads:[~2014-08-06 17:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 15:01 [Qemu-devel] [Bug 1285708] [NEW] FreeBSD Guest crash on boot due to xsave instruction issue Jesse Pretorius
2014-04-02 11:29 ` [Qemu-devel] [Bug 1285708] " Jesse Pretorius
2014-06-16 18:16 ` Serge Hallyn
2014-06-16 18:30 ` [Qemu-devel] [Bug 1285708] Missing required logs Brad Figg
2014-08-04 22:25 ` [Qemu-devel] [Bug 1285708] Re: FreeBSD Guest crash on boot due to xsave instruction issue Chris J Arges
2014-08-05 20:46 ` Chris J Arges
2014-08-06 16:03 ` Chris J Arges
2014-08-06 16:30 ` Paolo Bonzini
2014-08-06 16:39 ` Jesse Pretorius
2014-08-06 16:56 ` Chris J Arges [this message]
2014-08-06 17:08 ` Chris J Arges

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=20140806165657.21032.5777.malone@soybean.canonical.com \
    --to=1285708@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /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.