Bug #7728

Suboptimal display resolution in VirtualBox

Added by kytv 2014-08-02 21:13:26 . Updated 2016-02-18 20:48:11 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Virtualization
Target version:
Start date:
2014-08-02
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

This is might be due to Bug #7602.

Note: My normal resolution is 1680x1050.

Outside of Tails

With the VirtualBox guest packages that are included in Debian, my guest machines work as one would potentially expect. The resolution upon booting is at 1024x768 but if I switch to a full screen display in my virtualbox guest, the resolution matches my workstation’s 1680x1050. At no point is the screen bigger than my display.

In Tails

In Tails, however, the resolution is set to 1600x1200. This means that by default the virtualbox window containing the tails session doesn’t fit on my screen. I can change it after logging in (or just deal with a missing part of the screen), but it’d be better if the resolution could be reduced to something that’s practically guaranteed to work, like 1024x768, 1280x1024, etc.)


Subtasks


Related issues

Related to Tails - Feature #5730: Virtualbox guest additions: enable by default the display management service Resolved
Related to Tails - Bug #10077: Tails 1.5 has resolution 720x366 in VirtualBox Resolved 2015-08-23

History

#1 Updated by kytv 2014-08-02 21:14:13

  • related to Bug #7602: Reintroduce VirtualBox support added

#2 Updated by intrigeri 2014-08-03 09:19:27

> With the VirtualBox guest packages that are included in Debian, my guest machines […]

It could be useful to make it clear what exact version of the guest packages these VMs are running.

> In Tails, however, the resolution is set to 1600x1200.

May you please confirm that the guest kernel modules are loaded, and the guest services are running?

> Related to Bug Bug #7602: Reintroduce VirtualBox support added

This only affects Tails based on Jessie. If you’re testing a Tails ISO based on Wheezy, then this is unrelated.

#3 Updated by intrigeri 2014-08-03 09:21:04

  • Subject changed from "wrong" resolution in virtualbox to Suboptimal display resolution in VirtualBox
  • Assignee set to kytv
  • Target version deleted (Tails_2.0)
  • QA Check set to Info Needed

#4 Updated by kytv 2014-08-03 12:44:50

  • related to deleted (Bug #7602: Reintroduce VirtualBox support)

#5 Updated by kytv 2014-08-03 12:51:40

  • Assignee changed from kytv to intrigeri
  • QA Check changed from Info Needed to Dev Needed

Sorry, this is in Wheezy. I’ve unlinked the other ticket.

root@amnesia:~# COLUMNS=150 dpkg -l '*virtualbox*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                            Version              Architecture         Description
+++-===============================-====================-====================-====================================================================
un  virtualbox-guest-dkms           <none>                                    (no description available)
un  virtualbox-guest-source         <none>                                    (no description available)
ii  virtualbox-guest-utils          4.3.12-dfsg-1~bpo70+ i386                 x86 virtualization solution - non-X11 guest utilities
ii  virtualbox-guest-x11            4.3.12-dfsg-1~bpo70+ i386                 x86 virtualization solution - X11 guest utilities
root@amnesia:~# lsmod |grep 'drm\|vbox'
vboxsf                 37350  0 
vboxvideo              12437  0 
drm                   236561  1 vboxvideo
vboxguest             189903  2 vboxsf
i2c_core               28324  2 drm,i2c_piix4
root@amnesia:~# /etc/init.d/virtualbox-guest-utils status
VBoxService daemon isn't running
root@amnesia:~# /etc/init.d/virtualbox-guest-utils start
[....] Starting VirtualBox AdditionsVBoxService 4.3.12_Debian r93733 (verbosity: 0) linux.x86 (Jun 12 2014 03:53:18) release log
00:00:00.000354 main     Log opened 2014-08-03T12:48:42.986633000Z
00:00:00.000438 main     OS Product: Linux
00:00:00.000453 main     OS Release: 3.14-2-amd64
00:00:00.000469 main     OS Version: #1 SMP Debian 3.14.13-2 (2014-07-24)
00:00:00.000482 main     OS Service Pack: #1 SMP Debian 3.14.13-2 (2014-07-24)
00:00:00.000500 main     Executable: /usr/sbin/VBoxService
00:00:00.000508 main     Process ID: 5862
00:00:00.000515 main     Package type: LINUX_32BITS_GENERIC (OSE)
00:00:00.000560 main     Error: Failed to connect to the guest property service, rc=VERR_INVALID_FUNCTION
00:00:00.000578 main     Error: Service 'control' failed pre-init: VERR_INVALID_FUNCTION
 failed!


#6 Updated by intrigeri 2014-08-03 13:52:17

  • Status changed from New to Confirmed
  • Assignee changed from intrigeri to sajolida
  • QA Check deleted (Dev Needed)

Thanks for the additional info! So, the guest utils don’t start properly, interesting.

sajolida: IIRC you reintroduced VirtualBox support in 1.1, may you please have look / try to reproduce?

#7 Updated by sajolida 2014-08-04 18:56:23

Do you think that having display management service enabled by default would fix your problem. That’s Feature #5730 and want to work on this for Tails 1.2.

#8 Updated by sajolida 2014-08-04 18:56:46

  • related to Feature #5730: Virtualbox guest additions: enable by default the display management service added

#9 Updated by kytv 2014-08-04 21:57:34

sajolida wrote:
> Do you think that having display management service enabled by default would fix your problem.

Perhaps, but if I run

sudo VBoxClient --display

, I don’t see a change in behaviour.

#10 Updated by sajolida 2014-09-29 01:38:23

  • Type of work changed from Code to Wait

This might be solved by in Tails 1.2 by Feature #5730. Let’s wait and see…

#11 Updated by intrigeri 2014-09-29 05:36:09

  • Assignee changed from sajolida to kytv
  • QA Check set to Info Needed
  • Type of work changed from Wait to Code

Kill Your TV, may you please try to reproduce this bug with a current build from the devel branch?

#12 Updated by sajolida 2014-11-16 11:11:33

  • Category changed from Hardware support to Virtualization

#13 Updated by sajolida 2015-08-25 09:45:42

  • related to Bug #10077: Tails 1.5 has resolution 720x366 in VirtualBox added

#14 Updated by intrigeri 2015-12-05 15:32:38

  • Target version set to Tails_2.0

Can you reproduce this on a current build from feature/jessie?

#15 Updated by intrigeri 2016-01-09 17:48:39

Ping? Last call to include a fix for that issue in Tails 2.0 :)

#16 Updated by intrigeri 2016-02-18 20:47:21

  • Target version changed from Tails_2.0 to Tails_2.2

(Tails 2.0 was released and I’d like to close the corresponding target version in Redmine accordingly.)

#17 Updated by intrigeri 2016-02-18 20:48:11

  • Status changed from Confirmed to Rejected
  • Assignee deleted (kytv)
  • Target version deleted (Tails_2.2)

The requested info was not provided since a year, closing.