I have reports of various issues with 4.1.1 and latest updates,
These are issues with at least 5 reports:
Qubes running very hot - far hotter than 4.0
Qubes running with increased RAM usage - for example, on x220/230 I had dom0 maxed
at 1536M, service qubes at 3/400M, and could comfortably run 14+ qubes
in 16GB RAM.
Now I have had to push up dom0 allocation, push up per qube
allocation, can run far fewer qubes without interruption, and regularly
have qubes failing to start. I have reports from users who have not
customised memory allocation
Random freezes and hard crashes - these have been reported in the
Forum generally. Usually there is no relevant information in the
Randomly qubes fail to start.
Issues with sleep - sleep used to work flawlessly. If sys-net was
left running, network connections were re-established and the Qubes
network stack worked.
Now, sys-net will reconnect, but downstream netvms become unusable.
They provide no network access, and it is not possible to open a
terminal using qvm-run xterm - the command just hangs.
It is not possible to restart the qube - the logs contain only
"libvirtd: internal error: libxenlight failed to create new domain "
These issues affect machines with stock BIOS and coreboot, and some
I think that issue 5 is specific to kernel-latest.
I’d like to hear if you recognise any of these, and any thoughts on how
to proceed before raising issues at GitHub.
I recognise 2 and commented on upstream issues. Fedora consumes lot more ram then before and requires either switching to Debian or sys-net and sys-usb to have increased memory allocated otherwise camera and wifi stops working. This is changed in OEM disk image which is probably why less reports on privacybeast but issues is known and commented on reports for camera, sys-net having drivers faults and loss of networking
Relevant Qubes issue linking to specific forum discussions:
I recognize 4 for 1/3 of sys-usb boot when usb thumb drives are connected prior of sys-usb booting. sys-usb sometimes down in resume as well, or not started on boot when thumb drives connected…
5 is known, diagnosed the problem with @adrelanos. Linked to tsc and xen, time keeping and suspend/resume mishandling. Poked @demi for pull request to produce package to test into unstable. (unrelated with tor bug on resume from suspend though, which can be experienced for anybody suspending for a long time and sdwdate reporting timeout).
I can only report a similar issue that affected me for a month or so (but seems to have been resolved), namely that after a reboot, sys-net wouldn’t actually work to provide networking until I restarted it about 2 minutes in. But no hangs, refusal to reboot the vm. My guess is that this was due to a kernel issue, as we’ve not seen many other updates aside from all of the xen vuln patches (but most of those came later, iirc).
Can’t comment on the heat issue though I don’t think I have heard my fans spin up (but hard to tell since it’s a pretty silent fan on a large cooling block) and I just allocate 4gb to dom0.