Bug 1346630

Summary:	Unable to start domain "Failed to recv file descriptor: Transport endpoint is not connected"
Product:	[Fedora] Fedora	Reporter:	York Possemiers <ypossem>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	agedosier, berrange, clalancette, itamar, jdenemar, laine, libvirt-maint, veillard, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-15 06:53:56 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:
Embargoed:

Description York Possemiers 2016-06-15 06:38:11 UTC

Description of problem:
As the title states


Version-Release number of selected component (if applicable):
Looking at dnf history, guessing it occurred somewhere between libvirt-daemon 1.3.4-2.fc25.x86_64 and 1.3.5-1.fc25.x86_64 

How reproducible:
100%

Steps to Reproduce:
1. Upgrade system
2. Attempt to start pre-existing domain with either virt-manager or virsh

Was already running in Permissive mode, so selinux likely not involved

Comment 1 York Possemiers 2016-06-15 06:43:24 UTC

Also just tested against a previously known good kernel, ruling that out.

Comment 2 Jiri Denemark 2016-06-15 06:53:56 UTC


*** This bug has been marked as a duplicate of bug 1344016 ***