Bug 718804

Summary:	Missing Requires: libvirt, qemu-kvm
Product:	[Fedora] Fedora	Reporter:	Severin Gehwolf <sgehwolf>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	berrange, crobinso, hbrock, jforbes, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-11 16:19:52 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 Severin Gehwolf 2011-07-04 17:57:24 UTC

Description of problem:
yum install virt-manager does not install libvirt. However, when virt-manager is started, it complains that no libvirtd is running. Note that libvirtd is provided by libvirt. This may be a Requires: libvirt problem in libvirt-python.

Version-Release number of selected component (if applicable):
$ rpm -q virt-manager
virt-manager-0.8.7-4.fc15.noarch

How reproducible:
Always.

Steps to Reproduce:
1. $ yum install virt-manager (on fresh F15 install)
2. $ virt-manager
3. virt-manager complains about libvirtd not running
  
Actual results:
Error regarding libvirtd not running.
# service libvirtd start
libvirtd: unrecognized service

Expected results:
# service libvirtd start works.

Additional info:
yum install libvirt solves the problem. Note that I ran into a similar problem with respect to qemu-kvm. After installing libvirt, virt-manager started without an error showing up immediately, but it warned me that no KVM/QEMU was available when I tried to create a new VM. It would be nice if virt-manager had reasonable requires so that it may work in theory after a yum install of virt-manager. Am I missing something?

Comment 1 Cole Robinson 2011-07-11 16:19:52 UTC

These are deliberately not hard requirements of virt-manager, since virt-manager can be used with other hypervisors like lxc or xen (so not strictly requiring qemu/kvm) and could be used to only connect to a remote host (thus not requiring libvirtd on local machine).

However virt-manager should try and talk to packagekit on first run and ask the user to install kvm and libvirt. did that not happen for you?

It is a pain for users but we can't use RPM dependencies to work around this issue since it will leave a small subset of users with no recourse except to break RPM deps. This would be a nice case to have a Recommends: or similar in RPM but that doesn't exist yet. Closing as NOTABUG.

Comment 2 Severin Gehwolf 2011-07-11 17:01:22 UTC

(In reply to comment #1)
> These are deliberately not hard requirements of virt-manager, since
> virt-manager can be used with other hypervisors like lxc or xen (so not
> strictly requiring qemu/kvm) and could be used to only connect to a remote host
> (thus not requiring libvirtd on local machine).

Ok.

> However virt-manager should try and talk to packagekit on first run and ask the
> user to install kvm and libvirt. did that not happen for you?

No that didn't happen.

> It is a pain for users but we can't use RPM dependencies to work around this
> issue since it will leave a small subset of users with no recourse except to
> break RPM deps. This would be a nice case to have a Recommends: or similar in
> RPM but that doesn't exist yet. Closing as NOTABUG.

Ok, thanks for clarifying.