Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1344509

Summary: Cannot start domain - Transport endpoint is not connected
Product: [Fedora] Fedora Reporter: Pavel Grunt <pgrunt>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: agedosier, berrange, clalancette, crobinso, itamar, 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-09 20:40:36 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:
Attachments:
Description Flags
dumpxml of the domain none

Description Pavel Grunt 2016-06-09 20:27:32 UTC 
Created attachment 1166427 [details]
dumpxml of the domain

Description of problem:
Cannot start any domain, it always fails with an error:
Failed to recv file descriptor: Transport endpoint is not connected

Version-Release number of selected component (if applicable):
libvirt-client-1.3.5-1.fc25.x86_64
libvirt-daemon-1.3.5-1.fc25.x86_64

How reproducible:
100%

Steps to Reproduce:
1. virsh start domain

Actual results:
error: Failed to start domain domain
error: Failed to recv file descriptor: Transport endpoint is not connected

Expected results:
domain starts
Comment 1 Cole Robinson 2016-06-09 20:40:36 UTC 

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