Re: [qubes-users] Dom0 kernel panic
On 3/3/21 3:29 PM, frag face wrote: Hi all, I'm running Qubes 4.0 My dom0 doesn't boot anymore (following an aborted Fedora update it seems...). Boot runs to kernel panic, see attached image. From a newly installed Qubes on a different disk, I can mount my crashed disk, decrypt it and access all my Qubes, DOM0... I see two options to recover my environment (and would prefer the first): 1- Fix my Dom0 environment on my crashed hard drive (I have another drive with a newly installed Qubes 4.0-rc3) 2- Save my qubes from my crashed disk, and restore them on my new 4.0-rc3 install. Any advise to perform a rescue for option 1 or 2 is welcomed ! 1) try to boot from a life system. Mount /boot and, in case of UEFI, have a look in efi/qubes/xen.cfg or efi/BOOT/xen.cfg you should be able to select a older kernel. Maybe that allows to reboot. 2) emergency backup is a good idea in any case. Open the encrypted volume (using luks)then runvgchange -ayto activate all logical volumes. With lvscan you should be able to see the names (something like qubes-...-work-private qubes-...-work-root etc It is the "private" one that you want. Mount them (they are all in /dev/mapper/ ) and "rsync -auv" your data to a harddrive in respective subdirs. That is less safe than the paranoid version of qubes-backup since its grasps all ".config" files, but at least you have a full take. Good luck! -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6ac3a6b2-9d0f-cb77-0ae0-a62e2f740d7c%40web.de.
Re: [qubes-users] Dom0 kernel panic
Thanks for your answer Bernhard, I wonder if I could make a Qube-style backup of the qubes in my hardrive instead of a rsync to restore/add them directly in the new installed Qube system, kind of lazy way ;) BR Le jeu. 4 mars 2021 à 16:34, Bernhard a écrit : > On 3/3/21 3:29 PM, frag face wrote: > > Hi all, > > > > I'm running Qubes 4.0 > > My dom0 doesn't boot anymore (following an aborted Fedora update it > > seems...). > > Boot runs to kernel panic, see attached image. > > > > From a newly installed Qubes on a different disk, I can mount my > > crashed disk, decrypt it and access all my Qubes, DOM0... > > > > I see two options to recover my environment (and would prefer the first): > > 1- Fix my Dom0 environment on my crashed hard drive (I have another > > drive with a newly installed Qubes 4.0-rc3) > > 2- Save my qubes from my crashed disk, and restore them on my new > > 4.0-rc3 install. > > > > Any advise to perform a rescue for option 1 or 2 is welcomed ! > > 1) try to boot from a life system. Mount /boot and, in case of UEFI, > have a look in efi/qubes/xen.cfg or efi/BOOT/xen.cfg you should be > able to select a older kernel. Maybe that allows to reboot. > > 2) emergency backup is a good idea in any case. Open the encrypted > volume (using luks)then runvgchange -ayto activate all > logical volumes. With lvscan you should be able to see the names > (something like qubes-...-work-private > qubes-...-work-root > etc > It is the "private" one that you want. Mount them (they are all in > /dev/mapper/ ) and "rsync -auv" your data to a harddrive in > respective subdirs. That is less safe than the paranoid version > of qubes-backup since its grasps all ".config" files, but at least > you have a full take. > > Good luck! > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/6ac3a6b2-9d0f-cb77-0ae0-a62e2f740d7c%40web.de > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAPrquWt6DK3w40VqYa_DoKHmMbn-P9gFzheK%2BEBQQMwUP%3D3gVA%40mail.gmail.com.
Re: [qubes-users] Dom0 kernel panic
On 3/4/21 9:16 PM, frag face wrote: Thanks for your answer Bernhard, I wonder if I could make a Qube-style backup of the qubes in my hardrive instead of a rsync to restore/add them directly in the new installed Qube system, kind of lazy way ;) BR You can, with some extra work: The complete qubes-backup procdure is explained online. It is, roughly speaking, a tar archive with special checksum files to ensure pwds are correct. I always to these backups by hand, to keep myself trained. My method "sous-entend" that you "safe backup": in your life system generate a container file (truncate -s 200G /externalstorage/backup.luks), then losetup: (first losetup -f to get a free slot, then bind it with losetup /dev/loopX /externalstorage/backup.luks ), and cryptsetup luksFormat /dev/loopX ;cryptsetup luksOpen /dev/loopX BACKUP; mkfs.ext2 /dev/mapper/BACKUP ; mount /dev/mapper/BACKUP /somemountpoint For rsync'ing back inside qubes from subfolders you - attach usb to dispVM1 (widget) - lopsetup the container - attach container mapper to dispVM2 (widget) - there start same procedure as above at "luksOpen" step and then attach the full decrypted backup to each VM with the widget, and rsync back the correct subfolder in your home. You can use --exclude to avoid "dot"-files ... best, Bernhard -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6d54904c-68ee-6ecf-4d59-10cddbd8941c%40web.de.
[qubes-users] Dom0 Kernel panic when using iGPU
I have been attempting to get Qubes installed on my Metabox Prime-V laptop, which has resulted in the following kernel panic on each boot. https://user-images.githubusercontent.com/43260698/67632046-025ddf00-f896-11e9-9012-e6813789a3f5.jpg This kernel panic seems to be caused by the interaction of Xen and the iGPU. I can boot Qubes using the Nvidia card or using the iGPU without Xen perfectly fine. Neither of these solutions are usable however, qubes without Xen defeats the purpose and the Nvidia card is not supported by Nouveau. Solutions I have tried so far: - Install from Normal 4.0, 4.0.1 and 4.0.2-rc1 ISO. - Manually create the above isos using Qubes Builder - Install on another machine, fully update the system and install kernel-latest. - Disabling power management (cstates, etc) in both bios and xen/linux boot line. - Hiding the nvidia pci device using `xen-pciback.hide` The following boot configuration has been used: ``` [qubes-verbose] options=console=vga efi=no-rs iommu=no-igfx loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan vga=current,keep guest_loglvl=all #noexitboot=1 #mapbs=1 kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-20190628-x86_64 i915.alpha_support=1 nouveau.modeset=0 iommu=no-igfx console=hvc0 acpi=off ramdisk=initrd.img ``` This has allowed be to gather error messages from the console (see above link). But I have run out of ideas. I've been posting this on the following github issue as well: https://github.com/QubesOS/qubes-issues/issues/5422 Thanks. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/63a8b55f-014d-a32a-d7d3-a58f10ce90e6%40TLRcommunications.com.au.
Re: [qubes-users] Dom0 Kernel panic when using iGPU
Jarrah Gosbell: > I have been attempting to get Qubes installed on my Metabox Prime-V > laptop, which has resulted in the following kernel panic on each boot. > [qubes-verbose] > options=console=vga efi=no-rs iommu=no-igfx loglvl=all > dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan vga=current,keep > guest_loglvl=all > #noexitboot=1 > #mapbs=1 > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-20190628-x86_64 > i915.alpha_support=1 nouveau.modeset=0 iommu=no-igfx console=hvc0 acpi=off > ramdisk=initrd.img > https://github.com/QubesOS/qubes-issues/issues/5422 Have you tried taking out iommu=no-igfx (in both places) and/or i915.alpha_support=1? -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/98d51909-8306-69a4-1895-47cf4062cb2b%40danwin1210.me.
Re: [qubes-users] Dom0 Kernel panic when using iGPU
> Have you tried taking out iommu=no-igfx (in both places) and/or i915.alpha_support=1? I have just tried this. No change. Using the serial console still results in the same kernel panic. Without the serial console, there is no output from Dom0. I also was recommend pci=nocrs in the console output while testing. Same result for this. Of interest, while testing the above I accidentally left the Nvidia GPU active. I received exactly the same kernel panic in serial console with the Nvidia GPU as I usually do with the iGPU. It may be that the error I am looking at is a result of the console, and the real error is something else. Thanks. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dbd84549-e0b6-5def-6684-088002526dca%40TLRcommunications.com.au.