[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: |
chandrashekar shastri |
Subject: |
[Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" |
Date: |
Thu, 04 Jul 2013 07:13:37 -0000 |
Moving to qemu component as qemu is crashing based on the inputs from
Michal Privoznik
Bugzilla : Bug 979411 - virsh migration copy-storage-all fails with
"Unable to read from monitor: Connection reset by peer"
** Project changed: libvirt => qemu
** Bug watch added: Red Hat Bugzilla #979411
https://bugzilla.redhat.com/show_bug.cgi?id=979411
** Also affects: libvirt (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=979411
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1192499
Title:
virsh migration copy-storage-all fails with "Unable to read from
monitor: Connection reset by peer"
Status in QEMU:
New
Status in “libvirt” package in Ubuntu:
Invalid
Status in “libvirt” package in Fedora:
Unknown
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 :
Interrupting
2013-06-19 08:43:12.253+0000: 4026: debug : virEventPollAddTimeout:248 :
EVENT_POLL_ADD_TIMEOUT: timer=1 frequency=0 cb=0x7fe930baa960 opaque=(nil)
ff=(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'>
<name>VM1</name>
<uuid>47feb0e1-0c23-9be9-da12-2ead34864de2</uuid>
<memory unit='KiB'>4096000</memory>
<currentMemory unit='KiB'>2048000</currentMemory>
<vcpu placement='auto'>1</vcpu>
<numatune>
<memory mode='strict' nodeset='0'/>
</numatune>
<os>
<type arch='x86_64' machine='pc-i440fx-1.5'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/local/bin/qemu-system-x86_64</emulator>
<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>
<disk type='block' device='cdrom'>
<driver name='qemu' type='raw'/>
<target dev='hdc' bus='ide'/>
<readonly/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
</disk>
<controller type='usb' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
function='0x2'/>
</controller>
<controller type='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
function='0x1'/>
</controller>
<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'
function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' listen='127.0.0.1'>
<listen type='address' address='127.0.0.1'/>
</graphics>
<video>
<model type='cirrus' vram='9216' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02'
function='0x0'/>
</video>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05'
function='0x0'/>
</memballoon>
</devices>
<seclabel type='none' model='selinux'/>
</domain>
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1192499/+subscriptions
- [Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer",
chandrashekar shastri <=
- [Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer", chandrashekar shastri, 2013/07/05
- [Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer", chandrashekar shastri, 2013/07/05
- [Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer", chandrashekar shastri, 2013/07/05
- [Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer", chandrashekar shastri, 2013/07/05
- [Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer", Stefan Hajnoczi, 2013/07/05
- [Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer", chandrashekar shastri, 2013/07/05
- [Qemu-devel] [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer", Stefan Hajnoczi, 2013/07/19