Sys-net not working: Hostdev already exists in the domain configuration

User Support General
1

hello guys, i need help with qubes os:

everything was working just fine, then i took my drive with qubes and put it in a second computer and when i started it in the second computer two vms only started which were dom0 and sys-usb.

now i put it back in the first computer and it still doesnt work.

now when i try to start sys-net manually there pops up:

start failed: XML error: Hostdev already exists in the domain configuration, see /var/log/libvirt/libxl-driver.log

now in the log there is:

libxl: libxl_pci.c:1590:libxl__device_pci_reset: The kernel doesn’t support reset from sysfs for PCI device 0000:00:14.0

and

libxl: libxl_event.c:855:libxl__ev_xswatch_deregister: remove watch for path @releaseDomain: Wrong file descriptor

please help guys what should i do

2

You need to enable the no-strict-reset option for the wifi card. Open the sys-net settings > devices. At the bottom, there will be a button that says configure strict reset for pci devices. Click it then click your card and then click ok. Click apply, then close the settings window. You should be able to start sys-net now.

3

Note that:

This may leak usage data even without malicious intent!

1 Like
4

but here is the problem:

the device stated in the error is on the left side in devices, so its not used by the vm sys-net

maybe i should reinstall?

5

That’s really weird. Reinstalling might be the best option.

6

I’m not an expert but, could you try to run qvm-pci in a terminal in dom0?

7

i ran qvm-pci

the problematic device is only attached to sys-usb and its no-strict-reset=True

is there and option to reinstall but without loosing my data?

8

Not really but you can use Qubes backup to achieve something similar except for some dom0 files.

If you want help on this matter, you need to provide the output and context. Is the device attached to sys-net also attaches to sys-usb?

9

no, the device is only attached to sys-usb, its an intel usb controller, there is no more errors including other devices besides that one, i think there is an unexplainable unfixable internal error, which may have happened after i tried to run the os on another computer, and it is persisting on the system, i think my only option to not lose data is backing up vms to a pendrive, reinstalling the system and restoring the vms. what do you think?

also the information about no strict reset true is the only output i got regarding that device.