<div dir="ltr">Just for clarity on that bug report; are you suggesting that the guest must go into a paused state to take a snapshot and that the admin shouldn&#39;t be aware of this state?<div><br></div><div>Although not horribly concerning for most tasks, wouldn&#39;t this lead to a 10 second clock skew every time there is a snapshot? Or does the guest sync from host hw clock on resume?</div>
<div><br></div><div>Thanks,</div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:16px"><strong>Steve Dainard </strong></span><span style="font-size:12px"></span><br>

<span style="font-family:arial,sans-serif;font-size:12px">IT Infrastructure Manager<br>
<a href="http://miovision.com/" target="_blank">Miovision</a> | <em>Rethink Traffic</em><br>
519-513-2407 ex.250<br>
877-646-8476 (toll-free)<br>
<br>
<strong style="font-family:arial,sans-serif;font-size:13px;color:#999999"><a href="http://miovision.com/blog" target="_blank">Blog</a>  |  </strong><font color="#999999" style="font-family:arial,sans-serif;font-size:13px"><strong><a href="https://www.linkedin.com/company/miovision-technologies" target="_blank">LinkedIn</a>  |  <a href="https://twitter.com/miovision" target="_blank">Twitter</a>  |  <a href="https://www.facebook.com/miovision" target="_blank">Facebook</a></strong></font> </span>
<hr style="font-family:arial,sans-serif;font-size:13px;color:#333333;clear:both">
<div style="color:#999999;font-family:arial,sans-serif;font-size:13px;padding-top:5px">
        <span style="font-family:arial,sans-serif;font-size:12px">Miovision Technologies Inc. | 148 Manitou Drive, Suite 101, Kitchener, ON, Canada | N2C 1L3</span><br>
        <span style="font-family:arial,sans-serif;font-size:12px">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.</span></div>
</div></div>
<br><br><div class="gmail_quote">On Tue, Feb 4, 2014 at 3:44 AM, Dafna Ron <span dir="ltr">&lt;<a href="mailto:dron@redhat.com" target="_blank">dron@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 02/04/2014 08:20 AM, Elad Ben Aharon wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 From what I saw in the thread, libvirt pauses the VM, which effects the continuity of its operation.<br>
I checked it also in one of the latest builds of 3.3 and I observed the same behaviour:<br>
2014-02-04 10:18:29,441 INFO  [org.ovirt.engine.core.<u></u>vdsbroker.<u></u>VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_<u></u>Worker-22) [5cbc7ab5] VM nfs2-1 86728f5c-3583-420f-9536-<u></u>bfabaf11b235 moved from Up --&gt; Paused<br>

<br>
Dafna, I saw you&#39;ve already opened a bug on that:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1057587" target="_blank">https://bugzilla.redhat.com/<u></u>show_bug.cgi?id=1057587</a><br>
</blockquote>
<br></div>
just proves I&#39;m getting senile :)<div class="HOEnZb"><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
----- Original Message -----<br>
From: &quot;Dafna Ron&quot; &lt;<a href="mailto:dron@redhat.com" target="_blank">dron@redhat.com</a>&gt;<br>
To: &quot;Maor Lipchuk&quot; &lt;<a href="mailto:mlipchuk@redhat.com" target="_blank">mlipchuk@redhat.com</a>&gt;<br>
Cc: &quot;Steve Dainard&quot; &lt;<a href="mailto:sdainard@miovision.com" target="_blank">sdainard@miovision.com</a>&gt;, &quot;Elad Ben Aharon&quot; &lt;<a href="mailto:ebenahar@redhat.com" target="_blank">ebenahar@redhat.com</a>&gt;, &quot;Karli Sjöberg&quot; &lt;<a href="mailto:Karli.Sjoberg@slu.se" target="_blank">Karli.Sjoberg@slu.se</a>&gt;, <a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a><br>

Sent: Tuesday, February 4, 2014 12:15:42 AM<br>
Subject: Re: [Users] oVirt 3.3.3 RC EL6 Live Snapshot<br>
<br>
Maor I am not saying that we are not doing a live snapshot :) I am<br>
saying that we need a print in the log that states live snapshot command<br>
was called i.e: Print in the log: LiveSnapshotCommand -&gt; this can call<br>
to the rest of snapshotVDSCreateCommand.<br>
<br>
<br>
On 02/03/2014 07:38 PM, Maor Lipchuk wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 02/03/2014 07:46 PM, Dafna Ron wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 02/03/2014 05:34 PM, Maor Lipchuk wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 02/03/2014 07:18 PM, Dafna Ron wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Maor,<br>
<br>
If snapshotVDSCommand is for live snapshot, what is the offline create<br>
snapshot command?<br>
</blockquote>
It is the CreateSnapshotVdsCommand which calls createVolume in VDSM<br>
</blockquote>
but we need to be able to know that a live snapshot was sent and not an<br>
offline snapshot.<br>
</blockquote>
Yes, at the logs we can see the all process :<br>
<br>
First a request to create a snapshot (new volume) sent to VDSM:<br>
2014-02-02 09:41:09,557 INFO<br>
[org.ovirt.engine.core.<u></u>vdsbroker.irsbroker.<u></u>CreateSnapshotVDSCommand]<br>
(pool-6-thread-49) [67ea047a] START, CreateSnapshotVDSCommand(<br>
storagePoolId = fcb89071-6cdb-4972-94d1-<u></u>c9324cebf814,<br>
ignoreFailoverLimit = false, storageDomainId =<br>
a52938f7-2cf4-4771-acb2-<u></u>0c78d14999e5, imageGroupId =<br>
c1cb6b66-655e-48c3-8568-<u></u>4975295eb037, imageSizeInBytes = 21474836480,<br>
volumeFormat = COW, newImageId = 6d8c80a4-328f-4a53-86a2-<u></u>a4080a2662ce,<br>
newImageDescription = , imageId = 5085422e-6592-415a-9da3-<u></u>9e43dac9374b,<br>
sourceImageGroupId = c1cb6b66-655e-48c3-8568-<u></u>4975295eb037), log id: 7875f3f5<br>
<br>
after the snapshot gets created :<br>
2014-02-02 09:41:20,553 INFO<br>
[org.ovirt.engine.core.bll.<u></u>CreateAllSnapshotsFromVmComman<u></u>d]<br>
(pool-6-thread-49) Ending command successfully:<br>
org.ovirt.engine.core.bll.<u></u>CreateAllSnapshotsFromVmComman<u></u>d<br>
<br>
then the engine calls the live snapshot (see also [1])<br>
2014-02-02 09:41:30,234 INFO<br>
[org.ovirt.engine.core.<u></u>vdsbroker.vdsbroker.<u></u>SnapshotVDSCommand]<br>
(pool-6-thread-49) FINISH, SnapshotVDSCommand, log id: 7e0d7872<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Elad, somewhere in this flow we need to know that the snapshot was taken<br>
on a running vm :) this seems like a bug to me.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
we did not say that live snapshot did not succeed :)  we said that the<br>
vm is paused and restarted - which is something that should not happen<br>
for live snapshot (or at least never did before).<br>
</blockquote>
It&#39;s not sure that the restart is related to the live snapshot. but that<br>
should be observed in the libvirt/vdsm logs.<br>
</blockquote>
yes, I am sure because the user is reporting it and the logs show it...<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
as I wrote before, we know that vdsm is reporting the vm as paused, that<br>
is because libvirt is reporting the vm as paused and I think that its<br>
happening because libvirt is not doing a live snapshot and so pauses the<br>
vm while taking the snapshot.<br>
</blockquote>
That sounds logic to me, it&#39;s need to be checked with libvirt, if that<br>
kind of behaviour could happen.<br>
</blockquote>
Elad, can you please try to reproduce and open a bug to libvirt?<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dafna<br>
<br>
<br>
On 02/03/2014 05:08 PM, Maor Lipchuk wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
    From the engine logs it seems that indeed live snapshot is called<br>
