On Thu, 6 Feb 2020 at 16:52, Wesley Chow wrote:
> Yes great, thank you for the tip.. I should have been looking in dmesg for
> PCI stuff all along. While CONFIG_PCI_HOST_GENERIC was not set, setting it
> didn't help. But that did give me an error which I tracked down to this:
>
>
> I realize this may not be a qemu issue at this point, but I am curious as
> to why rngd takes so long to initialize /dev/hwrng.
>
ding ding ding! The rngd startup latency appears to be an issue that was
fixed in the most recent rng-tools 6.9 release and unrelated to QEMU.
If anybody is
>
>
> > CONFIG_PCI=y
> > CONFIG_VIRTIO=y
> > CONFIG_VIRTIO_PCI=y
> > CONFIG_VIRTIO_BLK=y
> > CONFIG_HW_RANDOM_VIRTIO=y
> > CONFIG_CRYPTO_DEV_VIRTIO=y
> > CONFIG_CRYPTO_HW=y
> > CONFIG_CRYPTO_RNG2=y
> > CONFIG_HW_RANDOM=y
> >
> > I honestly don't know which of these actually matter. I'm wondering,
On Wed, 5 Feb 2020 at 22:03, Wesley Chow wrote:
>
> I'm building a kernel suitable to boot Raspbian and a custom buildroot based
> ARM OS via qemu-system-arm. Everything appears to work except for the
> hardware rng device. I'm using a virt machine with:
>
> -object
> On Feb 5, 2020, at 2:02 PM, Wesley Chow wrote:
>
>
> I'm building a kernel suitable to boot Raspbian and a custom buildroot based
> ARM OS via qemu-system-arm. Everything appears to work except for the
> hardware rng device. I'm using a virt machine with:
>
> -object
I'm building a kernel suitable to boot Raspbian and a custom buildroot
based ARM OS via qemu-system-arm. Everything appears to work except for the
hardware rng device. I'm using a virt machine with:
-object rng-random,filename=/dev/urandom,id=rng0 -device
virtio-rng-pci,rng=rng0
In both
