[Qemu-devel] [Bug 1811758] Re: virtio-rng backend should use getentropy() syscall when available

2019-04-17 Thread Amit Shah
Yes, using getrandom() in qemu by default on systems that support it will be an improvement, and is the right approach. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1811758 Title: virtio-rng backe

[Qemu-devel] [Bug 1811758] Re: virtio-rng backend should use getentropy() syscall when available

2019-04-15 Thread Thomas Huth
Feel free to send some patches to implement this! Alternatively, you could also try to write a mail to the virtio-rng maintainer (see the MAINTAINER file in the top directory of the sources), maybe he can help. ** Changed in: qemu Importance: Undecided => Wishlist -- You received this bug not

[Qemu-devel] [Bug 1811758] Re: virtio-rng backend should use getentropy() syscall when available

2019-04-15 Thread dkg
any word on this? If this is not considered for adoption, i would like to know the reason, so that we can have better predictions about what to do for entropy in a QEMU system. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://

[Qemu-devel] [Bug 1811758] Re: virtio-rng backend should use getentropy() syscall when available

2019-01-15 Thread dkg
To be clear, the problem with using /dev/urandom as a backend is that it's possible to feed data from an uninitialized pool into the guest. and the problem with using /dev/random as a backend is that it's possible for a guest to starve the other host (and other guests) of entropy, since it pulls f