Actions

Dev/Virtualization Platform

From Whonix

< Dev(Redirected from Dev/Other Virtualization Platforms)


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 maintainer to support the other virtualization platform.

Important:

Ideal:

  • Someone who creates, signs, uploads .ova images for the other virtualization platform (such as VMware, KVM, etc.).

Partially Finished Attempts[edit]

  • QEMU (deprecated)
  • VMware (proof of concept, no maintainer)

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]



Follow: Twitter.png Facebook.png 1280px-Gab text logo.svg.png Rss.png Matrix logo.svg.png 1024px-Telegram 2019 Logo.svg.png Discourse logo.svg

Donate: Donate Bank Wire Paypal Bitcoin accepted here Monero accepted here Contriute

Whonix donate bitcoin.png Monero donate whonix.png

Share: Twitter | Facebook

https link onion link

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.

Copyright (C) 2012 - 2019 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.