Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
err:1c25e0 [2016/07/10 19:51] mcb30 |
err:1c25e0 [2021/01/05 18:44] mcb30 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| This error indicates that the cryptographic random bit generator could not be initialised. This usually indicates that there is no good source of entropy available. | This error indicates that the cryptographic random bit generator could not be initialised. This usually indicates that there is no good source of entropy available. | ||
| + | |||
| + | Some versions of the VMware hypervisor provide a "side channel mitigations" feature which unfortunately breaks the entropy source used by iPXE. You can disable side channel mitigations using the Advanced Settings for the virtual machine. See https://kb.vmware.com/s/article/79832 for more details, including the security implications of disable side channel mitigations. | ||
| There is a known bug in the Microsoft Hyper-V hypervisor (as used for Microsoft Azure virtual machines), in which the emulated CMOS RTC hardware seems to be incapable of generating an interrupt. This breaks the entropy generation mechanism used by iPXE, and will result in this error. There are some indications that this problem affects only AMD hardware, though this has not been proved conclusively. If you are using Microsoft Azure, then you may be able to work around the problem by using a larger instance (which is more likely to use an Intel CPU). | There is a known bug in the Microsoft Hyper-V hypervisor (as used for Microsoft Azure virtual machines), in which the emulated CMOS RTC hardware seems to be incapable of generating an interrupt. This breaks the entropy generation mechanism used by iPXE, and will result in this error. There are some indications that this problem affects only AMD hardware, though this has not been proved conclusively. If you are using Microsoft Azure, then you may be able to work around the problem by using a larger instance (which is more likely to use an Intel CPU). | ||
