Hi, and thanks for the followup. Both Tails 4.4 and 4.3
virt-manager VM sessions freeze/seize in place. They become
completely unresponsive no matter how long you wait, and regardless
of how they are installed/run (i.e., by either CD or USB). Nothing
can be done within the Tails virtual machine session/interface once
they seize up. This leaves only virt-manager's shutdown menu
commands viable for reclaiming the system RAM previously dedicated
to the stalled Tails session.
This seizing up problem only began happening with the
introduction of Tails ver. 4.3; and now it happens with 4.4 as
well. I've downgraded back to ver. 4.2, since it won't upgrade to
ver. 4.2.2., which was the last best-performing Tails version in a
virt-manager VM session (which runs in my continuously-upgrading
Parrot 4.8 Linux host OS). Meanwhile, all Debian upgrades to
the Parrot host OS function flawlessly under proper conditions, so
it's definitely the changes made only to the Tails distro since ver.
4.3 that cause the VM sessions to freeze/seize up in my Hewlett-Packard
Elitebook machine with 12 Gb of RAM.
intrigeri wrote on 03/18/2020 04:33 AM:
Hi,
Terry Gruzebeck (2020-02-18):
Even if I don't modify Tails beyond setting an OBFS4 custom network bridge, unfortunately, version 4.3 locks up in the Virt-Manager USB installation described below. The
host system is a fully-upgraded Parrot Linux 4.7 Debian 10 OS. I've tried 4.3 only as a SCSI-CD install, too, to no avail. Allocating more RAM only delays the inevitable seizing
up. Ver. 4.2.2 works flawlessly under these same circumstances.
Could you please describe the lock up you're experiencing?
Hoping you can fix this for the next version release. During the
meanwhile, are there any ver. 4.2.2 security upgrades I can do
through either the Synaptic Package Manager or a terminal?
No, unfortunately:
https://tails.boum.org/support/faq/#upgrade
Cheers,
