From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 61971] Migration problem of qemu-kvm guests
Date: Thu, 17 Oct 2013 10:58:27 +0000 [thread overview]
Message-ID: <bug-61971-28872-qi7R77zA7N@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-61971-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=61971
--- Comment #11 from Paolo Bonzini <bonzini@gnu.org> ---
This is XSAVE -> non-XSAVE migration. Alexander Graf reported to me on IRC
that the XSAVE patches we recently committed to kvm/next fixed this for him.
xstate_bv is saved as 7 and this check fails on the destination:
if (xstate_bv & ~XSTATE_FPSSE)
return -EINVAL;
I think it is because your CPU has xsave but not xsaveopt.
However, those patches introduced regressions that have to be fixed. I'll look
at those soon, but your bug should get fixed in 3.13.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-10-17 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 7:24 [Bug 61971] New: Migration problem of qemu-kvm guests bugzilla-daemon
2013-09-25 21:31 ` [Bug 61971] " bugzilla-daemon
2013-10-02 20:07 ` bugzilla-daemon
2013-10-16 17:07 ` bugzilla-daemon
2013-10-16 17:23 ` bugzilla-daemon
2013-10-16 18:51 ` bugzilla-daemon
2013-10-16 21:01 ` bugzilla-daemon
2013-10-17 9:37 ` bugzilla-daemon
2013-10-17 9:57 ` bugzilla-daemon
2013-10-17 9:58 ` bugzilla-daemon
2013-10-17 9:58 ` bugzilla-daemon
2013-10-17 10:58 ` bugzilla-daemon [this message]
2013-10-17 12:11 ` bugzilla-daemon
2013-10-17 12:13 ` bugzilla-daemon
2013-10-17 12:19 ` bugzilla-daemon
2013-10-18 19:21 ` bugzilla-daemon
2013-10-19 6:37 ` bugzilla-daemon
2013-10-19 21:00 ` bugzilla-daemon
2013-10-21 15:12 ` 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-61971-28872-qi7R77zA7N@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).