Start failed: internal error: libxenlight failed to create new domain 'sys-net'

[entruevz]

Qubes OS version
4.0.1, 4.0.2-rc2.

Affected component(s) or functionality
PCI / VM sys-net.

Brief summary
The VM sys-net as well as sys-firewall and sys-whonix refuses to start, both at system startup and manually with Qubes Manager..

Actual behavior
The following message appears when I try to start the VM from Qubes manager:
Start failed: internal error: libxenlight failed to create new domain 'sys-net'.

Additional context
qvm-start told me to look at /var/log/libvirt/libxl/libxl-driver.log:

libxl: libxl_device.c:1385:libxl__wait_for_backend: Backend /local/domain/0/backend/pci/2/0 not ready
libxl: libxl_pci.c:1361:libxl__add_pcidevs: libxl_device_pci_add failed: -3
libxl: libxl_create.c:1512:domcreate_attach_devices: unable to add pci devices
libxl: libxl_device.c:1385:libxl__wait_for_backend: Backend /local/domain/0/backend/pci/2/0 not ready
libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop0: No such device or address
libxl: libxl_pci.c:1199:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.0
libxl: libxl_device.c:1385:libxl__wait_for_backend: Backend /local/domain/0/backend/pci/4/0 not ready
libxl: libxl_pci.c:1361:libxl__add_pcidevs: libxl_device_pci_add failed: -3
libxl: libxl_create.c:1512:domcreate_attach_devices: unable to add pci devices
libxl: libxl_pci.c:1199:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.0
libxl: libxl_device.c:1385:libxl__wait_for_backend: Backend /local/domain/0/backend/pci/4/0 not ready
libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop0: No such device or address
libxl: libxl_device.c:1385:libxl__wait_for_backend: Backend /local/domain/0/backend/pci/6/0 not ready
libxl: libxl_pci.c:1361:libxl__add_pcidevs: libxl_device_pci_add failed: -3
libxl: libxl_create.c:1512:domcreate_attach_devices: unable to add pci devices
libxl: libxl_device.c:1385:libxl__wait_for_backend: Backend /local/domain/0/backend/pci/6/0 not ready
libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop0: No such device or address

Laptop model and version: Librem 13 Version 4 (which is supposed to work with Qubes Os)
My wifi card model:
01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
With the stable version it worked 1 time out of 4, if the vm did not start I would restart the machine and the vm may or may not start. (and so I could use NetworkManager).
With the testing version it worked after installation but now even after about twenty restarts, sys-net refuses to launch.

Solutions you've tried
I tried the stable and testing version..
I changed the fedora template to debian

Related, non-duplicate issues
_
#3125 (VT-x is enabled..)
.

[marmarek]

Duplicate of #5445

[marmarek]

Specifically see there for a question for more logs.

[entruevz]

Strangely, after restarting my computer, sys-net started and I have access to the Internet.
After verification, 0000:00:14.0 and 0000:00:14.1 match my usb ports. The problem does not come from there because sys-usb starts without any problem

What can I provide you with as a log? I would really like to be able to use Qubes-Os every time I start my computer.

[entruevz]

[root@dom0 myusername]# systemctl status [email protected]

[email protected] - Start Qubes VM sys-net
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2019-11-06 23:16:34 CET; 13min ago
Process: 7191 ExecStart=/usr/bin/qvm-start --skip-if-running %i (code=exited, status=1/FAILURE)
Main PID: 7191 (code=exited, status=1/FAILURE)
[root@dom0 mylogin]# systemctl status [email protected]
Nov 06 23:16:09 dom0 systemd[1]: Starting Start Qubes VM sys-net...
Nov 06 23:16:34 dom0 qvm-start[7191]: Start failed: internal error: libxenlight failed to create new domain 'sys-net', see /var/log/libvirt/libxl/libxl-driver.log for details
Nov 06 23:16:34 dom0 systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Nov 06 23:16:34 dom0 systemd[1]: Failed to start Start Qubes VM sys-net.
Nov 06 23:16:34 dom0 systemd[1]: [email protected]: Unit entered failed state.
Nov 06 23:16:34 dom0 systemd[1]: [email protected]: Failed with result 'exit-code'.

[root@dom0 myusername]# journalctl -xe