(The<br>
command is snapshotVDSCommand see [1]).<br>
This is done right after the snapshot has been created in the VM and it<br>
signals the qemu process to start using the new volume created.<br>
<br>
When live snapshot does not succeed we should see in the log something<br>
like &quot;Wasn&#39;t able to live snapshot due to error:...&quot;, but it does not<br>
appear so it seems that this worked out fine.<br>
<br>
At some point I can see in the logs that VDSM reports to the engine<br>
that<br>
the VM is paused.<br>
<br>
<br>
[1]<br>
2014-02-02 09:41:20,564 INFO<br>
[org.ovirt.engine.core.<u></u>vdsbroker.vdsbroker.<u></u>SnapshotVDSCommand]<br>
(pool-6-thread-49) START, SnapshotVDSCommand(HostName = ovirt002,<br>
HostId<br>
= 3080fb61-2d03-4008-b47f-<u></u>9b66276a4257,<br>
vmId=e261e707-a21f-4ae8-9cff-<u></u>f535f4430446), log id: 7e0d7872<br>
2014-02-02 09:41:21,119 INFO<br>
[org.ovirt.engine.core.<u></u>vdsbroker.<u></u>VdsUpdateRunTimeInfo]<br>
(DefaultQuartzScheduler_<u></u>Worker-93) VM snapshot-test<br>
e261e707-a21f-4ae8-9cff-<u></u>f535f4430446 moved from Up --&gt; Paused<br>
2014-02-02 09:41:30,234 INFO<br>
[org.ovirt.engine.core.<u></u>vdsbroker.vdsbroker.<u></u>SnapshotVDSCommand]<br>
(pool-6-thread-49) FINISH, SnapshotVDSCommand, log id: 7e0d7872<br>
2014-02-02 09:41:30,238 INFO<br>
[org.ovirt.engine.core.bll.<u></u>CreateSnapshotCommand] (pool-6-thread-49)<br>
[67ea047a] Ending command successfully:<br>
org.ovirt.engine.core.bll.<u></u>CreateSnapshotCommand<br>
...<br>
<br>
Regards,<br>
Maor<br>
<br>
On 02/03/2014 06:24 PM, Dafna Ron wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Steve.<br>
<br>
from the logs I can see that the create snapshot succeeds and that the<br>
vm is resumed.<br>
the vm moves to pause as part of libvirt flows:<br>
<br>
2014-02-02 14:41:20.872+0000: 5843: debug :<br>
qemuProcessHandleStop:728 :<br>
Transitioned guest snapshot-test to paused state<br>
2014-02-02 14:41:30.031+0000: 5843: debug :<br>
qemuProcessHandleResume:776<br>
: Transitioned guest snapshot-test out of paused into resumed state<br>
<br>
There are bugs here but I am not sure yet if this is libvirt<br>
regression<br>
or engine.<br>
<br>
I&#39;m adding Elad and Maor since in engine logs I can&#39;t see anything<br>
calling for live snapshot (only for snapshot) - Maor, shouldn&#39;t live<br>
snapshot command be logged somewhere in the logs?<br>
Is it possible that engine is calling to create snapshot and not<br>
create<br>
live snapshot which is why the vm pauses?<br>
<br>
Elad, if engine is not logging live snapshot anywhere I would open<br>
a bug<br>
for engine (to print that in the logs).<br>
Also, there is a bug in vdsm log for sdc where the below is logged as<br>
ERROR and not INFO:<br>
<br>
Thread-23::ERROR::2014-02-02<br>
09:51:19,497::sdc::137::<u></u>Storage.StorageDomainCache::(_<u></u>findDomain)<br>
looking for unfetched domain a52938f7-2cf4-4771-acb2-<u></u>0c78d14999e5<br>
Thread-23::ERROR::2014-02-02<br>
09:51:19,497::sdc::154::<u></u>Storage.StorageDomainCache::(_<u></u>findUnfetchedDomain)<br>
<br>
<br>
looking for domain a52938f7-2cf4-4771-acb2-<u></u>0c78d14999e5<br>
<br>
If the engine was sending live snapshot or if there is no<br>
difference in<br>
the two commands in engine side than I would open a bug for libvirt<br>
for<br>
pausing the vm during live snapshot.<br>
<br>
Dafna<br>
<br>
On 02/03/2014 02:41 PM, Steve Dainard wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[root@ovirt002 ~]# vdsClient -s 0 getStorageDomainInfo<br>
a52938f7-2cf4-4771-acb2-<u></u>0c78d14999e5<br>
uuid = a52938f7-2cf4-4771-acb2-<u></u>0c78d14999e5<br>
pool = [&#39;fcb89071-6cdb-4972-94d1-<u></u>c9324cebf814&#39;]<br>
lver = 5<br>
version = 3<br>
role = Master<br>
remotePath = gluster-store-vip:/rep1<br>
spm_id = 2<br>
type = NFS<br>
class = Data<br>
master_ver = 1<br>
name = gluster-store-rep1<br>
<br>
<br>
*Steve Dainard *<br>
IT Infrastructure Manager<br>
Miovision &lt;<a href="http://miovision.com/" target="_blank">http://miovision.com/</a>&gt; | /Rethink Traffic/<br>
<a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a> ex.250<br>
<a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a> (toll-free)<br>
<br>
*Blog &lt;<a href="http://miovision.com/blog" target="_blank">http://miovision.com/blog</a>&gt; | **LinkedIn<br>
&lt;<a href="https://www.linkedin.com/company/miovision-technologies" target="_blank">https://www.linkedin.com/<u></u>company/miovision-technologies</a><u></u>&gt;  | Twitter<br>
&lt;<a href="https://twitter.com/miovision" target="_blank">https://twitter.com/miovision</a><u></u>&gt;  | Facebook<br>
&lt;<a href="https://www.facebook.com/miovision" target="_blank">https://www.facebook.com/<u></u>miovision</a>&gt;*<br>
------------------------------<u></u>------------------------------<u></u>------------<br>
<br>
<br>
Miovision Technologies Inc. | 148 Manitou Drive, Suite 101,<br>
Kitchener,<br>
ON, Canada | N2C 1L3<br>
This e-mail may contain information that is privileged or<br>
confidential. If you are not the intended recipient, please delete<br>
the<br>
e-mail and any attachments and notify us immediately.<br>
<br>
<br>
On Sun, Feb 2, 2014 at 2:55 PM, Dafna Ron &lt;<a href="mailto:dron@redhat.com" target="_blank">dron@redhat.com</a><br>
&lt;mailto:<a href="mailto:dron@redhat.com" target="_blank">dron@redhat.com</a>&gt;&gt; wrote:<br>
<br>
        please run vdsClient -s 0 getStorageDomainInfo<br>
        a52938f7-2cf4-4771-acb2-<u></u>0c78d14999e5<br>
<br>
        Thanks,<br>
<br>
        Dafna<br>
<br>
<br>
<br>
        On 02/02/2014 03:02 PM, Steve Dainard wrote:<br>
<br>
            Logs attached with VM running on qemu-kvm-rhev packages<br>
installed.<br>
<br>
            *Steve Dainard *<br>
            IT Infrastructure Manager<br>
            Miovision &lt;<a href="http://miovision.com/" target="_blank">http://miovision.com/</a>&gt; | /Rethink Traffic/<br>
            <a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a> &lt;tel:<a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a>&gt; ex.250<br>
<br>
            <a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a> &lt;tel:<a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a>&gt; (toll-free)<br>
<br>
            *Blog &lt;<a href="http://miovision.com/blog" target="_blank">http://miovision.com/blog</a>&gt; | **LinkedIn<br>
           &lt;<a href="https://www.linkedin.com/company/miovision-technologies" target="_blank">https://www.linkedin.com/<u></u>company/miovision-technologies</a><u></u>&gt;  |<br>
            Twitter &lt;<a href="https://twitter.com/miovision" target="_blank">https://twitter.com/miovision</a><u></u>&gt;  | Facebook<br>
            &lt;<a href="https://www.facebook.com/miovision" target="_blank">https://www.facebook.com/<u></u>miovision</a>&gt;*<br>
         ------------------------------<u></u>------------------------------<u></u>------------<br>
<br>
<br>
            Miovision Technologies Inc. | 148 Manitou Drive, Suite 101,<br>
            Kitchener, ON, Canada | N2C 1L3<br>
            This e-mail may contain information that is privileged or<br>
            confidential. If you are not the intended recipient, please<br>
            delete the e-mail and any attachments and notify us<br>
immediately.<br>
<br>
<br>
            On Sun, Feb 2, 2014 at 5:05 AM, Dafna Ron &lt;<a href="mailto:dron@redhat.com" target="_blank">dron@redhat.com</a><br>
            &lt;mailto:<a href="mailto:dron@redhat.com" target="_blank">dron@redhat.com</a>&gt; &lt;mailto:<a href="mailto:dron@redhat.com" target="_blank">dron@redhat.com</a><br>
            &lt;mailto:<a href="mailto:dron@redhat.com" target="_blank">dron@redhat.com</a>&gt;&gt;&gt; wrote:<br>
<br>
                can you please upload full engine, vdsm, libvirt and<br>
vm&#39;s<br>
            qemu logs?<br>
<br>
<br>
                On 02/02/2014 02:08 AM, Steve Dainard wrote:<br>
<br>
                    I have two CentOS 6.5 Ovirt hosts (ovirt001,<br>
ovirt002)<br>
<br>
                    I&#39;ve installed the applicable qemu-kvm-rhev<br>
packages<br>
            from this<br>
                    site:<br>
<a href="http://www.dreyou.org/ovirt/vdsm32/Packages/" target="_blank">http://www.dreyou.org/ovirt/<u></u>vdsm32/Packages/</a> on<br>
            ovirt002.<br>
<br>
                    On ovirt001 if I take a live snapshot:<br>
<br>
                    Snapshot &#39;test qemu-kvm&#39; creation for VM<br>
            &#39;snapshot-test&#39; was<br>
                    initiated by admin@internal.<br>
                    The VM is paused<br>
                    Failed to create live snapshot &#39;test qemu-kvm&#39;<br>
for VM<br>
                    &#39;snapshot-test&#39;. VM restart is recommended.<br>
                    Failed to complete snapshot &#39;test qemu-kvm&#39;<br>
creation<br>
            for VM<br>
                    &#39;snapshot-test&#39;.<br>
                    The VM is then started, and the status for the<br>
snapshot<br>
                    changes to OK.<br>
<br>
                    On ovirt002 (with the packages from dreyou) I don&#39;t<br>
            get any<br>
                    messages about a snapshot failing, but my VM is<br>
still<br>
            paused<br>
                    to complete the snapshot. Is there something else<br>
            other than<br>
                    the qemu-kvm-rhev packages that would enable this<br>
            functionality?<br>
<br>
                    I&#39;ve looked for some information on when the<br>
packages<br>
            would be<br>
                    built as required in the CentOS repos, but I<br>
don&#39;t see<br>
                    anything definitive.<br>
<br>
          <a href="http://lists.ovirt.org/pipermail/users/2013-December/019126.html" target="_blank">http://lists.ovirt.org/<u></u>pipermail/users/2013-December/<u></u>019126.html</a><br>
                    Looks like one of the maintainers is waiting for<br>
            someone to<br>
                    tell him what flags need to be set.<br>
<br>
                    Also, another thread here:<br>
           <a href="http://comments.gmane.org/gmane.comp.emulators.ovirt.arch/1618" target="_blank">http://comments.gmane.org/<u></u>gmane.comp.emulators.ovirt.<u></u>arch/1618</a><br>
                    same maintainer, mentioning that he hasn&#39;t seen<br>
            anything in<br>
                    the bug tracker.<br>
<br>
                    There is a bug here:<br>
            <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1009100" target="_blank">https://bugzilla.redhat.com/<u></u>show_bug.cgi?id=1009100</a> that<br>
seems<br>
                    to have ended in finding a way for qemu to expose<br>
            whether it<br>
                    supports live snapshots, rather than figuring<br>
out how<br>
            to get<br>
                    the CentOS team the info they need to build the<br>
            packages with<br>
                    the proper flags set.<br>
<br>
                    I have bcc&#39;d both dreyou (packaged the<br>
qemu-kvm-rhev<br>
            packages<br>
                    listed above) and Russ (CentOS maintainer<br>
mentioned in<br>
the<br>
                    other threads) if they wish to chime in and perhaps<br>
                    collaborate on which flags, if any, should be set<br>
