On Tue, Mar 22, 2016 at 02:49:42PM +0000, Richard W.M. Jones wrote:
I got this error when trying to use /dev/urandom as a backend for virtio-rng. Is there a reason for that? Plain qemu allows you to specify /dev/urandom and seems to work OK.
There's a tetchy bugzilla on this subject:
https://bugzilla.redhat.com/show_bug.cgi?id=1074464
but I think for cases where people don't care / throwaway appliances, we should allow /dev/urandom. The main reason is that it doesn't block.
Having it block is desirable, even for throwaway appliances like libguestfs, as even if the appliance is throway, the work they do should not be assumed to be throwaway. For example if libguestfs is creating or modifying a LUKS volume in a disk image, the guestfs appliance is throwaway, but the resulting LUKS volume with cryptographic keys lives for ever Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|