similar to: [PATCH 0/2] rng-tools: add udev rule for virtio-rng

Il 07/08/2014 15:09, Amit Shah ha scritto: > +udevrules_DATA = 90-virtio-rng.rules If rng-tools is packaged with "make dist" you need this to be dist_udevrules_DATA = 90-virtio-rng.rules or alternatively EXTRA_DIST = 90-virtio-rng.rules udevrules_DATA = 90-virtio-rng.rules > +AC_ARG_WITH([udevrulesdir], > + AS_HELP_STRING([--with-udevrulesdir=DIR], [Directory for udev

Il 07/08/2014 15:09, Amit Shah ha scritto: > +udevrules_DATA = 90-virtio-rng.rules If rng-tools is packaged with "make dist" you need this to be dist_udevrules_DATA = 90-virtio-rng.rules or alternatively EXTRA_DIST = 90-virtio-rng.rules udevrules_DATA = 90-virtio-rng.rules > +AC_ARG_WITH([udevrulesdir], > + AS_HELP_STRING([--with-udevrulesdir=DIR], [Directory for udev

On 08/07/2014 06:08 AM, Amit Shah wrote: > On KVM guests where the virtio-rng device is available, and set as the > current rng, this udev rule will start rngd which will feed in the > host-provided entropy to /dev/random. > > Signed-off-by: Amit Shah <amit.shah at redhat.com> > --- > 90-virtio-rng.rules | 1 + > 1 file changed, 1 insertion(+) > create mode

On 08/07/2014 06:08 AM, Amit Shah wrote: > On KVM guests where the virtio-rng device is available, and set as the > current rng, this udev rule will start rngd which will feed in the > host-provided entropy to /dev/random. > > Signed-off-by: Amit Shah <amit.shah at redhat.com> > --- > 90-virtio-rng.rules | 1 + > 1 file changed, 1 insertion(+) > create mode

Hello. I'm a distro maintainer and was wondering about the efficacy of entropy daemons like haveged and jitterentropyd in qemu-kvm. One of the authors of haveged [0] pointed out if the hardware cycles counter is emulated and deterministic, and thus predictible. He therefore does not recommend using HAVEGE on those systems. Is this the case with KVM's counters? PS. I will be setting VM CPU

Amit, Kees, On Wed, Jul 09, 2014 at 06:55:24PM +0530, Amit Shah wrote: > On (Wed) 09 Jul 2014 [09:17:37], Jason Cooper wrote: > > On Wed, Jul 09, 2014 at 06:38:22PM +0530, Amit Shah wrote: > > > On (Wed) 09 Jul 2014 [07:53:17], Jason Cooper wrote: > > > > On Sat, Jul 05, 2014 at 11:04:52AM +0530, Amit Shah wrote: > > > > > Commit d9e7972619334

Amit, Kees, On Wed, Jul 09, 2014 at 06:55:24PM +0530, Amit Shah wrote: > On (Wed) 09 Jul 2014 [09:17:37], Jason Cooper wrote: > > On Wed, Jul 09, 2014 at 06:38:22PM +0530, Amit Shah wrote: > > > On (Wed) 09 Jul 2014 [07:53:17], Jason Cooper wrote: > > > > On Sat, Jul 05, 2014 at 11:04:52AM +0530, Amit Shah wrote: > > > > > Commit d9e7972619334

I have a new centos 6 install. Randomly i get out of memory messages and my ssh file transfer dies. I have tried this in filezilla as well as winscp. I have disabled motd in ssh and i also had entropy problems so i enacted rngd -r /dev/urandom -o /dev/random but did not stop the out of memory errors. I am seeing the below in the logs. It only occurs during ssh file transfers. Feb 28

On Fri, Jul 11, 2014 at 06:56:26PM +0530, Amit Shah wrote: > On (Wed) 09 Jul 2014 [12:07:25], Jason Cooper wrote: > > Amit, Kees, > > (snip) > > > I'm cooling to the idea of the init function for virtio-rng, and it > > might be best just to admit that there's no way to seed the entropy pool > > from the virtio-rng at probe time. After all, once

On Fri, Jul 11, 2014 at 06:56:26PM +0530, Amit Shah wrote: > On (Wed) 09 Jul 2014 [12:07:25], Jason Cooper wrote: > > Amit, Kees, > > (snip) > > > I'm cooling to the idea of the init function for virtio-rng, and it > > might be best just to admit that there's no way to seed the entropy pool > > from the virtio-rng at probe time. After all, once

Hi, I've discovered an issue which I don't understand. On a new test install of EL9 I saw this message in the logs: Mar 01 08:09:18 <hostname> pcp-pmie[2870]: Low random number entropy available 15.6%avail at beta.corp.invoca.ch This is on a 64 core "AMD Opteron(tm) Processor 6282 SE" server but I also got the same low entropy on an EL9 KVM guest running on a "AMD

Am Freitag, 29. Juli 2016, 09:03:45 CEST schrieb Alex Xu: Hi Alex, > On Fri, 29 Jul 2016 12:24:27 +0200 > > Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote: > > On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller > > > > <smueller at chronox.de> wrote: > > > And finally, you have a coding error that is very very common but > > > fatal

Am Freitag, 29. Juli 2016, 09:03:45 CEST schrieb Alex Xu: Hi Alex, > On Fri, 29 Jul 2016 12:24:27 +0200 > > Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote: > > On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller > > > > <smueller at chronox.de> wrote: > > > And finally, you have a coding error that is very very common but > > > fatal

On (Thu) 07 Aug 2014 [12:31:11], H. Peter Anvin wrote: > On 08/07/2014 06:08 AM, Amit Shah wrote: > > On KVM guests where the virtio-rng device is available, and set as the > > current rng, this udev rule will start rngd which will feed in the > > host-provided entropy to /dev/random. > > > > Signed-off-by: Amit Shah <amit.shah at redhat.com> > > ---

On Wed, Jul 09, 2014 at 06:38:22PM +0530, Amit Shah wrote: > On (Wed) 09 Jul 2014 [07:53:17], Jason Cooper wrote: > > On Sat, Jul 05, 2014 at 11:04:52AM +0530, Amit Shah wrote: > > > Commit d9e7972619334 "hwrng: add randomness to system from rng sources" > > > added a call to rng_get_data() from the hwrng_register() function. > > > However, some rng

On Wed, Jul 09, 2014 at 06:38:22PM +0530, Amit Shah wrote: > On (Wed) 09 Jul 2014 [07:53:17], Jason Cooper wrote: > > On Sat, Jul 05, 2014 at 11:04:52AM +0530, Amit Shah wrote: > > > Commit d9e7972619334 "hwrng: add randomness to system from rng sources" > > > added a call to rng_get_data() from the hwrng_register() function. > > > However, some rng

All, I am running into a situation in which one of my ext3 filesystems is getting hung during normal usage. There are three ext3 filesystems on a CompactFLASH. One is mounted as / and one as /tmp. In my test, I am copying a 100 MB file from /root to /tmp repeatedly. While doing this test, I eventually see the copying stop, and any attempts to access /tmp fail - if I even do ls /tmp the

I ran rpm -Va and received almost a thousand bad entries on a clean install of 5.1 after doing some 'rpm -e' ... S.5..... /usr/sbin/ypserv_test S.5..... /usr/sbin/ypset S.5..... /usr/sbin/yptest S.5..... /sbin/rngd S.5..... /usr/bin/rngtest S.5..... /lib/security/pam_ccreds.so S.5..... /usr/sbin/cc_dump S.5..... /usr/sbin/cc_test S.5..... /usr/lib/libpng12.so.0.10.0

On KVM guests where the virtio-rng device is available, and set as the current rng, this udev rule will start rngd which will feed in the host-provided entropy to /dev/random. Signed-off-by: Amit Shah <amit.shah at redhat.com> --- 90-virtio-rng.rules | 1 + 1 file changed, 1 insertion(+) create mode 100644 90-virtio-rng.rules diff --git a/90-virtio-rng.rules b/90-virtio-rng.rules new

Has anyone yet written a "hw" RNG module for virt, that reads the host's random number pool? All this talk[1] about IRQF_SAMPLE_RANDOM in network drivers reminds me that virt guest instances should be grabbing random numbers from the host, especially if the host has a hardware RNG. Jeff [1] lkml&netdev thread: "[PATCH] drivers/net: remove network drivers' last