Hi Michal, I saw some old bugs where you were involved in same topic and I toughed you can help us. So far I understand what are the hex numbers, but I could not figure out how can I check the old in-memory rom size (to identify all guests which must be power-cycled). Do you know the code? 0x20000 hex == 131072 decimal == 128K 0x40000 hex == 262144 decimal == 256K ~]# du -k /usr/share/ipxe/1af41000.rom 256 /usr/share/ipxe/1af41000.rom Kind regards, Ladislav On 06.03.19 13:25, Ladislav Humenik wrote:
Hi all,
in the past we have used customized ipxe (to allow boot over network with 10G cards), now we have finally updated our hypervisors to the latest ipxe-roms-qemu Of course the sum now differs and during live-migration the libvirtd throws this error:
Mar 4 11:37:14 hypevisor-01 libvirtd: 2019-03-04 10:37:14.084+0000: 15862: error : qemuMigrationJobCheckStatus:1313 : operation failed: migration out job: unexpectedly failed Mar 4 11:37:15 hypevisor-01 libvirtd: 2019-03-04T10:37:13.941040Z qemu-kvm: Length mismatch: 0000:00:03.0/virtio-net-pci.rom: 0x20000 in != 0x40000: Invalid argument Mar 4 11:37:15 hypevisor-0 libvirtd: 2019-03-04T10:37:13.941090Z qemu-kvm: error while loading state for instance 0x0 of device 'ram' Mar 4 11:37:15 hypevisor-0 libvirtd: 2019-03-04T10:37:13.941530Z qemu-kvm: load of migration failed: Invalid argument
is there an easy command we can use to identify what guests are still using the old .rom and must be powercycled ?
Thank you in advance
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EUK66G7PCC6AHM...