devel

devel@lists.centos.org

11 participants
4618 discussions

6.4 CR: oVirt 3.1 breaks with missing cpu features after update to CentOS 6.4 (6.3 + CR)
by Patrick Hurrelmann 05 Mar '13

05 Mar '13

Hi list, I tested the upcoming CentOS 6.4 release with my lab installation of oVirt 3.1 and it fails to play well. Background: freshly installed CentOS 6.3 host in a Nehalem CPU-type Cluster with 2 other hosts. Storage is iSCSI. Datacenter and Cluster are both version 3.1. oVirt 3.1 was installed via Dreyou's repo. In CentOS 6.3 all is fine and the following rpms are installed: libvirt.x86_64 0.9.10-21.el6_3.8 libvirt-client.x86_64 0.9.10-21.el6_3.8 libvirt-lock-sanlock.x86_64 0.9.10-21.el6_3.8 libvirt-python.x86_64 0.9.10-21.el6_3.8 vdsm.x86_64 4.10.0-0.46.15.el6 vdsm-cli.noarch 4.10.0-0.46.15.el6 vdsm-python.x86_64 4.10.0-0.46.15.el6 vdsm-xmlrpc.noarch 4.10.0-0.46.15.el6 qemu-kvm.x86_64 2:0.12.1.2-2.295.el6_3.10 uname -a Linux vh-test1.mydomain.com 2.6.32-279.22.1.el6.x86_64 #1 SMP Wed Feb 6 03:10:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux virsh cpu capabilities on 6.3: <cpu> <arch>x86_64</arch> <model>Nehalem</model> <vendor>Intel</vendor> <topology sockets='1' cores='4' threads='1'/> <feature name='rdtscp'/> <feature name='pdcm'/> <feature name='xtpr'/> <feature name='tm2'/> <feature name='est'/> <feature name='smx'/> <feature name='vmx'/> <feature name='ds_cpl'/> <feature name='monitor'/> <feature name='dtes64'/> <feature name='pbe'/> <feature name='tm'/> <feature name='ht'/> <feature name='ss'/> <feature name='acpi'/> <feature name='ds'/> <feature name='vme'/> </cpu> and corresponding cpu features from vdsClient: cpuCores = 4 cpuFlags = fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,mtrr,pge,mca, cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht, tm,pbe,syscall,nx,rdtscp,lm,constant_tsc,arch_perfmon, pebs,bts,rep_good,xtopology,nonstop_tsc,aperfmperf,pni, dtes64,monitor,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr, pdcm,sse4_1,sse4_2,popcnt,lahf_lm,ida,dts,tpr_shadow,vnmi, flexpriority,ept,vpid,model_Conroe,model_Penryn, model_Nehalem cpuModel = Intel(R) Xeon(R) CPU X3430 @ 2.40GHz cpuSockets = 1 cpuSpeed = 2394.132 So the system was updated to 6.4 using the continuous release repo. Installed rpms after update to 6.4 (6.3 + CR): libvirt.x86_64 0.10.2-18.el6 libvirt-client.x86_64 0.10.2-18.el6 libvirt-lock-sanlock.x86_64 0.10.2-18.el6 libvirt-python.x86_64 0.10.2-18.el6 vdsm.x86_64 4.10.0-0.46.15.el6 vdsm-cli.noarch 4.10.0-0.46.15.el6 vdsm-python.x86_64 4.10.0-0.46.15.el6 vdsm-xmlrpc.noarch 4.10.0-0.46.15.el6 qemu-kvm.x86_64 2:0.12.1.2-2.355.el6_4_4.1 uname -a Linux vh-test1.mydomain.com 2.6.32-358.0.1.el6.x86_64 #1 SMP Wed Feb 27 06:06:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux virsh capabilities on 6.4: <cpu> <arch>x86_64</arch> <model>Nehalem</model> <vendor>Intel</vendor> <topology sockets='1' cores='4' threads='1'/> <feature name='rdtscp'/> <feature name='pdcm'/> <feature name='xtpr'/> <feature name='tm2'/> <feature name='est'/> <feature name='smx'/> <feature name='vmx'/> <feature name='ds_cpl'/> <feature name='monitor'/> <feature name='dtes64'/> <feature name='pbe'/> <feature name='tm'/> <feature name='ht'/> <feature name='ss'/> <feature name='acpi'/> <feature name='ds'/> <feature name='vme'/> </cpu> and corresponding cpu features from vdsClient: cpuCores = 4 cpuFlags = fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca, cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht, tm,pbe,syscall,nx,rdtscp,lm,constant_tsc,arch_perfmon, pebs,bts,rep_good,xtopology,nonstop_tsc,aperfmperf,pni, dtes64,monitor,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr, pdcm,sse4_1,sse4_2,popcnt,lahf_lm,ida,dts,tpr_shadow,vnmi, flexpriority,ept,vpid,model_coreduo,model_Conroe cpuModel = Intel(R) Xeon(R) CPU X3430 @ 2.40GHz cpuSockets = 1 cpuSpeed = 2394.098 Full outputs of virsh capabilities and vdsCaps are attached. The only difference I can see is that 6.4 exposes one additional cpu flags (sep) and this seems to break the cpu recognition of vdsm. Anyone has some hints on how to resolve or debug this further? What more information can I provide to help? Best regards Patrick -- Lobster LOGsuite GmbH, Münchner Straße 15a, D-82319 Starnberg HRB 178831, Amtsgericht München Geschäftsführer: Dr. Martin Fischer, Rolf Henrich

