You’re probably seeing this error not for your personal VM but for sys-net VM. So check the Devices tab in Qubes Settings for sys-net.
If your personal VM has sys-net as networking VM (or sys-firewall as networking VM and sys-firewall has sys-net as networking VM) and sys-net is not running when you’re starting personal VM then QubesOS will first start its networking VM sys-net.
OK - the problem is not with creating the personal qube, but in
starting it.
If you set the netvm to none (Settings->Basic->“Net qube”), are you able
to start firefox then?
If so, then the issue lies with the netvm , probably sys-firewall, or
sys-net.
See if you can start either of them, and check the Devices allocated
to them.
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.
I set the NetVM to none, in the Qubes:personal settings and i could start the VM with Firefox.
The sys-firewall settings has netVM set to sys-net.
And sys- net has netVM set to none.
The sys-net Settings-> Devices tab has the 01:00_0 Unknown device in the Selected box on the right. I believe this unknown device is causing the errors.
When I unselected the unknown device, I was able to get my personal:Firefox qubes to start !
My next step is to connect this VM to the sys-usb so i can get access to my local home network.