Jump to: navigation, search

Template:Expected Build Warnings

Can not write log, openpty() failed (/dev/pts not mounted?)

Does not affect the build. [1]

[....] Your system does not have the CPU extensions required to use KVM. Not doing anything. ...[ FAIL ]

Does not affect the build. [2]

[....] 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.

Does not affect the build. [3]

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.

Does not affect the build. [4]

dpkg: warning: failed to open configuration file '/root/.dpkg.cfg' for reading: Permission denied

Does not affect the build. [5]

Related forum topic:

Expected Build Warnings
  1. This is nothing to worry about. It only happens because we are running commands inside chroot. If you research this "issue", you'll find that it is purely cosmetic.
  2. KVM gets installed as a dependency of our build dependency libguestfs-tools. We don't need KVM for building the actual images.
  3. This only means that VirtualBox cannot be started. VirtualBox kernel modules could not be compiled, because the linux-headers-$(uname -r) package was not installed prior to installing VirtualBox (prior to starting Whonix's build script). The build script doesn't start VirtualBox, hence does not affect the build. The build script only uses VBoxManage for creation of virtual machine description files and that tool doesn't need VirtualBox kernel modules.
  4. The same issue referenced above.
  5. This happens because we are running debuild as user, not root. It is probably a bug in dpkg. If you research this, you'll find there are many similar bugs in dpkg.