Advertisement Tracking - Real threat to Whonix Project

Patrick · December 5, 2016, 7:27pm

Meanwhile I did run into the same error: Internal error: failed to maintain the domain 9 using libxenlight error. Created a new Qubes bug report.

github.com/QubesOS/qubes-issues

DispVM start error - error: internal error: Failed to save domain '30' with libxenlight

opened 05:27PM - 04 Dec 16 UTC

closed 04:34PM - 02 Sep 20 UTC

adrelanos

T: bug C: core

#### Qubes OS version (e.g., `R3.2`): R3.2 with testing repository. #### A…ffected TemplateVMs (e.g., `fedora-23`, if applicable): whonix-ws (but probably not a template issue) --- ### Actual behavior: ``` /usr/lib/qubes/qfile-daemon-dvm qubes.VMShell dom0 DEFAULT red time=1480778855.52, qfile-daemon-dvm init time=1480778855.52, creating DispVM Can't get domid of domain name 'whonix-ws', maybe this domain does not exist. --> Creating volatile image: /var/lib/qubes/appvms/whonix-ws-dvm/volatile.img... --> Loading the VM (type = AppVM)... --> Starting Qubes DB... --> Setting Qubes DB info for the VM... --> Updating firewall rules... --> Starting the VM... --> Starting Qubes GUId... Connecting to VM's GUI agent: ..............connected Waiting for DVM whonix-ws-dvm ... DVM boot complete, memory used=648672. Saving image... error: Failed to save domain whonix-ws-dvm to /var/lib/qubes/appvms/whonix-ws-dvm/dvm-savefile error: internal error: Failed to save domain '30' with libxenlight ``` Already managed to reproduce this twice. Beforehand it was save domain '23' and now save domain '30'. No power loss at any time. No ctrl + c at any time. No hdd disk errors at any time. ### Steps to reproduce the behavior: Playing around with DispVMs a lot to deepen understanding. However, nothing unjustifiable. Steps here: https://forums.whonix.org/t/qubes-dispvm-technical-discussion/3232/8

Might be that you are having too many VMs running.

Since I cannot reproduce this issue at the moment, please contribute to that bug report by providing the requested debug information when you run into this issue again.

Meanwhile we we working on DispVM documentation. ( Qubes DispVM technical discussion - #17 by Patrick )

Now there is a strong warning against DispVM for anonymity generally at the top of that page that will probably last until Qubes 4.0 unless one knows about these issues and works around those. ( Qubes Disposables )

And there now is a specific warning against using Firefox. ( Qubes Disposables )

Thanks for the report!