virtualbox.org

hi,

issue with debian new stable release: even after guest add-ons install, I cannot switch to full screen. I mean, I switch to full screen but debian gnome frame is not resized.

win 7 64 bits host, debian 8 64 bits guest.

am i the only one with this issue?

thanks a lot!

yohann

Make sure that auto-resize is enabled in the guest. Use (Host-G) or look in the view tab.

I just checked and autoresize is enabled in the guest.

I have a similar problem with a Jessie guest and VB 4.3.28. My guest will resize, but only the resolution changes, not the physical size in millimeters (according to xdpyinfo in the guest). Result is that the dots-per-inch depends on the size of the guest window rather than being fairly constant.

The same guest worked fine with 4.3.26 and if I re-install the guest additions from 4.3.26 it works fine again.

Thanks for the clue, i also suspect the guest additions.

Did they add scaling to VB 4.3.28? I don't have the same problem with VB 5.0 B4.

edit: I installed VB 4.3.28 and I don't have the problem.

I am having a similar problem. Glad this a current thread. The host+G is greyed out. I am running Gnome3 desktop on top of VB 4.3.6 on Win 7 64. should i try a different guest additions with my version? should i upgrade VB?

I tried this from http://virtualboxes.org/doc/installing- ... on-debian/:

Installing Guest Additions on Debian

Follow these steps to install the Guest Additions on your Debian virtual machine:

Login as root;
Update your APT database with apt-get update;
Install the latest security updates with apt-get upgrade;
Install required packages with apt-get install build-essential module-assistant;
Configure your system for building kernel modules by running m-a prepare;
Click on Install Guest Additions… from the Devices menu, then run mount /media/cdrom.
Run sh /media/cdrom/VBoxLinuxAdditions.run, and follow the instructions on screen.

I am seeing:

@dividschmivid,
You have two issue to resolve.
1) you need the headers installed
2) you need a newer version of VirtualBox

Well, then. That just about settles that. I will get on that. In the meantime, thank you for decoding the real meaning of those two lines.

Upon boot of the system, the only thing that failed was:
I was thinking update VB, but didn't want it to break what I already have going on.

viewtopic.php?f=1&t=67974

btw noob forum posting syntax questions...what is the code to imbed a link in some text, like <a href="cool.com">cool</a> ?
and how do you put in an image from your desktop inline in the post?

Images should be posted as an attachment ( see below the reply window )
All other tags are at the top of the reply windows and the syntax is not the same as html tags

see faq.php

You know, it's pretty weird state of affairs when getting the screen resolution working properly is, by far, the most involved and uncertain part of using VirtualBox with Linux.

Pretty much *every single time* I go to set up a new round of machines with updated debian-based OSes, the process has changed. It *never* is just a matter of installing the guest additions. *Never*.

I don't know what you're supposed to do about that. I'm just sayin'.

jjjjjj wrote:You know, it's pretty weird state of affairs when getting the screen resolution working properly is, by far, the most involved and uncertain part of using VirtualBox with Linux.
Pretty much *every single time* I go to set up a new round of machines with updated debian-based OSes, the process has changed. It *never* is just a matter of installing the guest additions. *Never*.
I don't know what you're supposed to do about that. I'm just sayin'.

The process has not changed since it came out. So the next step it to figure out why you think so. How familiar are you with Linux?

FWIW, I haven't noticed it changing myself.

hi,

I tried to debug the guest addons using the instructions provided on those pages: X11Clipboard and VBoxLogging.

I tried to restart the VBoxClient --display on guest. I also tried with VBoxClient --seamless as it may have a link to X11.

Here is what I got:

debian-8 (where resize issue appears):

test@debian:~$ VBOX_RELEASE_LOG_DEST=file=/home/test/log/vboxguest-display.log VBOX_RELEASE_LOG=+all.e.l.f VBoxClient -d --display
Screen 0: minimum 64 x 64, current 1183 x 853, maximum 32766 x 32766
VGA-0 connected primary 1183x853+0+0 0mm x 0mm
1183x853 60.00*+
Screen 0: minimum 64 x 64, current 1183 x 853, maximum 32766 x 32766
VGA-0 connected primary 1183x853+0+0 0mm x 0mm
1183x853 60.00*+

display log file:

test@debian:~/log$ cat vboxguest-display.log
runDisplay:
runDisplay: Got size hint from host cx=1201, cy=861, bpp=0, iDisplay=0, x=0, y=0 fEnabled=1
runDisplay: Got size hint from host cx=1203, cy=862, bpp=0, iDisplay=0, x=0, y=0 fEnabled=1
runDisplay: Got size hint from host cx=1204, cy=863, bpp=0, iDisplay=0, x=0, y=0 fEnabled=1
runDisplay: Got size hint from host cx=1204, cy=863, bpp=0, iDisplay=0, x=0, y=0 fEnabled=1
runDisplay: Got size hint from host cx=1205, cy=863, bpp=0, iDisplay=0, x=0, y=0 fEnabled=1
runDisplay: Got size hint from host cx=1207, cy=864, bpp=0, iDisplay=0, x=0, y=0 fEnabled=1
runDisplay: Got size hint from host cx=1208, cy=864, bpp=0, iDisplay=0, x=0, y=0 fEnabled=1
test@debian:~/log$

