Red Hat Bugzilla – Bug 503118
kvm doesn't run with older libgcrypt, but doesn't have a RPM dependency for it
Last modified: 2014-03-25 20:57:07 EDT
Description of problem: When running qemu-kvm, I get: 20090528-185034 Win2008.64.install: DEBUG: track_process: (qemu) libgcrypt initialization error Version-Release number of selected component (if applicable): kvm-83-44.el5 libgcrypt-1.2.4-1.el5 How reproducible: Always Steps to Reproduce: 1. Install kvm-83-44.el5 on RHEL-5.3, but keep RHEL-5.3 libgcrypt package installed (libgcrypt-1.2.4-1.el5) 2. Run qemu-kvm Actual results: libgcrypt initialization error Expected results: Either kvm RPM should have a RPM dependency for a newer libgcrypt package (if a newer library is really necessary), or the libgcrypt initialization code on kvm should be changed to work with an older libgcrypt package.
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: If the kvm package is installed but libgcrypt version is earlier than 1.4.4, the qemu-kvm process may refuse to start, with a "libgcrypt initialization error" message.
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -If the kvm package is installed but libgcrypt version is earlier than 1.4.4, the qemu-kvm process may refuse to start, with a "libgcrypt initialization error" message.+the kvm package has incorrect dependencies related to the libgcrypt package. Consequently, if the libgcrypt package installed on a system is earlier than version 1.4.4, the qemu-kvm process may refuse to start, returning a "libgcrypt initialization error" message. To work around this issue, update libgcrypt to the version provided by Red Hat Enterprise Linux 5.4.
verified with kvm-83-207.el5
Verified this issue on kvm-83-207.el5 according to Technical Notes provides way. 1. confirm libgcrypt > 1.4.4XX #rpm -qa|grep libgcrypt libgcrypt-1.4.4-5.el5 libgcrypt-devel-1.4.4-5.el5 libgcrypt-1.4.4-5.el5 2. install kvm and load modules #rpm -qa|grep kvm etherboot-zroms-kvm-5.4.4-13.el5 kvm-83-207.el5 kmod-kvm-83-204.el5 kvm-qemu-img-83-207.el5 etherboot-roms-kvm-5.4.4-13.el5 kvm-debuginfo-83-204.el5 #lsmod |grep kvm kvm_intel 85128 0 kvm 224800 2 ksm,kvm_intel 3. run kvm #/usr/libexec/qemu-kvm -no-hpet -rtc-td-hack -usbdevice tablet -startdate now -name RHEL-Server-3.9 -smp 4 -m 4G -boot c -net nic,vlan=1,macaddr=a9:22:45:91:7f:11,model=virtio -net tap,vlan=1,script=/etc/qemu-ifup -drive file=/root/chayang/r3u9-hugmem.raw,media=disk,if=ide,cache=none,format=raw,werror=stop -vnc :18 -cpu qemu64 -M rhel5.6.0 -notify all -balloon virtio -monitor stdio after step3,didn't find any error messages.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0028.html