Bug 1382808 - virt-manager unable to connect to libvirt using Xen hypervisor
Summary: virt-manager unable to connect to libvirt using Xen hypervisor
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-07 19:04 UTC by Geoffrey Marr
Modified: 2017-05-03 18:29 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-03 18:29:41 UTC
Type: Bug


Attachments (Terms of Use)
Output of virt-manager after attempting to run a VM with Xen (614 bytes, text/plain)
2016-10-07 19:04 UTC, Geoffrey Marr
no flags Details

Description Geoffrey Marr 2016-10-07 19:04:32 UTC
Created attachment 1208215 [details]
Output of virt-manager after attempting to run a VM with Xen

Description of problem:

Attempted to run  QA:Testcase_Boot_Methods_Xen_Para_Virt [1] testcase and ran into an issue where virt-manager tells me that it was "Unable to connect to libvirt". When I check to see if libvirtd.service is running, it reports status=failed. Also tried using "virt-install" run into "ERROR    Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory". If the directory is manually created, virt-install reports "Connection refused".

Version-Release number of selected component (if applicable):
Fedora 25 Beta 1.1 Workstation x86_64

How reproducible:
Able to reproduce on both bare-metal and in a VM consistently.

Steps to Reproduce:
1. Install Fedora 25 Beta 1.1 Workstation x86_64
2. Install Xen hypervisor and attempt to run a VM
3. Run into "Unable to connect to libvirt"

Additional info:
[1] https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Xen_Para_Virt

Comment 1 Adam Williamson 2016-10-13 00:29:08 UTC
Can you also try running F25 guest on an F23 or F24 host? The criterion only requires the guest side of things to work (that's 'domU' vs 'dom0').

Comment 2 Cole Robinson 2017-05-03 18:29:41 UTC
Connecting to xen works fine in my testing, so I suspect this was a transient issue during the f25 cycle, or maybe upgrade related. Closing, but if anyone can still reproduce, please reopen


Note You need to log in before you can comment on or make changes to this bug.