From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40866) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XF4ey-0003mQ-E0 for qemu-devel@nongnu.org; Wed, 06 Aug 2014 13:06:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XF4es-00034Q-Uh for qemu-devel@nongnu.org; Wed, 06 Aug 2014 13:05:56 -0400 Received: from indium.canonical.com ([91.189.90.7]:49019) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XF4es-000345-PD for qemu-devel@nongnu.org; Wed, 06 Aug 2014 13:05:50 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1XF4er-0007zB-Ke for ; Wed, 06 Aug 2014 17:05:49 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 993192E80BA for ; Wed, 6 Aug 2014 17:05:49 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 06 Aug 2014 16:56:57 -0000 From: Chris J Arges <1285708@bugs.launchpad.net> Sender: bounces@canonical.com References: <20140227150100.32637.87688.malonedeb@gac.canonical.com> Message-Id: <20140806165657.21032.5777.malone@soybean.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1285708] Re: FreeBSD Guest crash on boot due to xsave instruction issue Reply-To: Bug 1285708 <1285708@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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 addi= tional features settings. In addition I've been able to use '-cpu SandyBrid= ge,+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 =3D> Won't Fix ** Changed in: linux (Ubuntu) Status: Fix Released =3D> Invalid ** Changed in: linux (Ubuntu Precise) Importance: Medium =3D> Undecided ** Changed in: linux (Ubuntu Trusty) Importance: Medium =3D> 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 =E2=80=9Clinux=E2=80=9D package in Ubuntu: Invalid Status in =E2=80=9Clinux=E2=80=9D source package in Precise: Won't Fix Status in =E2=80=9Clinux=E2=80=9D 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=3DFreeBSD-9.2-RELEASE-amd64.qcow2,if=3Dvirtio -net nic,model=3Dvirtio -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