Cannot start sys-net after dom0 update (current-testing)

[AhmedAA]

Qubes OS version:

4 RC3

Affected TemplateVMs:

No template affected, only sys-net appvm

---

Steps to reproduce the behavior:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
Should update qubes-core-dom0 (I got the update yesterday 18/01/2018 in the evening, around 21:00, perhaps later)

Expected behavior:

sys-net can start normally

Actual behavior:

sys-net cannot start, and I get the following error message: Not enough memory to start domain 'sys-net'

General notes:

This ONLY seems to affect sys-net. I can start my fedora-26 template, which sys-net is based on, and even fire up a gnome-terminal.
I can also start my debian template which also works fine. I only seem to get the error with sys-net.

As a general note:
sys-net and sys-firewall did not autostart since my install, I don't know why, I always had to run a qvm-start sys-firewall on login to get network. If I check journalctl --boot I can see that Qubes fails on starting sys-net on boot due to lack of memory, but I never had issues starting it manually after login.
After my update yesterday, it seems to be completely broken.

---

Related issues:

Maybe this: #3462

[AhmedAA]

I fixed this issue with the help of awokd and Tom Zander over on the qubes-users list, but to cut it short:

qvm-prefs sys-net maxmem 1

qvm-prefs sys-net memory 800

fixed the issue.. I have no idea why this happened, and some insight would be cool :S

All my VM's are in HVM mode, dom0 is provided with 4GB of RAM (out of a total of 8GB). According to the system monitor tools (htop and xentop) stated that I had ~3.8GB RAM to use.

This obviously leads me to the conclusion that it wasn't a question of memory, but something else. If anyone can make me smarter, I would appreciate it :)

[AhmedAA]

I fixed this issue with the help of awokd and Tom Zander over on the qubes-users list, but to cut it short:

qvm-prefs sys-net maxmem 1

qvm-prefs sys-net memory 800

fixed the issue.. I have no idea why this happened, and some insight would be cool :S

All my VM's are in HVM mode, dom0 is provided with 4GB of RAM (out of a total of 8GB). According to the system monitor tools (htop and xentop) stated that I had ~3.8GB RAM to use.

This obviously leads me to the conclusion that it wasn't a question of memory, but something else. If anyone can make me smarter, I would appreciate it :)

[marmarek]

What version of qubes-core-dom0 do you have?

[marmarek]

What version of qubes-core-dom0 do you have?

[AhmedAA]

@marmarek

After getting network I updated immediately, so I have the newest version from current-testing now.
Can I list previously installed packages somehow?

[AhmedAA]

@marmarek

After getting network I updated immediately, so I have the newest version from current-testing now.
Can I list previously installed packages somehow?

[marmarek]

See sudo dnf history, then sudo dnf history info <transaction number>

[marmarek]

See sudo dnf history, then sudo dnf history info <transaction number>

[AhmedAA]

Okay!

I had version 4.0.16-1 after my update yesterday that broke sys-net.

Now I have version 4.0.18-1

[AhmedAA]

Okay!

I had version 4.0.16-1 after my update yesterday that broke sys-net.

Now I have version 4.0.18-1

[marmarek]

Ok, so this was a broken qmemman in 4.0.16, which is fixed in 4.0.18.

[marmarek]

Ok, so this was a broken qmemman in 4.0.16, which is fixed in 4.0.18.