ovirt及kvm 安装过程中报libvirt无法启动

ovirt 添加主机时报Host node2 installation failed. Command returned failure code 1 during SSH session 'root@192.168.0.75'.  
在这里我对yum源等做了检查,ssh连接也没有任何问题,检查vdsm及libvirt发现

[root@node2 yum.repos.d]# systemctl restart vdsmd
A dependency job for vdsmd.service failed. See ‘journalctl -xe’ for details.
[root@node2 yum.repos.d]# journalctl -xe
Dec 17 10:13:50 node2.gzky.com systemd[1]: libvirtd.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Dec 17 10:13:50 node2.gzky.com systemd[1]: Failed to start Virtualization daemon.
– Subject: Unit libvirtd.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit libvirtd.service has failed.

– The result is failed.
Dec 17 10:13:50 node2.gzky.com systemd[1]: Unit libvirtd.service entered failed state.
Dec 17 10:13:50 node2.gzky.com systemd[1]: libvirtd.service failed.
Dec 17 10:13:51 node2.gzky.com systemd[1]: libvirtd.service holdoff time over, scheduling restart.
Dec 17 10:13:51 node2.gzky.com systemd[1]: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
Dec 17 10:13:51 node2.gzky.com systemd[1]: Stopping Auxiliary vdsm service for running helper functions as root…
– Subject: Unit supervdsmd.service has begun shutting down
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit supervdsmd.service has begun shutting down.
Dec 17 10:13:51 node2.gzky.com systemd[1]: start request repeated too quickly for libvirtd.service
Dec 17 10:13:51 node2.gzky.com systemd[1]: Failed to start Virtualization daemon.
– Subject: Unit libvirtd.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit libvirtd.service has failed.

– The result is failed.
Dec 17 10:13:51 node2.gzky.com systemd[1]: Unit libvirtd.service entered failed state.
Dec 17 10:13:51 node2.gzky.com systemd[1]: libvirtd.service failed.
Dec 17 10:13:51 node2.gzky.com systemd[1]: start request repeated too quickly for supervdsmd.service
Dec 17 10:13:51 node2.gzky.com systemd[1]: Failed to start Auxiliary vdsm service for running helper functions as root.
– Subject: Unit supervdsmd.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit supervdsmd.service has failed.

– The result is failed.
Dec 17 10:13:51 node2.gzky.com systemd[1]: Unit supervdsmd.service entered failed state.
Dec 17 10:13:51 node2.gzky.com systemd[1]: supervdsmd.service failed.

[root@node2 yum.repos.d]# systemctl restart libvirtd
Job for libvirtd.service failed because the control process exited with error code. See “systemctl status libvirtd.service” and “journalctl -xe” for details.
[root@node2 yum.repos.d]# journalctl -xe

– Unit libvirtd.service has failed.

