Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upAppVM fails to start with "device_backend_callback: unable to add device with path /local/domain/7/backend/vif/18/0" #3696
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
fishilico
Mar 13, 2018
After asking for help on IRC, I tried to reboot my computer and the issue disappeared. I reported the issue nonetheless in order to help other people who may encounter it.
I would also be very interested in knowing what commands I could have used in order to debug the issue more and find out what caused it (or what commands will be helpful if the issue happens again).
fishilico
commented
Mar 13, 2018
|
After asking for help on IRC, I tried to reboot my computer and the issue disappeared. I reported the issue nonetheless in order to help other people who may encounter it. I would also be very interested in knowing what commands I could have used in order to debug the issue more and find out what caused it (or what commands will be helpful if the issue happens again). |
fishilico
closed this
Mar 13, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 13, 2018
Member
One thing to check is if xendriverdomain.service is running in sys-firewall. Also it would be helpful to know if libxl_device.c:1081:device_backend_callback: unable to add device with path /local/domain/7/backend/vif/18/0 line appears immediately at VM startup try, or after some timeout (10s? 30s?).
|
One thing to check is if |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
fishilico
Mar 13, 2018
I have posted the full logs of running tail -F on all .log files in /var/log on https://pastebin.com/4DhLMe0W , when I tried starting an AppVM named "testing-debian" created from debian-9 template, in PVH mode. Here are the relevant lines (with times):
==> /var/log/qubes/qubes.log <==
2018-03-13 15:59:05,389 Starting testing-debian
==> /var/log/libvirt/libxl/libxl-driver.log <==
2018-03-13 14:59:18.943+0000: libxl: libxl_device.c:1081:device_backend_callback: unable to add device with path /local/domain/7/backend/vif/18/0
2018-03-13 14:59:18.943+0000: libxl: libxl_create.c:1512:domcreate_attach_devices: unable to add nic devices
2018-03-13 14:59:29.006+0000: libxl: libxl_device.c:1081:device_backend_callback: unable to remove device with path /local/domain/7/backend/vif/18/0
2018-03-13 14:59:29.011+0000: libxl: libxl.c:1669:devices_destroy_cb: libxl__devices_destroy failed for 18
==> /var/log/qubes/qubes.log <==
2018-03-13 15:59:29,117 Start failed: internal error: libxenlight failed to create new domain 'testing-debian'
Therefore libxl_device.c:1081:device_backend_callback: unable to add device with path /local/domain/7/backend/vif/18/0 appeared 13 seconds after starting the VM and there were 10 seconds before libxl: libxl_device.c:1081:device_backend_callback: unable to remove device with path /local/domain/7/backend/vif/18/0.
fishilico
commented
Mar 13, 2018
|
I have posted the full logs of running
Therefore |
fishilico commentedMar 13, 2018
Qubes OS version: R4.0-rc5
Affected component(s):
Steps to reproduce the behavior:
Expected behavior:
personal AppVM runs with networking, without needed to reboot the computer.
Actual behavior:
personal AppVM runs without networking but fails to start with networking right after booting Qubes for the first time. This fails with both fedora-26 and debian-9 templates, and both PVH and HVM modes.
General notes:
Qube Manager shows the following message box when personal AppVM fails to start:
This log files contains:
By the way, /var/log/qubes/qubes.log contains:
I am not sure whether this warning is related with the issue.
Related issues: