Loading tsa/howto/upgrades.mdwn +14 −14 Original line number Diff line number Diff line Loading @@ -29,18 +29,18 @@ this: WARNING: Kernel needs upgrade [linux-image-4.9.0-9-amd64 != linux-image-4.9.0-8-amd64] If this is only a virtual machine, and the only one affected, it can be rebooted directly. If it has an encrypted filesystem and is hooked up with Mandos, it will return automatically. Otherwise it might need a password to be entered at boot time, either through the initramfs (if it has the `profile::fde` class in Puppet) or manually, after the boot. Generally, KVM hosts are the latter and need special attention, as the guests need to be individually rebooted. The `tor-libvirt-reboot` takes care of the hand-holding necessary here. When the server returns, the encrypted partitions need to be unlocked as well, with the `tor-libvirt-luks-start` command. A full reboot procedure will look something like this: be rebooted directly. If the host has an encrypted filesystem and is hooked up with Mandos, it will return automatically. Otherwise it might need a password to be entered at boot time, either through the initramfs (if it has the `profile::fde` class in Puppet) or manually, after the boot. Generally, KVM hosts are the latter case and need special attention, as the guests need to be individually rebooted. The `tor-libvirt-reboot` takes care of the hand-holding necessary here. When the server returns, the encrypted partitions need to be unlocked as well, with the `tor-libvirt-luks-start` command. A full reboot procedure will look something like this: host=unifolium.torproject.org ssh -tt root@$host tor-libvirt-reboot && Loading Loading
tsa/howto/upgrades.mdwn +14 −14 Original line number Diff line number Diff line Loading @@ -29,18 +29,18 @@ this: WARNING: Kernel needs upgrade [linux-image-4.9.0-9-amd64 != linux-image-4.9.0-8-amd64] If this is only a virtual machine, and the only one affected, it can be rebooted directly. If it has an encrypted filesystem and is hooked up with Mandos, it will return automatically. Otherwise it might need a password to be entered at boot time, either through the initramfs (if it has the `profile::fde` class in Puppet) or manually, after the boot. Generally, KVM hosts are the latter and need special attention, as the guests need to be individually rebooted. The `tor-libvirt-reboot` takes care of the hand-holding necessary here. When the server returns, the encrypted partitions need to be unlocked as well, with the `tor-libvirt-luks-start` command. A full reboot procedure will look something like this: be rebooted directly. If the host has an encrypted filesystem and is hooked up with Mandos, it will return automatically. Otherwise it might need a password to be entered at boot time, either through the initramfs (if it has the `profile::fde` class in Puppet) or manually, after the boot. Generally, KVM hosts are the latter case and need special attention, as the guests need to be individually rebooted. The `tor-libvirt-reboot` takes care of the hand-holding necessary here. When the server returns, the encrypted partitions need to be unlocked as well, with the `tor-libvirt-luks-start` command. A full reboot procedure will look something like this: host=unifolium.torproject.org ssh -tt root@$host tor-libvirt-reboot && Loading