DVM fails to start after whonix update/dist-upgrade

System: Qubes 3.1 and Whonix 13.

Immediately after updating the whonix ws and gw templates today, whonix ws dvm failed to start. The DVM was created using the instructions at:

Using Whonix-Workstation as a DisposableVM (DispVM)

The DVM usually works perfectly although this is the second time this has happened and had to recreate it.
Originally assumed a one time only problem but apparently not the case.

Any idea as to what the cause might be? Can provide logs if they might help.

Possible relation to a problem after whonix updates to a normal whonix AppVM recently?

Whonix AppVM fails to start after update

Is the affected DVM based on one of the Whonix appVMs that fail to start? What makes you think the issues are related?

I haven’t experienced either of the issues you describe with a similar system.

Can you run some hardware diagnostics outside of Qubes? RAM, HDD…

Also, what is your graphics adapter?

The DVM is (was) based on the Whonix-ws Template VM.[quote=“entr0py, post:2, topic:3109”]
What makes you think the issues are related?
Only the fact that it started immediatetly after a whonix-ws and gw update.

Extended RAM and HDD diagnostics show passed with 0 errors.
Checked motherboard, PCI, etc., while at it, all passed.[quote=“entr0py, post:2, topic:3109”]
Also, what is your graphics adapter?
Intel Broadwell-U Intigrated Graphics

Perhaps this is a KDE related problem?
Am getting 2 KDE popup errors on startup;

KDE crash handler

“Executable: kded4 PID: **** Signal; Bus error (7) Time; ************”

“Executable: kmix PID: **** Signal; Bus error (7) Time; ************”

Also, another KDE crash handler error if I try to open the application editor.

“Unable to contact khotkeys. Your changes are saved, but they could not be activated.”

“Executable: knotify4 PID: **** Signal; Bus error (7) Time; ************”

The editor then opens but the dvm entry is gone.

Sorry, didn’t answer this question adequately.

The Whonix appVM that fails to start is based on the whonix-ws template as are other whonix appVMs that continue to function correctly.
The DVM is (was) based on the same Whonix-ws template.

Something else interesting that I just noticed is that in Qubes VM manager for the failed DVM, VM settings/advanced shows:

Initial memory:3412MB
Max memory: 4000MB
VCPUs no. 1

I did not change any defaults when the DVM was created.

I’m sorry, I can’t be of much help here. The only issues I’ve had with KDE involved openGL compositing with an ATI card, but Intel Graphics seem to be well supported. I see you’re getting a bus error for kmix. I also had an issue with multiple audio adapters crashing the audio subsystem.

Wow, that is a huge chunk of RAM to be auto-assigned to the DVM… Mine is ~800 MB. I have no idea if that is the cause or the symptom of your issues though.

To debug this (or a VM that does not start generally…). (Do we have more generic debugging instructions on this @adw?)

Set QVMM to show internal and inactive VMs. (Qubes VM Manager -> View)

Then right after starting the VM, open a console.

sudo xl console name-vm-dispvm

(Such as Disp1 or so.)

See if there are any errors. Login as root. See if any systemd services failed loading.

sudo systemctl list-units --failed

Some strangeness happening…

The whonix-DVM would not start at all initially, then went to staying at the yellow phase if started directly from Qubes VM manager. Now it continues to the green phase if started from Qubes VM manager.
Regardless, I’m unable to start an app in the DVM, ie tor browser, which indicates " save file creation failed" and am unable to start a konsole session in the dvm.

Forgive my ignorance, but did you mean I should start a DOM0 konsole after starting the dvm @Patrick?

I tried that too and if so, the only error I can see with the above commands is an app-armor failure.

There are available logs from Qubes VM Manager if that might help?

Perhaps I should delete and recreate the DVM again but will wait for your answer in case you have other questions or would like to try some more debugging.


No failed systemd units?

I’m afraid not (at least not that I’m aware of).

Checked again to verify. No systemd units show failed.

1 Like

Your help in debugging this is appreciated!

