After the upgrade from Proxmox VE 1.8 to the latest vzevents based binaries, new errors are showing up in the startup logs for a CentOS 5.6 container. These errors do not affect the operation of the CentOS container though. The errors that show up anew are:
The device urandom is present but random is not.
Code:
Starting vzquota: quotaon: using //aquota.group on /dev/simfs [/]: Device or resource busy
quotaon: using //aquota.user on /dev/simfs [/]: Device or resource busy
[FAILED]
Starting named: named: could not open pre-chroot entropy source /dev/random: file not found
[ OK ]
Starting vzquota: quotaon: using //aquota.group on /dev/simfs [/]: Device or resource busy
quotaon: using //aquota.user on /dev/simfs [/]: Device or resource busy
[FAILED]