Can't Start Network, V4

[Ray Joseph]

I have installed Qubes on a Toshiba laptop with wirless only. When attempting to start sys-net from Qube Manager, an error is emitted:
Domain sys-net has failed to start: internal error: Unable to reset PCI device 000:00:14.0: Internal error:
libxenlight failed to create new domain 'sys-net'.

lpsci reports the Network controller correctly.

All items in (Dom0) Editing Wi-Fi connection 1 are greyed out and unresponsive.

A previous message said to look at the logs in
/var/lob/libvirt/...
but when I attempt to open libvirt, I get a permission denied error. I have tried sudo but get the same result.

I would appreciate any suggestions, thank you.

[awokd]

Ray Joseph wrote on 3/25/19 11:20 PM:

You do have to do it with sudo. In dom0, you are trying "sudo ls
/var/log/libvirt/libxl"?

[unman]

Read www.qubes-os.org/doc/assigning-devices particularly the section on
PCI passthrough issues.
These features can now be accessed in the QubeManager GUI - look at the
Devices tab for sys-net Settings, and the "Configure Strict Reset"
button.

[Ray Joseph]

awokd,

> You do have to do it with sudo. In dom0, you are trying "sudo ls
> /var/log/libvirt/libxl"?

Thank you. I tried that and it did not work. You brought me back and now its working.

[Ray Joseph]

unman

Thank you for the trip through the qube. Currently, sys-net is still not working. I have tried both strict and not. And I have rebooted also rebooted after the change.

What looks odd is under sys-net device, the wireless card number is 02:00.0 and reports my card. The error message states 00:14.0 which is called out in the device as USB controller.

This appears to mean it is trying to use the USB for the network IF.

Any suggestions?

[unman]

I recall using an Acer where to get the wifi working I had to add the
card-reader to sys-net also.
Try adding 00:14.0 to sys-net, and then set no-strict on that device
too.

[Ray Joseph]

unman,

Thank you.

On opening sys-net, there were two USB controllers already attached, one was 00:14.0. So I removed both and added the nic. Sys-net is now running.

So I now want to test it. I thought I could just open a vm such as debian, but I found it says it can't have networking. Further reading said networking can be enabled in the Basic tab. I am guessing sys-firewall should be the choice. Then connect with Tor.

Bootstrap phase stuck on 5% (10 minutes before I stopped it). There is only one AP and it is open (out of my control).

Any suggestions on progressing?

[awokd]

Ray Joseph wrote on 4/5/19 3:37 AM:

Skip Tor for now and verify you have network connectivity with a
standard browser & AppVM like "Work". You can't browse from templates.

[Ray Joseph]

Thank you. It is great to learn where/what I need to read.

[Ray Joseph]

I would like to config sys-net to access my wireless AP. I have not found a method to config the network. I looked for /etc/network/interface to see if anything was there but the network folder does not exist.

I found suggestions that I could get to them via sys-net settings. I have added 'settings' to the vm through Qube Manager. But when I go to
Service: sysnet, sys-net:Settings shows up. But when I click on it, nothing happens.

How do I define my AP connections?

[unman]

You can configure your networking from the nm-applet: there's nothing Qubes
specific in that.
When you start sys-net you should see the applet opening in the panel.
If you don't see that, then open a terminal in sys-net and run nm-applet.

If you don't see the wifi in the applet, then it's possible that you
don't have the right drivers for your wifi device. Again, there's nothing
Qubes specific in this - run 'journalctl -b' and look for any references
to the wifi NIC - you may see a pointer to missing firmware.

[Ray Joseph]

Thank you for your support. I don't know what 'panel' I should see the nm-applet opening in. I opened a terminal in sys-net and entered nm-applet and obtained a response that said it was not meant to run in terminal and to use NetworkManager in the desktop. I don't see a way to open a desktop in sys-net.

BTW, my little Linux background is Debian and almost all of it was at the command line using /etc/network/interfaces. My intent was to use Debian to run Xen. But I was not able to find a way to get Debian/Xen to use wireless. Qubes doesn't have this problem, if I can just discover how.

[haaber]

On 4/9/19 12:58 PM, Ray Joseph wrote:
> Thank you for your support. I don't know what 'panel' I should see the nm-applet opening in. I opened a terminal in sys-net and entered nm-applet and obtained a response that said it was not meant to run in terminal and to use NetworkManager in the desktop. I don't see a way to open a desktop in sys-net.

If NM works you see it in the upper right corner, see attached image. Be
sure that all needed packages are in your sys-net: firmware, but also
the qubes-core-agent-networkmanager and qubes-core-agent-networking
that you simply install in the TEMPLATE used for sys-net with apt-get as
usual.