All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: kvm-kmod.git
Date: Mon, 01 Jun 2009 21:17:54 +0300	[thread overview]
Message-ID: <4A241B52.3070501@redhat.com> (raw)
In-Reply-To: <20090601180057.GB6411@us.ibm.com>

Ryan Harper wrote:
>> So:
>>  LINUX= is for the kvm sources (further controlled by whatever branch 
>> is checked out)
>>  --kerneldir= is for the host kernel
>>     
>
> Ah, excellent, I didn't see it documented on the Code page of the wiki
> and I blindly assumed that it went away.  Thanks for correction.
>   

It actually did go away, but Jan brought it back.

>>> The reason I'm digging is that I'm seeing 64-bit migration failing on
>>> maint/2.6.29 kvm modules, but not on upstream kvm kernel bits and I
>>> wanted to bisect to find where 64-bit migration is fixed so I can
>>> suggest what to pull into maint/2.6.29.
>>>  
>>>       
>> Thanks, that's helpful.  How does it fail?  maybe I can supply an 
>> educated guess.
>>     
>
> Migration succeeds, but source and target are frozen (though monitor of
> guest is still interactive. 
>
> Nothing interesting in host dmesg, and of course no output from either
> guest (they seemed locked).  Reproduced this sort of hang for any number
> of guests (RHEL4u7/8, SLES10 SP2, SLES11, Win2k3-r2, win2k8, etc.) as
> long as they are 64-bit
>   

SMP?  Uniprocessor?

Try 'info registers' on both source and target and compare.  Maybe we 
lose some bit in EFER.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-06-01 18:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 12:32 kvm-kmod.git Avi Kivity
2009-04-27 14:08 ` kvm-kmod.git Farkas Levente
2009-04-27 14:56   ` kvm-kmod.git Avi Kivity
2009-04-27 17:18 ` kvm-kmod.git Cam Macdonell
2009-04-28  6:39   ` kvm-kmod.git Avi Kivity
2009-04-28 10:20 ` kvm-kmod.git Michael S. Tsirkin
2009-04-28 10:24   ` kvm-kmod.git Avi Kivity
2009-04-28 10:34     ` kvm-kmod.git Michael S. Tsirkin
2009-04-28 10:53       ` kvm-kmod.git Avi Kivity
2009-04-28 10:53         ` kvm-kmod.git Michael S. Tsirkin
2009-04-28 11:00           ` kvm-kmod.git Avi Kivity
2009-06-01 16:53         ` kvm-kmod.git Ryan Harper
2009-06-01 17:01           ` kvm-kmod.git Avi Kivity
2009-06-01 18:00             ` kvm-kmod.git Ryan Harper
2009-06-01 18:17               ` Avi Kivity [this message]
2009-06-01 18:15             ` kvm-kmod.git Ryan Harper
2009-06-01 18:19               ` kvm-kmod.git Avi Kivity
2009-06-01 18:47                 ` kvm-kmod.git Ryan Harper
2009-06-01 19:40                   ` kvm-kmod.git Avi Kivity

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=4A241B52.3070501@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=ryanh@us.ibm.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 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.