Description of problem: After upgrading to Fedora 18, virt-manager and other virtualization related commands did not work. virsh list --all returned: ERROR unable to connect to 'localhost:8000': Connection refused xendomain, xenconsoled, and xenstoraged were still enabled and running. It took me a while to realize the problem was easily solved by simply starting (and enabling) xend. Version-Release number of selected component (if applicable): How reproducible: Since it was the result of the upgrade, it's hard to reproduce. I am mostly hoping to document my experience for others. Whatever caused xend to be disabled my be quite obscure. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Easily diagnosed by: systemctl is-enabled xend.service If disabled and not started: systemctl enable xend.service systemctl start xend.service
fedup does not directly touch any services. All it does is install packages. If you're having a problem with xend, this is a bug with the xen package, or some other package that disabled xend.service. Reassigning to xen.
xend.service was probably disabled in your Fedora 17 as well so fedup didn't change anything. You didn't notice this as there is a bug in Fedora 17 which means libvirt starts xend rather than checking it is running. In Fedora 18 changes to libvirt means that it notices something strange is happening and reports that xend isn't running (when technically it is). These issues with xend and libvirt in Fedora 18 are being dealt with in Bug 893699. *** This bug has been marked as a duplicate of bug 893699 ***
(In reply to comment #2) > xend.service was probably disabled in your Fedora 17 as well so fedup didn't > change anything. You didn't notice this as there is a bug in Fedora 17 which > means libvirt starts xend rather than checking it is running. > > In Fedora 18 changes to libvirt means that it notices something strange is > happening and reports that xend isn't running (when technically it is). > > These issues with xend and libvirt in Fedora 18 are being dealt with in Bug > 893699. > > *** This bug has been marked as a duplicate of bug 893699 *** Thanks for the explanation.