Bug #12298

Can't build the devel branch due to virtualbox-guest-dkms incompatibility with Linux 4.9

Added by intrigeri 2017-03-05 17:00:51 . Updated 2017-03-08 12:14:37 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Virtualization
Target version:
Tails_2.12
Start date:
2017-03-05
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

I’ll see if pulling vbox-dkms from sid is enough. if not, I’ll disable the vbox dkms hook for now. and then we have a full cycle to decide what we do for 2.12 (https://tails.boum.org/contribute/meetings/201703/#index4h2 might help), between a) prepare a custom backport; and b) give up.

Subtasks

Related issues

Related to Tails - Bug #12307: devel branch lacks virtualbox-guest-x11 Resolved 2017-03-08
Blocks Tails - Feature #12089: Enable the kernel page allocator poisoning Resolved 2016-12-27
Blocks Tails - Bug #12218: AMD graphics regression since Tails 2.10 Resolved 2017-02-09

History

#1 Updated by intrigeri 2017-03-05 17:02:03

  • blocks Feature #12089: Enable the kernel page allocator poisoning added

#2 Updated by intrigeri 2017-03-05 17:02:15

  • blocks Bug #12218: AMD graphics regression since Tails 2.10 added

#3 Updated by intrigeri 2017-03-05 17:03:42

  • Priority changed from Elevated to High

#4 Updated by intrigeri 2017-03-06 07:51:14

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

Fixed the FTBFS but I had to drop virtualbox-guest-x11. Next step is to test what’s the impact for VirtualBox guests (iirc this should not harm 32-bit ones that have the kernel modules, but it might be that 64-bit guests can’t start X anymore).

#6 Updated by intrigeri 2017-03-08 11:02:56

  • % Done changed from 10 to 50

intrigeri wrote:
> Fixed the FTBFS but I had to drop virtualbox-guest-x11. Next step is to test what’s the impact for VirtualBox guests (iirc this should not harm 32-bit ones that have the kernel modules, but it might be that 64-bit guests can’t start X anymore).

Both 32-bit and 64-bit guests work for me, but display is limited to 1024x768. If it were broken more severely I would look into a backport, but given it mostly works I’ll document this known issue and move on, if anonym agrees.

#7 Updated by intrigeri 2017-03-08 11:30:57

  • Assignee changed from intrigeri to anonym
  • QA Check set to Info Needed

intrigeri wrote:
> Both 32-bit and 64-bit guests work for me, but display is limited to 1024x768. If it were broken more severely I would look into a backport, but given it mostly works I’ll document this known issue and move on, if anonym agrees.

Do you?

#8 Updated by anonym 2017-03-08 11:39:21

intrigeri wrote:
> intrigeri wrote:
> > Fixed the FTBFS but I had to drop virtualbox-guest-x11. Next step is to test what’s the impact for VirtualBox guests (iirc this should not harm 32-bit ones that have the kernel modules, but it might be that 64-bit guests can’t start X anymore).
>
> Both 32-bit and 64-bit guests work for me, but display is limited to 1024x768. If it were broken more severely I would look into a backport, but given it mostly works I’ll document this known issue and move on, if anonym agrees.

I think it’s ok, but I think we should at least do a low-effort try with the backports to get the x11 drivers before we release.

#9 Updated by intrigeri 2017-03-08 12:11:54

  • Assignee changed from anonym to intrigeri
  • QA Check deleted (Info Needed)

anonym wrote:
> I think it’s ok, but I think we should at least do a low-effort try with the backports to get the x11 drivers before we release.

OK. Asked the maintainer to push his (unofficial) backport to the packaging Git repo. Will file another ticket to track this, as what this one is about has been fixed.

#10 Updated by intrigeri 2017-03-08 12:13:03

  • related to Bug #12307: devel branch lacks virtualbox-guest-x11 added

#11 Updated by intrigeri 2017-03-08 12:14:19

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100

#12 Updated by intrigeri 2017-03-08 12:14:37

Bug #12307 tracks the follow-ups.