Hi,
Can anyone explain why sys-usb (a non-networked VM) shows as NetVM?
user@sys-usb:~ > qubesdb-read /qubes-vm-type
NetVM
Hi,
Can anyone explain why sys-usb (a non-networked VM) shows as NetVM?
user@sys-usb:~ > qubesdb-read /qubes-vm-type
NetVM
No other VM is configured as its netvm, and provides_network is enabled (for use with a USB network adapter). That’s what makes dom0 set /qubes-vm-type to NetVM:
Before Qubes OS R4, VM types were more rigid and /qubes-vm-type basically tells you what class of VM it would have been back then. It’s still used by startup scripts inside the VM to enable some services by default:
Thanks @rustybird
I am confused by the fact that during installation I was asked whether I want sys-usb to be used as a NetVM and I explicitly refused. After your reply, I had a look and “Provides network” was checked. After unchecking it hows as AppVM.
I wonder if that means it is a bug.
What do you think?
I don’t remember such a question. Do you mean the installer’s “Use sys-net qube for both networking and USB devices” checkbox?
Enabling “Provides network” unconditionally for sys-usb is intentional:
Do you mean the installer’s Use sys-net qube for both networking and USB devices checkbox?
Exactly.
Thanks for the link!
There is a bug in r4.2 that service vm feature is not persistent and to make qube be a service qube you need to enable provides network. That’s why that is in sys-audio guide.
Dunno about r4.3
I unset the “Provides network” and after restarting the VM it is AppVM. I guess this means persistence.
In r4.2, if you set just qvm-features sys-audio servicevm 1 then after restart is not set and sys-audio is seen as normal appVM.
If you set provides network then after restart sys-audio is seen as serviceVM and feature servicevm is set.
That’s probably why in r4.2 sys-usb have provides network even if you opted that out.
As I said dunno about r4.3, so unset provides network and do qvm-features sys-usb servicevm 1 in dom0 and test if sys-usb will be still serviceVM after restart.
I see no such feature of sys-usb in 4.3.0. I see it for sys-net and sys-firewall. I don’t know if it was there before unsetting “Provides network”.
What is the purpose of this feature?
To mark qube as service qube.
To mark qube as service qube.
What is a “service qube” and how is it different from a non-service qube. I might be missing something that I need to learn.
P.S. I am just wondering if the flag “service qube” has any other function besides how qubes are filtered in Qube Manager. Currently I am running a sys-usb qube that is not a “service qube” and I don’t see any issues.
https://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-service.html
Changes the qube icon to ServiceVM theme and moves the qube to
SERVICEtab of Qubes
That is all I see…
Thanks.
So, it seems just another flag, similar to the “disposable template”, aimed to serve cosmetic purposes in the UI.
This setting is enabled by default during installation to support users who may connect USB Wi-Fi or Ethernet adapters to sys-usb . This is not Bug.