[Users] oVirt 3.3.3 RC EL6 Live Snapshot
Steve Dainard
sdainard at miovision.com
Sun Feb 2 02:08:28 UTC 2014
I have two CentOS 6.5 Ovirt hosts (ovirt001, ovirt002)
I've installed the applicable qemu-kvm-rhev packages from this site:
http://www.dreyou.org/ovirt/vdsm32/Packages/ on ovirt002.
On ovirt001 if I take a live snapshot:
Snapshot 'test qemu-kvm' creation for VM 'snapshot-test' was initiated by
admin at internal.
The VM is paused
Failed to create live snapshot 'test qemu-kvm' for VM 'snapshot-test'. VM
restart is recommended.
Failed to complete snapshot 'test qemu-kvm' creation for VM 'snapshot-test'.
The VM is then started, and the status for the snapshot changes to OK.
On ovirt002 (with the packages from dreyou) I don't get any messages about
a snapshot failing, but my VM is still paused to complete the snapshot. Is
there something else other than the qemu-kvm-rhev packages that would
enable this functionality?
I've looked for some information on when the packages would be built as
required in the CentOS repos, but I don't see anything definitive.
http://lists.ovirt.org/pipermail/users/2013-December/019126.html Looks like
one of the maintainers is waiting for someone to tell him what flags need
to be set.
Also, another thread here:
http://comments.gmane.org/gmane.comp.emulators.ovirt.arch/1618 same
maintainer, mentioning that he hasn't seen anything in the bug tracker.
There is a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1009100 that
seems to have ended in finding a way for qemu to expose whether it supports
live snapshots, rather than figuring out how to get the CentOS team the
info they need to build the packages with the proper flags set.
I have bcc'd both dreyou (packaged the qemu-kvm-rhev packages listed above)
and Russ (CentOS maintainer mentioned in the other threads) if they wish to
chime in and perhaps collaborate on which flags, if any, should be set for
the qemu-kvm builds so we can get a CentOS bug report going and hammer this
out.
Thanks everyone.
**crosses fingers and hopes for live snapshots soon**
*Steve Dainard *
IT Infrastructure Manager
Miovision <http://miovision.com/> | *Rethink Traffic*
519-513-2407 ex.250
877-646-8476 (toll-free)
*Blog <http://miovision.com/blog> | **LinkedIn
<https://www.linkedin.com/company/miovision-technologies> | Twitter
<https://twitter.com/miovision> | Facebook
<https://www.facebook.com/miovision>*
------------------------------
Miovision Technologies Inc. | 148 Manitou Drive, Suite 101, Kitchener, ON,
Canada | N2C 1L3
This e-mail may contain information that is privileged or confidential. If
you are not the intended recipient, please delete the e-mail and any
attachments and notify us immediately.
On Fri, Jan 31, 2014 at 1:26 PM, Steve Dainard <sdainard at miovision.com>wrote:
>
>> How would you developers, speaking for the oVirt-community, propose to
>> solve this for CentOS _now_ ?
>>
>> I would imagine that the easiest way is that you build and host this one
>> package(qemu-kvm-rhev), since you´ve basically already have the source
>> and recipe (since you´re already providing it for RHEV anyway). Then,
>> once that´s in place, it´s more a question of where to host the
>> packages, in what repository. Be it your own, or some other repo set up
>> for the SIG.
>>
>> This is my view, how I as a user view this issue.
>>
>>
>>
> I think this is a pretty valid view.
>
> What would it take to get the correct qemu package hosted in the ovirt
> repo?
>
>
>
>> --
>>
>> Med Vänliga Hälsningar
>>
>>
>> -------------------------------------------------------------------------------
>> Karli Sjöberg
>> Swedish University of Agricultural Sciences Box 7079 (Visiting Address
>> Kronåsvägen 8)
>> S-750 07 Uppsala, Sweden
>> Phone: +46-(0)18-67 15 66
>> karli.sjoberg at slu.se
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140201/8e8bfb6b/attachment-0001.html>
More information about the Users
mailing list