Displaying 3 results from an estimated 3 matches for "_rng0".
Did you mean:
rng0
2014 Jul 28
2
When I boot two virtio-rng devices, guest will hang
On Mon, Jul 28, 2014 at 02:42:13PM +0530, Amit Shah wrote:
> On (Mon) 28 Jul 2014 [16:49:20], Amos Kong wrote:
> > On Mon, Jul 28, 2014 at 01:25:14PM +0530, Amit Shah wrote:
> > > On (Mon) 28 Jul 2014 [15:32:42], Amos Kong wrote:
> > > > QEMU commandline:
> > > >
> > > > ./x86_64-softmmu/qemu-system-x86_64 --enable-kvm -m 2000 -drive
2014 Jul 28
2
When I boot two virtio-rng devices, guest will hang
On Mon, Jul 28, 2014 at 02:42:13PM +0530, Amit Shah wrote:
> On (Mon) 28 Jul 2014 [16:49:20], Amos Kong wrote:
> > On Mon, Jul 28, 2014 at 01:25:14PM +0530, Amit Shah wrote:
> > > On (Mon) 28 Jul 2014 [15:32:42], Amos Kong wrote:
> > > > QEMU commandline:
> > > >
> > > > ./x86_64-softmmu/qemu-system-x86_64 --enable-kvm -m 2000 -drive
2014 Aug 05
0
When I boot two virtio-rng devices, guest will hang
...t-remove rng0, then hot-remove rng1 -> result: _only rng1_ can't be removed until dd process is killed
3 (option 2). hot-remove rng1, then hot-remove rng0 -> result: two devices can be removed successfully, dd process will exit automatically.
If we use /dev/urandom for rng0 and rng1, _rng0 & rng1_ can be removed, dd process will exit automatically.
Hotplug issue 2:
If we use /dev/random for rng0 and rng1, _rng0 & rng1_ can't be removed until dd process is killed.
Hotplug issue 3:
If we use /dev/random for rng0 and rng1, _only rng1_ can't be removed until dd proc...