Please post the output of qvm-ls (run in dom0 terminal) after failed
start of dvm.

Please also check contents of files in dom0 /var/log/qubes containing
whonix-ws-dvm. To get a list of interesting log files you can use find /var/log/qubes | grep whonix-ws-dvm.

Same for /var/log/qubes folder in whonix-ws-dvm. (After you login using
xl console.)

Thanks. Just a user here trying to muddle through.
The work you are doing is very much appreciated!

@dom0 ~]$ qvm-ls
name | on | state | updbl | type | template | netvm | label |
{dom0} | * | Running | Yes | Admin | None | n/a | black |
{sys-net} | * | Running | | Net | fedora-23 | n/a | red |
{sys-firewall} | * | Running | | Proxy | fedora-23 | sys-net | green |
{sys-whonix} | * | Running | | Proxy | whonix-gw | sys-firewall | black |
[debian-8] | | Halted | Yes | Tpl | n/a | *sys-whonix | black |
[whonix-ws] | | Halted | Yes | Tpl | n/a | *sys-whonix | black |
whonix-ws-dvm | * | Running | | | whonix-ws | *sys-whonix | gray |
anon-whonix-bad | | Halted | | | whonix-ws | sys-whonix | red |
whonix | | Halted | | | whonix-ws | sys-whonix | orange |
anon-whonix | | Halted | | | whonix-ws | *sys-whonix | red |
anon-whonix-clone-1 | * | Running | | | whonix-ws | *sys-whonix | red |
[whonix-gw] | | Halted | Yes | Tpl | n/a | sys-whonix | black |
=>[fedora-23] | | Halted | Yes | Tpl | n/a | *sys-whonix | black |
untrusted | * | Halted | | | fedora-23 | sys-firewall | red |
personal | * | Halted | | | fedora-23 | - | yellow |
banking | | Halted | | | fedora-23 | sys-firewall | green |
work-New | | Halted | | | fedora-23 | *sys-whonix | blue |
Vault | | Halted | | | fedora-23 | - | black |
fedora-23-dvm | | Halted | | | fedora-23 | sys-firewall | gray |

Icon size: 128x128
invalid PMinSize for 0x3c00005 (0/0)
invalid PMaxSize for 0x3c00005 (0/0)
invalid PResizeInc for 0x3c00005 (0/0)
invalid PBaseSize for 0x3c00005 (0/0)
invalid PMinSize for 0x3c00006 (0/0)
invalid PMaxSize for 0x3c00006 (0/0)
invalid PResizeInc for 0x3c00006 (0/0)
invalid PBaseSize for 0x3c00006 (0/0)
invalid PMaxSize for 0x3c00006 (0/0)
invalid PResizeInc for 0x3c00006 (0/0)
Icon size: 128x128

Icon size: 128x128
invalid PMinSize for 0x4400005 (0/0)
invalid PMaxSize for 0x4400005 (0/0)
invalid PResizeInc for 0x4400005 (0/0)
invalid PBaseSize for 0x4400005 (0/0)
invalid PMinSize for 0x4400006 (0/0)
invalid PMaxSize for 0x4400006 (0/0)
invalid PResizeInc for 0x4400006 (0/0)
invalid PBaseSize for 0x4400006 (0/0)
invalid PMaxSize for 0x4400006 (0/0)
invalid PResizeInc for 0x4400006 (0/0)
Icon size: 128x128
domain dead
Failed to connect to gui-agent

0 bytes

0 bytes

Rpc allowed: whonix-ws-dvm dom0 qubes.WindowIconUpdater
Rpc allowed: whonix-ws-dvm dom0 qubes.NotifyUpdates

vchan closed
vchan closed

This produced no info.
@dom0 ~]$ sudo xl console whonix-ws-dvm

user@host:~$ find /var/log/qubes | grep whonix-ws-dvm

1 Like

Can you make head or tail of this report or could use any further debug output? @marmarek

If more debug info is desired, please let me know. If not, will delete the affected dvm and recreate.

1 Like