2 2

another 6.4 gotcha
by Joe Pruett 03 Mar '13

03 Mar '13

something changed in the kvm audio subsystem, so a virt that was suspended during shutdown wouldn't resume after reboot. the logs had complaints of: savevm: unsupported version 2 for 'hda-audio' v1 load of migration failed i poked around on the rh bz site and found a few hits, but they seemed to be related to older versions. i forced a clean boot of my vm and it was happy.

3 3

CetOS-6.4 via 6.3/cr
by Karanbir Singh 01 Mar '13

01 Mar '13

hi, By now most people would have seen or atleast have spotted the 6.3/cr/ repos are populated and updates there announced to the cr-announce list. 6.4 is a big release, lots of changes and lots of feedback about things ( also, we found in our limited testing that there are some surprises around the corners! ) Most people on the -devel list here should know about how we use the /cr/ repo and its implications - So with that in mind, please test the package payloads and provide feedback on this list. We are going to start working on the isos from today/tomorrow and start testing those right away, but in the mean time it would be great if we could get as wide as possible testing done against 6.3 + cr, and then document into the Release Notes whatever comes through. And remember, even if the test passes - let us know what you tested and that it passes'. Its important for us to build a coverage model as well. Thanks - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

9 11

Re: [CentOS-devel] CetOS-6.4 via 6.3/cr
by Iain Douglas 01 Mar '13

01 Mar '13

On 02/28/2013 12:07 AM, Karanbir Singh wrote: > And remember, even if the test passes - let us know what you tested and > that it passes'. Its important for us to build a coverage model as well. I've run my copy of t_functional on an updated system (an x86_64 VM running on VMWare ESXi 5.1) no problems encountered. Iain

3 3

Google+ Community / Web page?
by Ljubomir Ljubojevic 27 Feb '13

27 Feb '13

Hi. Someone posted a Google+'s CentOS page link (https://plus.google.com/105218000125199596028) in CentOS Facebook group, so I was wandering if it is official group, and if we have CentOS group (Community) on G+? I found https://plus.google.com/communities/110237188526999056491 admined by "Brian Schueler". -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant

2 1

rpm and ls.do issues
by Oleg Tsarev 25 Feb '13

25 Feb '13