– The result is failed.
Dec 17 10:14:32 node2.gzky.com systemd[1]: Unit libvirtd.service entered failed state.
Dec 17 10:14:32 node2.gzky.com systemd[1]: libvirtd.service failed.
Dec 17 10:14:32 node2.gzky.com systemd[1]: libvirtd.service holdoff time over, scheduling restart.
Dec 17 10:14:32 node2.gzky.com systemd[1]: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
Dec 17 10:14:32 node2.gzky.com systemd[1]: Starting Virtualization daemon…
– Subject: Unit libvirtd.service has begun start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit libvirtd.service has begun starting up.
Dec 17 10:14:32 node2.gzky.com libvirtd[36026]: 2018-12-17 02:14:32.673+0000: 36026: info : libvirt version: 4.5.0, package: 10.el7_6.3 (CentOS BuildSystem http://bugs.centos.org, 2018-
Dec 17 10:14:32 node2.gzky.com libvirtd[36026]: 2018-12-17 02:14:32.673+0000: 36026: info : hostname: node2.gzky.com
Dec 17 10:14:32 node2.gzky.com libvirtd[36026]: 2018-12-17 02:14:32.673+0000: 36026: error : virModuleLoadFile:53 : internal error: Failed to load module '/usr/lib64/libvirt/storage-backe
Dec 17 10:14:32 node2.gzky.com systemd[1]: libvirtd.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Dec 17 10:14:32 node2.gzky.com systemd[1]: Failed to start Virtualization daemon.
– Subject: Unit libvirtd.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit libvirtd.service has failed.

– The result is failed.
Dec 17 10:14:32 node2.gzky.com systemd[1]: Unit libvirtd.service entered failed state.
Dec 17 10:14:32 node2.gzky.com systemd[1]: libvirtd.service failed.
Dec 17 10:14:32 node2.gzky.com systemd[1]: libvirtd.service holdoff time over, scheduling restart.
Dec 17 10:14:32 node2.gzky.com systemd[1]: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
Dec 17 10:14:32 node2.gzky.com systemd[1]: start request repeated too quickly for libvirtd.service
Dec 17 10:14:32 node2.gzky.com systemd[1]: Failed to start Virtualization daemon.
– Subject: Unit libvirtd.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit libvirtd.service has failed.

– The result is failed.
Dec 17 10:14:32 node2.gzky.com systemd[1]: Unit libvirtd.service entered failed state.
Dec 17 10:14:32 node2.gzky.com systemd[1]: libvirtd.service failed.

[root@node2 yum.repos.d]# tailf /var/log/messages
Dec 17 10:14:32 node2 systemd: libvirtd.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Dec 17 10:14:32 node2 systemd: Failed to start Virtualization daemon.
Dec 17 10:14:32 node2 systemd: Unit libvirtd.service entered failed state.
Dec 17 10:14:32 node2 systemd: libvirtd.service failed.
Dec 17 10:14:32 node2 systemd: libvirtd.service holdoff time over, scheduling restart.
Dec 17 10:14:32 node2 systemd: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
Dec 17 10:14:32 node2 systemd: start request repeated too quickly for libvirtd.service
Dec 17 10:14:32 node2 systemd: Failed to start Virtualization daemon.
Dec 17 10:14:32 node2 systemd: Unit libvirtd.service entered failed state.
Dec 17 10:14:32 node2 systemd: libvirtd.service failed.

对此我猜测可能是libvirt版本过高与系统中特定包不一致导致,对此做了yum update

-y 主机添加成功
有没有大牛对此理解比较深的具体升级哪一个包可以对libvirt兼容还望告知**

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 3
    评论
要在Ubuntu上安装oVirt,可以按照以下步骤进行操作: 1. 首先,确保您的Ubuntu系统已经更新到最新版本。您可以使用以下命令进行系统更新: ``` sudo apt update sudo apt upgrade ``` 2. 安装oVirt引擎管理节点。执行以下命令来安装所需的软件包: ``` sudo apt install ovirt-engine ``` 3. 安装oVirt引擎数据库。默认情况下,oVirt使用PostgreSQL数据库。您可以使用以下命令来安装: ``` sudo apt install ovirt-engine-extension-aaa-ldap-setup ovirt-engine-extension-aaa-ldap ovirt-engine-dwh-setup ovirt-engine-sdk-python ovirt-engine-tools-backup ovirt-engine-webadmin-portal ovirt-engine-yubikey-setup ovirt-guest-agent-common ovirt-host-deploy ovirt-imageio-common ovirt-imageio-daemon ovirt-imageio-proxy ovirt-provider-ovn-common ovirt-provider-ovn-driver ovirt-provider-ovn-hosted-engine-ha ovirt-provider-ovn-provider ovirt-provider-ovn-vdsm ovirt-release-master ``` 4. 安装oVirt引擎虚拟化节点。执行以下命令进行安装: ``` sudo apt install ovirt-hosted-engine-ha ``` 5. 配置oVirt引擎。执行以下命令开始配置过程: ``` sudo engine-setup ``` 6. 按照引导程序的指示完成oVirt引擎的配置。您需要提供必要的信息,例如管理员密码、数据库配置等。 7. 完成配置后,您可以通过Web浏览器访问oVirt引擎的管理控制台。 请注意,以上步骤提供了安装oVirt引擎的基本过程。根据您的特定需求和环境,可能还需要进行其他配置和调整。建议您参考官方文档或oVirt社区以获取更详细和具体的信息。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 3
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值