for the<br>
                    qemu-kvm builds so we can get a CentOS bug report<br>
            going and<br>
                    hammer this out.<br>
<br>
                    Thanks everyone.<br>
<br>
                    **crosses fingers and hopes for live snapshots<br>
soon**<br>
<br>
<br>
<br>
                    *Steve Dainard *<br>
                    IT Infrastructure Manager<br>
                    Miovision &lt;<a href="http://miovision.com/" target="_blank">http://miovision.com/</a>&gt; | /Rethink<br>
Traffic/<br>
            <a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a> &lt;tel:<a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a>&gt; &lt;tel:<a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a><br>

            &lt;tel:<a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a>&gt;&gt; &lt;tel:<a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a> &lt;tel:<a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a>&gt;<br>

                    &lt;tel:<a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a> &lt;tel:<a href="tel:519-513-2407" value="+15195132407" target="_blank">519-513-2407</a>&gt;&gt;&gt; ex.250<br>

            <a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a> &lt;tel:<a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a>&gt; &lt;tel:<a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a><br>

            &lt;tel:<a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a>&gt;&gt; &lt;tel:<a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a> &lt;tel:<a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a>&gt;<br>

<br>
                    &lt;tel:<a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a> &lt;tel:<a href="tel:877-646-8476" value="+18776468476" target="_blank">877-646-8476</a>&gt;&gt;&gt; (toll-free)<br>

