[ovirt-users] Re: Unable to migrate VMs to or from oVirt node 4.4.7
On Fri, Jul 9, 2021 at 5:57 PM nroach44--- via Users wrote: > > Hi All, > > After upgrading some of my hosts to 4.4.7, and after fixing the policy issue, > I'm no longer able to migrate VMs to or from 4.4.7 hosts. Starting them works > fine regardless of the host version. > > HE 4.4.7.6-1.el8, Linux and Windows VMs. > > The log on the receiving end (4.4.7 in this case): > VDSM: > 2021-07-09 22:02:17,491+0800 INFO (libvirt/events) [vds] Channel state for > vm_id=5d11885a-37d3-4f68-a953-72d808f43cdd changed from=UNKNOWN(-1) > to=disconnected(2) (qemuguestagent:289) > 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] > (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') underlying process disconnected > (vm:1134) > 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] > (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Release VM resources (vm:5313) > 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] > (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection > (guestagent:438) > 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [virt.vm] > (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection > (guestagent:438) > 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [vdsm.api] START > inappropriateDevices(thiefId='5d11885a-37d3-4f68-a953-72d808f43cdd') > from=internal, task_id=7abe370b-13bc-4c49-bf02-2e40db142250 (api:48) > 2021-07-09 22:02:55,544+0800 WARN (vm/5d11885a) [virt.vm] > (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Couldn't destroy incoming VM: > Domain not found: no domain with matching uuid > '5d11885a-37d3-4f68-a953-72d808f43cdd' (vm:4046) > 2021-07-09 22:02:55,544+0800 INFO (vm/5d11885a) [virt.vm] > (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Changed state to Down: VM > destroyed during the startup (code=10) (vm:1895) > > syslog shows: > Jul 09 22:35:01 HOSTNAME abrt-hook-ccpp[177862]: Process 177022 (qemu-kvm) of > user 107 killed by SIGABRT - dumping core > > qemu: > qemu-kvm: ../util/yank.c:107: yank_unregister_instance: Assertion > `QLIST_EMPTY(&entry->yankfns)' failed. > 2021-07-09 14:02:54.521+: shutting down, reason=failed Looks like another qemu 6.0.0 regression. Please file ovirt bug for this. Note that on RHEL we are still using qemu 5.2.0. qemu 6.0.0 is expected in RHEL 8.5. > When migrating from 4.4.7 to 4.4.6, syslog shows: > Jul 09 22:36:36 HOSTNAME libvirtd[2775]: unsupported configuration: unknown > audio type 'spice' Sharing vm xml can help to understand this issue. Milan, did we test migration from 4.4.7 to 4.4.6? Nir ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/OXBKQ5TZ4G64TU4XFZVYENA4BB4OLT6K/
[ovirt-users] Re: Unable to migrate VMs to or from oVirt node 4.4.7
On 10/7/21 3:31 am, Nir Soffer wrote: On Fri, Jul 9, 2021 at 5:57 PM nroach44--- via Users wrote: Hi All, After upgrading some of my hosts to 4.4.7, and after fixing the policy issue, I'm no longer able to migrate VMs to or from 4.4.7 hosts. Starting them works fine regardless of the host version. HE 4.4.7.6-1.el8, Linux and Windows VMs. The log on the receiving end (4.4.7 in this case): VDSM: 2021-07-09 22:02:17,491+0800 INFO (libvirt/events) [vds] Channel state for vm_id=5d11885a-37d3-4f68-a953-72d808f43cdd changed from=UNKNOWN(-1) to=disconnected(2) (qemuguestagent:289) 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') underlying process disconnected (vm:1134) 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Release VM resources (vm:5313) 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection (guestagent:438) 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection (guestagent:438) 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [vdsm.api] START inappropriateDevices(thiefId='5d11885a-37d3-4f68-a953-72d808f43cdd') from=internal, task_id=7abe370b-13bc-4c49-bf02-2e40db142250 (api:48) 2021-07-09 22:02:55,544+0800 WARN (vm/5d11885a) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Couldn't destroy incoming VM: Domain not found: no domain with matching uuid '5d11885a-37d3-4f68-a953-72d808f43cdd' (vm:4046) 2021-07-09 22:02:55,544+0800 INFO (vm/5d11885a) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Changed state to Down: VM destroyed during the startup (code=10) (vm:1895) syslog shows: Jul 09 22:35:01 HOSTNAME abrt-hook-ccpp[177862]: Process 177022 (qemu-kvm) of user 107 killed by SIGABRT - dumping core qemu: qemu-kvm: ../util/yank.c:107: yank_unregister_instance: Assertion `QLIST_EMPTY(&entry->yankfns)' failed. 2021-07-09 14:02:54.521+: shutting down, reason=failed Looks like another qemu 6.0.0 regression. Please file ovirt bug for this. Note that on RHEL we are still using qemu 5.2.0. qemu 6.0.0 is expected in RHEL 8.5. Filed: https://bugzilla.redhat.com/show_bug.cgi?id=1981005 When migrating from 4.4.7 to 4.4.6, syslog shows: Jul 09 22:36:36 HOSTNAME libvirtd[2775]: unsupported configuration: unknown audio type 'spice' Sharing vm xml can help to understand this issue. Looks like it will be this section: passwdValidTo='1970-01-01T00:00:01'> ---> heads='1' primary='yes'/> function='0x0'/> Milan, did we test migration from 4.4.7 to 4.4.6? Nir ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/OXBKQ5TZ4G64TU4XFZVYENA4BB4OLT6K/ -- Thanks! *Nathaniel Roach* ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/JKULNPGVQNCYMSOZLZQ6TJLMDPWEVIJL/
[ovirt-users] Re: Unable to migrate VMs to or from oVirt node 4.4.7
On 10/7/21 9:07 pm, Nathaniel Roach wrote: On 10/7/21 3:31 am, Nir Soffer wrote: On Fri, Jul 9, 2021 at 5:57 PM nroach44--- via Users wrote: Hi All, After upgrading some of my hosts to 4.4.7, and after fixing the policy issue, I'm no longer able to migrate VMs to or from 4.4.7 hosts. Starting them works fine regardless of the host version. HE 4.4.7.6-1.el8, Linux and Windows VMs. The log on the receiving end (4.4.7 in this case): VDSM: 2021-07-09 22:02:17,491+0800 INFO (libvirt/events) [vds] Channel state for vm_id=5d11885a-37d3-4f68-a953-72d808f43cdd changed from=UNKNOWN(-1) to=disconnected(2) (qemuguestagent:289) 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') underlying process disconnected (vm:1134) 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Release VM resources (vm:5313) 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection (guestagent:438) 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection (guestagent:438) 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [vdsm.api] START inappropriateDevices(thiefId='5d11885a-37d3-4f68-a953-72d808f43cdd') from=internal, task_id=7abe370b-13bc-4c49-bf02-2e40db142250 (api:48) 2021-07-09 22:02:55,544+0800 WARN (vm/5d11885a) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Couldn't destroy incoming VM: Domain not found: no domain with matching uuid '5d11885a-37d3-4f68-a953-72d808f43cdd' (vm:4046) 2021-07-09 22:02:55,544+0800 INFO (vm/5d11885a) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Changed state to Down: VM destroyed during the startup (code=10) (vm:1895) syslog shows: Jul 09 22:35:01 HOSTNAME abrt-hook-ccpp[177862]: Process 177022 (qemu-kvm) of user 107 killed by SIGABRT - dumping core qemu: qemu-kvm: ../util/yank.c:107: yank_unregister_instance: Assertion `QLIST_EMPTY(&entry->yankfns)' failed. 2021-07-09 14:02:54.521+: shutting down, reason=failed Looks like another qemu 6.0.0 regression. Please file ovirt bug for this. Note that on RHEL we are still using qemu 5.2.0. qemu 6.0.0 is expected in RHEL 8.5. Filed: https://bugzilla.redhat.com/show_bug.cgi?id=1981005 When migrating from 4.4.7 to 4.4.6, syslog shows: Jul 09 22:36:36 HOSTNAME libvirtd[2775]: unsupported configuration: unknown audio type 'spice' Sharing vm xml can help to understand this issue. Looks like it will be this section: passwdValidTo='1970-01-01T00:00:01'> ---> heads='1' primary='yes'/> function='0x0'/> I just thought to check, the VM above does not have not have sound enabled, and is missing this line when running on 4.4.6. When it's running on 4.4.7 it *does* have** this line in the config. Milan, did we test migration from 4.4.7 to 4.4.6? Nir ___ Users mailing list --users@ovirt.org To unsubscribe send an email tousers-le...@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/OXBKQ5TZ4G64TU4XFZVYENA4BB4OLT6K/ -- Thanks! *Nathaniel Roach* -- Thanks! *Nathaniel Roach* ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/GPBVJRZANIXKZ2VQOSAW65E4MOM7NQRX/
[ovirt-users] Re: Unable to migrate VMs to or from oVirt node 4.4.7
Nir Soffer writes: > On Fri, Jul 9, 2021 at 5:57 PM nroach44--- via Users wrote: >> >> Hi All, > >> >> After upgrading some of my hosts to 4.4.7, and after fixing the >> policy issue, I'm no longer able to migrate VMs to or from 4.4.7 >> hosts. Starting them works fine regardless of the host version. >> >> HE 4.4.7.6-1.el8, Linux and Windows VMs. >> >> The log on the receiving end (4.4.7 in this case): >> VDSM: >> 2021-07-09 22:02:17,491+0800 INFO (libvirt/events) [vds] Channel >> state for vm_id=5d11885a-37d3-4f68-a953-72d808f43cdd changed >> from=UNKNOWN(-1) to=disconnected(2) (qemuguestagent:289) >> 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] >> (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') underlying process >> disconnected (vm:1134) >> 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] >> (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Release VM resources >> (vm:5313) >> 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] >> (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection >> (guestagent:438) >> 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [virt.vm] >> (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection >> (guestagent:438) >> 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [vdsm.api] START >> inappropriateDevices(thiefId='5d11885a-37d3-4f68-a953-72d808f43cdd') >> from=internal, task_id=7abe370b-13bc-4c49-bf02-2e40db142250 (api:48) >> 2021-07-09 22:02:55,544+0800 WARN (vm/5d11885a) [virt.vm] >> (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Couldn't destroy >> incoming VM: Domain not found: no domain with matching uuid >> '5d11885a-37d3-4f68-a953-72d808f43cdd' (vm:4046) >> 2021-07-09 22:02:55,544+0800 INFO (vm/5d11885a) [virt.vm] >> (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Changed state to Down: >> VM destroyed during the startup (code=10) (vm:1895) >> >> syslog shows: >> Jul 09 22:35:01 HOSTNAME abrt-hook-ccpp[177862]: Process 177022 >> (qemu-kvm) of user 107 killed by SIGABRT - dumping core >> >> qemu: >> qemu-kvm: ../util/yank.c:107: yank_unregister_instance: Assertion >> `QLIST_EMPTY(&entry->yankfns)' failed. >> 2021-07-09 14:02:54.521+: shutting down, reason=failed > > Looks like another qemu 6.0.0 regression. Please file ovirt bug for this. As pointed out by Jean-Louis Dupond, we already have one: https://bugzilla.redhat.com/1964326 > Note that on RHEL we are still using qemu 5.2.0. qemu 6.0.0 is expected > in RHEL 8.5. > >> When migrating from 4.4.7 to 4.4.6, syslog shows: >> Jul 09 22:36:36 HOSTNAME libvirtd[2775]: unsupported configuration: unknown >> audio type 'spice' > > Sharing vm xml can help to understand this issue. > > Milan, did we test migration from 4.4.7 to 4.4.6? I don't know but they work for me with QEMU 5.2. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/YO2XQEKYCH5LKPOKTM3B4SYILZHTQJKR/
[ovirt-users] Re: Unable to migrate VMs to or from oVirt node 4.4.7
Nathaniel Roach via Users writes: > On 10/7/21 9:07 pm, Nathaniel Roach wrote: >> On 10/7/21 3:31 am, Nir Soffer wrote: >>> On Fri, Jul 9, 2021 at 5:57 PM nroach44--- via Users >>> wrote: > Hi All, After upgrading some of my hosts to 4.4.7, and after fixing the policy issue, I'm no longer able to migrate VMs to or from 4.4.7 hosts. Starting them works fine regardless of the host version. HE 4.4.7.6-1.el8, Linux and Windows VMs. The log on the receiving end (4.4.7 in this case): VDSM: 2021-07-09 22:02:17,491+0800 INFO (libvirt/events) [vds] Channel state for vm_id=5d11885a-37d3-4f68-a953-72d808f43cdd changed from=UNKNOWN(-1) to=disconnected(2) (qemuguestagent:289) 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') underlying process disconnected (vm:1134) 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Release VM resources (vm:5313) 2021-07-09 22:02:55,537+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection (guestagent:438) 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Stopping connection (guestagent:438) 2021-07-09 22:02:55,539+0800 INFO (libvirt/events) [vdsm.api] START inappropriateDevices(thiefId='5d11885a-37d3-4f68-a953-72d808f43cdd') from=internal, task_id=7abe370b-13bc-4c49-bf02-2e40db142250 (api:48) 2021-07-09 22:02:55,544+0800 WARN (vm/5d11885a) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Couldn't destroy incoming VM: Domain not found: no domain with matching uuid '5d11885a-37d3-4f68-a953-72d808f43cdd' (vm:4046) 2021-07-09 22:02:55,544+0800 INFO (vm/5d11885a) [virt.vm] (vmId='5d11885a-37d3-4f68-a953-72d808f43cdd') Changed state to Down: VM destroyed during the startup (code=10) (vm:1895) syslog shows: Jul 09 22:35:01 HOSTNAME abrt-hook-ccpp[177862]: Process 177022 (qemu-kvm) of user 107 killed by SIGABRT - dumping core qemu: qemu-kvm: ../util/yank.c:107: yank_unregister_instance: Assertion `QLIST_EMPTY(&entry->yankfns)' failed. 2021-07-09 14:02:54.521+: shutting down, reason=failed >>> Looks like another qemu 6.0.0 regression. Please file ovirt bug for this. >>> >>> Note that on RHEL we are still using qemu 5.2.0. qemu 6.0.0 is expected >>> in RHEL 8.5. >> Filed: https://bugzilla.redhat.com/show_bug.cgi?id=1981005 When migrating from 4.4.7 to 4.4.6, syslog shows: Jul 09 22:36:36 HOSTNAME libvirtd[2775]: unsupported configuration: unknown audio type 'spice' >>> Sharing vm xml can help to understand this issue. >> >> Looks like it will be this section: >> >> >> >> >> >> >> >> > passwdValidTo='1970-01-01T00:00:01'> >> >> >> >> >> >> >> >> >> >> >> ---> >> >> > heads='1' primary='yes'/> >> >> > function='0x0'/> >> >> > I just thought to check, the VM above does not have not have sound > enabled, and is missing this line when running on 4.4.6. When it's > running on 4.4.7 it *does* have** this line in the config. This is the following bug: https://bugzilla.redhat.com/1977891 >>> Milan, did we test migration from 4.4.7 to 4.4.6? >>> >>> Nir >>> ___ >>> Users mailing list --users@ovirt.org >>> To unsubscribe send an email tousers-le...@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/OXBKQ5TZ4G64TU4XFZVYENA4BB4OLT6K/ >> -- Thanks! >> >> *Nathaniel Roach* >> ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/CY4DBRAGCBZ5TXN72EDJ7QS6VE4GLUJQ/
