-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Installing new kernel breaks custom kernel= line in xen.cfg #5716
Comments
The issue appears to come from the Below is the culprit code # then change the default
sed -e "s/default=.*/default=$KVER/" -i $EFI_DIR/xen.cfg Working on a possible solution now by replacing the |
Replacing the # then change the default
awk -F = --assign "kver=${KVER}" '
/^\[/ {
# section header - previous section (if any) ended
in_global=0;
}
/\[global\]/ {
# we are now in the global block - set flag
in_global=1;
}
/^default=/ {
# only pay attention to default= if we are in the global block
if (in_global) {
sub("=[^ ]*", "=" kver);
}
}
{
print;
}
' $EFI_DIR/xen.cfg > $EFI_DIR/xen.cfg.tmp
mv $EFI_DIR/xen.cfg.tmp $EFI_DIR/xen.cfg Maybe someone more familiar with bash / awk could suggest a solution that doesn't require a temporary file, however this seems to work wonders on my test machine. |
Just adding # then change the default
sed -e "s/^default=.*/default=$KVER/" -i $EFI_DIR/xen.cfg |
(cherry picked from commit 1a28a1c) Notes from origin: Fixes QubesOS/qubes-issues#5716
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Fully updated R4.0, with both kernel and kernel-latest installed.
My machine requires the kernel= line in /boot/efi/EFI/qubes/xen.cfg to include the entry "mem_sleep_default=deep".
When I upgrade dom0 and get a new kernel, seemingly from either kernel or kernel-latest, this line is broken. It gets replaced by mem_sleep_default=[latest kernel installed].
For example, this is what my xen.cfg looked like after updating kernel-latest yesterday:
This is probably a fairly simple parsing bug somewhere, but I'm sorry, I don't have the time myself to try to track it down right now.
The text was updated successfully, but these errors were encountered: