From: Avi Kivity <avi@redhat.com>
To: BuraphaLinux Server <buraphalinuxserver@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: random crash in post_kvm_run()
Date: Wed, 07 Jul 2010 12:12:01 +0300 [thread overview]
Message-ID: <4C3444E1.8000908@redhat.com> (raw)
In-Reply-To: <AANLkTiljKC7DaXTOZXdsQHazy8g26BhuN16K-vI3p4JI@mail.gmail.com>
On 07/06/2010 06:58 PM, BuraphaLinux Server wrote:
> I spent the day getting things ready for you to log in, but was amazed
> to find you already had a patch ready for testing, which was good
> news. I wasn't sure which kernel that was for. I applied it by hand
> to 2.6.34.1 and then regenerated the patch for that (attached). That
> patch on top of 2.6.34.1 works for me. I tested running the qmeu_kvm
> 5 times in a row, and updated the kernel in the guest to match and it
> worked fine as the host and the guest (and I ran that on the client
> machine too). If you want me to test your original unmodified patch,
> I will be happy to do that too. What kernel version is it for? Your
> patch updates the line with vmx_set_efer() in exit_lmode() in vmx.c,
> but that line wasn't in 2.6.34.1, so I guessed it should be added.
>
Thanks, no need for further testing.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-07-07 9:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 17:28 random crash in post_kvm_run() BuraphaLinux Server
2010-06-28 18:38 ` Brian Jackson
2010-06-30 17:57 ` BuraphaLinux Server
2010-06-29 12:16 ` Avi Kivity
2010-06-30 18:25 ` BuraphaLinux Server
2010-07-01 11:44 ` Avi Kivity
2010-07-02 19:08 ` BuraphaLinux Server
2010-07-03 10:28 ` Avi Kivity
2010-07-03 14:23 ` BuraphaLinux Server
2010-07-05 7:42 ` Avi Kivity
2010-07-05 8:52 ` BuraphaLinux Server
2010-07-05 10:15 ` Avi Kivity
2010-07-06 7:46 ` Avi Kivity
2010-07-06 8:37 ` Avi Kivity
2010-07-06 15:58 ` BuraphaLinux Server
2010-07-07 9:12 ` Avi Kivity [this message]
2010-06-30 18:06 ` Anthony Liguori
2010-06-30 18:32 ` BuraphaLinux Server
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=4C3444E1.8000908@redhat.com \
--to=avi@redhat.com \
--cc=buraphalinuxserver@gmail.com \
--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).