------- Comment From <email address hidden> 2018-09-11 13:24 EDT-------
For etoken support for KVM guests we also need qemu support to add this to the cpumodel.
Please tell me if you want a backport patch for both upstream commits or if you prefer to do the backport yourself. (Do you want a separate launchpad for qemu or can we handle that here?)
The backport would be necessary for the qemu in bionic and cosmic and all relevant cloud archive versions.
------- Comment From <email address hidden> 2018-09-11 13:24 EDT-------
For etoken support for KVM guests we also need qemu support to add this to the cpumodel.
The feature is provided by the following upstream commit /git.qemu. org/?p= qemu.git; a=commit; h=27e84d4ebd25b 981ab27cb590fe0 6d1b0fcd06d2 1ab27cb590fe06d 1b0fcd06d2
https:/
commit: 27e84d4ebd25b98
title: s390x/kvm: add etoken facility
we also need the following commit to make this compile /git.qemu. org/?p= qemu.git; a=commit; h=d36f7de82995a 42b749c29c5b60b a31483995a42 b749c29c5b60ba3 1483995a42
https:/
commit: d36f7de82995a42
title: linux-headers: update
To simplify things, this part of the headers update is sufficient: /git.qemu. org/?p= qemu.git; a=blobdiff; f=linux- headers/ asm-s390/ kvm.h;h= 1ab9901911bf55e 3aba55488bb20a1 84d85bbce5; hp=11def143015d 572f208bbdf4aa4 ecfa094c700a1; hb=d36f7de82995 a42b749c29c5b60 ba31483995a42; hpb=c61177881cb da50704207dd9fb 4811659bbf913e
https:/
Please tell me if you want a backport patch for both upstream commits or if you prefer to do the backport yourself. (Do you want a separate launchpad for qemu or can we handle that here?)
The backport would be necessary for the qemu in bionic and cosmic and all relevant cloud archive versions.