Hello,

On Mon, Mar 05, 2012 at 04:11:41PM +0100, Stanislaw Gruszka wrote:

Perhaps bug was triggered because KVM 32-bit guest had CONFIG_CRYPTO_AES_NI_INTEL
enabled ?

Nope. CONFIG_CRYPTO_AES_NI_INTEL is enabled only in the 64-bit host kernel.
Guest kernel version is 2.6.32-220.2.1.el6.i686 and there's no mention of
AES_NI_INTEL in its .config.

(And I do run a 32-bit userspace, perhaps if I had 64-bit userspace, the guest
would be safe. Or maybe not. I have no idea and no time to get a 64-bit
userspace. :-))

-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/