Error:volume qubes_dom0 / vm-sys-net-private missing

[higgin...@gmail.com]

Help!!!!!! When I login - everything seems to be fine (albeit quicker boot) . Standard menus available, qubes manager etc but no VM starts. If I try to start a VM via qubes manager, I get the above message. Grateful for any suggestion. If all else fails - is there any way to get my data off system - did a lot of work yesterday, that I don’t want to lose.

[higgin...@gmail.com]

Managed to get all my data. Had to disable networking on each VM - could then start VM, attach USB stick - and copy data to there.

Cant get system working however. Can't get sys-net or sys-firewall started.
Likewise with VM's (unless networking stopped).

Any thoughts - or am I looking at another full reinstall?

Cheers

[awokd]

Would be good to know why it vanished, but you could try to manually
create a new sys-net, point the right Qubes to it, and delete the old one.

[higgin...@gmail.com]

Did a hard shutdown (probably shouldn't have -but have done it before and that was OK).
Have found another thread somewhere where someone else had same issue as result of same action.

How do I create a sys-net? (Am ok with VM's ordinary and standalone plus VM templates) - but not sure with sys-net (and sys-firewall).
Thanks.

[awokd]

Create a regular AppVM but check the "provides networking" box. Then,
assign your NIC(s) to it in the Devices tab. Point sys-firewall and any
others you had set to use sys-net to point to your new one. Same with
qubes-prefs- by default it's your clockvm. Before rebooting, test to make
sure everything works on your new sys-net, then delete the old one.

[higgin...@gmail.com]

Thanks for speedy reply. Had a long day walking in the Lakes - so a bit tired.
Will try in the morning!
Cheers.

[higgin...@gmail.com]

So I create a regular AppVM and check the "provides networking" tab.

THEN USING QUBE MANAGER - I "select" my ethernet controller (this is the only one "selected" in my faulty "sys-net"- likewise with my Qubes 3.2 on old computer).

Once selected (before applying it) I get message highlighted "YOU'VE ENABLED DYNAMIC MEMORY BALANCING - SOME DEVICES MIGHT NOT WORK".

If I then try and apply it - I get message "Can't attach PCI device to VM in ph mode.

I don't know what "ph mode" means or whether to be concerned about the other warning message.

Should I be concerned?

THE QUBES DOCS GUIDE has section entitled "ASSIGNING DEVICES TO VM's". The small section for QUBES4.0 seems straightforward. If I follow this - would it overcome warning notices as per above when assigning via QUBES MANAGER?

[awokd]

On Sun, June 24, 2018 10:44 am, higgin...@gmail.com wrote:
> So I create a regular AppVM and check the "provides networking" tab.
>
> THEN USING QUBE MANAGER - I "select" my ethernet controller (this is the
> only one "selected" in my faulty "sys-net"- likewise with my Qubes 3.2 on
> old computer).
>
> Once selected (before applying it) I get message highlighted "YOU'VE
> ENABLED DYNAMIC MEMORY BALANCING - SOME DEVICES MIGHT NOT WORK".

On the Advanced tab, uncheck memory balancing and set virt. mode to HVM
before assigning the device.

[higgin...@gmail.com]

Brilliant!!!!!!!!!!

System fully functional again - and I've learned a bit more on the way.

Thanks again (and for previous support).

[higgin...@gmail.com]

Just a footnote for anyone else with this problem ---

Worth a look at /etc/qubes-rpc/policy/qubes.UpdatesProxy

This file has a reference to "sys-net" as target for TemplateVM.

If you add a new "sys-net" and give it a new name - you will have to update the above file reference (i.e from "sys-net" to "newname") to facilitate Fedora Template updates.
I didn't initially and kept getting "Error:failed to synchronize cache for repo "updates" when trying to update Fedora template".

[brenda...@gmail.com]

On Thursday, July 26, 2018 at 2:13:49 PM UTC-4, higgin...@gmail.com wrote:
> Just a footnote for anyone else with this problem ---
>
> Worth a look at /etc/qubes-rpc/policy/qubes.UpdatesProxy
>
> This file has a reference to "sys-net" as target for TemplateVM.

Hmm, my recollection was that sys-firewall was used for this purpose. Has this config changed in 4.0?

B