From: Avi Kivity <avi@redhat.com>
To: Markus Schade <markus.schade@gmail.com>
Cc: Joerg Roedel <joro@8bytes.org>, kvm@vger.kernel.org
Subject: Re: Restoring saved guest causes guest to reboot
Date: Tue, 24 May 2011 16:42:43 +0300 [thread overview]
Message-ID: <4DDBB5D3.3020403@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1105241534060.16474@perseus.csn.tu-chemnitz.de>
On 05/24/2011 04:37 PM, Markus Schade wrote:
> On Tue, 24 May 2011, Avi Kivity wrote:
>
>>> Hmm, only 19 patches between .37 and .38 touch vmx.c. Avi, any idea
>>> which
>>> of those patches could cause this?
>>
>> Might be several.
>>
>> Markus, can you try a bisect?
>>
>> The command
>>
>> $ git bisect start v2.6.38 v2.6.37 arch/x86/kvm
>>
>> will generate test kernels for you to compile and run. There will be
>> 7-8 tests needed, and most of the compiles should be short (esp. if
>> you install ccache).
>
> Sure. I will take some time, though. Shall I use Linus git tree or the
> kvm one?
Either will work - the kvm tree includes the Linus tree. Since you
tested .37 and .38, best to give those to git as starting points.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-24 13:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 7:11 Restoring saved guest causes guest to reboot Markus Schade
2011-05-24 9:18 ` Joerg Roedel
2011-05-24 9:35 ` Markus Schade
2011-05-24 9:40 ` Joerg Roedel
2011-05-24 11:42 ` Markus Schade
2011-05-24 13:02 ` Joerg Roedel
2011-05-24 13:20 ` Avi Kivity
2011-05-24 13:37 ` Markus Schade
2011-05-24 13:42 ` Avi Kivity [this message]
2011-05-25 6:49 ` Markus Schade
2011-05-26 6:44 ` Avi Kivity
2011-05-26 11:28 ` Markus Schade
2011-05-26 15:20 ` Markus Schade
2011-05-26 15:25 ` Joerg Roedel
2011-05-30 12:16 ` Markus Schade
2011-05-30 18:02 ` Marcelo Tosatti
2011-05-31 9:44 ` Markus Schade
2011-06-06 13:57 ` Markus Schade
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=4DDBB5D3.3020403@redhat.com \
--to=avi@redhat.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=markus.schade@gmail.com \
/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