Hi to all, we have the same problem.
we are tryng to migrate some VM from:
qemu 6.1 /libvirt 7.8
to
qemu 6.0 /libvirt 7.10
We cannot maintain qemu61, because one of this vm crash on snapshot remove.
How can we have a stable version of quemu(6.0?) and the live migrate
functionality?
Il 16/12/2021 12:13, Sandro Bonazzola ha scritto:
+Arik Hadas <mailto:ahadas@redhat.com> can you suggest a
workaround
here? Giving context:
4.4.9.1 shipped qemu-kvm 6.1 and libvirt 7.9.0
4.4.9.2 downgraded qemu-kvm to 6.0 due to pcie bug
4.4.9.3 upgraded libvirt to 7.10 as it was released in CentOS Stream.
So it seems a migration problem between 6.1/7.9 -> 6.0/7.10
qemu-kvm 6.2 got released upstream
https://www.qemu.org/2021/12/14/qemu-6-2-0/ but it's not yet available
in CentOS Stream.
Il giorno gio 16 dic 2021 alle ore 11:52 Giulio Casella
<giulio(a)di.unimi.it> ha scritto:
Hi guys,
I just faced a problem after updating a host. I cannot migrate VM to
updated host.
Here's the error I see trying to migrate a VM to that host.
Dec 16 10:13:11 host01.ovn.di.unimi.it
<
http://host01.ovn.di.unimi.it> systemd[1]: Starting Network
Manager Script Dispatcher Service...
Dec 16 10:13:11 host01.ovn.di.unimi.it
<
http://host01.ovn.di.unimi.it> libvirtd[5667]: Unable to read
from monitor: Connection reset by peer
Dec 16 10:13:11 host01.ovn.di.unimi.it
<
http://host01.ovn.di.unimi.it> libvirtd[5667]: internal error:
qemu unexpectedly closed the monitor: 2021-12-16T10:13:00.447480Z
qemu-kvm: -numa node,nodeid=0,cpus=0-15,mem=8192: warning: Parameter
-numa node,mem is deprecated, use -numa node,memdev instead
2021-12-16T10:13:11.158057Z qemu-kvm: Failed to load pckbd:kbd
2021-12-16T10:13:11.158114Z qemu-kvm: error while loading state for
instance 0x0 of device 'pckbd'
2021-12-16T10:13:11.158744Z qemu-kvm: load of migration failed: No
such
file or directory
Dec 16 10:13:11 host01.ovn.xx.xxxxx.it
<
http://host01.ovn.xx.xxxxx.it> kvm[35663]: 0 guests now active
Instead I can start VM on that host, and migrate away VM from that
host.
Rolling back to ovirt-node-ng-4.4.9.1-0.20211207.0+1 via host console
restores full functionality.
The affected version is ovirt-node-ng-4.4.9.3-0.20211215.0+1 (and
also
previous one, I don't remember precisely, it was another async
release).
Any ideas?
TIA,
gc
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VJEZGEW6X77...
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <
https://www.redhat.com/>
sbonazzo(a)redhat.com
<
https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need
to answer this email out of your office hours.
*
*
*
_______________________________________________
Users mailing list --users(a)ovirt.org
To unsubscribe send an email tousers-leave(a)ovirt.org
Privacy
Statement:https://www.ovirt.org/privacy-policy.html
oVirt Code of
Conduct:https://www.ovirt.org/community/about/community-guidelines/
List
Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/WA...
--
--
Shellrent - Il primo hosting italiano Security First
*Tommaso De Marchi*
/COO - Chief Operating Officer/
Shellrent Srl
Via dell'Edilizia, 19 - 36100 Vicenza
Tel. 0444321155 <tel:+390444321155> | Fax 04441492177