Comment 17 for bug 1790457

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- 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
https://git.qemu.org/?p=qemu.git;a=commit;h=27e84d4ebd25b981ab27cb590fe06d1b0fcd06d2
commit: 27e84d4ebd25b981ab27cb590fe06d1b0fcd06d2
title: s390x/kvm: add etoken facility

we also need the following commit to make this compile
https://git.qemu.org/?p=qemu.git;a=commit;h=d36f7de82995a42b749c29c5b60ba31483995a42
commit: d36f7de82995a42b749c29c5b60ba31483995a42
title: linux-headers: update

To simplify things, this part of the headers update is sufficient:
https://git.qemu.org/?p=qemu.git;a=blobdiff;f=linux-headers/asm-s390/kvm.h;h=1ab9901911bf55e3aba55488bb20a184d85bbce5;hp=11def143015d572f208bbdf4aa4ecfa094c700a1;hb=d36f7de82995a42b749c29c5b60ba31483995a42;hpb=c61177881cbda50704207dd9fb4811659bbf913e

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.