I'm trying to install Qubes 3.2 on a Thinkpad T450s (i7), which is listed on the hardware compatibility list as being generally successful with both releases 3.1 and 3.2.
I have had to use the UEFI Lenovo workaround documented at https://www.qubes-os.org/doc/uefi-troubleshooting/ so my install process has been as follows: - dd write a checksum and signature verified Qubes-R3.2-x86_64.iso to a 32GB USB drive - Enable legacy boot in the Thinkpad BIOS - Boot from the USB drive - Select "Troubleshooting" > "Boot from local disk" to enter secondary GRUB menu - Highlight the "Verify and Install" option and press 'e' - Add '/mapbs /noexitboot' to the 'chainloader' GRUB line - Press ctrl-x to boot with modified config - See successful verification of the USB drive contents and launch of Qubes 3.2 installer - Secondarily verify the install media from the "Installation Source" GUI panel - Configure install destination to "reclaim all space" by deleting the existing partitions and use the automatic paritioning - Begin the install About halfway through the progress bar, the status reads: "Installing qubes-template-fedora-23.noarch (800/930)" Switching to tty-1 with ctrl-alt-f1 shows the error message: "Error unpacking rpm package qubes-fedora-23-3.0.6-201608081228.noarch" If left along for long enough, this rpm task seems to error out completely and get skipped over to finish the rest of the installation. I then add the documented UEFI workaround to /mnt/sysimage/boot/efi/EFI/qubes/xen.cfg. After rebooting into the Qubes install, asking the Configuration helper to set up the default system qubes (sys-net, sys-firewall) fails with an alert message: [Dom0] Error ['/usr/bin/qubes-prefs'. '--set', 'default-template', 'fedora-23'] failed: stdout: "" stderr: "A VM with the name 'fedora-23' does not exist in the system." I'm confused about why such a specific package would consistently fail to install from good installation media over multiple install runs on my laptop. I've now tried with two different USB drives and ISO files from different sources. When running the installed Qubes, manually adding the package to dom0 with: sudo yum install /run/media/<user>/Qubes-R3.2-x86_64/Packages/q/qubes-template-fedora-23-3.0.6-201608081228.noarch.rpm installs successfully and provides the fedora-23 vm template in the VM Manager, from which I'm able to create a new NetVM and connect to a wired network. So that's all working, once it's in place. I would very much like to have the default sys-net and sys-firewall qubes. The way I see it, there are two semi-automated ways to get them: 1) Re-run the firstboot qubes-anaconda-addon now that the fedora-23 vm template is installed. 2) Re-install again, manually adding the qubes-template-fedora-23 package before the reboot so that it's available for the normal firstboot process. [Implicit option 3) Figure out and manually type the sys-net and sys-firewall creation commands by picking through the qubes-anaconda-addon source.] Any helpful hints come to mind? Thanks, Evan -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8d246f46-132a-4b52-97a3-73fc3fc01e5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
