[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails wi

From: Stefan Hajnoczi
Subject: [Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
Date: Fri, 05 Jul 2013 08:22:42 -0000

The destination VM's log says:

  qemu: warning: error while loading state section id 1

This indicates that either there was an error on the destination while
loading state or the migration stream got out of sync.

Please check that QEMU on source and destination are identical.  If you
are running different versions of QEMU on source and destination this
could be the cause.

Try with qemu.git/master and a simple QEMU command-line (without

  qemu-system-x86_64 -machine pc-i440fx-1.5,accel=kvm -m 4000 \
      -drive file=/home/images/rhel64-64.qcow2,if=ide,format=qcow2,cache=none

Use the same command-line on the destination but also add "-incoming
tcp::1234".  To start the migrate on the source, run "migrate -b tcp
:<destination-ip>:1234" in the QEMU monitor.

If the failure can be reproduce on qemu.git/master in this way it will
be easier to debug.

I will be away next week and therefore unable to look into this more.

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  virsh migration copy-storage-all  fails with "Unable to read from
  monitor: Connection reset by peer"

Status in QEMU:
Status in “libvirt” package in Ubuntu:
Status in “libvirt” package in Fedora:

Bug description:
  virsh migration copy-storage-all  fails with "Unable to read from
  monitor: Connection reset by peer" and shut downs the guest on the
  source host.

  Kernel Version:  3.10.0-rc5+

  Libvirt Version: 1.0.6

  Qemu Version: 1.5.50

  Steps to reproduce the issue:
  1. Created the qemu-img create -f qcow2 vm.qcow2 11G on the destination host 
which is same as the source.
  2. Started the guest on the source
  3. Started the vncdisplay to monitor the guest
  4. Initiated the migration "virsh migrate --live VM1 
qemu+ssh://host-ip/system tcp://host-ip --verbose --copy-storage-all"
  5. It started the copying the storage from souce to destination (conitinously 
monitored it was growing)
  6. Guest on the destination was paused and was running on the source
  7. At some point the VM on the source got shutdown and migration failed with 
"Unable to read from monitor: Connection reset by peer"

  Attached the libvirt debug logs.

  The debug logs shows :

  2013-06-19 08:43:12.253+0000: 4026: debug : virEventPollInterruptLocked:716 : 
  2013-06-19 08:43:12.253+0000: 4026: debug : virEventPollAddTimeout:248 : 
EVENT_POLL_ADD_TIMEOUT: timer=1 frequency=0 cb=0x7fe930baa960 opaque=(nil) 

  Note: The virsh live migration works fine with nfs storage from source to 
destination and vice versa.
  With libvirt 1.0.5 and qemu 1.5 also we were facing the same issue, but with 
that even "Live migration with nfs also was not working".

  Guest XML:

  <domain type='kvm'>
    <memory unit='KiB'>4096000</memory>
    <currentMemory unit='KiB'>2048000</currentMemory>
    <vcpu placement='auto'>1</vcpu>
      <memory mode='strict' nodeset='0'/>
      <type arch='x86_64' machine='pc-i440fx-1.5'>hvm</type>
      <boot dev='hd'/>
    <clock offset='utc'/>
      <disk type='file' device='disk'>
        <driver name='qemu' type='qcow2' cache='none'/>
        <source file='/home/images/VM1.qcow2'/>
        <target dev='hda' bus='ide'/>
        <address type='drive' controller='0' bus='0' target='0' unit='0'/>
      <disk type='block' device='cdrom'>
        <driver name='qemu' type='raw'/>
        <target dev='hdc' bus='ide'/>
        <address type='drive' controller='0' bus='1' target='0' unit='0'/>
      <controller type='usb' index='0'>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 
      <controller type='ide' index='0'>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 
      <controller type='pci' index='0' model='pci-root'/>
      <interface type='network'>
        <mac address='52:54:00:9d:cf:bb'/>
        <source network='default'/>
        <model type='rtl8139'/>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 
      <serial type='pty'>
        <target port='0'/>
      <console type='pty'>
        <target type='serial' port='0'/>
      <input type='mouse' bus='ps2'/>
      <graphics type='vnc' port='-1' autoport='yes' listen=''>
        <listen type='address' address=''/>
        <model type='cirrus' vram='9216' heads='1'/>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 
      <memballoon model='virtio'>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x05' 
    <seclabel type='none' model='selinux'/>

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]