Hi gang,
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.
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?
Terry
On 11/01/2019 04:53 AM, intrigeri
wrote:
Hi,
sajolida:
You're right, we're missing proper instructions to do a manual upgrade
of a virt-manager installation with a Persistence. I should fix this.
Now tracked with
https://redmine.tails.boum.org/code/issues/17187.
I'm not a user a virt-manager myself and I know that some of us do use
it with a Persistence. It would save me quite a lot of time if they gave
me a synopsis of how they do their manual upgrades :)
segfault, intrigeri: How do you do that? Do you start the VM on an ISO
image plugged as a DVD and use it to do the upgrade? Something else?
Essentially yes, but some extra steps are needed to ensure one actually
starts from that virtual DVD:
1. In "Boot Options", ensure the DVD is listed first (or select
"Enable boot menu" and then you can pick the boot device when
starting the VM).
2. To tell live-boot to use the SquashFS from the DVD, add this boot
option:
live-media=/dev/sr0
This works for a "SCSI CDROM" device. If the virtual DVD reader is
plugged into the SATA bus instead, the /dev/sr0 path might need to
be adjusted.
And then yes, I use Tails Installer to clone the running system and
upgrade the Tails system that's on the virtual USB drive.
Cheers,
