I see with the introduction of CentOS 7.5 there's a new qemu-kvm-ma package on ppc64le (which is actually newer than qemu-kvm-ev currently). Does anyone know what the difference is between these two packages? We currently use qemu-kvm-ev and we've run into this bug [1] which got me wondering if we should be switching to that package on ppc64le.
Thanks!
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1570533
2018-05-10 21:57 GMT+02:00 Lance Albertson lance@osuosl.org:
I see with the introduction of CentOS 7.5 there's a new qemu-kvm-ma package on ppc64le (which is actually newer than qemu-kvm-ev currently). Does anyone know what the difference is between these two packages? We currently use qemu-kvm-ev and we've run into this bug [1] which got me wondering if we should be switching to that package on ppc64le.
qemu-kvm-ma is the non-x86_64 counterpart for qemu-kvm, so it is present in CentOS and have some features disabled. Upgrade path is qemu-kvm -> qemu-kvm-ma (as we provided some packages on non-x86_64 archs) -> qemu-kvm-ev (in case you enable CentOS Virt SIG QEMU repo). Opposite way is not supported and will probably break.
Please wait a few days, libguestfs package will be updated fixing the bug you've hit around next week.
Sadly, the new qemu-kvm-ev we prepared for CentOS 7.5 didn't get released ( https://bugs.centos.org/view.php?id=14764) but the new build is ready.
Thanks!
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1570533
-- Lance Albertson Director Oregon State University | Open Source Lab
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
On Fri, May 11, 2018 at 2:19 AM, Sandro Bonazzola sbonazzo@redhat.com wrote:
2018-05-10 21:57 GMT+02:00 Lance Albertson lance@osuosl.org:
I see with the introduction of CentOS 7.5 there's a new qemu-kvm-ma package on ppc64le (which is actually newer than qemu-kvm-ev currently). Does anyone know what the difference is between these two packages? We currently use qemu-kvm-ev and we've run into this bug [1] which got me wondering if we should be switching to that package on ppc64le.
qemu-kvm-ma is the non-x86_64 counterpart for qemu-kvm, so it is present in CentOS and have some features disabled. Upgrade path is qemu-kvm -> qemu-kvm-ma (as we provided some packages on non-x86_64 archs) -> qemu-kvm-ev (in case you enable CentOS Virt SIG QEMU repo). Opposite way is not supported and will probably break.
Please wait a few days, libguestfs package will be updated fixing the bug you've hit around next week.
Sadly, the new qemu-kvm-ev we prepared for CentOS 7.5 didn't get released ( https://bugs.centos.org/view.php?id=14764) but the new build is ready.
Thanks for the clarification. So it looks like I should wait until the new qemu-kvm-ev is pushed out since that's what I'm currently using? What's really the primary difference between qemu-kvm-ev and qemu-kmv-ma on ppc64le at this point? Also, I'm curious what the "ma" stands for :)
Cheers-
Hello, Sandro!
On 11.05.2018 12:19, Sandro Bonazzola wrote:
Sadly, the new qemu-kvm-ev we prepared for CentOS 7.5 didn't get released ( https://bugs.centos.org/view.php?id=14764) but the new build is ready.
After installing CentOS 7.5 and installing package qemu-kvm-ev I can't install KVM on x86_64 arch:
command "yum -y install perf qemu-kvm-ev qemu-kvm-tools-ev virt-top" failed with error code 1 and such error message:
failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more mirrors to try. http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/repodata/repomd.xm...: [Errno 14] HTTP Error 404 - Not Found
======================================================================
Is known time when this bug https://bugs.centos.org/view.php?id=14764 will be fixed and repository qemu-kvm-ev will work fine for CentOS 7.5 ?
I see your message "Packages landed on mirrors, we can close this bug." But this is not true, packages for x86_64 can't be found on the site:
http://mirror.centos.org/altarch/7/virt/
only aarch64 and ppc64le directories exists, and no x86_64 one.
Can you help me install qemu-kvm-ev on CentOS 7.5 on x86_64 arch?
P.S.
# cat /etc/redhat-release CentOS Linux release 7.5.1804 (Core)
# rpm -qf /etc/yum.repos.d/CentOS-QEMU-EV.repo centos-release-qemu-ev-1.0-3.el7.centos.noarch
# cat /etc/yum.repos.d/CentOS-QEMU-EV.repo # CentOS-QEMU-EV.repo # # Please see http://wiki.centos.org/SpecialInterestGroup/Virtualization for more # information
[centos-qemu-ev] name=CentOS-$releasever - QEMU EV baseurl=http://mirror.centos.org/$contentdir/$releasever/virt/$basearch/kvm-common/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
Hello, Sandro!
On 15.05.2018 13:24, Gena Makhomed wrote:
failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more mirrors to try. http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/repodata/repomd.xm...: [Errno 14] HTTP Error 404 - Not Found
I found workaround:
# diff -u CentOS-QEMU-EV.repo.old CentOS-QEMU-EV.repo --- CentOS-QEMU-EV.repo.old 2018-05-15 13:30:27.500156416 +0300 +++ CentOS-QEMU-EV.repo 2018-05-15 13:30:38.980208715 +0300 @@ -5,7 +5,7 @@
[centos-qemu-ev] name=CentOS-$releasever - QEMU EV -baseurl=http://mirror.centos.org/$contentdir/$releasever/virt/$basearch/kvm-common/ +baseurl=http://mirror.centos.org/centos/$releasever/virt/$basearch/kvm-common/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
=================================================================================
now all works fine.
But as I understand, this is bug and it should be fixed.
Something wrong with $contentdir variable, it points to altarch for x86_64 $basearch.
2018-05-15 12:38 GMT+02:00 Gena Makhomed gmm@csdoc.com:
Hello, Sandro!
On 15.05.2018 13:24, Gena Makhomed wrote:
failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more
mirrors to try. http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/ repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
I found workaround:
# diff -u CentOS-QEMU-EV.repo.old CentOS-QEMU-EV.repo --- CentOS-QEMU-EV.repo.old 2018-05-15 13:30:27.500156416 +0300 +++ CentOS-QEMU-EV.repo 2018-05-15 13:30:38.980208715 +0300 @@ -5,7 +5,7 @@
[centos-qemu-ev] name=CentOS-$releasever - QEMU EV -baseurl=http://mirror.centos.org/$contentdir/$releasever/vi rt/$basearch/kvm-common/ +baseurl=http://mirror.centos.org/centos/$releasever/virt/$b asearch/kvm-common/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
============================================================
now all works fine.
But as I understand, this is bug and it should be fixed.
Something wrong with $contentdir variable, it points to altarch for x86_64 $basearch.
can't reproduce on a fresh x86_64 installation. Adding Brian in case he has a clue for this.
-- Best regards, Gena _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Yep. We are seeing the same thing.
http://mirror.centos.org/altarch/7/virt/x86_64/kvm- common/repodata/repomd.xml: https://mandrillapp.com/track/click/30215943/mirror.centos.org?p=eyJzIjoibGRlaFdSUTl3VlJITkRlY3pURTZlYW9nMDdVIiwidiI6MSwicCI6IntcInVcIjozMDIxNTk0MyxcInZcIjoxLFwidXJsXCI6XCJodHRwOlxcXC9cXFwvbWlycm9yLmNlbnRvcy5vcmdcXFwvYWx0YXJjaFxcXC83XFxcL3ZpcnRcXFwveDg2XzY0XFxcL2t2bS1jb21tb25cXFwvcmVwb2RhdGFcXFwvcmVwb21kLnhtbDpcIixcImlkXCI6XCJmYmY1YjcyNmRmYWY0N2Y3YmRkNWRlNGMxOGY3MTg3ZVwiLFwidXJsX2lkc1wiOltcIjEzMTViNTUwNDczYzI2ZTFhZGM2NDEzNTEzZTIwNDc2ODMzZWIyYTFcIl19In0 [Errno 14] HTTP Error 404 - Not Found
On 15 May 2018 at 11:52, Sandro Bonazzola sbonazzo@redhat.com wrote:
2018-05-15 12:38 GMT+02:00 Gena Makhomed gmm@csdoc.com:
Hello, Sandro!
On 15.05.2018 13:24, Gena Makhomed wrote:
failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more
mirrors to try. http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/re podata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
I found workaround:
# diff -u CentOS-QEMU-EV.repo.old CentOS-QEMU-EV.repo --- CentOS-QEMU-EV.repo.old 2018-05-15 13:30:27.500156416 +0300 +++ CentOS-QEMU-EV.repo 2018-05-15 13:30:38.980208715 +0300 @@ -5,7 +5,7 @@
[centos-qemu-ev] name=CentOS-$releasever - QEMU EV -baseurl=http://mirror.centos.org/$contentdir/$releasever/vi rt/$basearch/kvm-common/ +baseurl=http://mirror.centos.org/centos/$releasever/virt/$b asearch/kvm-common/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
============================================================
now all works fine.
But as I understand, this is bug and it should be fixed.
Something wrong with $contentdir variable, it points to altarch for x86_64 $basearch.
can't reproduce on a fresh x86_64 installation. Adding Brian in case he has a clue for this.
-- Best regards, Gena _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA https://www.redhat.com/
sbonazzo@redhat.com https://red.ht/sig https://redhat.com/summit
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
On 15.05.2018 13:52, Sandro Bonazzola wrote:
failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more
mirrors to try. http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/ repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Something wrong with $contentdir variable, it points to altarch for x86_64 $basearch.
can't reproduce on a fresh x86_64 installation. Adding Brian in case he has a clue for this.
I use fresh installed x86_64 CentOS 7.5 via VNC with partially filled config anaconda-ks.cfg
And I can see in /etc/yum/vars/contentdir:
# cat /etc/yum/vars/contentdir altarch
As I understand, on the fresh x86_64 installation file /etc/yum/vars/contentdir should have centos value.
P.S.
I will report this issue to my hoster (hetzner.com) may be this is hoster issue and not CentOS issue ?
But I am not sure what this is hoster bug, it may be CentOS 7.5 anaconda installer bug.
I delete after installation all anaconda configs and all anaconda log files, so now I can't debug this issue more deeply, sorry.
On Tue, 15 May 2018 14:45:23 +0300 Gena Makhomed gmm@csdoc.com wrote:
Something wrong with $contentdir variable, it points to altarch for x86_64 $basearch.
can't reproduce on a fresh x86_64 installation. Adding Brian in case he has a clue for this.
I use fresh installed x86_64 CentOS 7.5 via VNC with partially filled config anaconda-ks.cfg
And I can see in /etc/yum/vars/contentdir:
# cat /etc/yum/vars/contentdir altarch
As I understand, on the fresh x86_64 installation file /etc/yum/vars/contentdir should have centos value.
P.S.
I will report this issue to my hoster (hetzner.com) may be this is hoster issue and not CentOS issue ?
But I am not sure what this is hoster bug, it may be CentOS 7.5 anaconda installer bug.
I delete after installation all anaconda configs and all anaconda log files, so now I can't debug this issue more deeply, sorry.
I have freshly installed CentOS 7.5 on a Dell server, and /etc/yum/vars/contentdir contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have 'centos'.
Regards, Nerijus
2018-05-15 13:53 GMT+02:00 Nerijus Baliunas nerijus@users.sourceforge.net:
On Tue, 15 May 2018 14:45:23 +0300 Gena Makhomed gmm@csdoc.com wrote:
Something wrong with $contentdir variable, it points to altarch for x86_64 $basearch.
can't reproduce on a fresh x86_64 installation. Adding Brian in case
he has
a clue for this.
I use fresh installed x86_64 CentOS 7.5 via VNC with partially filled config anaconda-ks.cfg
And I can see in /etc/yum/vars/contentdir:
# cat /etc/yum/vars/contentdir altarch
As I understand, on the fresh x86_64 installation file /etc/yum/vars/contentdir should have centos value.
P.S.
I will report this issue to my hoster (hetzner.com) may be this is hoster issue and not CentOS issue ?
But I am not sure what this is hoster bug, it may be CentOS 7.5 anaconda installer bug.
I delete after installation all anaconda configs and all anaconda log files, so now I can't debug this issue more deeply, sorry.
I have freshly installed CentOS 7.5 on a Dell server, and /etc/yum/vars/contentdir contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have 'centos'.
I see in %post: /usr/bin/uname -m | grep -q 'x86_64' && echo 'centos'
/etc/yum/vars/contentdir || echo 'altarch' > /etc/yum/vars/contentdir
can you please check
/usr/bin/uname -m
on your system?
Regards, Nerijus _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
2018-05-15 14:16 GMT+02:00 Sandro Bonazzola sbonazzo@redhat.com:
2018-05-15 13:53 GMT+02:00 Nerijus Baliunas <nerijus@users.sourceforge.net
:
On Tue, 15 May 2018 14:45:23 +0300 Gena Makhomed gmm@csdoc.com wrote:
Something wrong with $contentdir variable, it points to altarch for x86_64 $basearch.
can't reproduce on a fresh x86_64 installation. Adding Brian in case
he has
a clue for this.
I use fresh installed x86_64 CentOS 7.5 via VNC with partially filled config anaconda-ks.cfg
And I can see in /etc/yum/vars/contentdir:
# cat /etc/yum/vars/contentdir altarch
As I understand, on the fresh x86_64 installation file /etc/yum/vars/contentdir should have centos value.
P.S.
I will report this issue to my hoster (hetzner.com) may be this is hoster issue and not CentOS issue ?
But I am not sure what this is hoster bug, it may be CentOS 7.5 anaconda installer bug.
I delete after installation all anaconda configs and all anaconda log files, so now I can't debug this issue more deeply, sorry.
I have freshly installed CentOS 7.5 on a Dell server, and /etc/yum/vars/contentdir contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have 'centos'.
I see in %post: /usr/bin/uname -m | grep -q 'x86_64' && echo 'centos'
/etc/yum/vars/contentdir || echo 'altarch' > /etc/yum/vars/contentdir
can you please check
/usr/bin/uname -m
on your system?
Also, can you share your anaconda logs? Maybe some package installation order issue prevents /usr/bin/uname -m | grep -q 'x86_64' to properly execute.
Regards, Nerijus _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA https://www.redhat.com/
sbonazzo@redhat.com https://red.ht/sig https://redhat.com/summit
On Tue, 15 May 2018 14:18:08 +0200 Sandro Bonazzola sbonazzo@redhat.com wrote:
I have freshly installed CentOS 7.5 on a Dell server, and /etc/yum/vars/contentdir contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have 'centos'.
I see in %post: /usr/bin/uname -m | grep -q 'x86_64' && echo 'centos'
/etc/yum/vars/contentdir || echo 'altarch' > /etc/yum/vars/contentdir
can you please check
/usr/bin/uname -m
on your system?
# /usr/bin/uname -m x86_64
Also, can you share your anaconda logs? Maybe some package installation order issue prevents /usr/bin/uname -m | grep -q 'x86_64' to properly execute.
In packaging.log: 14:38:25,111 INFO packaging: centos-release-7-5.1804.el7.centos.x86_64 (43/296) 14:38:25,111 INFO packaging: /var/tmp/rpm-tmp.Zk5yvn: line 1: /usr/bin/uname: No such file or directory
Logs are at http://sat.lt/anaconda.tgz
Regards, Nerijus
2018-05-15 14:39 GMT+02:00 Nerijus Baliunas nerijus@users.sourceforge.net:
On Tue, 15 May 2018 14:18:08 +0200 Sandro Bonazzola sbonazzo@redhat.com wrote:
I have freshly installed CentOS 7.5 on a Dell server, and /etc/yum/vars/contentdir contains 'altarch' too. CentOS 7.4->7.5 upgraded servers have
'centos'.
I see in %post: /usr/bin/uname -m | grep -q 'x86_64' && echo 'centos'
/etc/yum/vars/contentdir || echo 'altarch' > /etc/yum/vars/contentdir
can you please check
/usr/bin/uname -m
on your system?
# /usr/bin/uname -m x86_64
Also, can you share your anaconda logs? Maybe some package installation order issue prevents /usr/bin/uname -m | grep -q 'x86_64' to properly execute.
In packaging.log: 14:38:25,111 INFO packaging: centos-release-7-5.1804.el7.centos.x86_64 (43/296) 14:38:25,111 INFO packaging: /var/tmp/rpm-tmp.Zk5yvn: line 1: /usr/bin/uname: No such file or directory
So this is a requirements error in the spec file.
centos-release should have:
Requires(post): coreutils
Logs are at http://sat.lt/anaconda.tgz
Regards, Nerijus _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
On Tue, 15 May 2018 14:48:13 +0200 Sandro Bonazzola sbonazzo@redhat.com wrote:
Also, can you share your anaconda logs? Maybe some package installation order issue prevents /usr/bin/uname -m | grep -q 'x86_64' to properly execute.
In packaging.log: 14:38:25,111 INFO packaging: centos-release-7-5.1804.el7.centos.x86_64 (43/296) 14:38:25,111 INFO packaging: /var/tmp/rpm-tmp.Zk5yvn: line 1: /usr/bin/uname: No such file or directory
So this is a requirements error in the spec file.
centos-release should have:
Requires(post): coreutils
rpm -q --requires centos-release /bin/sh config(centos-release) = 7-5.1804.el7.centos coreutils
I assume it is not enough?
Regards, Nerijus
2018-05-15 15:08 GMT+02:00 Nerijus Baliunas nerijus@users.sourceforge.net:
On Tue, 15 May 2018 14:48:13 +0200 Sandro Bonazzola sbonazzo@redhat.com wrote:
Also, can you share your anaconda logs? Maybe some package installation order issue prevents /usr/bin/uname
-m |
grep -q 'x86_64' to properly execute.
In packaging.log: 14:38:25,111 INFO packaging: centos-release-7-5.1804.el7.centos.x86_64 (43/296) 14:38:25,111 INFO packaging: /var/tmp/rpm-tmp.Zk5yvn: line 1: /usr/bin/uname: No such file or directory
So this is a requirements error in the spec file.
centos-release should have:
Requires(post): coreutils
rpm -q --requires centos-release /bin/sh config(centos-release) = 7-5.1804.el7.centos coreutils
I assume it is not enough?
Correct, that's not enough. It should have: Requires(post): coreutils
Regards, Nerijus
-
Gena Makhomed -
Lance Albertson -
Nerijus Baliunas -
Phill Bandelow -
Sandro Bonazzola