qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Pierre Riteau <Pierre.Riteau@irisa.fr>
Cc: Anthony@gnu.org, Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [BUG] Migration segfaults
Date: Thu, 17 Sep 2009 14:41:59 -0300	[thread overview]
Message-ID: <20090917144159.5578b3f4@doriath> (raw)
In-Reply-To: <7D6C4BFE-0DBA-4755-921D-BD34279CA92D@irisa.fr>

On Thu, 17 Sep 2009 17:05:17 +0200
Pierre Riteau <Pierre.Riteau@irisa.fr> wrote:

> The commit 7e72abc382b700a72549e8147bdea413534eeedc (vmstate: port  
> cirrus_vga device) appears to break migration for me.
> I'm migrating a Debian Lenny with 128 MB of RAM, and it segfaults at  
> the end of the migration.
> 
> The following backtrace was acquired with the current HEAD  
> (b348113d2161a339780e2d9e0479b1f9a53c6cbc).

 I'm also getting a migration problem with current HEAD: right
when the migration process finishes the destination guest
reboots.

 Reverting the above commit doesn't fix the problem, though.

 Also, it's been hard to 'bisect' it because:

1. doesn't appear to be caused by a recent commit
2. taking too old 'good' commits makes 'bisect' hit all
   recent migration bugs

 So, not sure what to do here... Maybe I'll go over committed
series manually.

  reply	other threads:[~2009-09-17 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200909111831.n8BIVER1023510@d01av03.pok.ibm.com>
2009-09-17 15:05 ` [Qemu-devel] [BUG] Migration segfaults Pierre Riteau
2009-09-17 17:41   ` Luiz Capitulino [this message]
2009-10-08  9:33   ` Pierre Riteau

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=20090917144159.5578b3f4@doriath \
    --to=lcapitulino@redhat.com \
    --cc=Anthony@gnu.org \
    --cc=Pierre.Riteau@irisa.fr \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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;
as well as URLs for NNTP newsgroup(s).