tests: Pretend the RNG is initialized withinthe VM
We don't particularly care about the quality of random numbers during the test. So far, there hasn't been an issue with the RNG not being initialized completely, we only get a few prints about uninitialized reads from urandom. However, if some tool were to actually use /dev/random, it might get stuck. Call the RNDADDTOENTCNT ioctl to unblock this. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
This commit is contained in:
parent
52e2516f1d
commit
2f336ca580
1 changed files with 5 additions and 0 deletions
|
@ -58,6 +58,11 @@ ln -s /proc/self/fd/0 /dev/stdin
|
|||
ln -s /proc/self/fd/1 /dev/stdout
|
||||
ln -s /proc/self/fd/2 /dev/stderr
|
||||
|
||||
# pretend we've initialized the RNG, we don't care here
|
||||
# about the actual quality of the randomness. The ioctl
|
||||
# is RNDADDTOENTCNT (at least on x86).
|
||||
PYTHONHASHSEED=0 python3 -c 'import fcntl; fd=open("/dev/random", "w"); fcntl.ioctl(fd.fileno(), 0x40045201, b"\x00\x01\x00\x00")'
|
||||
|
||||
echo "VM has started up" > /dev/ttyS0
|
||||
|
||||
# create stub sudo - everything runs as uid 0
|
||||
|
|
Loading…
Reference in a new issue