Project

General

Profile

Bug #11848

Clarify that VirtualBox guest utilities only work in 32-bit virtual machines

Added by goupille about 3 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Virtualization
Target version:
-
Start date:
09/28/2016
Due date:
% Done:

50%

Estimated time:
1.00 h
Feature Branch:
emmapeel:docs/11848-clarify-VirtualBox-32bits
Type of work:
End-user documentation
Blueprint:
Starter:
Yes
Affected tool:

Description

two whisperback reports pointed that virtualbox-guest-utils does not work anymore since Tails 2.6. There was an upgrade of the package (now 5.0.24), but maybe it was not enough to work with linux-image-4.6* because le logs are saying :

amnesia virtualbox-guest-utils[1746]: Starting VirtualBox AdditionsNo suitable module for running kernel found ... failed!
amnesia virtualbox-guest-utils[1746]: failed!
amnesia systemd[1]: virtualbox-guest-utils.service: control process exited, code=exited status=1
amnesia systemd[1]: Failed to start LSB: VirtualBox Linux Additions.
-- Subject: Unit virtualbox-guest-utils.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit virtualbox-guest-utils.service has failed.
-- 
-- The result is failed.

Related issues

Related to Tails - Bug #11992: Tails 2.7 is missing 64-bit VirtualBox kernel modules Rejected 11/22/2016
Related to Tails - Bug #11965: Tails 2.7 won't start in Virtual Box Resolved 11/19/2016
Related to Tails - Bug #12001: Document that Tails requires I/O APIC being enabled in the VirtualBox VM config Resolved 11/27/2016

History

#1 Updated by intrigeri about 3 years ago

  • Assignee set to goupille
  • QA Check set to Info Needed

two whisperback reports pointed that virtualbox-guest-utils does not work anymore since Tails 2.6.

Is the VM a 32-bit or 64-bit one?

We only support 32-bit guests on VirtualBox, as our doc tries to make it clear.

#2 Updated by goupille about 3 years ago

  • Assignee changed from goupille to intrigeri

I don't think our doc is that clear... since one report is about shared folders not working and our doc is saying that "The shared folders work both on 32-bit and 64-bit guests" then, there is an issue...

anyway, I asked the user if its vm is configured in 32bits.

#3 Updated by intrigeri about 3 years ago

  • Assignee changed from intrigeri to sajolida

I don't think our doc is that clear... since one report is about shared folders not working and our doc is saying that "The shared folders work both on 32-bit and 64-bit
guests" then, there is an issue...

Good catch ⇒ sending to sajolida's plate to make this consistent with our saying "Other Linux (32 bit)" a few lines above.

anyway, I asked the user if its vm is configured in 32bits.

Cool. Note that you can probably see that yourself in the WhisperBack bug report, if there's one.

If the VM was indeed a 64-bit guest (I guess it is), then this is a "End-user documentation" task. Otherwise, there's a more serious problem going on and I'll need to take a closer look.

#4 Updated by goupille about 3 years ago

  • Assignee changed from sajolida to intrigeri

Cool. Note that you can probably see that yourself in the WhisperBack bug report, if there's one.

that wasn't that clear to me... if the VM is configured in 32bits, then it shouldn't start Linux version 4.6.0-0.bpo.1-amd64 ?

#5 Updated by intrigeri about 3 years ago

that wasn't that clear to me... if the VM is configured in 32bits, then it shouldn't start Linux version 4.6.0-0.bpo.1-amd64 ?

Right.

#6 Updated by intrigeri about 3 years ago

  • Assignee changed from intrigeri to sajolida

#7 Updated by goupille about 3 years ago

then the reports are about 64bits VM... good to know :)

#8 Updated by goupille about 3 years ago

I let sajolida decide if it is better to change this ticket's name or close it and open a new one about clarifying the documentation

#9 Updated by intrigeri about 3 years ago

  • Status changed from New to Confirmed
  • QA Check changed from Info Needed to Dev Needed

#10 Updated by sajolida about 3 years ago

  • Subject changed from Virtualbox-guest-utils does not seem to work with kernel 4.6 to Clarify that VirtualBox guest modules only work in 32-bit virtual machines
  • Category set to Virtualization
  • Assignee deleted (sajolida)
  • QA Check deleted (Dev Needed)
  • Type of work changed from Research to End-user documentation
  • Starter set to Yes

That should be easy :)

#11 Updated by emmapeel about 3 years ago

  • Assignee set to emmapeel

#12 Updated by emmapeel almost 3 years ago

  • Status changed from Confirmed to In Progress
  • Assignee deleted (emmapeel)
  • % Done changed from 0 to 50
  • Estimated time set to 1.00 h
  • QA Check set to Ready for QA
  • Feature Branch set to emmapeel:docs/11848-clarify-VirtualBox-32bits

#13 Updated by intrigeri almost 3 years ago

  • Assignee set to sajolida
  • Target version set to Tails_2.7

#14 Updated by sajolida almost 3 years ago

  • Target version deleted (Tails_2.7)

#15 Updated by elouann almost 3 years ago

  • Related to Bug #11992: Tails 2.7 is missing 64-bit VirtualBox kernel modules added

#16 Updated by intrigeri almost 3 years ago

  • Related to Bug #11965: Tails 2.7 won't start in Virtual Box added

#17 Updated by intrigeri almost 3 years ago

  • Subject changed from Clarify that VirtualBox guest modules only work in 32-bit virtual machines to Clarify that VirtualBox guest utilities only work in 32-bit virtual machines

#18 Updated by intrigeri almost 3 years ago

  • Related to Bug #12001: Document that Tails requires I/O APIC being enabled in the VirtualBox VM config added

#19 Updated by intrigeri almost 3 years ago

  • Assignee changed from sajolida to anonym
  • QA Check changed from Ready for QA to Info Needed

On #11965 anonym wrote:

  • "filesystem sharing, host-to-guest time syncing and clipboard sharing are the only features missing with the 64-bit kernel."
  • "#11848 (Clarify that VirtualBox guest utilities only work in 32-bit virtual machines) seems wrong, so it should probably be rejected."

... which seem somewhat contradictory to me. The guest utilities seem to only partially work on 64-bit, i.e. without the guest modules loaded. But I guess I've misunderstood something, then. anonym, can you please clarify?

#20 Updated by anonym almost 3 years ago

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

Sorry for not being clear! What I mean is that the guest utilities work sufficiently on 64-bit now that we have mouse-integration and good screen resolution; the basic experience is now solid, imho. Calling it "partial" is technically correct, but my point is rather that there's no reason to make users avoid 64-bit any more, so let's instead frame it as: "shared folders and clipboard sharing is only available in 32-bit virtual machines" (I think we can ignore mentioning host-to-guest time syncing).

Clear?

#21 Updated by intrigeri almost 3 years ago

so let's instead frame it as: "shared folders and clipboard sharing is only available in 32-bit virtual machines"

Perfect!

#22 Updated by intrigeri almost 3 years ago

  • Assignee changed from sajolida to emmapeel

Emma, can you please make sure that the latest info provided by anonym is taken into account in your proposed branch?

#23 Updated by u over 2 years ago

hey!

any update on this one?
Does this still apply for Tails 3.0/amd64?

#24 Updated by intrigeri over 2 years ago

  • Status changed from In Progress to Rejected

One can't start Tails in a 32-bit VM anymore.

Also available in: Atom PDF