<br>
                    *Blog &lt;<a href="http://miovision.com/blog" target="_blank">http://miovision.com/blog</a>&gt; | **LinkedIn<br>
                        &lt;<a href="https://www.linkedin.com/company/miovision-technologies" target="_blank">https://www.linkedin.com/<u></u>company/miovision-technologies</a><u></u>&gt;  |<br>
                    Twitter &lt;<a href="https://twitter.com/miovision" target="_blank">https://twitter.com/miovision</a><u></u>&gt;  | Facebook<br>
                    &lt;<a href="https://www.facebook.com/miovision" target="_blank">https://www.facebook.com/<u></u>miovision</a>&gt;*<br>
                        ------------------------------<u></u>------------------------------<u></u>------------<br>
<br>
<br>
<br>
<br>
                    Miovision Technologies Inc. | 148 Manitou Drive,<br>
Suite<br>
            101,<br>
                    Kitchener, ON, Canada | N2C 1L3<br>
                    This e-mail may contain information that is<br>
privileged or<br>
                    confidential. If you are not the intended<br>
recipient,<br>
            please<br>
                    delete the e-mail and any attachments and notify us<br>
            immediately.<br>
<br>
<br>
                    On Fri, Jan 31, 2014 at 1:26 PM, Steve Dainard<br>
                    &lt;<a href="mailto:sdainard@miovision.com" target="_blank">sdainard@miovision.com</a><br>
            &lt;mailto:<a href="mailto:sdainard@miovision.com" target="_blank">sdainard@miovision.com</a><u></u>&gt;<br>
