Description of problem: Error message changed to a unhelpful message when QEMU fails with vtpm migration Version-Release number of selected component (if applicable): libvirt-8.0.0-6.el9.x86_64 qemu-kvm-6.2.0-10.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install swtpm and swtpm-tools on both hosts. # yum install swtpm swtpm-tools 2. Create vtpm secret with same uuid but different values on both hosts. # virsh secret-list UUID Usage ----------------------------------------------------------- 1498c26a-fead-4b2f-8071-94f2aa6ca0c0 vtpm VTPM_example 3. Start guest with encrypted vtpm on source host. <tpm model='tpm-crb'> <backend type='emulator' version='2.0'> <encryption secret='1498c26a-fead-4b2f-8071-94f2aa6ca0c0'/> </backend> <alias name='tpm0'/> </tpm> 4. Migrate guest to target host. # virsh -c 'qemu:///system' migrate --live --verbose --domain avocado-vt-vm1 --desturi qemu+ssh://X.X.X.X/system Migration: [ 98 %]error: operation failed: domain is no longer running 5. Check guest log on target host. # cat /var/log/libvirt/qemu/vm1.log ... 2022-03-07T02:46:53.281294Z qemu-kvm: tpm-emulator: Setting the stateblob (type 1) failed with a TPM error 0x21 decryption error 2022-03-07T02:46:53.281312Z qemu-kvm: error while loading state for instance 0x0 of device 'tpm-emulator' 2022-03-07T02:46:53.281713Z qemu-kvm: load of migration failed: Input/output error 2022-03-07 02:46:53.499+0000: shutting down, reason=crashed Actual results: libvirt report following error message: error: operation failed: domain is no longer running Expected results: libvirt report following error message: qemu-kvm: tpm-emulator: Setting the stateblob (type 1) failed with a TPM error 0x21 decryption error qemu-kvm: error while loading state for instance 0x0 of device 'tpm-emulator' qemu-kvm: load of migration failed: Input/output error Additional info: Cannot reproduce this issue on libvirt-7.10.0-1. # virsh -c 'qemu:///system' migrate --live --verbose --domain avocado-vt-vm1 --desturi qemu+ssh://X.X.X.X/system Migration: [ 89 %]error: internal error: qemu unexpectedly closed the monitor: 2022-01-06T18:18:00.877274Z qemu-kvm: tpm-emulator: Setting the stateblob (type 1) failed with a TPM error 0x21 decryption error 2022-01-06T18:18:00.877312Z qemu-kvm: error while loading state for instance 0x0 of device 'tpm-emulator' 2022-01-06T18:18:00.877780Z qemu-kvm: load of migration failed: Input/output error
Can you please retest this with current libvirt build? Thanks.
Hi Jaroslav, Liping(lcheng) gave me the auto case url: https://libvirt-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/libvirt/view/RHEL-9.2%20x86_64/job/libvirt-RHEL-9.2-runtest-x86_64-function-migration_priority_3/32/testReport/rhel.virsh/migrate_options_shared/negative_test_vtpm_emulator_without_postcopy/ The latest error msg changed to: "error: operation failed: job 'migration out' unexpectedly failed" And per my manual test, besides this error output, target qemu log got same detailed msgs as previous. # virsh migrate avocado-vt-vm1 qemu+ssh://hostB/system --live --verbose Migration: [ 97 %]error: operation failed: job 'migration out' unexpectedly failed [hostB]# tail -4 /var/log/libvirt/qemu/avocado-vt-vm1.log 2023-03-30T03:28:22.430806Z qemu-kvm: tpm-emulator: Setting the stateblob (type 1) failed with a TPM error 0x1f 2023-03-30T03:28:22.430841Z qemu-kvm: error while loading state for instance 0x0 of device 'tpm-emulator' 2023-03-30T03:28:22.433638Z qemu-kvm: load of migration failed: Input/output error 2023-03-30 03:28:22.637+0000: shutting down, reason=crashed So the current error output is still somewhat vague. Is it possible to print specific msgs since they're already there in qemu log? Thanks!
This feels like we're overwriting error message somewhere in cleanup path after failed migration. But unfortunately, I'm unable to reproduce the error during migration. Is there anything special I need to do?
(In reply to Michal Privoznik from comment #3) > But unfortunately, I'm unable to reproduce the error > during migration. Is there anything special I need to do? Hi Michal, Just try vtpm secrets with different values please: host A: # MYSECRET=`printf %s "open sesame" | base64` # virsh secret-set-value 6dd3e4a5-1d76-44ce-961f-f119f5aad935 $MYSECRET Secret value set hostB: # MYSECRET=`printf %s "my abc" | base64` # virsh secret-set-value 6dd3e4a5-1d76-44ce-961f-f119f5aad935 $MYSECRET Secret value set