[Ovirt-devel] QCOW2 image support?

[Perry Myers]

Daire Byrne wrote:
...
>> I also believe that libvirt functionality for snapshots would be
>> required here as well, and I think that is already in libvirt so hopefully we 
>> should just be able to use that.  Probably the most challenging piece
>> would be modifying the db model to track the snapshots.  (Scott you
>> have any thoughts on this?)
> 
> I'm not too bothered about snapshotting running machines (although that 
> would be cool too) so much as the initial creation of a COW image using
> the golden image as a common read-only base. Basically it would be great
> if oVirt could use all the qemu-img functionality.

Agreed.  Nothing preventing us from doing that, just needs additional 
development effort.

>>> Also on an unrelated note is oVirt going to be part of the "Enterprise
>>> Virtualization Manager for Servers" mentioned in Redhat's recent press
>>> release?
>> oVirt is a project developing virtualization management technology on
>> Fedora.  As some parts of Fedora feed into RHEL, some parts of oVirt
>> may feed into RHEL virtualization in the future.
> 
> Okay, thanks. Maybe the press release is talking more about the 
> Qumranet solutions that were acquired. Are there plans to give oVirt 
> the ability to schedule and migrate machines based on load etc. or will 
> this be managed by a separate system (via libvirt)? Is oVirt only
> supposed to be used for used the initial provisioning?

There are plans to provide migration based on load in oVirt.  I don't 
think that'll be part of core libvirt, but it will be part of oVirt. 
oVirt is not just for initial provisioning.  It's about managing the guest 
through it's entire lifecycle, monitoring it, tracking state and 
eventually neat things like chargeback.  Hugh is heading up this effort, 
so I'll let him elaborate :)

Perry