Hi everybody, I am sorry if my question simple and well-known. After several hours investigating man-pages, google and books I did not found answer to my question. Short version of question: Does rpm update ld.so config files after/during install rpm package with so-files? Longer version of question. Our software (to some reasons) uses boost 1.46.1 under CentOS 6.3. We can not downgrade to lower version of boost to some reasons, most important - we support also Ubuntu 12.04 LTS, and really do not want develop/test/support two version of product with different boost versions. We built related boost packages, put their to our repository, and everything works fine. Unfortunately, one customer use boost 1.41 version in some internal software from official CentOS repository, and customer can not use together our software and his internal software. We decided rename our "boost" packages to "product_name-boost-*" and move library files from /usr/lib64 to /opt/product_name/version/lib (path /opt/product_name/version we use for our internal software). I rebuilt boost packages, everything works fine. The question which I try to understand: do we need update LD_LIBRARY_PATH for our binaries? As far I can see, ldd show correct pathes to boost. I do not understand well, how exactly works rpm in this moment, and what the best solution: 1) find way to have together boost 1.41 and 1.46.1 without package renames (which problem we can meet? how "yum remove boost*" would works? how to remove specific version of boost? etc) 2) rename packages from "boost* to "product_name-boost-*" and do not change path from /usr/lib64 3) rename packages from "boost*" to "product_name-boost-*" and change install pathes for libraries/include to /opt/product_name/version/... 4) (3) + setup LD_LIBRARY_PATH for every our binary I hope to your advices, links, help. Thank you very much, Oleg

2 3

JBoss EAP6 rebuild from srpms
by Baptiste AGASSE 22 Feb '13

22 Feb '13

Hi all, Because i'm interested by functional JBoss EAP6 clone running on CentOS 6 server, I'm trying to rebuild JBoss EAP6 srpms from redhat (found here http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/JBEAP/SRPMS/) To achieve that, i've setup CentOS 6.3 x86_64 VM + rpmbuild and mock environments. JBoss EAP6 is about 226 srpms packages. Why this email ? Because i want to share my current work on this, ask if someone else is interested to have JBoss EAP6 server clone working on CentOS, and if someone is also interested to help me to get it working. At this time i've already successfully built 209 of 226 srpms packages (description of this work above). Step #0: Mock configs ===================== In all mock configs, there is centos 6, epel6 and jpackage/6.0/generic/free repos enabled Step #1: building packages ========================== Build iteration #1: ------------------- Basic mock config with EPEL6 93 of 226 packages are building fine out of the box Build iteration #2: ------------------- At this step, we can see that a lot of packages have "jpackage-utils" not listed in their build dependencies. I've tried to rebuild previous failed build with: mock -r $MOCK_CFG --install jpackage-utils mock -r $MOCK_CFG --no-clean --rebuild $SRPMS_PATH/$src_rpm_name Result: 97 of 133 remaining packages built successfully Build iteration #3: ------------------- Adding jpackage/6.0/generic/devel repo 14 of the 36 remaining packages are building fine. Build iteration #4: ------------------- >From this step, i tried to build packages one by one to see what goes wrong. Removing jpackage/6.0/generic/devel by default Adding repo with previously built rpms, and search missing deps. packages built : 1) ironjacamar-1.0.13-1.Final_redhat_1.ep6.el6.src.rpm - Needs jpackage/6.0/generic/devel repo - Deps found on fedora koji server: jboss-logging-tools 2) jbossas-bundles-7.1.3-4.Final_redhat_4.ep6.el6.src.rpm 3) jbossas-core-7.1.3-4.Final_redhat_4.ep6.el6.src.rpm 4) velocity-eap6-1.6.3-7.redhat_2.ep6.el6.4.src.rpm - Needs jpackage/6.0/generic/devel repo 4 of 22 remaining packages are building fine. Remaining packages (18): ------------------- 1) antlr-eap6-2.7.7-15_redhat_2.ep6.el6.src.rpm - Needs jpackage/6.0/generic/devel repo - Last error => build error: /bin/mv: target `maven2-brew/antlr/antlr/2.7.7-redhat-2/' is not a directory 2) atinject-1-8.2_redhat_2.ep6.el6.5.src.rpm - Last error => missing deps: vman (https://github.com/jdcasey/pom-version-manipulator) 3) codehaus-jackson-1.9.2-6_redhat_2.ep6.el6.5.src.rpm - Deps found on fedora koji server: jsr-311 - Last error => missing deps: vman (https://github.com/jdcasey/pom-version-manipulator) 4) dom4j-1.6.1-14_redhat_3.ep6.el6.src.rpm - Last error => missing deps: msv-core 5) glassfish-jaxb-2.2.5-10_redhat_3.ep6.el6.src.rpm - Needs jpackage/6.0/generic/devel repo - Last error => missing deps: jboss-component-management 6) glassfish-jsf-2.1.13-1_redhat_1.ep6.el6.src.rpm - Last error => missing deps: jboss-component-management 7) h2database-1.3.168-2_redhat_1.ep6.el6.src.rpm - Last error => missing deps: lucene-core >= 3.0.2 8) hibernate4-4.1.6-7.Final_redhat_3.ep6.el6.src.rpm - Deps found on fedora koji server: gradle, jboss-logging-tools - Last error => missing deps: java-classmate 9) hornetq-2.2.23-1.Final_redhat_1.ep6.el6.src.rpm - Last error => missing deps: jboss-component-management 10) hornetq-native-2.2.21-1.Final.ep6.el6.src.rpm - Last error => missing deps: hornetq 11) jbossas-modules-eap-7.1.3-4.Final_redhat_4.ep6.el6.src.rpm - Last error => missing deps: hibernate4-core 12) jboss-ec2-eap-7.1.3-6.Final_redhat_1.ep6.el6.src.rpm - Last error => build error: [ERROR] FATAL ERROR 13) jboss-integration-7.0.0-0.6.Final_redhat_1.ep6.el6.src.rpm - Last error => missing deps: jboss-component-management 14) jbossts-4.16.6-1.Final_redhat_1.ep6.el6.src.rpm - Deps found on fedora koji server: byteman, emma - Last error => missing deps: hibernate4-core 15) jdom-eap6-1.1.2-4.GA_redhat_2.ep6.el6.src.rpm - Needs jpackage/6.0/generic/devel repo - Last error => build error: /bin/mv: target `maven2-brew/org/jdom/jdom/1.1.2-redhat-2/' is not a directory 16) jython-eap6-2.5.2-5.redhat_2.ep6.el6.4.src.rpm - Deps found on fedora koji server: jnr-constants, jaffl, jnr-netdb, jnr-posix - Last error => missing deps: jboss-parent >= 8 17) woodstox-core-4.1.1-1.redhat_2.ep6.el6.4.src.rpm - Last error => missing deps: msv-core 18) xerces-j2-eap6-2.9.1-13_redhat_3.ep6.el6.src.rpm - Last error => build error: /bin/mv: target `maven2-brew/xerces/xercesImpl/2.9.1-redhat-3/' is not a directory Step #2: [TODO] Installing and testing ====================================== Install packages and try to run JBoss server Step #3: [TODO] Removing logos and trademarks ============================================= ... Have a nice day. Regards. Baptiste.

