-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use kernel installed in debian-8 VM #3178
Comments
AppVMs based on such templates (and having |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Updated a clone of debian-9 to current-testing and symlink works- no more fatal errors on a grub update. I don't see |
That one package (qubes-core-agent) wasn't part of that update. Should be in qubes-core-agent-4.0.32 |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Qubes OS version:
R4.0
Affected TemplateVMs:
debian-8
Steps to reproduce the behavior:
Expected behavior:
VM boots correctly with the guest provided kernel which makes it easy to use out-of-tree kernel modules (like wireguard) inside VMs.
Actual behavior:
VM boot fails with the following error message:
Digging from the initramfs shell shows that
/dev/mapper/dmroot
doesn't exist, don't know how it's supposed to be created?General notes:
I've followed documentation on how to use kernel installed in the VM.
Work-around
Manually changing
/dev/mapper/dmroot
to/dev/xvda1
in/etc/default/grub.d/30-qubes.cfg
makes the VM boot correctly. Not sure about the side-effects of this though.The text was updated successfully, but these errors were encountered: