Bug #12001
Document that Tails requires I/O APIC being enabled in the VirtualBox VM config
100%
Description
The follow-ups to various bug reports about regressions against Tails 2.7 tell us that enabling I/O APIC in the guest’s motherboard settings fixes the regression many people have reported.
Side-note: I’ve also seen recommandations to switch the VM to 64-bit. I trust it helps (apparently it somehow enables I/O APIC) but that’s sub-optimal since Tails 2.x only support the guest utilities in 32-bit VMs (Bug #11848).
Subtasks
Related issues
Related to Tails - |
Rejected | 2016-09-28 | |
Related to Tails - |
Resolved | 2016-11-19 |
History
#1 Updated by intrigeri 2016-11-27 17:19:22
- related to
Bug #11848: Clarify that VirtualBox guest utilities only work in 32-bit virtual machines added
#2 Updated by intrigeri 2016-11-27 17:19:46
- related to
Bug #11965: Tails 2.7 won't start in Virtual Box added
#3 Updated by intrigeri 2016-11-27 17:20:38
- Target version set to Tails_2.9.1
This seems to be a commonly reported regression in Tails 2.7, so it would be nice if our doc was updated promptly. sajolida, help desk, anyone up to it?
#5 Updated by spriver 2016-11-30 20:27:29
With VirtualBox 5.1.8-dfsg-6~bpo8+2 on Debian 8 with enabled I/O APIC Tails 2.7 and 2.7.1 is not booting for me (halting after loading the guest additions while boot time).
#6 Updated by intrigeri 2016-12-04 09:09:18
spriver wrote:
> With VirtualBox 5.1.8-dfsg-6~bpo8+2 on Debian 8 with enabled I/O APIC Tails 2.7 and 2.7.1 is not booting for me (halting after loading the guest additions while boot time).
Please report this on Bug #11965: this ticket is about enabling I/O APIC, which solves part of the problem, while Bug #11965 is about finding out what else is needed to solve the problem entirely. You’ll want to try adding modprobe.blacklist=vboxvideo
to the kernel command-line.
#7 Updated by nikograus 2016-12-08 20:31:59
Don’t waste your breath with poking around VirtualBox guest additions, it’s not the issue. The proposed workaround of enabling the I/O APIC is perfectly right. This is purely a Linux 4.7 bug, and it’s tracked here: https://patchwork.kernel.org/patch/9357253/
You’ll notice that there’s not a single mention of VirtualBox in that ticket, because the very same issue happens with real PCs which don’t have an I/O APIC.
Please update the Known Issues page at https://tails.boum.org/support/known_issues/ accordingly so that your users know what to do if 32-bit Tails 2.7 hangs with a black screen in VirtualBox. There is only a very small performance hit by enabling this setting, which clearly is outweighed by the benefits of being able to run Tails without trouble.
#8 Updated by anonym 2016-12-09 15:38:53
- Status changed from Confirmed to In Progress
- Assignee changed from emmapeel to sajolida
- % Done changed from 0 to 50
- QA Check set to Ready for QA
- Feature Branch set to doc/12001-virtualbox-needs-io-apic
Thanks for the explanation, nikograus!
Please review’n’merge the feature branch into the master
branch. sajolida, will you take it?
#10 Updated by anonym 2016-12-13 14:13:36
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
#11 Updated by anonym 2016-12-14 20:10:52
- Status changed from Fix committed to Resolved