[BUG/Question] HyperV Entropy doesn't appear to be consumed through new agent system
See original GitHub issueDescribe the bug
Per the README, Consume Hyper-V entropy for /dev/random
this appears to only be done through the waagent2.0 script. The waagent script will only run the waagent2.0 script when __name__ == 'waagent'
.
Unless I’m missing some other way that HyperV Entropy is being consumed especially since the HyperV VMBUS doesn’t invoke the LRNG interrupt handler in the Linux kernel.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Troubleshoot issues when adding a Hyper-V host - Virtual ...
Describes how to troubleshoot issues when you add a Hyper-V host in System Center 2012 Virtual Machine Manager and later versions.
Read more >Analysis of Random Number Generation in Virtual Environments
The quality of the Linux random number generator is assessed when executing it in the VMMs of KVM, VirtualBox, Microsoft Hyper-V and VMWare....
Read more >Entropy and Random Number Generation on Virtual Machines
This article covers the basics on random numbers generation and show you how to circumvent the problems that may arise. A complete description ......
Read more >Virtual Machine Management Guide - oVirt
Explanation of Settings in the New Virtual Machine and Edit Virtual ... Adding an operating system that does not appear in the list...
Read more >QEMU - ArchWiki
QEMU can use other hypervisors like Xen or KVM to use CPU extensions (HVM) ... Note: At present, Arch does not offer a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kovacs-andras @colemickens The Agent was rewritten in late 2014 and the new version did not include this code, but the documentation was not updated. I have updated the documentation. The VM Agent is not the best place to do this; the place where it was done in the code may be too late for components that need this during boot. Also, the agent can be disabled/deleted. We are not planning on adding this functionality back.
So is it not necessary to do this anymore in Azure VMs or… why was this functionality removed?