&lt;mailto:<a href="mailto:sdainard@miovision.com" target="_blank">sdainard@miovision.com</a><br>
            &lt;mailto:<a href="mailto:sdainard@miovision.com" target="_blank">sdainard@miovision.com</a><u></u>&gt;&gt;<br>
                    &lt;mailto:<a href="mailto:sdainard@miovision.com" target="_blank">sdainard@miovision.com</a><br>
            &lt;mailto:<a href="mailto:sdainard@miovision.com" target="_blank">sdainard@miovision.com</a><u></u>&gt;<br>
<br>
                    &lt;mailto:<a href="mailto:sdainard@miovision.com" target="_blank">sdainard@miovision.com</a><br>
            &lt;mailto:<a href="mailto:sdainard@miovision.com" target="_blank">sdainard@miovision.com</a><u></u>&gt;&gt;&gt;&gt; wrote:<br>
<br>
<br>
                            How would you developers, speaking for the<br>
                    oVirt-community,<br>
                            propose to<br>
                            solve this for CentOS _now_ ?<br>
<br>
                            I would imagine that the easiest way is<br>
that<br>
            you build and<br>
                            host this one<br>
                            package(qemu-kvm-rhev), since you´ve<br>
basically<br>
            already<br>
                    have<br>
                            the source<br>
                            and recipe (since you´re already<br>
providing it<br>
            for RHEV<br>
                            anyway). Then,<br>
                            once that´s in place, it´s more a<br>
