Skip to content

Dev: Provisioning logic debugging

mickael e edited this page Dec 12, 2019 · 2 revisions

In some situations make all might take a very long time or even hang. When it's the first time provisioning, this is normal, because it is pulling 3 different template VMs (> 2GB of packages, which could take 1h or more). Once the first make all successfully completes, it is possible that bugs in the provisioning logic make subsequent runs hang. The following will provide helpful debugging information

Identify VM(s) causing issues

[user@dom0]$ qvm-ls --running

Observe the VMs that are running that are prefixed by disp-mgmt-. Those will indicate which VM provisioning steps are slow/handing.

Recovering and re-running make all

To recover, you can qvm-kill the management machine:

[user@dom0]$ qvm-kill disp-mgmt-sd-whatever

If whatever-vm is not automatically shut down afterwards, kill that one too:

[user@dom0]$ qvm-kill sd-whatever

You can then safely run make all or make sd-whatever again