So the host exposing some of the physical cpu characteristics is
triggering use of this specific syndrome generator (which makes sense as
it is h/w specific) raid6_avx21_gen_syndrome().
** Summary changed:
- Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel
exception
+
I will note that this has thrown an illegal instruction trap while doing
this:
[ 522.963634] invalid opcode: [#1] SMP
So it is likely that dispite offering up the avx2 flags to the guest the
host is not actually providing the instructions?
--
You received this bug notification because
