-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.2.32版升级至4.4.40后无法启动主机 #1325
Comments
看一下物理机上使用的 qemu 和 libvirt 的版本 |
zstack 4.4.x 版本使用的是 qemu 4.2 + libvirt 4.9.0,但升级 ZStack 不会帮你升级 qemu libvirt 为了避免还有类似问题,以下命令可以把 host 上的 qemu libvirt 升级到ZS使用的最新版本,kernel 也会升级到 4.18 zstack-cli执行 |
请问内网如何离线升级? |
内网用 cli 的升级方法已经在上面贴了,在管理节点执行 cli |
我以为需要联网升级呢,我试一下,多谢! |
明白,非常感谢! |
已安装Libvirt 4.9.0版,可以正常启动主机了。 |
yum 可以指定 repo |
failed to start vm[uuid:2b99exxxxxxxxxxxxxxxxxxxxxxx53e9 name:AlmaLinux-8.6] on kvm host[uuid:56f8xxxxxxxxxxxxxxxxx4a75e, ip:192.xx.xx.xx], because Traceback (most recent call last): File "/var/lib/zstack/virtualenv/kvm/lib/python2.7/site-packages/kvmagent/plugins/vm_plugin.py", line 5514, in start_vm self._start_vm(cmd) File "/var/lib/zstack/virtualenv/kvm/lib/python2.7/site-packages/kvmagent/plugins/vm_plugin.py", line 5430, in _start_vm 'unable to start vm[uuid:%s, name:%s], libvirt error: %s' % (cmd.vmInstanceUuid, cmd.vmName, str(e))) KvmError: unable to start vm[uuid:2b99xxxxxxxxxxxxxxxxxxxxxxxx53e9, name:AlmaLinux-8.6], libvirt error: internal error: process exited while connecting to monitor: qemu-kvm: -realtime mlock=off: warning: '-realtime mlock=...' is deprecated, please use '-overcommit mem-lock=...' instead 2022-11-09T04:00:47.423664Z qemu-kvm: -drive file=/zstack_ps/rootVolumes/acct-36c2xxxxxxxxxxxxxxxxxxxxxxxxf22e/vol-fd4axxxxxxxxxxxxxxxxxxxxxxxxe4e7/fd4axxxxxxxxxxxxxxxxxxxxxxxxe4e7.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,serial=fd4axxxxxxxxxxxxxxxxxxxxxxxxe4e7,cache=none: Block format 'qcow2' does not support the option 'serial'
4.2.32版Bug无法打开控制台,升级至4.4.38版后控制台可以打开,但是启动主机失败,升级至4.4.40版后启动主机仍然失败,请问是什么原因?
The text was updated successfully, but these errors were encountered: