Bug 1044715

Summary:	libvirt-guests: restoring VMs is reported as failed
Product:	[Fedora] Fedora	Reporter:	Zbigniew Jędrzejewski-Szmek <zbyszek>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	berrange, clalancette, crobinso, itamar, jforbes, laine, libvirt-maint, veillard, virt-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-29 13:36:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Zbigniew Jędrzejewski-Szmek 2013-12-18 21:09:00 UTC

Description of problem:
If I suspend and restore machines using libvirt-guests, errors are logged during resume:

Dec 18 16:02:02 bupkis systemd[1]: Starting Virtual Machine qemu-fedora20.
Dec 18 16:02:02 bupkis systemd-machined[15204]: New machine qemu-fedora20.
Dec 18 16:02:02 bupkis systemd[1]: Started Virtual Machine qemu-fedora20.
Dec 18 16:02:03 bupkis avahi-daemon[20630]: Registering new address record for fe80::fc54:ff:fe25:dd9f on vnet1.*.
Dec 18 16:02:04 bupkis avahi-daemon[20630]: Registering new address record for fe80::fc54:ff:fe19:faab on vnet2.*.
Dec 18 16:02:04 bupkis kernel: virbr0: port 2(vnet2) entered learning state
Dec 18 16:02:05 bupkis libvirtd[21255]: Unable to restore from managed state /var/lib/libvirt/qemu/save/fedora20.save. Maybe the file is corrupted?
Dec 18 16:02:05 bupkis libvirt-guests.sh[9942]: Resuming guest fedora20: done
Dec 18 16:02:05 bupkis kernel: device vnet3 entered promiscuous mode
Dec 18 16:02:05 bupkis kernel: br0: port 4(vnet3) entered forwarding state
Dec 18 16:02:05 bupkis kernel: br0: port 4(vnet3) entered forwarding state

I get the identical sequence for each of my three VMs. AFAICT, they *are* resumed correctly, and even ssh session I had open to the VMs are still working. So the error from libvirtd is quite confusing.

Version-Release number of selected component (if applicable):
libvirt-client-1.2.0-1.fc20.x86_64
libvirt-1.2.0-1.fc20.x86_64
qemu-1.7.0-1.fc20.x86_64

How reproducible:
100%

Steps to Reproduce:
1. sudo systemctl start libvirt-guests
2. sudo systemctl stop libvirt-guests
3. sudo systemctl start libvirt-guests

Comment 1 Fedora End Of Life 2015-05-29 10:02:29 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Cole Robinson 2015-05-31 18:47:38 UTC

Zbigniew, have you seen this at all with f21+?

Comment 3 Fedora End Of Life 2015-06-29 13:36:31 UTC

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Zbigniew Jędrzejewski-Szmek 2015-06-29 15:09:31 UTC

So, I finally got around to testing this again. Seems to be fixed in F21.