Auto-resize feature doesn't work on solaris guest -> configuration problem

[mn]

I have downloaded the source pack of 4.3.8 and its extention pack and wnt to install a Solaris 11.1 as guest. Problme is that after installing the guest additions, the auto-resize feature doesn't work so I can not use the whole diplay area for my guest. Here is the host information

$ uname -a Linux tiger 2.6.32-279.5.1.el6.x86_64 #1 SMP Tue Aug 14 16:11:42 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0- amd64:printing-4.0-noarch Distributor ID: Scientific Description: Scientific Linux release 6.3 (Carbon) Release: 6.3 Codename: Carbon

I used the following commands to build

$ ./configure --disable-hardening $ source ./env.sh $ kmk all

After several minutes it finished without any error Then I ran

$ cd out/linux.x86/release/bin/src $ make $ su # make install # modprobe vboxdrv # exit

Then I added myself to vboxusers and fixed the vboxdrv permission

# usermod -G vboxusers mahmood # chmod 766 /dev/vboxdrv # exit

Then as a normal user 'mahmood', I created a solaris 11.1 guest and installed the OS from live cd. Immediately after installing the Solaris, I mounted the VBoxAdditions and ran

Inside solaris: $ su # cd /media/VBOXADDITIONS_4.3.8_92456/ # pkgadd -G -d ./VBoxSolarisAdditions.pkg ...

It doesn't report any error so the guest additions were successfully installed. I rebooted the guest Solaris. After boot, maximizing the guest window has no effect? I can not use the whole diplay area for my guest.

All related log files are attached.

Please note that in the screenshot, the seamless feature is disabled however the showinfo.log says that seamless is active.

[mn]

The log files

[mn]

I have downloaded the source pack of 4.3.8 and its extention pack and wnt to install a Solaris 11.1 as guest. Problme is that after installing the guest additions, the auto-resize feature doesn't work so I can not use the whole diplay area for my guest. Here is the host information

$ uname -a Linux tiger 2.6.32-279.5.1.el6.x86_64 #1 SMP Tue Aug 14 16:11:42 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0- amd64:printing-4.0-noarch Distributor ID: Scientific Description: Scientific Linux release 6.3 (Carbon) Release: 6.3 Codename: Carbon

I used the following commands to build

$ ./configure --disable-hardening

$ source ./env.sh

$ kmk all

After several minutes it finished without any error Then I ran

$ cd out/linux.x86/release/bin/src

$ make

$ su

# make install

# modprobe vboxdrv

# exit

Then I added myself to vboxusers and fixed the vboxdrv permission

# usermod -G vboxusers mahmood

# chmod 766 /dev/vboxdrv

# exit

Then as a normal user 'mahmood', I created a solaris 11.1 guest and installed the OS from live cd. Immediately after installing the Solaris, I mounted the VBoxAdditions and ran

Inside solaris:

$ su

# cd /media/VBOXADDITIONS_4.3.8_92456/

# pkgadd -G -d ./VBoxSolarisAdditions.pkg ...

It doesn't report any error so the guest additions were successfully installed. I rebooted the guest Solaris. After boot, maximizing the guest window has no effect? I can not use the whole diplay area for my guest.

All related log files are attached. Please note that in the screenshot, the seamless feature is disabled however the showinfo.log says that seamless is active.

[mn]

I have downloaded the source pack of 4.3.8 and its extention pack and wnt to install a Solaris 11.1 as guest. Problme is that after installing the guest additions, the auto-resize feature doesn't work so I can not use the whole diplay area for my guest. Here is the host information

$ uname -a

Linux tiger 2.6.32-279.5.1.el6.x86_64 #1 SMP Tue Aug 14 16:11:42 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a

LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0- amd64:printing-4.0-noarch

Distributor ID: Scientific

Description: Scientific Linux release 6.3 (Carbon)

Release: 6.3

Codename: Carbon ==

I used the following commands to build

$ ./configure --disable-hardening

$ source ./env.sh

$ kmk all

After several minutes it finished without any error Then I ran

$ cd out/linux.x86/release/bin/src

$ make

$ su

# make install

# modprobe vboxdrv

# exit

Then I added myself to vboxusers and fixed the vboxdrv permission

# usermod -G vboxusers mahmood

# chmod 766 /dev/vboxdrv

# exit

Then as a normal user 'mahmood', I created a solaris 11.1 guest and installed the OS from live cd. Immediately after installing the Solaris, I mounted the VBoxAdditions and ran

Inside solaris:

$ su

# cd /media/VBOXADDITIONS_4.3.8_92456/

# pkgadd -G -d ./VBoxSolarisAdditions.pkg ...

It doesn't report any error so the guest additions were successfully installed. I rebooted the guest Solaris. After boot, maximizing the guest window has no effect? I can not use the whole diplay area for my guest.

All related log files are attached. Please note that in the screenshot, the seamless feature is disabled however the showinfo.log says that seamless is active.

[Michael Thayer]

Sounds to me like the VirtualBox video driver is not properly installed. Could you please attach the files "/var/log/Xorg.0.log" and if it exists "/etc/X11/xorg.conf" from the guest?

[mn]

I have attached two files

[Michael Thayer]

I'm afraid I can't remember the precise details of how this works, but I can see from the log file that you installed Solaris with an option which makes it always use the VESA driver through a special configuration file ("/usr/lib/X11/xorg.conf.vesa") and ignore "xorg.conf". That is why the VirtualBox video driver is not being loaded, despite being configured in "xorg.conf".

[mn]

Briliant. In the boot menu of the installation media, I chose VESA driver. I don't know why! I reinstall the Solaris and this time I chose the default boot option. After that by installing the additions, I see that the auto-resize feature works properly.

We had two days of discussion in the forum and lastly I thought it might be a bug. thanks.

[Michael Thayer]

Thanks for the feedback.