Red Hat Bugzilla – Bug 978300
[Hyper-V][RHEL6.5]Failed to start the hypervkvpd service with error "Hyper-V drivers are not loaded"
Last modified: 2013-11-20 23:52:13 EST
Description of problem:
Failed to start the hypervkvpd service with error "Hyper-V drivers are not loaded". There was a typo in the command that check the hyper-v pv drivers in the file /etc/rc.d/init.d/hypervkvd. It should be ture always with the command 'if [ -z "`lsmod | grep -q hv_utils`" ]'. It should be 'if [ -z "`lsmod | grep hv_utils`" ]'.
if [ -z "`lsmod | grep -q hv_utils`" ]; then
echo "Hyper-V drivers are not loaded."
echo -n "Hyper-V KVP daemon not started:"
# lsmod |grep hv
hv_utils 5956 0
Version-Release number of selected component (if applicable):
Host: Windows 2012 Hyper-V Server Core
Guest: Both i386 and x86_64 RHEL6 guest (kernel-2.6.32-358.el6)
Hypervkvpd pacakge hypervkvpd-0-0.10.el6
Steps to Reproduce:
1.Install hypervkvpd pacakge hypervkvpd-0-0.10.el6
# rpm -ivh hypervkvpd-0-0.10.el6.*
2.Start the hypervkvpd service.
# service hypervkvpd start
3.Check the status of the hypervkvpd service.
# service hypervkvpd status
At step2, failed to start the service with the error "Hyper-V drivers are not loaded"
At step3, the status is stopped.
At step2, start the service successfully without errors.
At step3, the status is running.
1. No this problem with hypervkvpd-0-0.9.3.el6 & hypervkvpd-0-0.9.2.el6 packages.
True, there should not be "-q" option when calling grep.
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
verify this bug on x86_64 and i386 with rhel6.5 guest(kernel:2.6.32-415.0.1.el6)
the hypervkvpd server start successfully.
so verify this bug
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.