Git-Mirrors/Qubes-Community-Content
1
0
Fork 0
mirror of https://github.com/Qubes-Community/Contents.git synced 2024-12-22 13:55:08 -05:00
Code Issues Packages Projects Releases Wiki Activity

usability edits

Browse Source
This commit is contained in:
awokd 2018-06-17 14:13:57 +00:00 committed by GitHub
parent a2a982f736
commit 048541908f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/system/restore-3.2.md
View File

@ -2,15 +2,15 @@ Restoring R3.2 Templates/Standalones To R4.0
=========================================================== ===========================================================
Although restoring R3.2 AppVMs to R4.0 generally works with no problem, there are additional steps that need to be performed when doing the same with Templates and Standalone VMs. Although restoring R3.2 AppVMs to R4.0 generally works with no problem, there are additional steps that need to be performed when doing the same with Templates and Standalone VMs.
If these steps are not done, the result is an inability to start programs in the restored VM. If these steps are not done, the result is an inability to start programs from the Qubes menu for the restored VM.
1. After restoring your Template or StandaloneVM, go to Qube Settings -> Basic tab. 1. After restoring your Template or StandaloneVM, go to Qube Settings -> Basic tab.
Confirm Networking is set to one valid for your R4.0 system. Confirm Networking is set to one valid for your R4.0 system.
Then, under the Advanced tab, confirm Virtualization Mode is `PVH`, and that Kernel is set to `default`. Then, under the Advanced tab, confirm Virtualization Mode is `PVH`, and that Kernel is set to `default`.
2. From a dom0 prompt, enter `qvm-run <templatename> gnome-terminal`. 2. From a dom0 prompt, enter `qvm-run <templatename> gnome-terminal` (or `xterm` if `gnome-terminal` is not installed).
3. Once the terminal window comes up, open another terminal window to a known good R4.0 template. 3. Once the terminal window comes up, open another terminal window to a known good R4.0 template.
4. From the known good template's terminal, `qvm-copy /etc/yum.repos.d/qubes-r4.repo` to the restored template. 4. From the known good template's terminal, `qvm-copy /etc/yum.repos.d/qubes-r4.repo` to the restored template.
5. Do the same with `qvm-copy /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4-{stable,unstable}`. 5. Do the same with `qvm-copy /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4-*`.
6. On the restored template's terminal, `cd` into the `QubesIncoming` subfolder that contains the files you copied over from the known good R4.0 template, then in `su` mode: 6. On the restored template's terminal, `cd` into the `QubesIncoming` subfolder that contains the files you copied over from the known good R4.0 template, then in `su` mode:
~~~ ~~~