libvirt/tests/qemuxml2argvdata/aarch64-tpm.xml

<domain type="qemu">
  <name>aarch64test</name>
  <uuid>496d7ea8-9739-544b-4ebd-ef08be936e8b</uuid>
  <memory>1048576</memory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch="aarch64" machine="virt">hvm</type>
  </os>
  <devices>
    <emulator>/usr/bin/qemu-system-aarch64</emulator>
    <tpm model='tpm-tis'>
      <backend type='emulator' version='2.0'/>
    </tpm>
  </devices>
</domain>
qemu: Fix swtpm device with aarch64 Starting a VM with swtpm device fails with qemu-system-aarch64. E.g. with TPM device config <tpm model='tpm-tis'> <backend type='emulator' version='2.0'/> </tpm> QEMU reports the following error error: internal error: process exited while connecting to monitor: 2021-02-07T05:15:35.378927Z qemu-system-aarch64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: 'tpm-tis' is not a valid device model name Indeed the TPM device name is 'tpm-tis-device' [1][2] for aarch64, versus the shorter 'tpm-tis' for x86. The devices are the same from a functional POV, i.e. they both emulate a TPM device conforming to the TIS specification. Account for the unfortunate name difference when building the TPM device option in qemuBuildTPMDevStr(). Also include a test case for 'tpm-tis-device'. [1] https://qemu.readthedocs.io/en/latest/specs/tpm.html [2] https://github.com/qemu/qemu/commit/c294ac327ca99342b90bd3a83d2cef9b447afaa7 Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> 2021-02-09 14:57:22 -07:00			`<domain type="qemu">`
			`<name>aarch64test</name>`
			`<uuid>496d7ea8-9739-544b-4ebd-ef08be936e8b</uuid>`
			`<memory>1048576</memory>`
			`<vcpu placement='static'>1</vcpu>`
			`<os>`
			`<type arch="aarch64" machine="virt">hvm</type>`
			`</os>`
			`<devices>`
			`<emulator>/usr/bin/qemu-system-aarch64</emulator>`
			`<tpm model='tpm-tis'>`
			`<backend type='emulator' version='2.0'/>`
			`</tpm>`
			`</devices>`
			`</domain>`