-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
SMAP cause Linux HVM boot failure #2881
Comments
The most important for us here is SMAP - unfortunately we need to not expose it to guests, because of Linux kernel bug. Fixes QubesOS/qubes-issues#2881
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
|
Linux kernel bug cause hypercall fails from HVM userspace (see referenced issue). As a simple workaround, do not advertise SMAP to VMs - but still use it as hypervisor level. Fixes QubesOS/qubes-issues#2881
Linux kernel bug cause hypercall fails from HVM userspace (see referenced issue). As a simple workaround, do not advertise SMAP to VMs - but still use it as hypervisor level. Fixes QubesOS/qubes-issues#2881
Automated announcement from builder-github The package
|
Can we reenable this yet? |
I guess so, Debian jessie should not be a thing anymore. |
Buggy Linux version is no longer present in any supported template (the last one was Debian jessie). QubesOS/qubes-issues#2881
Buggy Linux version is no longer present in any supported template (the last one was Debian jessie). QubesOS/qubes-issues#2881
Buggy Linux version is no longer present in any supported template (the last one was Debian jessie). QubesOS/qubes-issues#2881 (cherry picked from commit 8f38753)
Qubes OS version (e.g.,
R3.2
): R4.0The effect is that QubesDB fails to start,
qubesdb-daemon
in dom0 try to connect, immediately fails and try to reconnect. When this happens, QubesDB socket in dom0 for given domain is not available and access to it from qubesd fails with:or
At the same time, VM try to start, QubesDB startup time out (1m30s), then every service depending on information retrieved from QubesDB (including
qubes-sysinit.service
) fails too. Pretty much unusable VM.More details in upstream report. The fix is already submitted upstream, but it will take time until the patch will be available in distribution kernel packages (especially Debian).
The text was updated successfully, but these errors were encountered: