Bug 682523

Summary:	virt-manager does not 'see' that libvirtd is running (with video)
Product:	[Fedora] Fedora	Reporter:	pleabargain <dennisgdaniels>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	14	CC:	berrange, crobinso, hbrock, jforbes, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-22 16:02:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description pleabargain 2011-03-06 12:12:10 UTC

Description of problem:

virt-manager will not start
no active connection to install on
asks if libvirtd is running and it is.
Please see video to see the bug(?) in action

Version-Release number of selected component (if applicable):
[user@localhost test]$ virt-manager --version
0.8.5
[user@localhost test]$ libvirtd --version
libvirtd (libvirt) 0.8.3
[user@localhost test]$ uname -r
2.6.35.11-83.fc14.i686


How reproducible:

every time
Steps to Reproduce:
1.start virt-manager
2.try to create connection
3.complains / no connection/ chk libvirtd is running (see video)
  
Actual results:


Expected results:


Additional info:
http://www.youtube.com/watch?v=XsH4g3Zn7QU

Comment 1 Cole Robinson 2011-07-11 16:29:02 UTC

Thanks for the clear video. Not really sure what's causing the problem here.

From the command line, can you show the output of

ps axwww | grep libvirt
service libvirtd status

As root, can you try

virsh --connect qemu:///system 

If that fails, does 'service libvirtd restart' as root make any difference?

Also, in the virt-manager UI, you can double click the 'qemu' row in the main screen to initiate connecting.

Comment 2 Cole Robinson 2011-09-22 16:02:23 UTC

No info for over 2 months, closing as INSUFFICIENT_DATA. If you are still encountering this issue, please reopen with the info requested in comment 1.