[ovirt-users] ipxe-roms-qemu question

2019-03-06 Thread laco.h...@gmail.com

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+: 
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: :00:03.0/virtio-net-pci.rom: 0x2 in 
!= 0x4: 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-le...@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/YWGV6PZLO7OFMHLE4F6KBHP777TV5MFX/


[ovirt-users] ipxe-roms-qemu question

2019-03-06 Thread Ladislav Humenik

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+: 
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: :00:03.0/virtio-net-pci.rom: 0x2 in 
!= 0x4: 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-le...@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/EUK66G7PCC6AHM6FP64FDBLI3E5INYJX/