Bug 554961 - add rudimentary libvirt support
Summary: add rudimentary libvirt support
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Barak
QA Contact: yeylon@redhat.com
Depends On: 563854
TreeView+ depends on / blocked
Reported: 2010-01-13 08:17 UTC by Dan Kenigsberg
Modified: 2016-04-18 06:28 UTC (History)
8 users (show)

Fixed In Version: vdsm-4.9-2
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2010-07-02 19:56:24 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Dan Kenigsberg 2010-01-13 08:17:18 UTC
Some time in rhev-6.0 we would like to have vdsm fire up VMs via libvirt, and not through qemu directly. To simplify future development, I'd like to add some of the basic support right now, turned off by default. Turning it on depends on having newer (and still unavailable) libvirt.

Comment 1 Dan Kenigsberg 2010-01-13 10:26:36 UTC
this change must not have any effect on vdsm behavior. it will always be off outside my test machines. qa should not worry about it, though as in any change, few bugs might be creeping.

Comment 2 Barak 2010-01-21 15:07:24 UTC
Didn't make it into 2.2 moving it to 3.0

Comment 3 Haim 2010-05-23 12:29:31 UTC
vdsm and libvirt integration effort started already and most of the basic features are working, thus, we have a tracker bug for libvirt and vdsm intergeneration effort - bz 581275 (contains all bugs opened on this project already) .
closing this bug as verified. 

currently we support the following: 

- create command is done using libvirt while we create an xml and fire it up via 
- vm life-cycle (start, stop, pause, migrate)

Comment 4 releng-rhel@redhat.com 2010-07-02 19:56:24 UTC
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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