Whonix ™ on Unsupported Virtualization Platforms
From Whonix
< Dev
Contents
Introduction[edit]
Whonix ™ is available for:
In an ideal world, Whonix ™ would support all Virtualization Platforms. Theoretically it could be done using libvirt [archive]. Practically libvirt is out of question. libvirt-users Does libvirt abstract each and any vm specific command? [archive] Libvirt does not (yet) abstract some commands Whonix ™ depends on.
Other Virtualization Platforms[edit]
Introduction[edit]
In theory, Whonix ™ could run inside any virtualizer, because its build scripts are very modular and extensible. In reality, Whonix ™ has no man power to test other virtualizers. As soon as contributors join the project and maintain support for other virtualizers, support for them can most likely be easily added.
Support Plan[edit]
Whonix ™ would need a contributor to support the other virtualization platform.
Important:
- Someone who runs those Test, LeakTests and tests from Protocol-Leak-Protection_and_Fingerprinting-Protection.
- Someone who otherwise looks around if everything is sane.
Ideal:
- Someone who creates, signs, uploads .ova images for the other virtualization platform (such as VMware, KVM, etc.).
Partially Finished Attempts[edit]
VirtualBox[edit]
Moved to Dev/VirtualBox.
Why Use KVM Over VirtualBox?[edit]
See Why Use KVM Over VirtualBox?
Misc[edit]
time sudo dd if=/dev/sda of=/dev/sdc bs=64K conv=noerror,sync status=progress qubes ticket https://github.com/QubesOS/qubes-issues/issues/5372 plus own ticket nobody has a solution how to get data out of qubes dd image undocumented how to get data out of qubes backup also undocumented questionmark dom0 upgrade risks making the system unbootabe backup required qubes internal backup not reliable past scrypt issue when restoring so without backup verification one would not know if it would actually be a sufficient backup takes very long time no automated verification hard to script since folder name is in VM verification of backup might actually fill up disk and thereby brick system dd based backup does not boot on same computer since it boots from internal rather than external disk removal of internal disk by BIOS not possible and physical removal is high effort dd based backup also does not boot on another notebook not sure if resoring back the dd backup would boot or what is missing snapshot_name="before-dev-upgrade" vboxmanage controlvm Whonix-Gateway-XFCE poweroff vboxmanage controlvm Whonix-Workstation-XFCE poweroff vboxmanage snapshot Whonix-Gateway-XFCE restore "$snapshot_name" vboxmanage snapshot Whonix-Workstation-XFCE restore "$snapshot_name"
References[edit]
Whonix ™ is Supported by Evolution Host DDoS Protected VPS. Stay private and get your VPS with Bitcoin or Monero.
Search engines: YaCy | Qwant | ecosia | MetaGer | peekier
Did you know that anyone can edit the Whonix wiki [archive] to improve it?
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! Read, understand and agree to Conditions for Contributions to Whonix ™, then Edit! Edits are held for moderation. Policy of Whonix Website and Whonix Chat and Policy On Nonfreedom Software applies.
Copyright (C) 2012 - 2020 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee [archive] of the Open Invention Network [archive]. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Freedom Software license as Whonix ™ itself. (Why?)
Whonix ™ is a derivative of and not affiliated with Debian [archive]. Debian is a registered trademark [archive] owned by Software in the Public Interest, Inc [archive].
Whonix ™ is produced independently from the Tor® [archive] anonymity software and carries no guarantee from The Tor Project [archive] about quality, suitability or anything else.
By using our website, you acknowledge that you have read, understood and agreed to our Privacy Policy, Cookie Policy, Terms of Service, and E-Sign Consent. Whonix ™ is provided by ENCRYPTED SUPPORT LP. See Imprint, Contact.