amitshah
https://github.com/lfit/ssh-gpg-smartcard-config/blob/master...
QEMU 2.5 Release and Maintainer Interviews
QEMU Maintainers on the 2.4 Release
The Container Coloring Book [pdf]
https://software.intel.com/en-us/blogs/2012/11/17/the-differ...
Edit to add: we can obviously pass on the RDRAND instruction directly to the VM, but that's less portable, because not all servers in a server farm may have that instruction available, limiting live migration capabilities.
So we can just pass on output from RDSEED into the host's /dev/random, and feed the VM /dev/random by default as described.
Keep in mind, though, that just accessing /dev/urandom in the guest won't need too much input from the host.
However, having a hwrng is obviously the preferred option where there is need for a lot of entropy.
Access to Random Numbers Made Easy in KVM-Based Linux VMs
FUDCon Pune: Fedora Users and Developers Conference, India, 4-6 Nov 2011
Red Hat's new PHP/Ruby/Python/Java PaaS Cloud
Pushing VM scalability: Nehalem and KVM
Take Healthy Breaks [pdf]
The mentality plays a second role: once you're in some position of power (a manager), you want to boss around everyone and prove that you're the person in charge. So managers of projects want everything in 20 days when they might charge clients for 90 days. There's hardly time for the people involved to understand the problem and solve it: they just want to make sure the manager gets what he wants.
Moreover, the employees are in a different set of mentality: they think they don't have much power and that they shouldn't question the manager else their job/backside will be on the line. So they just do what's needed, else come up with creative arguments on the last day.
Red Hat does have an office in Pune, you know that -- right?