-- Unit [email protected] has begun starting up.
Nov 06 23:16:09 dom0 qubesd[3433]: Starting sys-net
Nov 06 23:16:09 dom0 qmemman.systemstate[3430]: do_balloon(memsize=577765376)
Nov 06 23:16:09 dom0 qmemman.systemstate[3430]: xenfree=133937668
Nov 06 23:16:09 dom0 qmemman.daemon.algo[3430]: balloon: dom 0 has actual memory 8246001664
Nov 06 23:16:09 dom0 qmemman.daemon.algo[3430]: req=496256508 avail=6890988262.4 donors=[('0', 6890988262.4)]
Nov 06 23:16:09 dom0 qmemman.daemon.algo[3430]: borrow 521069333.4 from 0
Nov 06 23:16:09 dom0 qmemman.systemstate[3430]: memset_reqs=[('0', 7724932330)]
Nov 06 23:16:09 dom0 qmemman.systemstate[3430]: mem-set domain 0 to 7724932330
Nov 06 23:16:09 dom0 qmemman.systemstate[3430]: xenfree=448283609
Nov 06 23:16:09 dom0 qmemman.daemon.algo[3430]: balloon: dom 0 has actual memory 7931191296
Nov 06 23:16:09 dom0 qmemman.daemon.algo[3430]: req=181910567 avail=6576177894.4 donors=[('0', 6576177894.4)]
Nov 06 23:16:09 dom0 qmemman.daemon.algo[3430]: borrow 191006095.35 from 0
Nov 06 23:16:09 dom0 qmemman.systemstate[3430]: memset_reqs=[('0', 7740185200)]
Nov 06 23:16:09 dom0 qmemman.systemstate[3430]: mem-set domain 0 to 7740185200
Nov 06 23:16:09 dom0 qmemman.systemstate[3430]: xenfree=635834299
Nov 06 23:16:09 dom0 dmeventd[2537]: No longer monitoring thin pool qubes_dom0-pool00-tpool.
Nov 06 23:16:09 dom0 lvm[2537]: Monitoring thin pool qubes_dom0-pool00-tpool.
Nov 06 23:16:09 dom0 dmeventd[2537]: No longer monitoring thin pool qubes_dom0-pool00-tpool.
Nov 06 23:16:09 dom0 lvm[2537]: Monitoring thin pool qubes_dom0-pool00-tpool.
Nov 06 23:16:11 dom0 kernel: xen-blkback: backend/vbd/10/51712: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Nov 06 23:16:11 dom0 kernel: xen-blkback: backend/vbd/10/51728: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Nov 06 23:16:11 dom0 kernel: xen-blkback: backend/vbd/10/51744: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Nov 06 23:16:11 dom0 kernel: xen-blkback: backend/vbd/10/51760: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Nov 06 23:16:11 dom0 kernel: xen_pciback: vpci: 0000:01:00.0: assign to virtual slot 0
Nov 06 23:16:11 dom0 kernel: pciback 0000:01:00.0: registering for 10
Nov 06 23:16:32 dom0 libvirtd[3471]: 2019-11-06 22:16:32.197+0000: 3494: error : libxlDomainStart:1308 : internal error: libxenlight failed to create new domain 'sys-net'
Nov 06 23:16:32 dom0 qubesd[3433]: Start failed: internal error: libxenlight failed to create new domain 'sys-net'
Nov 06 23:16:32 dom0 dmeventd[2537]: No longer monitoring thin pool qubes_dom0-pool00-tpool.
Nov 06 23:16:33 dom0 lvm[2537]: Monitoring thin pool qubes_dom0-pool00-tpool.
Nov 06 23:16:33 dom0 dmeventd[2537]: No longer monitoring thin pool qubes_dom0-pool00-tpool.
Nov 06 23:16:34 dom0 lvm[2537]: Monitoring thin pool qubes_dom0-pool00-tpool.
Nov 06 23:16:34 dom0 qmemman.daemon.reqhandler[3430]: EOF
Nov 06 23:16:34 dom0 qvm-start[7191]: Start failed: internal error: libxenlight failed to create new domain 'sys-net', see /var/log/libvirt/libxl/libxl-driver.log for details
Nov 06 23:16:34 dom0 qmemman.daemon.algo[3430]: balance_when_enough_memory(xen_free_memory=583405499, total_mem_pref=1355013401.6, total_available_memory=6968577297.4)
Nov 06 23:16:34 dom0 qmemman.systemstate[3430]: stat: dom '0' act=7740185200 pref=1355013401.6 last_target=7740185200
Nov 06 23:16:34 dom0 qmemman.systemstate[3430]: stat: xenfree=635834299 memset_reqs=[('0', 8246001664)]
Nov 06 23:16:34 dom0 qmemman.systemstate[3430]: mem-set domain 0 to 8246001664
Nov 06 23:16:34 dom0 qmemman.daemon.algo[3430]: balance_when_enough_memory(xen_free_memory=73427234, total_mem_pref=1355013401.6, total_available_memory=6964415496.4)
Nov 06 23:16:34 dom0 qmemman.daemon.algo[3430]: balance_when_enough_memory(xen_free_memory=77637790, total_mem_pref=1355013401.6, total_available_memory=6968626052.4)
Nov 06 23:16:34 dom0 qmemman.daemon.algo[3430]: balance_when_enough_memory(xen_free_memory=77654042, total_mem_pref=1355013401.6, total_available_memory=6968642304.4)
Nov 06 23:16:34 dom0 systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Nov 06 23:16:34 dom0 systemd[1]: Failed to start Start Qubes VM sys-net.
-- Subject: Unit [email protected] has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[entruevz]

To be able to launch the sys-net vm, I had to disable all vms started at startup (including sys-net so sys-whonix, sys-firewall, and even sys-usb).
After unlocking my user session, I am able to run sys-net manually without getting this error message: "Domain sys-net has failed to start: internal error: libxenlight failed to create new domain 'sys-net".
Then simply create a script that launches the desired vms at startup.
I guarantee to provide the logs that may be necessary to understand and correct the problem.

[andrewdavidwong]

@entruevz, this issue has been closed as a duplicate of #5445. Please comment on that issue instead. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

[stman]

Well, with a MacBookPro Retina 15" mid-2012 (Macbookpro 10,1 - with EFI ROM : MBP101.00EE.B0B) I have the exact same problem as you do, the same logs.

I can't detach the USB controller in PCI 0000:00:14.0 that handles the two external USB Ports of the MacBookPro (There are 3 USB controllers listed in the macbookpro motherboard) from dom0 to attach it to my sys-usb qube and be able to handle networking thanks to this.

This is really terrible and raging.

I saw the other topic #5445 and no solution was found.

If you have a way to correct this small error, because it must be a very simple misconfiguration somewhere, please let me know because it is raging not to be able to make Qubes-OS run on this damned macbookpro just for this.