Dev/Expected Build Warnings
None of the following warnings affect the build. Refer to relevant footnotes for further information.
dpkg-source: warning: extracting unsigned source package
dpkg-source: warning: extracting unsigned source package (anon-gw-anonymizer-config_5.0-1.dsc)
Can not write log, openpty() failed (/dev/pts not mounted?)
[....] Your system does not have the CPU extensions required to use KVM. Not doing anything. ...[ FAIL ]
[....] Stopping VirtualBox kernel modules [ ok ]. [....] Starting VirtualBox kernel modules[....] No suitable module for running kernel found ...[ FAIL ] invoke-rc.d: initscript virtualbox, action "restart" failed.
WARNING: The character device /dev/vboxdrv does not exist. Please install the virtualbox-ose-dkms package and the appropriate headers, most likely linux-headers-486. You will not be able to start VMs until this problem is fixed.
dpkg: warning: failed to open configuration file '/root/.dpkg.cfg' for reading: Permission denied
sudo: unable to resolve host host
- end-to-end signed debs. debsign, debsig and dpkg-sig [archive]
- This is nothing to be concerned about; it only happens because commands are run inside chroot. Research of this "issue" indicates it is purely cosmetic.
- KVM is installed as a dependency of the build dependency
libguestfs-tools. KVM is not needed to build the actual images.
- This only means that VirtualBox cannot be started. VirtualBox kernel modules could not be compiled because the
VBoxManagefor creation of virtual machine description files and that tool does not need VirtualBox kernel modules. package was not installed prior to installing VirtualBox (before starting Whonix's build script). The build script does not start VirtualBox, hence does not affect the build. The build script only uses
- This is caused by the same issue referenced above.
- This happens because
debuildis run as user, not root. It is probably a bug in dpkg. Research of this issue reveals there are many similar bugs in dpkg.
The hostname is changed intentionally to
hostinside the VM image. The cause is probably package
hostname host. This change should only happen inside the change root
chroot. This issue might be resolved by porting from
systemd-nspawn, but it is not very important.