Of course it is possible. Just create 2 sys-net qubes, for example: sys-net-home and sys-net-work, attach respective device to each, and set correspondent netVM to personal and work qube.
This is all what Qubes exactly is for.
Note that you will have to make sure each qube has the correct network qube set, individually.
Watch out, though, for updates. Without the correct settings, if there’s no qube named sys-net or sys-firewall, they will be automatically re-created when you do an update. The new sys-net qube will probably try to take control of all of your network devices, causing a lot of problems.
For several months I did as tempmail suggested, but had to leave my home wifi qubes named sys-net and sys-firewall so that this wouldn’t happen. Then I changed something to fix that. I tried to figure out how I set this not to happen, but couldn’t make sense out of what I saw on my system.
I am not aware of any automatic sys-net or sys-usb recreating. It is true that in Global settings and in 90-default.policy and other correspondent RPC policies, entries should be updated following qubes name change.
Start failed: Requested operation is not valid: PCI device 0000:00:14.3 is in use by driver xenlight, domain sys-net, see /var/log/libvirt/libxl/
libxl-driver.log for details
I interpret that error message as: the qube you’re trying to start (presumably sys-net-usb?) cannot be started because you’ve assigned PCI device 0000:00:14.3 to it, and that PCI device is currently in use by sys-net.
Yes, @gonzalo-bulnes ! You are right about the interpretation of the erro message. Everything proposed by you works, except the fact that sys-net and sys-net-usb can’t Start and keep running at same time.
On sys-net-usb I must remove (dettach) PCI device 0000:00:14.3 (that is my PCI Wifi Card) and add (attach) USB Wifi Dongle.
But I couldn’t run this test yet, because of errors below:
[root@dom0 lstavares84]# qvm-pci d sys-net-usb dom0:00:14.3
Traceback (most recent call last):
File "/usr/bin/qvm-pci", line 5, in <module>
File "/usr/lib/python3.8/site-packages/qubesadmin/tools/qvm_device.py", line 291, in main
args = parser.parse_args(args, app=app)
File "/usr/lib/python3.8/site-packages/qubesadmin/tools/__init__.py", line 411, in parse_args
File "/usr/lib/python3.8/site-packages/qubesadmin/tools/qvm_device.py", line 200, in parse_qubes_app
dev = vm.devices[devclass][device_id]
File "/usr/lib/python3.8/site-packages/qubesadmin/devices.py", line 282, in __getitem__
for dev in self.available():
File "/usr/lib/python3.8/site-packages/qubesadmin/devices.py", line 235, in available
File "/usr/lib/python3.8/site-packages/qubesadmin/base.py", line 76, in qubesd_call
return self.app.qubesd_call(dest, method, arg, payload,
File "/usr/lib/python3.8/site-packages/qubesadmin/app.py", line 765, in qubesd_call
File "/usr/lib/python3.8/site-packages/qubesadmin/base.py", line 89, in _parse_qubesd_response
qubesadmin.exc.QubesDaemonAccessError: Got empty response from qubesd. See journalctl in dom0 for details.
qvm-pci d sys-net-usb 00:14.3
qvm-pci: error: no backend vm '00'
qvm-pci d sys-net-usb 0000:00:14.3
qvm-pci: error: no backend vm '0000'
Sadly I have no idea how PCI device are named, and don’t know what the BACKEND is supposed to look like in this case. I would have tried the same things you’ve tried. I take note that dom0:00:14.3 seems to progress further!
@disp6252’s suggestion is a lot more promising than anything I can think of at this point. It seems like the issue linked in their post does indeed match closely the error printed by:
Clone “sys-net” AND “sys-firewall” and give them the name that you want like “sys-net-clone”;
Open the Settings of “sys-net-clone” and go to Devices TAB*
*If Device Tab is disable (aka GRAY OUT or GRAYED OUT), shutdown your notebook, go to BIOS and check if VMD is enable (check image below). Change this config for another one that do not to reinstall QOS
Remove Wifi PCI Card from “sys-net-clone”
In Qube Manager change the Network of sys-firewall-clone from sys-net to sys-net-clone;
Change the Network of qubes (VMs) that you and to use the USB Wifi from sys-firewall to sys-firewall-clone