Re: [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
On 07/05/2013 01:52 PM, Stefan Hajnoczi wrote: > 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 > libvirt): > >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 > ::1234" in the QEMU monitor. I tried this "migrate -b tcp ::1234" comes out and gives me the qemu prompt [ I mean it doesn't wait till the migration completes] and also on the destination the image is not growing, the status shows paused. ~Shastri > > 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1199416] [NEW] Hot-add qcow2 [virtio-scsi] devices doesn't work in SlLES-11-SP2guest
Public bug reported: The hot-adding virtio-scsi devices doesn't get recognized the sles guest even after running the rescan-scsi-bus.sh or echo ' - - - ' > /sys/class/scsi_host/host#/scan commands. It requires a reboot to get recognized. This issue is not observed in case of rhel64-64 guests, soon after adding if we run the echo ' - - - ' > /sys/class/scsi_host/host#/scan, the devices gets recognizes. Sles Guest kernel : 3.0.13-0.27-default qemu-version : 1.5.50 Host kernel : 3.10.0-rc5+ Steps to reproduce: 1. Install the sles guest 2. Run the script to add the devices #!/usr/bin/bash if [ x$1 != x ]; then cmd=$1 c=1 while [ $c -le 2 ] do qemu-img create -f qcow2 /home/virtio-scsi$c.qcow2 1G #sleep 1 i="`cat file | head -$c | tail -1`" virsh attach-disk $cmd /home/images/virtio-scsi$c.qcow2 $i --persistent --cache writethrough --sourcetype file --driver qemu --subdriver qcow2 #virsh detach-disk $cmd $i ((c++)) done else echo "enter the vm name" fi 3. Run the rescan-scsi-bus.sh or echo ' - - - ' > /sys/class/scsi_host/host#/scan commands, inside the guest. ## rescan-scsi-bus.sh Host adapter 0 (ata_piix) found. Host adapter 1 (ata_piix) found. Host adapter 2 (sym53c8xx) found. Host adapter 3 (sym53c8xx) found. Host adapter 4 (sym53c8xx) found. Host adapter 5 (sym53c8xx) found. Host adapter 6 (sym53c8xx) found. Host adapter 7 (sym53c8xx) found. Host adapter 8 (sym53c8xx) found. Host adapter 9 (sym53c8xx) found. Host adapter 10 (sym53c8xx) found. Host adapter 11 (sym53c8xx) found. Host adapter 12 (sym53c8xx) found. Host adapter 13 (sym53c8xx) found. Host adapter 14 (sym53c8xx) found. Host adapter 15 (sym53c8xx) found. Host adapter 16 (sym53c8xx) found. Host adapter 17 (sym53c8xx) found. Host adapter 18 (sym53c8xx) found. Host adapter 19 (sym53c8xx) found. Host adapter 20 (sym53c8xx) found. Host adapter 21 (sym53c8xx) found. Host adapter 22 (sym53c8xx) found. Host adapter 23 (sym53c8xx) found. Host adapter 24 (sym53c8xx) found. Host adapter 25 (sym53c8xx) found. Host adapter 26 (sym53c8xx) found. Scanning SCSI subsystem for new devices Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning for device 0 0 0 0 ... OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: QEMU HARDDISKRev: 1.5. Type: Direct-AccessANSI SCSI revision: 05 Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning for device 1 0 0 0 ... OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: QEMU Model: QEMU DVD-ROM Rev: 1.5. Type: CD-ROM ANSI SCSI revision: 05 Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 3 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 4 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 5 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 6 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 7 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 8 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 9 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 10 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 11 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 12 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 13 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 14 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 15 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 16 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 17 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 18 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 19 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 20 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 21 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 22 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 23 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 24 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 25 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 26 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs 0 new device(s) found. 0 device(s) removed. 4. At this point the devices should recognize, but it won't Note: " fdisk -l /dev/sd* | grep -v /dev/sda " only after rebooting the guest. ** Affects: ubuntu Importance: Undecided Status: New ** Affects: opensuse Importance: Undecided Status: New ** Package changed: linux-lts-raring (Ubuntu) => ubuntu ** Also affects: opensuse Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1199416 Title: Hot-add qcow2 [virtio-s
[Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
Thanks, I ll work on this and update it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
** Attachment added: "Destination Libvirtd logs" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725331/+files/destination_libvirtd.logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
** Attachment added: "source guest logs" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725328/+files/source.log.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
** Attachment added: "Source Libvirtd logs" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725330/+files/source_libvirtd.logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
** Attachment added: "Destination guest logs" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725329/+files/dest.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
I am sorry. Host Kernel : 3.10.0-rc5+ [upstream kernel fedora base], both the source and destination host are the same. We test the upstream kernel, qemu and libvirt. We don't have ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
On 06/29/2013 12:15 AM, Serge Hallyn wrote: > Thanks for submitting this bug. I can' t reproduce it with an empty > image (sitting at cd boot menu). > > What is the underlying fs (/home/images) on both source and destination? For both source and destination the fs is ext4. > > Could you run 'apport-collect 1192499' on the destination host? We are using fedora base, hence I have attached the sosreport of both source and destination in the bug. > > Oh, actually I notice you have > > /usr/local/bin/qemu-system-x86_64 > > listed as the emulator in the .xml. That is not the qemu-system-x86_64 > shipped with the qemu-system-x86 package. Does switching that for > > /usr/bin/qemu-system-x86_64 We tried with /usr/bin/qemu-system-x86_64 and we are facing the same issue. > > and see if that helps matters? > > ** Changed in: libvirt (Ubuntu) > Status: New => Incomplete > Thanks, Shastri -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
** Attachment added: "Source sosreport" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3720183/+files/sosreport-source.1192499-20130701151939-cc68.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192499] Re: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
We tried with /usr/bin/qemu-system-x86_64 and we are facing the same issue. For both source and destination the fs is ext4. We are using fedora base, hence I have attached the sosreport of both source and destination. ** Attachment added: "Destination sosreport" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3720182/+files/sosreport-destination.1192499-20130701054850-8f87.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192847] Re: NMI watchdog fails to increment the NMI counter in /proc/interrupts
I tried with QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2) and I was able to reproduce the issue [ NMI counter didn't increment]. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192847 Title: NMI watchdog fails to increment the NMI counter in /proc/interrupts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1192847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192847] [NEW] NMI watchdog fails to increment the NMI counter in /proc/interrupts
Public bug reported: NMI watchdog fails to increment the NMI counter in /proc/interrupts Kernel Version: 3.10.0-rc5+ Libvirt Version: 1.0.6 Qemu Version: 1.5.50 Steps to reproduce the issue: 1. Booted the VM with : qemu-system-x86_64 VM1.qcow2 -enable-kvm -watchdog i6300esb -watchdog-action reset -smp 2 -m 2000 2. Edit the /boot/grub/grub/grub.conf with "nmi_watchdog = 1" before the initrd image. 3. Restart the guests, the NMI counter in /proc/interrupts was 0 4. Installed the watchdog rpm and ran chkconfig watchdog on 5. Restart the guest, even then the NMI counter did not increment 6. Changed the /boot/grub/grub/grub.conf with "nmi_watchdog = 1" to /boot/grub/grub/grub.conf with "nmi_watchdog = 2" and restarted the guest. Even then NMI conuter did not increment (The NMI counter was showing 0 all the time for all the above steps). ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192847 Title: NMI watchdog fails to increment the NMI counter in /proc/interrupts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192499] [NEW] virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer"
Public bug reported: 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+: 4026: debug : virEventPollInterruptLocked:716 : Interrupting 2013-06-19 08:43:12.253+: 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: VM1 47feb0e1-0c23-9be9-da12-2ead34864de2 4096000 2048000 1 hvm destroy restart restart /usr/local/bin/qemu-system-x86_64 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Libvirt Debug logs" https://bugs.launchpad.net/bugs/1192499/+attachment/3707239/+files/migrate.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192499 Title: virsh migration copy-storage-all fails with "Unable to read from monitor: Connection reset by peer" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
