virtio-rng device causing old guest kernels(2.6.32) to hang on latest qemu.
The driver attempts to read from the virtio-rng device too early in it's
initialization. Qemu detects guest is not ready and returns, resulting in
hang. Below patches fix this.
Stefan Hajnoczi(1):
virtio-rng: proces
On (Tue) 29 Jul 2014 [19:28:56], John Snow wrote:
> My previous commit, 713e8a10, did not address the fact that
> the error checking pathways do not attempt to call
> virtio_cleanup and thus can leak memory in hotplug scenarios.
>
> This patchset shuffles around the error checking so it does not
>
On Tue, Jul 29, 2014 at 07:28:56PM -0400, John Snow wrote:
> My previous commit, 713e8a10, did not address the fact that
> the error checking pathways do not attempt to call
> virtio_cleanup and thus can leak memory in hotplug scenarios.
>
> This patchset shuffles around the error checking so it d
John Snow writes:
> My previous commit, 713e8a10, did not address the fact that
> the error checking pathways do not attempt to call
> virtio_cleanup and thus can leak memory in hotplug scenarios.
>
> This patchset shuffles around the error checking so it does not
> need to perform said cleanup,
My previous commit, 713e8a10, did not address the fact that
the error checking pathways do not attempt to call
virtio_cleanup and thus can leak memory in hotplug scenarios.
This patchset shuffles around the error checking so it does not
need to perform said cleanup, and changes the error functions
Hi!
I've cleaned up and rebased the virtio-rng patch, including the
comments made on the previous version.
I've dropped socket reconnect support because I don't have the
time to make it into some kind of generic does-everything
subsystem, so here is whats left - a pure rng / egd device.
-Ian
