[Users] about live snapshot and qemu-kvm
This is a multi-part message in MIME format. --------------080009080202040109020900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi all, I'm about to migrate from the dreyou 3.2 repo to the official 3.3 repositories. I was used to take live snapshot with qemu-kvm-rhev-0.12.1.2-2.355.el6.5.x86_64 which was recompiled from the redhat srpms, because live snapshot was not supported by the official qemu-kvm in el6.4. * Does now 6.5 include the correct qemu-kvm version for live snapshot? * If not why does redhat provide a separate qemu package for RHEV while fedora has got the correct package? * Does ovirt team provide support for el6 live snapshot "out of the box" or do they recommend to get the correct qemu-kvm version from the rhev repository? Assuming that redhat doesn't provide the same qemu-kvm in rhev than in el6, what about including qemu-kvm-rhev in the ovirt el6 repository as dreyou did ? Thanks -- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr --------------080009080202040109020900 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> <font size="-1">Hi all,<br> <br> I'm about to migrate from the dreyou 3.2 repo to the official 3.3 repositories. I was used to take live snapshot with qemu-kvm-rhev-0.12.1.2-2.355.el6.5.x86_64 which was recompiled from the redhat srpms, because live snapshot was not supported by the official qemu-kvm in el6.4.<br> </font> <ul> <li><font size="-1">Does now 6.5 include the correct qemu-kvm version for live snapshot?</font></li> <li><font size="-1">If not why does redhat provide a separate qemu package for RHEV while fedora has got the correct package? <br> </font></li> <li><font size="-1">Does ovirt team provide support for el6 live snapshot "out of the box" or do they recommend to get the correct qemu-kvm version from the rhev repository?</font></li> </ul> <font size="-1">Assuming that redhat doesn't provide the same qemu-kvm in rhev than in el6, what about including qemu-kvm-rhev in the ovirt el6 repository as dreyou did ?<br> <br> Thanks <br> </font><br> <font size="-1"><br> </font> <pre class="moz-signature" cols="72">-- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 <a class="moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr">blanchet@abes.fr</a> </pre> </body> </html> --------------080009080202040109020900--
----- Original Message -----
Hi all,
I'm about to migrate from the dreyou 3.2 repo to the official 3.3 repositories. I was used to take live snapshot with qemu-kvm-rhev-0.12.1.2-2.355.el6.5.x86_64 which was recompiled from the redhat srpms, because live snapshot was not supported by the official qemu-kvm in el6.4.
* Does now 6.5 include the correct qemu-kvm version for live snapshot?
afaik, Centos uses the same compile options as RHEL which means it will *not* include live snapshot capability. Up until recently dreyou indeed provided qemu-kvm-rhev, but I believe that this is no longer compiled.
* If not why does redhat provide a separate qemu package for RHEV while fedora has got the correct package? * Does ovirt team provide support for el6 live snapshot "out of the box" or do they recommend to get the correct qemu-kvm version from the rhev repository?
We're still working to find an easy, maintainable way to fill the gap and this should be resolved sometime soon. In the interim you can either compile it yourself or if you have the package from other sources, use that.
Assuming that redhat doesn't provide the same qemu-kvm in rhev than in el6, what about including qemu-kvm-rhev in the ovirt el6 repository as dreyou did ?
We're looking into including a qemu-kvm package that has the capabilities compiled in, in the oVirt el6 repository indeed. The alternative would be to have it shipped with el6 proper as it was up until now.
Thanks
-- Nathanaël Blanchet
Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Yes, but is the reason of different versions something you can share or not? Just to let the people understand.. Perhaps something related to compatibilities to maintain with 6.0 initial release due to policies red hat uses? I think duplicating the maintenance effort is negative for red hat too.. Or not? Gianluca
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Ayal Baron" <abaron@redhat.com> Cc: "users" <users@ovirt.org> Sent: Wednesday, December 25, 2013 5:34:25 AM Subject: Re: [Users] about live snapshot and qemu-kvm
Yes, but is the reason of different versions something you can share or not? Just to let the people understand.. Perhaps something related to compatibilities to maintain with 6.0 initial release due to policies red hat uses? I think duplicating the maintenance effort is negative for red hat too.. Or not?
There are a few packages in RHEL that we need to move more quickly that would be possible within the RHEL policies. OpenvSwitch and QEMU are two such packages. The version of QEMU in RHEL started on 0.12 and has since had a large amount of backported features and bugfixes in many cases the backports were significant, perhaps more than should have been done. We're getting to the point that in future versions of RHEL we're likely to carry a newer version of packages like QEMU in the layered products (such as RHEV and RHEL-OSP) so that we can keep the base versions in RHEL and more aggressively rebase in the layered products. The qemu-kvm-rhev binary that's shipped in RHEV is built from the same source as qemu-kvm but with a different build option. If CentOS doesn't currently build that package it could easily be done or perhaps built by oVirt.
Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Skickat från min iPhone 28 dec 2013 kl. 16:04 skrev "Andrew Cathrow" <acathrow@redhat.com>:
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Ayal Baron" <abaron@redhat.com> Cc: "users" <users@ovirt.org> Sent: Wednesday, December 25, 2013 5:34:25 AM Subject: Re: [Users] about live snapshot and qemu-kvm
Yes, but is the reason of different versions something you can share or not? Just to let the people understand.. Perhaps something related to compatibilities to maintain with 6.0 initial release due to policies red hat uses? I think duplicating the maintenance effort is negative for red hat too.. Or not?
There are a few packages in RHEL that we need to move more quickly that would be possible within the RHEL policies. OpenvSwitch and QEMU are two such packages. The version of QEMU in RHEL started on 0.12 and has since had a large amount of backported features and bugfixes in many cases the backports were significant, perhaps more than should have been done. We're getting to the point that in future versions of RHEL we're likely to carry a newer version of packages like QEMU in the layered products (such as RHEV and RHEL-OSP) so that we can keep the base versions in RHEL and more aggressively rebase in the layered products.
The qemu-kvm-rhev binary that's shipped in RHEV is built from the same source as qemu-kvm but with a different build option. If CentOS doesn't currently build that package it could easily be done or perhaps built by oVirt.
I for one would very much like to see this built. I was surprised to learn that this was not handled already, because if live snap works in Fedora, why not CentOS, you know... /K
Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Karli, ----- Original Message -----
Skickat från min iPhone
28 dec 2013 kl. 16:04 skrev "Andrew Cathrow" <acathrow@redhat.com>:
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Ayal Baron" <abaron@redhat.com> Cc: "users" <users@ovirt.org> Sent: Wednesday, December 25, 2013 5:34:25 AM Subject: Re: [Users] about live snapshot and qemu-kvm
Yes, but is the reason of different versions something you can share or not? Just to let the people understand.. Perhaps something related to compatibilities to maintain with 6.0 initial release due to policies red hat uses? I think duplicating the maintenance effort is negative for red hat too.. Or not?
There are a few packages in RHEL that we need to move more quickly that would be possible within the RHEL policies. OpenvSwitch and QEMU are two such packages. The version of QEMU in RHEL started on 0.12 and has since had a large amount of backported features and bugfixes in many cases the backports were significant, perhaps more than should have been done. We're getting to the point that in future versions of RHEL we're likely to carry a newer version of packages like QEMU in the layered products (such as RHEV and RHEL-OSP) so that we can keep the base versions in RHEL and more aggressively rebase in the layered products.
The qemu-kvm-rhev binary that's shipped in RHEV is built from the same source as qemu-kvm but with a different build option. If CentOS doesn't currently build that package it could easily be done or perhaps built by oVirt.
I for one would very much like to see this built. I was surprised to learn that this was not handled already, because if live snap works in Fedora, why not CentOS, you know...
Up until recently this was taken care of by Centos so there was no problem. Now that it is not we're working on finding the best path to solve this. There is no question that we will handle this.
/K
Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Le 29/12/2013 12:07, Ayal Baron a écrit :
Hi Karli,
----- Original Message -----
Skickat från min iPhone
28 dec 2013 kl. 16:04 skrev "Andrew Cathrow" <acathrow@redhat.com>:
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Ayal Baron" <abaron@redhat.com> Cc: "users" <users@ovirt.org> Sent: Wednesday, December 25, 2013 5:34:25 AM Subject: Re: [Users] about live snapshot and qemu-kvm Yes, but is the reason of different versions something you can share or not? Just to let the people understand.. Perhaps something related to compatibilities to maintain with 6.0 initial release due to policies red hat uses? I think duplicating the maintenance effort is negative for red hat too.. Or not? There are a few packages in RHEL that we need to move more quickly that would be possible within the RHEL policies. OpenvSwitch and QEMU are two such packages. The version of QEMU in RHEL started on 0.12 and has since had a large amount of backported features and bugfixes in many cases the backports were significant, perhaps more than should have been done. We're getting to the point that in future versions of RHEL we're likely to carry a newer version of packages like QEMU in the layered products (such as RHEV and RHEL-OSP) so that we can keep the base versions in RHEL and more aggressively rebase in the layered products.
The qemu-kvm-rhev binary that's shipped in RHEV is built from the same source as qemu-kvm but with a different build option. If CentOS doesn't currently build that package it could easily be done or perhaps built by oVirt. I for one would very much like to see this built. I was surprised to learn that this was not handled already, because if live snap works in Fedora, why not CentOS, you know...
Up until recently this was taken care of by Centos so there was no problem. Now that it is not we're working on finding the best path to solve this. There is no question that we will handle this. However, glusterfs-3.4 is provided in the repos by the ovirt team (http://resources.ovirt.org/releases/3.3.2/rpm/EL/6.5/x86_64/glusterfs-3.4.0-...) since an other gluster package is already available in the default el6 one... the same for jasperreport-server (http://resources.ovirt.org/releases/3.3.2/rpm/EL/6.5/noarch/jasperreports-se...) since jasperreport-server 4.7.0 is available in the centos repo... Why couldn't be the case for qemu-kvm with qemu-kvm-rhev?
/K
Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr
On 12/29/2013 11:50 AM, Karli Sjöberg wrote:
Skickat från min iPhone
28 dec 2013 kl. 16:04 skrev "Andrew Cathrow" <acathrow@redhat.com>:
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Ayal Baron" <abaron@redhat.com> Cc: "users" <users@ovirt.org> Sent: Wednesday, December 25, 2013 5:34:25 AM Subject: Re: [Users] about live snapshot and qemu-kvm
Yes, but is the reason of different versions something you can share or not? Just to let the people understand.. Perhaps something related to compatibilities to maintain with 6.0 initial release due to policies red hat uses? I think duplicating the maintenance effort is negative for red hat too.. Or not?
There are a few packages in RHEL that we need to move more quickly that would be possible within the RHEL policies. OpenvSwitch and QEMU are two such packages. The version of QEMU in RHEL started on 0.12 and has since had a large amount of backported features and bugfixes in many cases the backports were significant, perhaps more than should have been done. We're getting to the point that in future versions of RHEL we're likely to carry a newer version of packages like QEMU in the layered products (such as RHEV and RHEL-OSP) so that we can keep the base versions in RHEL and more aggressively rebase in the layered products.
The qemu-kvm-rhev binary that's shipped in RHEV is built from the same source as qemu-kvm but with a different build option. If CentOS doesn't currently build that package it could easily be done or perhaps built by oVirt.
I for one would very much like to see this built. I was surprised to learn that this was not handled already, because if live snap works in Fedora, why not CentOS, you know...
did anyone ask centos to simply build with this flag to enable these features?
On Dec 29, 2013 12:39 PM, "Itamar Heim" <iheim@redhat.com> wrote:
did anyone ask centos to simply build with this flag to enable these
features?
CentOS builds packages exactly as Red Hat does for Rhel. It is strictly the same. But eventually we can ask to build a special package with this flag into the CentOS plus repo: http://wiki.centos.org/AdditionalResources/Repositories/CentOSPlus Gianluca
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 29 Dec 2013, Itamar Heim wrote:
I for one would very much like to see this built. I was surprised to learn that this was not handled already, because if live snap works in Fedora, why not CentOS, you know...
did anyone ask centos to simply build with this flag to enable these features?
The CentOS bug tracker is open for suggestions from all The RHEL buildsystem flags used are not published systematically by Red Hat, in any venue that I am that I am aware of. Obviously command line 'defines' and build environment cause certain conditionals in a .spec file to be triggered, one way or the other. Also the presence of -devel type packages in a build chroot, not explicitly enumerated through BuildRequires cause the auto-tools to add options conditionally. Tool versions not publically released sometimes are used to build packages [there were 'header marks' from a gcc [and implied toolchain], that was never externally released by Red Hat in the early 6 series, as I recall]. And so on. The complexity explodes combinatorially ... and so a SRPM rebuild effort [of which CentOS is one] builds, and tests, sometimes with ldd, and sometimes in other ways, to see that a 'close enough' reproduction of the binaries issued by Red Hat, are achieved Out of curiousity, _what_ build environment 'flags' do you all, participating in this thread, refer to? -- the thread does not enumerate them explicitly, and one cannot expect to hit by 'indirect fire', a target not exposed With best regards, this New Year's eve - -- Russ herrold -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlLDjcgACgkQMRh1QZtklkRMWACeJpv5D4Lmo/pk+bn/fdVEBYCY JscAn369cgjOKVUZqJHrAYjRu/XkodCl =d1tY -----END PGP SIGNATURE-----
On Wed, Jan 1, 2014 at 4:38 AM, R P Herrold wrote:
Out of curiousity, _what_ build environment 'flags' do you all, participating in this thread, refer to? -- the thread does not enumerate them explicitly, and one cannot expect to hit by 'indirect fire', a target not exposed
With best regards, this New Year's eve
I'm far from being a programmer, but as I went to compare build environments, between qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.src.rpm and qemu-kvm-0.12.1.2-2.415.el6_5.3.src.rpm in related spec file I see [g.cecchi@tekkaman SPECS]$ diff qemu-kvm.spec.upstream qemu-kvm.spec.rhev 3c3 < %define rhev 0 ---
%define rhev 1 12928a12929
>> rhel-6.5
and apart other probably not trivial implications, such as guest agent part, I see that the "configure" command takes one extra argument in base RH EL 6.5, that is --disable-rhev-features The only patch file containing this keyword is kvm-Block-streaming-disable-for-RHEL.patch and inside it there are these lines that impacts configure options and related built qemu-kvm: --- a/configure +++ b/configure @@ -286,6 +286,7 @@ spice="" smartcard="" smartcard_nss="" live_snapshots="yes" +block_stream="yes" usb_redir="" # OS specific @@ -686,10 +687,22 @@ for opt do ;; --enable-live-snapshots) live_snapshots="yes" ;; + --disable-block-stream) block_stream="no" + ;; + --enable-block-stream) block_stream="yes" + ;; --disable-usb-redir) usb_redir="no" ;; --enable-usb-redir) usb_redir="yes" ;; + --disable-rhev-features) + live_snapshots="no"; + block_stream="no"; + ;; + --enable-rhev-features) + live_snapshots="yes"; + block_stream="yes"; + ;; *) echo "ERROR: unknown option $opt"; show_help="yes" ;; esac @@ -863,8 +876,12 @@ echo " --disable-smartcard-nss disable smartcard nss support" echo " --enable-smartcard-nss enable smartcard nss support" echo " --disable-live-snapshots disable live block device snapshot support" echo " --enable-live-snapshots enable live block device snapshot support" +echo " --disable-block-stream disable block streaming support" +echo " --enable-block-stream enable block streaming support" echo " --disable-usb-redir disable usb network redirection support" echo " --enable-usb-redir enable usb network redirection support" +echo " --disable-rhev-features disable RHEV-only features" +echo " --enable-rhev-features enable RHEV-only features" echo "" echo "NOTE: The object files are built at the place where configure is launched" exit 1 @@ -2271,6 +2288,7 @@ echo "Trace backend $trace_backend" echo "spice support $spice" echo "nss used $smartcard_nss" echo "Live snapshots $live_snapshots" +echo "Block streaming $block_stream" echo "xfsctl support $xfs" echo "usb net redir $usb_redir" @@ -2526,6 +2544,10 @@ if test "$live_snapshots" = "yes" ; then echo "CONFIG_LIVE_SNAPSHOTS=y" >> $config_host_mak fi +if test "$block_stream" = "yes" ; then + echo "CONFIG_BLOCK_STREAM=y" >> $config_host_mak +fi + if test "$usb_redir" = "yes" ; then echo "CONFIG_USB_REDIR=y" >> $config_host_mak fi I don't think the rhev argument has instead implications in upstream source qemu-kvm-0.12.1.2.tar.gz So I think that if you want to dig more and if you have more competences, you have to see the full spec file and the full patch above. Files downloaded here: upstream http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/qemu-kvm-0... rhev http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/qemu-kvm... Gianluca
On 01/01/2014 06:24 AM, Gianluca Cecchi wrote:
On Wed, Jan 1, 2014 at 4:38 AM, R P Herrold wrote:
Out of curiousity, _what_ build environment 'flags' do you all, participating in this thread, refer to? -- the thread does not enumerate them explicitly, and one cannot expect to hit by 'indirect fire', a target not exposed
With best regards, this New Year's eve
I'm far from being a programmer, but as I went to compare build environments, between qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.src.rpm and qemu-kvm-0.12.1.2-2.415.el6_5.3.src.rpm in related spec file I see [g.cecchi@tekkaman SPECS]$ diff qemu-kvm.spec.upstream qemu-kvm.spec.rhev 3c3 < %define rhev 0 ---
%define rhev 1 12928a12929
>>> rhel-6.5
and apart other probably not trivial implications, such as guest agent part, I see that the "configure" command takes one extra argument in base RH EL 6.5, that is
--disable-rhev-features
The only patch file containing this keyword is
kvm-Block-streaming-disable-for-RHEL.patch
and inside it there are these lines that impacts configure options and related built qemu-kvm:
--- a/configure +++ b/configure @@ -286,6 +286,7 @@ spice="" smartcard="" smartcard_nss="" live_snapshots="yes" +block_stream="yes" usb_redir=""
# OS specific @@ -686,10 +687,22 @@ for opt do ;; --enable-live-snapshots) live_snapshots="yes" ;; + --disable-block-stream) block_stream="no" + ;; + --enable-block-stream) block_stream="yes" + ;; --disable-usb-redir) usb_redir="no" ;; --enable-usb-redir) usb_redir="yes" ;; + --disable-rhev-features) + live_snapshots="no"; + block_stream="no"; + ;; + --enable-rhev-features) + live_snapshots="yes"; + block_stream="yes"; + ;; *) echo "ERROR: unknown option $opt"; show_help="yes" ;; esac @@ -863,8 +876,12 @@ echo " --disable-smartcard-nss disable smartcard nss support" echo " --enable-smartcard-nss enable smartcard nss support" echo " --disable-live-snapshots disable live block device snapshot support" echo " --enable-live-snapshots enable live block device snapshot support" +echo " --disable-block-stream disable block streaming support" +echo " --enable-block-stream enable block streaming support" echo " --disable-usb-redir disable usb network redirection support" echo " --enable-usb-redir enable usb network redirection support" +echo " --disable-rhev-features disable RHEV-only features" +echo " --enable-rhev-features enable RHEV-only features" echo "" echo "NOTE: The object files are built at the place where configure is launched" exit 1 @@ -2271,6 +2288,7 @@ echo "Trace backend $trace_backend" echo "spice support $spice" echo "nss used $smartcard_nss" echo "Live snapshots $live_snapshots" +echo "Block streaming $block_stream" echo "xfsctl support $xfs" echo "usb net redir $usb_redir"
@@ -2526,6 +2544,10 @@ if test "$live_snapshots" = "yes" ; then echo "CONFIG_LIVE_SNAPSHOTS=y" >> $config_host_mak fi
+if test "$block_stream" = "yes" ; then + echo "CONFIG_BLOCK_STREAM=y" >> $config_host_mak +fi + if test "$usb_redir" = "yes" ; then echo "CONFIG_USB_REDIR=y" >> $config_host_mak fi
I don't think the rhev argument has instead implications in upstream source qemu-kvm-0.12.1.2.tar.gz So I think that if you want to dig more and if you have more competences, you have to see the full spec file and the full patch above.
Files downloaded here:
upstream http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/qemu-kvm-0...
rhev http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/qemu-kvm...
Just for the record, we have setup a jenkins job to rebuild qemu-kvm for el6 until we get it officially from centos: http://jenkins.ovirt.org/view/Packaging/job/qemu-kvm-rhev_create_rpms_el6/ -- Cheers Douglas
On Thu, Feb 13, 2014 at 8:42 PM, Douglas Schilling Landgraf wrote:
Just for the record, we have setup a jenkins job to rebuild qemu-kvm for el6 until we get it officially from centos: http://jenkins.ovirt.org/view/Packaging/job/qemu-kvm-rhev_create_rpms_el6/
Great! And thanks! Gianluca
On Thu, 2014-02-13 at 14:42 -0500, Douglas Schilling Landgraf wrote:
On 01/01/2014 06:24 AM, Gianluca Cecchi wrote:
On Wed, Jan 1, 2014 at 4:38 AM, R P Herrold wrote:
Out of curiousity, _what_ build environment 'flags' do you all, participating in this thread, refer to? -- the thread does not enumerate them explicitly, and one cannot expect to hit by 'indirect fire', a target not exposed
With best regards, this New Year's eve
I'm far from being a programmer, but as I went to compare build environments, between qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.src.rpm and qemu-kvm-0.12.1.2-2.415.el6_5.3.src.rpm in related spec file I see [g.cecchi@tekkaman SPECS]$ diff qemu-kvm.spec.upstream qemu-kvm.spec.rhev 3c3 < %define rhev 0 ---
%define rhev 1 12928a12929
>>>> rhel-6.5
and apart other probably not trivial implications, such as guest agent part, I see that the "configure" command takes one extra argument in base RH EL 6.5, that is
--disable-rhev-features
The only patch file containing this keyword is
kvm-Block-streaming-disable-for-RHEL.patch
and inside it there are these lines that impacts configure options and related built qemu-kvm:
--- a/configure +++ b/configure @@ -286,6 +286,7 @@ spice="" smartcard="" smartcard_nss="" live_snapshots="yes" +block_stream="yes" usb_redir=""
# OS specific @@ -686,10 +687,22 @@ for opt do ;; --enable-live-snapshots) live_snapshots="yes" ;; + --disable-block-stream) block_stream="no" + ;; + --enable-block-stream) block_stream="yes" + ;; --disable-usb-redir) usb_redir="no" ;; --enable-usb-redir) usb_redir="yes" ;; + --disable-rhev-features) + live_snapshots="no"; + block_stream="no"; + ;; + --enable-rhev-features) + live_snapshots="yes"; + block_stream="yes"; + ;; *) echo "ERROR: unknown option $opt"; show_help="yes" ;; esac @@ -863,8 +876,12 @@ echo " --disable-smartcard-nss disable smartcard nss support" echo " --enable-smartcard-nss enable smartcard nss support" echo " --disable-live-snapshots disable live block device snapshot support" echo " --enable-live-snapshots enable live block device snapshot support" +echo " --disable-block-stream disable block streaming support" +echo " --enable-block-stream enable block streaming support" echo " --disable-usb-redir disable usb network redirection support" echo " --enable-usb-redir enable usb network redirection support" +echo " --disable-rhev-features disable RHEV-only features" +echo " --enable-rhev-features enable RHEV-only features" echo "" echo "NOTE: The object files are built at the place where configure is launched" exit 1 @@ -2271,6 +2288,7 @@ echo "Trace backend $trace_backend" echo "spice support $spice" echo "nss used $smartcard_nss" echo "Live snapshots $live_snapshots" +echo "Block streaming $block_stream" echo "xfsctl support $xfs" echo "usb net redir $usb_redir"
@@ -2526,6 +2544,10 @@ if test "$live_snapshots" = "yes" ; then echo "CONFIG_LIVE_SNAPSHOTS=y" >> $config_host_mak fi
+if test "$block_stream" = "yes" ; then + echo "CONFIG_BLOCK_STREAM=y" >> $config_host_mak +fi + if test "$usb_redir" = "yes" ; then echo "CONFIG_USB_REDIR=y" >> $config_host_mak fi
I don't think the rhev argument has instead implications in upstream source qemu-kvm-0.12.1.2.tar.gz So I think that if you want to dig more and if you have more competences, you have to see the full spec file and the full patch above.
Files downloaded here:
upstream http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/qemu-kvm-0...
rhev http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/qemu-kvm...
Just for the record, we have setup a jenkins job to rebuild qemu-kvm for el6 until we get it officially from centos: http://jenkins.ovirt.org/view/Packaging/job/qemu-kvm-rhev_create_rpms_el6/
-- Cheers Douglas _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I think this calls for an oldschool question/statement; Who da man? ... You da man! :) Live snapshot now just works. Haven´t verified quiesce yet though, but looks good as far as the events in webadmin is concerned. Next to test is live disk migration. -- 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@slu.se
participants (8)
-
Andrew Cathrow -
Ayal Baron -
Douglas Schilling Landgraf -
Gianluca Cecchi -
Itamar Heim -
Karli Sjöberg -
Nathanaël Blanchet -
R P Herrold