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
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
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
> 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
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
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
