qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Bug 1169375 <1169375@bugs.launchpad.net>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org,
	Lucas Meneghel Rodrigues <lookkas@gmail.com>
Subject: [Qemu-devel] pointer to patch for [Bug 1169375] [NEW] qemu.git master -> qemu segfaults during tcp migration (and other modes when using MALLOC_PERTURB_=1)
Date: Tue, 16 Apr 2013 18:08:05 +0200	[thread overview]
Message-ID: <516D7765.1020406@redhat.com> (raw)
In-Reply-To: <20130416011019.20493.59957.malonedeb@gac.canonical.com>

Il 16/04/2013 03:10, Lucas Meneghel Rodrigues ha scritto:
> Public bug reported:
> 
> Relevant qemu.git master commit:
> 
> 24a6e7f4d91e9ed5f8117ecb083431a23f8609a0
> 
> When trying to migrate a VM using the TCP protocol, a segfault happened:

This fixes it in my tests (didn't get a segfault, but I reproduced some
funny behavior on the destination):

http://permalink.gmane.org/gmane.comp.emulators.qemu/205155

Anthony, this is another migration-but-not-quite patch that Juan was
leaving to you.

Paolo

> 21:45:07 INFO | Running qemu command (reformatted):
> /home/lmr/Code/qemu/x86_64-softmmu/qemu-system-x86_64 \
>     -S \
>     -name 'virt-tests-vm1' \
>     -nodefaults \
>     -chardev socket,id=hmp_id_hmp1,path=/tmp/monitor-hmp1-20130415-214507-8fDeX7Fj,server,nowait \
>     -mon chardev=hmp_id_hmp1,mode=readline \
>     -chardev socket,id=serial_id_serial1,path=/tmp/serial-serial1-20130415-214507-8fDeX7Fj,server,nowait \
>     -device isa-serial,chardev=serial_id_serial1 \
>     -chardev socket,id=seabioslog_id_20130415-214507-8fDeX7Fj,path=/tmp/seabios-20130415-214507-8fDeX7Fj,server,nowait \
>     -device isa-debugcon,chardev=seabioslog_id_20130415-214507-8fDeX7Fj,iobase=0x402 \
>     -device ich9-usb-uhci1,id=usb1 \
>     -drive file='/home/lmr/Code/virt-test.git/shared/data/images/jeos-17-64.qcow2',if=none,id=virtio0 \
>     -device virtio-blk-pci,drive=virtio0,bootindex=1 \
>     -device virtio-net-pci,netdev=idr5RNof,mac='9a:42:43:44:45:46',id='idJVlBu3' \
>     -netdev user,id=idr5RNof,hostfwd=tcp::5000-:22 \
>     -m 1024 \
>     -smp 2,maxcpus=2,cores=1,threads=1,sockets=2 \
>     -cpu 'SandyBridge' \
>     -M pc \
>     -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
>     -vnc :1 \
>     -vga std \
>     -rtc base=utc,clock=host,driftfix=none  \
>     -boot order=cdn,once=c,menu=off  \
>     -enable-kvm \
>     -incoming tcp:0:5200
> 21:45:08 INFO | [qemu output] qemu-system-x86_64: -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1: Bus 'virtio-pci-bus.0' is full
> 21:45:08 DEBUG| VM appears to be alive with PID 2002
> 21:45:08 DEBUG| (monitor hmp1) Sending command 'info cpus' 
> 21:45:08 DEBUG| (monitor hmp1) Response to 'info cpus'
> 21:45:08 DEBUG| (monitor hmp1)    * CPU #0: pc=0x00000000fffffff0 thread_id=2004
> 21:45:08 DEBUG| (monitor hmp1)      CPU #1: pc=0x00000000fffffff0 thread_id=2005
> 21:45:09 DEBUG| (monitor hmp1) Sending command 'cont' 
> 21:45:09 INFO | Migrating to tcp:0:5200
> 21:45:09 DEBUG| (monitor hmp1) Sending command 'migrate -d tcp:0:5200' 
> 21:45:10 WARNI| Could not find (qemu) prompt after command 'screendump /dev/shm/scrdump-MDE7wl.ppm'. Output so far: ''
> 21:45:10 WARNI| VM 'virt-tests-vm1' produced an invalid screendump
> 21:45:10 INFO | [qemu output] qemu: warning: error while loading state section id 3
> 21:45:10 INFO | [qemu output] load of migration failed
> 21:45:10 INFO | [qemu output] /bin/sh: line 1:  1867 Segmentation fault      /home/lmr/Code/qemu/x86_64-softmmu/qemu-system-x86_64 -S -name 'virt-tests-vm1' -nodefaults -chardev socket,id=hmp_id_hmp1,path=/tmp/monitor-hmp1-20130415-214454-pGmRwNvs,server,nowait -mon chardev=hmp_id_hmp1,mode=readline -chardev socket,id=serial_id_serial1,path=/tmp/serial-serial1-20130415-214454-pGmRwNvs,server,nowait -device isa-serial,chardev=serial_id_serial1 -chardev socket,id=seabioslog_id_20130415-214454-pGmRwNvs,path=/tmp/seabios-20130415-214454-pGmRwNvs,server,nowait -device isa-debugcon,chardev=seabioslog_id_20130415-214454-pGmRwNvs,iobase=0x402 -device ich9-usb-uhci1,id=usb1 -drive file='/home/lmr/Code/virt-test.git/shared/data/images/jeos-17-64.qcow2',if=none,id=virtio0 -device virtio-blk-pci,drive=virtio0,bootindex=1 -device virtio-net-pci,netdev=id33wvth,mac='9a:42:43:44:45:46',id='idavPVhj' -netdev user,id=id33wvth,hostfwd=tcp::5001-:22 -m 1024 -smp 2,maxcpus=2,cores=1,threads=1,so:
> 
> We've missed those problems during the last couple of weeks due to
> problems in our test grid. The problem can be seen running the default
> test set on virt-test. By default, virt-test does not use
> MALLOC_PERTURB_=1. When using MALLOC_PERTURB_=1, pretty much all
> migration modes will fail.
> 
> ** Affects: qemu
>      Importance: Undecided
>          Status: New
> 

  reply	other threads:[~2013-04-16 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  1:10 [Qemu-devel] [Bug 1169375] [NEW] qemu.git master -> qemu segfaults during tcp migration (and other modes when using MALLOC_PERTURB_=1) Lucas Meneghel Rodrigues
2013-04-16 16:08 ` Paolo Bonzini [this message]
2013-04-17 19:03 ` [Qemu-devel] [Bug 1169375] " Lucas Meneghel Rodrigues
2013-05-20 17:31 ` Aurelien Jarno

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=516D7765.1020406@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=1169375@bugs.launchpad.net \
    --cc=aliguori@us.ibm.com \
    --cc=lookkas@gmail.com \
    --cc=qemu-devel@nongnu.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).