question of<br>
            where to<br>
                    host the<br>
                            packages, in what repository. Be it your<br>
own,<br>
            or some<br>
                    other<br>
                            repo set up<br>
                            for the SIG.<br>
<br>
                            This is my view, how I as a user view this<br>
issue.<br>
<br>
<br>
<br>
                        I think this is a pretty valid view.<br>
<br>
                        What would it take to get the correct qemu<br>
package<br>
            hosted<br>
                    in the<br>
                        ovirt repo?<br>
<br>
                            --<br>
<br>
                            Med Vänliga Hälsningar<br>
<br>
                                       ------------------------------<u></u>------------------------------<u></u>-------------------<br>
<br>
<br>
<br>
                            Karli Sjöberg<br>
                            Swedish University of Agricultural Sciences<br>
            Box 7079<br>
                    (Visiting<br>
                            Address<br>
                            Kronåsvägen 8)<br>
                            S-750 07 Uppsala, Sweden<br>
                            Phone: <a href="tel:%2B46-%280%2918-67%2015%2066" value="+4618671566" target="_blank">+46-(0)18-67 15 66</a><br>
            &lt;tel:%2B46-%280%2918-67%2015%<u></u>2066&gt;<br>
                    &lt;tel:%2B46-%280%2918-67%2015%<u></u>2066&gt;<br>
                    &lt;tel:%2B46-%280%2918-67%2015%<u></u>2066&gt;<br>
            <a href="mailto:karli.sjoberg@slu.se" target="_blank">karli.sjoberg@slu.se</a> &lt;mailto:<a href="mailto:karli.sjoberg@slu.se" target="_blank">karli.sjoberg@slu.se</a>&gt;<br>
            &lt;mailto:<a href="mailto:karli.sjoberg@slu.se" target="_blank">karli.sjoberg@slu.se</a> &lt;mailto:<a href="mailto:karli.sjoberg@slu.se" target="_blank">karli.sjoberg@slu.se</a>&gt;&gt;<br>
                    &lt;mailto:<a href="mailto:karli.sjoberg@slu.se" target="_blank">karli.sjoberg@slu.se</a><br>
            &lt;mailto:<a href="mailto:karli.sjoberg@slu.se" target="_blank">karli.sjoberg@slu.se</a>&gt; &lt;mailto:<a href="mailto:karli.sjoberg@slu.se" target="_blank">karli.sjoberg@slu.se</a><br>
            &lt;mailto:<a href="mailto:karli.sjoberg@slu.se" target="_blank">karli.sjoberg@slu.se</a>&gt;&gt;<u></u>&gt;<br>
<br>
                          ______________________________<u></u>_________________<br>
                            Users mailing list<br>
            <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>&gt;<br>
            &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>&gt;&gt;<br>
                    &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>&gt;<br>
            &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>&gt;&gt;&gt;<br>
<br>
            <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/users</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
                    ______________________________<u></u>_________________<br>
                    Users mailing list<br>
            <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>&gt;<br>
            &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> &lt;mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>&gt;&gt;<br>
<br>
            <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/users</a><br>
<br>
<br>
<br>
                --     Dafna Ron<br>
<br>
<br>
<br>
<br>
        --     Dafna Ron<br>
<br>
<br>
</blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>
<br>
</blockquote>
<br>
<br>
-- <br>
Dafna Ron<br>
</div></div></blockquote></div><br></div>