All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 63121] The guest will hang after live migration.
Date: Mon, 04 Nov 2013 03:23:03 +0000	[thread overview]
Message-ID: <bug-63121-28872-O9SbU9EUKB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-63121-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=63121

Zhou, Chao <chao.zhou@intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #3 from Zhou, Chao <chao.zhou@intel.com> ---
this commit fixed the bug:
commit 46c34cb059d519601fb567b55cf45c300fea2928
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Thu Oct 17 16:50:46 2013 +0200

    KVM: x86: fix KVM_SET_XCRS for CPUs that do not support XSAVE

    The KVM_SET_XCRS ioctl must accept anything that KVM_GET_XCRS
    could return.  XCR0's bit 0 is always 1 in real processors with
    XSAVE, and KVM_GET_XCRS will always leave bit 0 set even if the
    emulated processor does not have XSAVE.  So, KVM_SET_XCRS must
    ignore that bit when checking for attempts to enable unsupported
    save states.

    Reviewed-by: Gleb Natapov <gleb@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-11-04  3:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16  1:41 [Bug 63121] New: The guest will hang after live migration bugzilla-daemon
2013-10-16  1:46 ` [Bug 63121] " bugzilla-daemon
2013-10-16  7:10 ` bugzilla-daemon
2013-11-04  3:23 ` bugzilla-daemon [this message]
2013-11-04  3:23 ` 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-63121-28872-O9SbU9EUKB@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.