FS#52689 - [libvirt] libvirtd quit during handshake: Input/output error

Attached to Project: Community Packages
Opened by John Shepard (jsheppardy) - Monday, 23 January 2017, 20:52 GMT
Last edited by Sergej Pupykin (sergej) - Sunday, 05 March 2017, 05:36 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No

Details

Description:
Qemu libvirt cannot start a virtual machine.
From the logs:
>>libvirtd quit during handshake: Input/output error<<

Additionally it is impossible to create a new guest. Fails with the same error.

Additional info:

/var/log/libvirt/qemu/>>DomainName<<.log

2017-01-23 19:29:24.419+0000: starting up libvirt version: 3.0.0, qemu version: 2.8.0, hostname: HOSTNAME.lan
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/sbin/qemu-system-x86_64 -name guest=GUEST,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-GUEST/master-key.aes -machine pc-i440fx-2.8,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Haswell -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid ec8c9a5f-738d-4178-ab57-07afda042758 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-GUEST/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/dev/vms/GUEST,format=raw,if=none,id=drive-virtio-disk0,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:ad:3d:c6,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
libvirt: error : libvirtd quit during handshake: Input/output error

Additional info:
* package version(s)
libvirt 3.0.0-1
libvirt-glib 1.0.0-1
libvirt-python 2.5.0-1
* config and/or log files etc.
/var/log/libvirt/qemu/>>DomainName<<.log

Steps to reproduce:
1) Create a virtual machine in virt manager/virsh with qemu with kvm enabled.
2) Upgrade packages:
libvirt 2.5.0-1 -> 3.0.0-1
libvirt-glib 0.2.3-1 -> 1.0.0-1
libvirt-python 2.2.0-2 -> 2.5.0-1
3) Launch a virtual machine.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Sunday, 05 March 2017, 05:36 GMT
Reason for closing:  Fixed
Comment by Michael Oczak (dsoul) - Tuesday, 24 January 2017, 09:08 GMT
same here
Comment by John Shepard (jsheppardy) - Tuesday, 24 January 2017, 10:24 GMT
Nice. I just saw that I craped up the Category, Architecture and Serverity... Noscript and browser reloads... Sorry about that...

As far as I can see there was a bug report made and a fix applied within the libvirt developer team.
https://bugzilla.redhat.com/show_bug.cgi?id=1413773

It looks like the problem seems to be symlinks to some devices, however they have a fix applied. I guess the next update will ship that fix.

Comment by Iacopo Isimbaldi (isiachi) - Wednesday, 25 January 2017, 22:27 GMT
Same problem
Comment by viq (viq) - Friday, 27 January 2017, 07:55 GMT
I'm seeing the same thing. Are there any plans to do something about this, or are we waiting for next release?
Comment by Kevin Piche (kpiche) - Sunday, 29 January 2017, 04:49 GMT Comment by Mark Titorenko (mjtko) - Saturday, 04 February 2017, 16:50 GMT
Ouch. This also caught me out. After upgrading, I was no longer able to start my KVM VMs.

As @kpiche says, the two patches above work and a manual download of the PKGBUILD (and other sources) for libvirt, modifiying the prepare section to apply the patches and a makepkg finally generated me a usable libvirt package.

Hope this gets fixed upstream/in community soon, this was the most pain I've suffered during an upgrade in a long time!
Comment by Ejner Fergo (numasan) - Friday, 10 February 2017, 15:32 GMT
I'm also hit by this problem, specifically creating VMs on LVM volumes. There is no problem creating VMs using disk-images on a regular fs-path. So:

--disk path=/dev/vg/vmvol = FAIL
--disk vol=pool/vmvol = FAIL
--disk path=/tmp/image/vm.img,size=5 = OK
Comment by Oliver Nisumaa (eragon) - Sunday, 12 February 2017, 17:48 GMT
Same here. An easy fix until these patches get to upstream/community is to add the LVM volume directly as /dev/something in virt-manager.
Comment by Lele aka eldios (eldios) - Thursday, 23 February 2017, 18:32 GMT
Any news/ETA about those patches reaching the community repo?

Thank you
Comment by Sergej Pupykin (sergej) - Thursday, 23 February 2017, 19:59 GMT
I'll try to take a look to this and other 5 libvirt bugs next week.
Comment by Lele aka eldios (eldios) - Thursday, 23 February 2017, 21:15 GMT
Thanks Sergej.
Comment by Sergej Pupykin (sergej) - Tuesday, 28 February 2017, 18:15 GMT Comment by Sergej Pupykin (sergej) - Friday, 03 March 2017, 19:15 GMT
was it fixed by 3.1.0?
Comment by Ejner Fergo (numasan) - Saturday, 04 March 2017, 22:58 GMT
Yes, with 3.1.0 I can install VMs on a LVM vol/pool now. Thanks!

Loading...