On 7/14/20 9:57 PM, Qubes wrote:
I installed a clean Fedora-32 template today, but I have some issues and
I am not sure where to start.
After installing the F-32 template I switched the default-mgmt-dvm qube
to use the F-32 template.
I then created a new qube basing it on the F-32 template,
test-fedora-32-template, just to check that everything is working ok on
this test vm before changing all of my F-31 based qubes over to F-32.
I am unable to boot the test-fedora-32-template qube. After a while I
receive a system notification, the ones that pop up top right of the
screen, saying,
'Cannot connect to qrexec agent for 60 seconds, see
/var/log/xen/console/guest-test-fedora-32-template.log for details'
and if I look in the log file I see hundreds of messages like this...
'.....Failed to fork() worker: Cannot allocate memory'
'.....systemd-udevd[272]: xvdc1: Failed to process device, ignoring: No
space left on device'
'.....eth0: Failed to process device, ignoring: No space left on device'
The F-32 template itself starts up without any problems.
The problem described above definitely has something to do with the f-32
specifically.
Even after changing my test qube to the f-31 template and starting it
the qube still refuses to boot and gives me the same issues in
/var/log/xen/console/guest-test-fedora-32-template.log.
However, if I create a new qube based on my f-31 template then
everything works as expected.
The after effect of this is also, because I changed my default-mgmt-dvm
to the f-32 template, in order to update the f-32 template, which
subsequently failed because machines based on the f-32 template don't
work, my default-mgmt-dvm is also bust. I guess I can recreate it, but
that still does not solve my f-32 problems.
AND, all of these issues started when I accidentally interrupted the
f-32-minimal template installation as I described in a previous email to
this group 'Template Installation Problem'.
In the meantime I have managed to get the minimal template installed
using the --action=reinstall option as described in the documentation.
'sudo qubes-dom0-update --action=reinstall qubes-template-fedora-32-minimal'
Following on from my previous email I also had to reinstall the f-32
template because it gave the same issues I I describe here now. I hoped
that reinstalling the template would fix the issues, but they appear
deeper than the template.
I really hoped I would be able to fix this without having to resort to
using a full system backup and starting from 'scratch'.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/3c1d6618-ba7a-2854-2be6-eb3eb7e48c91%40ak47.co.za.
