Jump to: navigation, search

Dev/Expected Build Warnings

< Dev

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

This does not affect the build. [1]

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

This 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.

This 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.

This does not affect the build. [4]

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

This does not affect the build. [5]

Related forum topic:
Expected Build Warnings

Random News:

Join us in testing our new AppArmor profiles for improved security! (forum discussion)

Impressum | Datenschutz | Haftungsausschluss

https | (forcing) onion
Share: Twitter | Facebook | Google+
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! See Conditions for Contributions to Whonix, then Edit! IP addresses are scrubbed, but editing over Tor is recommended. Edits are held for moderation.

Whonix (g+) is a licensee of the Open Invention Network. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Libre Software license as Whonix itself.
  1. 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.
  2. KVM is installed as a dependency of the build dependency libguestfs-tools. KVM is not needed to build 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 (before 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. This is caused by the same issue referenced above.
  5. This happens because debuild is run as user, not root. It is probably a bug in dpkg. Research of this issue reveals there are many similar bugs in dpkg.