From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 53361] New: Wrong CPUID data returned by KVM
Date: Sat, 2 Feb 2013 20:22:32 +0000 (UTC) [thread overview]
Message-ID: <bug-53361-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=53361
Summary: Wrong CPUID data returned by KVM
Product: Virtualization
Version: unspecified
Kernel Version: 3.2.0-37
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: kaloqn.ganchev@gmail.com
Regression: No
When booted like this
kvm -cpu core2duo,+xsave -enable-kvm -m 8192 -drive file=freebsd-9.1-qcow2.img
-boot d -net nic -net user -nographic -vnc :0 -cdrom
./isos/FreeBSD-9.1-RELEASE-amd64-disc1.iso
Freebsd crash immediately after the loader with error;
CPU0 does not support X87 or SSE2 : 0
Without the xsave instruction the FreeBSD boot as expected.
I had response from the FreeBSD developers that CPUID should return presence
of the FPU extensions and since long mode capable CPU , X87 and SSE2 should be
present according to Unix amd64 ABI .
It seems this is not the case when xsave flag is set.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2013-02-02 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 20:22 bugzilla-daemon [this message]
2014-08-04 16:55 ` [Bug 53361] Wrong CPUID data returned by KVM bugzilla-daemon
2014-08-09 2:10 ` bugzilla-daemon
2019-04-08 15:02 ` bugzilla-daemon
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=bug-53361-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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.