Re: [qubes-users] Qubes 3.2 UEFI install media
On Tuesday, 11 July 2017 10:49:20 UTC+2, Stephan Marwedel wrote: > I was able to determine the cause of the problem. After having changed > the label by editing xen.cfg as described the following needs to be done > in addition before the media can be used on an UEFI system to install Qubes: > > 5. Unmount the USB media, but leave it connected to the machine. > Assuming that the USB device is named /dev/xvdi, execute the following > command: > > dosfslabel /dev/xvdi1 BOOT > > This creates a label name that the UEFI bootloader uses to identify the > root image. Now the media can be used to install Qubes 3.2. > > On 07/10/2017 06:46 PM, Stephan Marwedel wrote: > > Thanks for this interesting hint. Following your detailed instructions I > > was able to create a bootable media that correctly boots on my Thinkpad > > in UEFI mode. However, when the kernel finished loading, an emergency > > shell appears and the following messages are displayed: > > > > Starting Dracut Emergency Shell... > > > > Warning: /dev/root does not exist > > > > Entering emergency mode > > > > It seems that the kernels loads OK, but is unable to find a root > > filesystem to mount. As I do not have Qubes currently installed on my > > machine, I am unsure about how to specify a root filesystem. The only > > valid root filesystem is the one on the installation media, but that > > should be found automatically. Or is it necessary to specify it manually? > > > > Regards, > > Stephan > > > > On 06/26/2017 08:29 AM, Dave C wrote: > >> I recently had some success install Qubes 3.2 on a lenovo p51, booting > >> UEFI. I went through a lot of a trial and error in the process. I'm > >> hoping this post can save others some time. I've seen in other > >> threads some struggling to get Qubes working with UEFI firmware. > >> > >> I intended to save my command history to disk so that I could post > >> step-by-step exactly what to do. But I must have been in a dispvm at > >> the time, because now I can't find that history. So the following is > >> from memory and not precise. > >> > >> I tried every trick I could find related to Qubes UEFI installation, > >> and thinkpad troubleshooting. What finally worked does not appear to > >> be documented in any of the Qubes documentation. Qubes uses Fedora's > >> installer, Anaconda, and the following approach is documented on > >> Fedora's wiki. > >> > >> 1. Follow Qubes install guide up to the `dd` command. Don't write to > >> usb with `dd`. > >> https://www.qubes-os.org/doc/installation-guide/ > >> > >> 2. Instead, use Fedora's `livecd-iso-to-disk` tool. You'll need the > >> `livecd-tools` package. See > >> https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB#Command_line_method:_Using_the_livecd-iso-to-disk_tool_.28Fedora_only.2C_non-graphical.2C_both_non-destructive_and_destructive_methods_available.29 > >> > >> > >> I don't recall for certain exactly what I passed to > >> `livecd-iso-to-disk`. Try this: > >> > >> sudo livecd-iso-to-disk --efi --format Qubes-R3.2-x86_64.iso > >> /dev/xvdi > >> > >> The media as written will not quite boot, yet. Qubes EFI boot is > >> configured to find a label "Qubes-R3.2-x86_64", but the media written > >> by the livecd tool is labelled "BOOT" (and the filesystem does not > >> support the longer label, so the --label option would not help). > >> > >> 3. Mount the usb media (/dev/xvdi in the example above) > >> > >> 4. Edit xen.cfg. If I recall correctly, `/EFI/BOOT/xen.cfg`. > >> > >> In this file, replace every occurrence of `LABEL=Qubes-R3.2-x86_64` > >> with `LABEL=BOOT` > >> > >> You should now have install media that work on UEFI firmware! > >> > >> > >> After install, I recommend upgrading kernel version for recent > >> hardware. I.e. with > >> > >> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel > >> kernel-qubes-vm > >> > >> > > Thanks a lot Dave C and Stephan Marwendel. By following both of your instructions I got the installation working on my Lenovo ThinkPad Yoga 460! -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4fa06b44-5b2f-4c82-9fdf-1fbc56accdc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 UEFI install media
I was able to determine the cause of the problem. After having changed the label by editing xen.cfg as described the following needs to be done in addition before the media can be used on an UEFI system to install Qubes: 5. Unmount the USB media, but leave it connected to the machine. Assuming that the USB device is named /dev/xvdi, execute the following command: dosfslabel /dev/xvdi1 BOOT This creates a label name that the UEFI bootloader uses to identify the root image. Now the media can be used to install Qubes 3.2. On 07/10/2017 06:46 PM, Stephan Marwedel wrote: Thanks for this interesting hint. Following your detailed instructions I was able to create a bootable media that correctly boots on my Thinkpad in UEFI mode. However, when the kernel finished loading, an emergency shell appears and the following messages are displayed: Starting Dracut Emergency Shell... Warning: /dev/root does not exist Entering emergency mode It seems that the kernels loads OK, but is unable to find a root filesystem to mount. As I do not have Qubes currently installed on my machine, I am unsure about how to specify a root filesystem. The only valid root filesystem is the one on the installation media, but that should be found automatically. Or is it necessary to specify it manually? Regards, Stephan On 06/26/2017 08:29 AM, Dave C wrote: I recently had some success install Qubes 3.2 on a lenovo p51, booting UEFI. I went through a lot of a trial and error in the process. I'm hoping this post can save others some time. I've seen in other threads some struggling to get Qubes working with UEFI firmware. I intended to save my command history to disk so that I could post step-by-step exactly what to do. But I must have been in a dispvm at the time, because now I can't find that history. So the following is from memory and not precise. I tried every trick I could find related to Qubes UEFI installation, and thinkpad troubleshooting. What finally worked does not appear to be documented in any of the Qubes documentation. Qubes uses Fedora's installer, Anaconda, and the following approach is documented on Fedora's wiki. 1. Follow Qubes install guide up to the `dd` command. Don't write to usb with `dd`. https://www.qubes-os.org/doc/installation-guide/ 2. Instead, use Fedora's `livecd-iso-to-disk` tool. You'll need the `livecd-tools` package. See https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB#Command_line_method:_Using_the_livecd-iso-to-disk_tool_.28Fedora_only.2C_non-graphical.2C_both_non-destructive_and_destructive_methods_available.29 I don't recall for certain exactly what I passed to `livecd-iso-to-disk`. Try this: sudo livecd-iso-to-disk --efi --format Qubes-R3.2-x86_64.iso /dev/xvdi The media as written will not quite boot, yet. Qubes EFI boot is configured to find a label "Qubes-R3.2-x86_64", but the media written by the livecd tool is labelled "BOOT" (and the filesystem does not support the longer label, so the --label option would not help). 3. Mount the usb media (/dev/xvdi in the example above) 4. Edit xen.cfg. If I recall correctly, `/EFI/BOOT/xen.cfg`. In this file, replace every occurrence of `LABEL=Qubes-R3.2-x86_64` with `LABEL=BOOT` You should now have install media that work on UEFI firmware! After install, I recommend upgrading kernel version for recent hardware. I.e. with sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel kernel-qubes-vm -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/76cb74a9-27f3-1694-a597-a09ed6ea48ca%40tu-ilmenau.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 UEFI install media
Thanks for this interesting hint. Following your detailed instructions I was able to create a bootable media that correctly boots on my Thinkpad in UEFI mode. However, when the kernel finished loading, an emergency shell appears and the following messages are displayed: Starting Dracut Emergency Shell... Warning: /dev/root does not exist Entering emergency mode It seems that the kernels loads OK, but is unable to find a root filesystem to mount. As I do not have Qubes currently installed on my machine, I am unsure about how to specify a root filesystem. The only valid root filesystem is the one on the installation media, but that should be found automatically. Or is it necessary to specify it manually? Regards, Stephan On 06/26/2017 08:29 AM, Dave C wrote: I recently had some success install Qubes 3.2 on a lenovo p51, booting UEFI. I went through a lot of a trial and error in the process. I'm hoping this post can save others some time. I've seen in other threads some struggling to get Qubes working with UEFI firmware. I intended to save my command history to disk so that I could post step-by-step exactly what to do. But I must have been in a dispvm at the time, because now I can't find that history. So the following is from memory and not precise. I tried every trick I could find related to Qubes UEFI installation, and thinkpad troubleshooting. What finally worked does not appear to be documented in any of the Qubes documentation. Qubes uses Fedora's installer, Anaconda, and the following approach is documented on Fedora's wiki. 1. Follow Qubes install guide up to the `dd` command. Don't write to usb with `dd`. https://www.qubes-os.org/doc/installation-guide/ 2. Instead, use Fedora's `livecd-iso-to-disk` tool. You'll need the `livecd-tools` package. See https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB#Command_line_method:_Using_the_livecd-iso-to-disk_tool_.28Fedora_only.2C_non-graphical.2C_both_non-destructive_and_destructive_methods_available.29 I don't recall for certain exactly what I passed to `livecd-iso-to-disk`. Try this: sudo livecd-iso-to-disk --efi --format Qubes-R3.2-x86_64.iso /dev/xvdi The media as written will not quite boot, yet. Qubes EFI boot is configured to find a label "Qubes-R3.2-x86_64", but the media written by the livecd tool is labelled "BOOT" (and the filesystem does not support the longer label, so the --label option would not help). 3. Mount the usb media (/dev/xvdi in the example above) 4. Edit xen.cfg. If I recall correctly, `/EFI/BOOT/xen.cfg`. In this file, replace every occurrence of `LABEL=Qubes-R3.2-x86_64` with `LABEL=BOOT` You should now have install media that work on UEFI firmware! After install, I recommend upgrading kernel version for recent hardware. I.e. with sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel kernel-qubes-vm -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/181c454b-acb3-f535-f470-c989d08e1d6c%40tu-ilmenau.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 UEFI install media
I recently had some success install Qubes 3.2 on a lenovo p51, booting UEFI. I went through a lot of a trial and error in the process. I'm hoping this post can save others some time. I've seen in other threads some struggling to get Qubes working with UEFI firmware. I intended to save my command history to disk so that I could post step-by-step exactly what to do. But I must have been in a dispvm at the time, because now I can't find that history. So the following is from memory and not precise. I tried every trick I could find related to Qubes UEFI installation, and thinkpad troubleshooting. What finally worked does not appear to be documented in any of the Qubes documentation. Qubes uses Fedora's installer, Anaconda, and the following approach is documented on Fedora's wiki. 1. Follow Qubes install guide up to the `dd` command. Don't write to usb with `dd`. https://www.qubes-os.org/doc/installation-guide/ 2. Instead, use Fedora's `livecd-iso-to-disk` tool. You'll need the `livecd-tools` package. See https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB#Command_line_method:_Using_the_livecd-iso-to-disk_tool_.28Fedora_only.2C_non-graphical.2C_both_non-destructive_and_destructive_methods_available.29 I don't recall for certain exactly what I passed to `livecd-iso-to-disk`. Try this: sudo livecd-iso-to-disk --efi --format Qubes-R3.2-x86_64.iso /dev/xvdi The media as written will not quite boot, yet. Qubes EFI boot is configured to find a label "Qubes-R3.2-x86_64", but the media written by the livecd tool is labelled "BOOT" (and the filesystem does not support the longer label, so the --label option would not help). 3. Mount the usb media (/dev/xvdi in the example above) 4. Edit xen.cfg. If I recall correctly, `/EFI/BOOT/xen.cfg`. In this file, replace every occurrence of `LABEL=Qubes-R3.2-x86_64` with `LABEL=BOOT` You should now have install media that work on UEFI firmware! After install, I recommend upgrading kernel version for recent hardware. I.e. with sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel kernel-qubes-vm -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/54565916-4ae7-4029-8349-3c0afc59bb24%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