2 5

contribution offer for web masters/developers
by cernekj 14 Feb '13

14 Feb '13

Hi, I'm willing to help with web mastering/development on any CentOS project. If there is interest in current web team please let me know. I tried to offer my contribution on IRC but nothing came to me. I really don't know how you cooperate to offer anything specific. Cheers J. C.

2 2

anaconda-11.1.2.259 is not a valid src.rpm
by Farkas Levente 14 Feb '13

14 Feb '13

hi, it seems that centos-vault/5.9/os/SRPMS/anaconda-11.1.2.259-1.src.rpm is not the real src.rpm from which centos build the anaconda rpm. this package contains patches which can not even be applied (actually the patch is the anaconda-centos-installclasses-2.patch). it seems it's a fake src.rpm and the real source of the anaconda-11.1.2.259-1. -- Levente "Si vis pacem para bellum!"

4 5

vault.centos.org SRPM is not updated for a while
by HAYASHI Kentaro 05 Feb '13

05 Feb '13

Hi, I've noticed that CentOS 6 SRPM is not updated for a while. (The last update is Jan 24, 2013?) For example, MySQL packages are updated to 5.1.66 -> 5.1.67 at Feb 1, 2013, (http://lwn.net/Articles/535681/) but there is no MySQL 5.1.67 SRPM package yet under http://vault.centos.org/6.3/updates/Source/SPackages/. It seems that SRPM packages are updated in a few days after RPM packages are released. Did something break or another reason? Thanks, -- HAYASHI Kentaro <kenhys(a)gmail.com>

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel