All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: KVM mailing list <kvm@vger.kernel.org>,
	Juan Quintela <quintela@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	QEMU devel <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] qemu-kvm crashes doing migration with disks + blkdebug files (does not happen with qemu)
Date: Mon, 07 Nov 2011 10:11:01 -0200	[thread overview]
Message-ID: <4EB7CAD5.2070702@redhat.com> (raw)
In-Reply-To: <4EB7A4EB.30307@redhat.com>

On 11/07/2011 07:29 AM, Kevin Wolf wrote:
> Am 05.11.2011 03:16, schrieb Lucas Meneghel Rodrigues:
>> Hi folks,
>>
>> qemu-kvm is segfaulting when executing migration with blkdebug files.
>>
>> 19:50:02 DEBUG| Git repo qemu_kvm uri: git://github.com/avikivity/qemu.git
>> 19:50:02 DEBUG| Git repo qemu_kvm branch: master
>> 19:50:30 INFO | Commit hash for qemu_kvm is
>> 7879db7e9c09b92d9af1c143fbe2cc212ec89e4b (no tag found)
>>
>> How to reproduce:
>>
>> 1) create a origin vm like:
>>
>> /usr/local/autotest/tests/kvm/qemu -name 'vm1' -nodefaults -vga std
>> -monitor
>> unix:'/tmp/monitor-humanmonitor1-20111104-200902-95j0',server,nowait
>> -qmp unix:'/tmp/monitor-qmpmonitor1-20111104-200902-95j0',server,nowait
>> -serial unix:'/tmp/serial-20111104-200902-95j0',server,nowait -drive
>> file=blkdebug:/usr/local/autotest/virt/blkdebug/default.conf:/tmp/kvm_autotest_root/images/rhel6.1-64.qcow2,index=0,if=virtio,cache=none,rerror=stop,werror=stop
>> -device
>> virtio-net-pci,netdev=idtzhBVb,mac='9a:d0:7b:07:18:72',id='id9JW3ZV'
>> -netdev tap,id=idtzhBVb,fd=23 -m 2048 -smp 2 -vnc :0
>>
>>
>> 2) create a destination vm like:
>>
>> /usr/local/autotest/tests/kvm/qemu -name 'vm1' -nodefaults -vga std
>> -monitor
>> unix:'/tmp/monitor-humanmonitor1-20111104-201329-Ia9o',server,nowait
>> -qmp unix:'/tmp/monitor-qmpmonitor1-20111104-201329-Ia9o',server,nowait
>> -serial unix:'/tmp/serial-20111104-201329-Ia9o',server,nowait -drive
>> file=blkdebug:/usr/local/autotest/virt/blkdebug/default.conf:/tmp/kvm_autotest_root/images/rhel6.1-64.qcow2,index=0,if=virtio,cache=none,rerror=stop,werror=stop
>> -device
>> virtio-net-pci,netdev=idup1xAf,mac='9a:d0:7b:07:18:72',id='idyvOQf3'
>> -netdev tap,id=idup1xAf,fd=19 -m 2048 -smp 2 -vnc :1  -S -incoming
>> "exec:nc -l 5200"
>>
>> Note that blkdebug file contains:
>>
>> [inject-error]
>> state = "2"
>> event = "read_aio"
>> errno = "7"
>> immediately = "off"
>> once = "on"
>>
>> [set-state]
>> state = "1"
>> event = "read_aio"
>> new_state = "2"
>>
>> [set-state]
>> state = "2"
>> event = "read_aio"
>> new_state = "3"
>>
>> Start the migration (on this example, using exec, but it reproduces with
>> tcp and unix sockets):
>>
>> 11/04 20:13:30 DEBUG|kvm_monito:0254| (monitor humanmonitor1) Sending
>> command 'migrate -d "exec:nc localhost 5200"'
>>
>> Then you will have:
>>
>> 11/04 20:13:33 INFO |   aexpect:0783| [qemu output] invalid runstate
>> transition
>
> Invalid runstate transition is something for Luiz (CCed). Though
> probably he doesn't need to do anything in this case: I think we're not
> allowing the transition from I/O error to migrating. This might be fixed
> by 8a9236f1 in qemu.git, so please retest with upstream.

In the end of my original message, I stated the same test does not yield 
a segfault in qemu.git, so the referred commit indeed fixes the issue.

Thanks!

      reply	other threads:[~2011-11-07 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-05  2:16 qemu-kvm crashes doing migration with disks + blkdebug files (does not happen with qemu) Lucas Meneghel Rodrigues
2011-11-05  2:16 ` [Qemu-devel] " Lucas Meneghel Rodrigues
2011-11-07  9:29 ` Kevin Wolf
2011-11-07  9:29   ` [Qemu-devel] " Kevin Wolf
2011-11-07 12:11   ` Lucas Meneghel Rodrigues [this message]

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=4EB7CAD5.2070702@redhat.com \
    --to=lmr@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mtosatti@redhat.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 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.