seamless log file:
test@debian:~/log$ cat vboxguest-seamless.log
SeamlessMain::init:
SeamlessX11::init:
SeamlessX11::init: returning VINF_SUCCESS
SeamlessMain::selfTest:
SeamlessMain::run:
SeamlessMain::nextStateChangeEvent:

dmesg
...
[ 15.071026] VBoxService 4.3.28 r100309 (verbosity: 0) linux.amd64 (May 13 2015 17:11:31) release log
00:00:00.000150 main Log opened 2015-06-02T12:09:35.084685000Z
[ 15.071240] 00:00:00.000536 main OS Product: Linux
[ 15.071394] 00:00:00.000710 main OS Release: 3.16.0-4-amd64
[ 15.071550] 00:00:00.000864 main OS Version: #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24)
[ 15.071699] 00:00:00.001011 main OS Service Pack: #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24)
[ 15.071968] 00:00:00.001161 main Executable: /opt/VBoxGuestAdditions-4.3.28/sbin/VBoxService
00:00:00.001170 main Process ID: 700
00:00:00.001172 main Package type: LINUX_64BITS_GENERIC
[ 15.074750] 00:00:00.004024 main 4.3.28 r100309 started. Verbose level = 0
[ 20.250901] VbglR0HGCMInternalCall: vbglR0HGCMInternalDoCall failed. rc=-2
[ 20.250963] VBoxGuestCommonIOCtl: HGCM_CALL: 64 Failed. rc=-2.
[ 23.634750] VbglR0HGCMInternalCall: vbglR0HGCMInternalDoCall failed. rc=-2
[ 23.634811] VBoxGuestCommonIOCtl: HGCM_CALL: 64 Failed. rc=-2.
[ 74.453037] VbglR0HGCMInternalCall: vbglR0HGCMInternalDoCall failed. rc=-2
[ 74.453097] VBoxGuestCommonIOCtl: HGCM_CALL: 64 Failed. rc=-2.
[ 84.274298] traps: gnome-shell[1140] general protection ip:7fd598a01524 sp:7ffc18e8c5b0 error:0 in libc-2.19.so[7fd598987000+19f000]
[ 84.514460] VbglR0HGCMInternalCall: vbglR0HGCMInternalDoCall failed. rc=-2
[ 84.514520] VBoxGuestCommonIOCtl: HGCM_CALL: 64 Failed. rc=-2.
[ 560.422192] atkbd serio0: Spurious NAK on isa0060/serio0. Some program might be trying to access hardware directly.
[ 600.336755] atkbd serio0: Spurious NAK on isa0060/serio0. Some program might be trying to access hardware directly.


debian-7 (where resize works as expected):

display log file:
vboxClientSetSignalHandlers:
vboxClientSetSignalHandlers: returning
initDisplay: testing dynamic resizing
initDisplay: dynamic resizing: result VINF_SUCCESS
initDisplay: enabling relative mouse re-capturing support
initDisplay: mouse re-capturing support: result VINF_SUCCESS
runDisplay:

seemless log file:
vboxClientSetSignalHandlers:
vboxClientSetSignalHandlers: returning
VBoxGuestSeamless::init:
VBoxGuestSeamlessHost::init:
VBoxGuestSeamlessHost::init: returning VINF_SUCCESS
VBoxGuestSeamlessX11::init:
VBoxGuestSeamlessX11::init: returning VINF_SUCCESS
VBoxGuestSeamlessHost::start:
VBoxClient: enabled seamless capability on host.
VBoxGuestThread::start: returning
VBoxGuestThread::start: returning VINF_SUCCESS
VBoxGuestSeamlessHost::start: returning VINF_SUCCESS
VBoxGuestSeamless::init: returning VINF_SUCCESS
VBoxGuestThread::threadFunction:
VBoxGuestSeamlessHostThread::threadFunction:
VBoxGuestSeamlessHost::nextEvent:

no error message in debian-7 dmesg. That said, this debian-7 is running 4.3.20 version of the guest addons. (My vbox host is 4.3.28)


I also compared the standard vm log file with a successful test on debian-7, but messages are the same. I think the issue is really in the VM itself.

I just tried with guest addons 4.3.28 on vbox 4.3.28 host and it still works.
I don't know what changed in debian between 7 and 8.