Increasing Screen Size/Resolution on a VirtualBox Instance of Centos
Clash Royale CLAN TAG#URR8PPP
up vote
22
down vote
favorite
I have VirtualBox instance of Centos 5. The screen size is quite small (800*600) and I'd like to increase it to 1280*1080. Under the Gnome preferences for "Screen Resolution" I only get the option for 600*800 or 640*480.
I've tried editing my xorg.conf (based on this tutorial http://paulsiu.wordpress.com/2008/09/08/creating-and-managing-centos-virtual-machine-under-virtualbox/) but it doesn't seem to have made a difference. Here is a snippet from the edited section:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800"
EndSubSection
EndSection
Does anyone know how to do this?
centos virtualbox display-settings
add a comment |
up vote
22
down vote
favorite
I have VirtualBox instance of Centos 5. The screen size is quite small (800*600) and I'd like to increase it to 1280*1080. Under the Gnome preferences for "Screen Resolution" I only get the option for 600*800 or 640*480.
I've tried editing my xorg.conf (based on this tutorial http://paulsiu.wordpress.com/2008/09/08/creating-and-managing-centos-virtual-machine-under-virtualbox/) but it doesn't seem to have made a difference. Here is a snippet from the edited section:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800"
EndSubSection
EndSection
Does anyone know how to do this?
centos virtualbox display-settings
1
How much video memory have you allocated to the graphics card in VB? Have you installed guest additions?
– Gilles
Nov 23 '11 at 23:42
According to the Device Manager it's the VirtualBox Graphics Adapter - looking into this now. EDIT - it looks like it may be an option under the Guest Additions (virtualbox.org/manual/ch04.html#idp11274368), so I'm looking into that now - thank you for the tip.
– Aaron Newton
Nov 23 '11 at 23:45
This seems to have solved my problem. For those looking for the ISO it is available here as VBoxGuestAdditions_4.1.6.iso - download.virtualbox.org/virtualbox/4.1.6. I mounted this using the VirtualBox Devices > CD/DVD > Choose DVD Disk File menu and ran "sh VboxLinuxAdditions.run" from the media/<nameofdisk> directory
– Aaron Newton
Nov 24 '11 at 1:31
add a comment |
up vote
22
down vote
favorite
up vote
22
down vote
favorite
I have VirtualBox instance of Centos 5. The screen size is quite small (800*600) and I'd like to increase it to 1280*1080. Under the Gnome preferences for "Screen Resolution" I only get the option for 600*800 or 640*480.
I've tried editing my xorg.conf (based on this tutorial http://paulsiu.wordpress.com/2008/09/08/creating-and-managing-centos-virtual-machine-under-virtualbox/) but it doesn't seem to have made a difference. Here is a snippet from the edited section:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800"
EndSubSection
EndSection
Does anyone know how to do this?
centos virtualbox display-settings
I have VirtualBox instance of Centos 5. The screen size is quite small (800*600) and I'd like to increase it to 1280*1080. Under the Gnome preferences for "Screen Resolution" I only get the option for 600*800 or 640*480.
I've tried editing my xorg.conf (based on this tutorial http://paulsiu.wordpress.com/2008/09/08/creating-and-managing-centos-virtual-machine-under-virtualbox/) but it doesn't seem to have made a difference. Here is a snippet from the edited section:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800"
EndSubSection
EndSection
Does anyone know how to do this?
centos virtualbox display-settings
centos virtualbox display-settings
edited Mar 10 '15 at 20:44
daveloyall
222110
222110
asked Nov 23 '11 at 23:36
Aaron Newton
245138
245138
1
How much video memory have you allocated to the graphics card in VB? Have you installed guest additions?
– Gilles
Nov 23 '11 at 23:42
According to the Device Manager it's the VirtualBox Graphics Adapter - looking into this now. EDIT - it looks like it may be an option under the Guest Additions (virtualbox.org/manual/ch04.html#idp11274368), so I'm looking into that now - thank you for the tip.
– Aaron Newton
Nov 23 '11 at 23:45
This seems to have solved my problem. For those looking for the ISO it is available here as VBoxGuestAdditions_4.1.6.iso - download.virtualbox.org/virtualbox/4.1.6. I mounted this using the VirtualBox Devices > CD/DVD > Choose DVD Disk File menu and ran "sh VboxLinuxAdditions.run" from the media/<nameofdisk> directory
– Aaron Newton
Nov 24 '11 at 1:31
add a comment |
1
How much video memory have you allocated to the graphics card in VB? Have you installed guest additions?
– Gilles
Nov 23 '11 at 23:42
According to the Device Manager it's the VirtualBox Graphics Adapter - looking into this now. EDIT - it looks like it may be an option under the Guest Additions (virtualbox.org/manual/ch04.html#idp11274368), so I'm looking into that now - thank you for the tip.
– Aaron Newton
Nov 23 '11 at 23:45
This seems to have solved my problem. For those looking for the ISO it is available here as VBoxGuestAdditions_4.1.6.iso - download.virtualbox.org/virtualbox/4.1.6. I mounted this using the VirtualBox Devices > CD/DVD > Choose DVD Disk File menu and ran "sh VboxLinuxAdditions.run" from the media/<nameofdisk> directory
– Aaron Newton
Nov 24 '11 at 1:31
1
1
How much video memory have you allocated to the graphics card in VB? Have you installed guest additions?
– Gilles
Nov 23 '11 at 23:42
How much video memory have you allocated to the graphics card in VB? Have you installed guest additions?
– Gilles
Nov 23 '11 at 23:42
According to the Device Manager it's the VirtualBox Graphics Adapter - looking into this now. EDIT - it looks like it may be an option under the Guest Additions (virtualbox.org/manual/ch04.html#idp11274368), so I'm looking into that now - thank you for the tip.
– Aaron Newton
Nov 23 '11 at 23:45
According to the Device Manager it's the VirtualBox Graphics Adapter - looking into this now. EDIT - it looks like it may be an option under the Guest Additions (virtualbox.org/manual/ch04.html#idp11274368), so I'm looking into that now - thank you for the tip.
– Aaron Newton
Nov 23 '11 at 23:45
This seems to have solved my problem. For those looking for the ISO it is available here as VBoxGuestAdditions_4.1.6.iso - download.virtualbox.org/virtualbox/4.1.6. I mounted this using the VirtualBox Devices > CD/DVD > Choose DVD Disk File menu and ran "sh VboxLinuxAdditions.run" from the media/<nameofdisk> directory
– Aaron Newton
Nov 24 '11 at 1:31
This seems to have solved my problem. For those looking for the ISO it is available here as VBoxGuestAdditions_4.1.6.iso - download.virtualbox.org/virtualbox/4.1.6. I mounted this using the VirtualBox Devices > CD/DVD > Choose DVD Disk File menu and ran "sh VboxLinuxAdditions.run" from the media/<nameofdisk> directory
– Aaron Newton
Nov 24 '11 at 1:31
add a comment |
6 Answers
6
active
oldest
votes
up vote
20
down vote
accepted
A maximum resolution of 800x600 suggests that your X server inside the virtual machine is using the SVGA driver. SVGA is the highest resolution for which there is standard support; beyond that, you need a driver.
VirtualBox emulates a graphics adapter that is specific to VirtualBox, it does not emulate a previously existing hardware component like most other subsystems. The guest additions include a driver for that adapter. Insert the guest additions CD from the VirtualBox device menu, then run the installation program. Log out, restart the X server (send Ctrl+Alt+Backspace
from the VirtualBox menu), and you should have a screen resolution that matches your VirtualBox window. If you find that you still need manual tweaking of your xorg.conf
, the manual has some pointers.
There's a limit to how high you can get, due to the amount of memory you've allocated to the graphics adapter in the VirtualBox configuration. 8MB will give you up to 1600x1200 in 32 colors. Going beyond that is mostly useful if you use 3D.
Thank you - marked as the correct answer as installing the VirtualBox Guest additions seems to have solved my problem. See my note above if you don't have the installation CDs.
– Aaron Newton
Nov 24 '11 at 1:55
1
I just followed this answer to fix the same problem with CentOS 7. I had to install kernel headers beforeautorun.sh
in the Guest Additions cd would work. The error message fromautorun.sh
gives the names of the packages to install withyum
. After installing Guest Additions, I just restarted the VM, and the problem is magically fixed.
– Michael Hoffmann
Nov 30 '17 at 18:20
add a comment |
up vote
4
down vote
I had the same problems with different setup:
Host OS: Linux Mint 17 Cinnamon 64-bit
Guest OS: Centos 6.6
Virtualbox: Oracle VM VirtualBox Manager 4.3.10_Ubuntu
Solution which worked for me:
Install Virtualbox --> Devices, Insert Guest Additions CD image
[root@centos6 ~]# cd /media/VBOXADDITIONS_4.3.10_93012/
./VBoxLinuxAdditions.runget custom resolution string:
[root@centos6 ~]$ cvt 1600 900
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsyncset custom resolution string:
[root@centos6 ~]$ xrandr
Screen 0: minimum 64 x 64, current 1024 x 768, maximum 16384 x 16384
VBOX0 connected 1024x768+0+0 0mm x 0mm
1024x768 60.0*+ 60.0*
1600x1200 60.0
1440x1050 60.0
1280x960 60.0
800x600 60.0
640x480 60.0
[root@centos6 ~]$ xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
[root@centos6 ~]$ xrandr --addmode VBOX0 "1600x900_60.00"use normal system administration config dialog to change resolution to 1600 x 900 which was not available before.
HTH,
Magnus
Please set your profile name, and remove the signature under your answer, that is the recommended way to "identify" yourself on this site. (I.e. keep Answers and Questions crisp)
– Anthon
Jan 3 '15 at 19:43
in centos 6 - after restarting the guest additional size options appeared and were made available to use successfully without adding a custom resolution.
– Ross
Dec 31 '15 at 4:57
add a comment |
up vote
1
down vote
You need Virtual Box guest extensions.
In order to install them you first need the RPMForge repository added for yum, follow these instructions:
http://wiki.centos.org/AdditionalResources/Repositories/RPMForge#head-5aabf02717d5b6b12d47edbc5811404998926a1b
Then run this command in a terminal:
yum install dkms
Thank you, but I already marked this as the answer last November.
– Aaron Newton
May 2 '13 at 12:49
3
@AaronNewton, I totally understand. I just had to go through more research to get it working for me. If I have to do that, I usually post. Not to answer your question as much to maybe help out someone else that comes along and has the same questions with the accepted answer as I did.
– Beachhouse
May 2 '13 at 15:17
add a comment |
up vote
0
down vote
In my case (virtualbox 5
+ centos 7
), all I did is install the "Guest additional cd image", then restart the vm, and make it full screen when start, it automatically take the biggest resolution.
I think u might forget to reboot or didn't full screen it via host + F
.
add a comment |
up vote
0
down vote
My virtual machine suddenly no longer supported full-screen.
Eventually, the fix was easy: I had to update to the newest version of VirtualBox, then re-install the newest version of Guest Additions. After doing that then restarting my VM, the resolution was automatically the correct (full-screen) size.
add a comment |
up vote
0
down vote
on CentOS 7.5 on VirtualBox 5.2.22 the solution was:
- install VirtualBox Additions
create a kernel module configuration file for the module "vboxvideo". Without the "modeset" parameter the module fails to load.
echo "options vboxvideo modeset=1" > /etc/modprobe.d/vboxvideo.conf
- reboot
New contributor
add a comment |
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
20
down vote
accepted
A maximum resolution of 800x600 suggests that your X server inside the virtual machine is using the SVGA driver. SVGA is the highest resolution for which there is standard support; beyond that, you need a driver.
VirtualBox emulates a graphics adapter that is specific to VirtualBox, it does not emulate a previously existing hardware component like most other subsystems. The guest additions include a driver for that adapter. Insert the guest additions CD from the VirtualBox device menu, then run the installation program. Log out, restart the X server (send Ctrl+Alt+Backspace
from the VirtualBox menu), and you should have a screen resolution that matches your VirtualBox window. If you find that you still need manual tweaking of your xorg.conf
, the manual has some pointers.
There's a limit to how high you can get, due to the amount of memory you've allocated to the graphics adapter in the VirtualBox configuration. 8MB will give you up to 1600x1200 in 32 colors. Going beyond that is mostly useful if you use 3D.
Thank you - marked as the correct answer as installing the VirtualBox Guest additions seems to have solved my problem. See my note above if you don't have the installation CDs.
– Aaron Newton
Nov 24 '11 at 1:55
1
I just followed this answer to fix the same problem with CentOS 7. I had to install kernel headers beforeautorun.sh
in the Guest Additions cd would work. The error message fromautorun.sh
gives the names of the packages to install withyum
. After installing Guest Additions, I just restarted the VM, and the problem is magically fixed.
– Michael Hoffmann
Nov 30 '17 at 18:20
add a comment |
up vote
20
down vote
accepted
A maximum resolution of 800x600 suggests that your X server inside the virtual machine is using the SVGA driver. SVGA is the highest resolution for which there is standard support; beyond that, you need a driver.
VirtualBox emulates a graphics adapter that is specific to VirtualBox, it does not emulate a previously existing hardware component like most other subsystems. The guest additions include a driver for that adapter. Insert the guest additions CD from the VirtualBox device menu, then run the installation program. Log out, restart the X server (send Ctrl+Alt+Backspace
from the VirtualBox menu), and you should have a screen resolution that matches your VirtualBox window. If you find that you still need manual tweaking of your xorg.conf
, the manual has some pointers.
There's a limit to how high you can get, due to the amount of memory you've allocated to the graphics adapter in the VirtualBox configuration. 8MB will give you up to 1600x1200 in 32 colors. Going beyond that is mostly useful if you use 3D.
Thank you - marked as the correct answer as installing the VirtualBox Guest additions seems to have solved my problem. See my note above if you don't have the installation CDs.
– Aaron Newton
Nov 24 '11 at 1:55
1
I just followed this answer to fix the same problem with CentOS 7. I had to install kernel headers beforeautorun.sh
in the Guest Additions cd would work. The error message fromautorun.sh
gives the names of the packages to install withyum
. After installing Guest Additions, I just restarted the VM, and the problem is magically fixed.
– Michael Hoffmann
Nov 30 '17 at 18:20
add a comment |
up vote
20
down vote
accepted
up vote
20
down vote
accepted
A maximum resolution of 800x600 suggests that your X server inside the virtual machine is using the SVGA driver. SVGA is the highest resolution for which there is standard support; beyond that, you need a driver.
VirtualBox emulates a graphics adapter that is specific to VirtualBox, it does not emulate a previously existing hardware component like most other subsystems. The guest additions include a driver for that adapter. Insert the guest additions CD from the VirtualBox device menu, then run the installation program. Log out, restart the X server (send Ctrl+Alt+Backspace
from the VirtualBox menu), and you should have a screen resolution that matches your VirtualBox window. If you find that you still need manual tweaking of your xorg.conf
, the manual has some pointers.
There's a limit to how high you can get, due to the amount of memory you've allocated to the graphics adapter in the VirtualBox configuration. 8MB will give you up to 1600x1200 in 32 colors. Going beyond that is mostly useful if you use 3D.
A maximum resolution of 800x600 suggests that your X server inside the virtual machine is using the SVGA driver. SVGA is the highest resolution for which there is standard support; beyond that, you need a driver.
VirtualBox emulates a graphics adapter that is specific to VirtualBox, it does not emulate a previously existing hardware component like most other subsystems. The guest additions include a driver for that adapter. Insert the guest additions CD from the VirtualBox device menu, then run the installation program. Log out, restart the X server (send Ctrl+Alt+Backspace
from the VirtualBox menu), and you should have a screen resolution that matches your VirtualBox window. If you find that you still need manual tweaking of your xorg.conf
, the manual has some pointers.
There's a limit to how high you can get, due to the amount of memory you've allocated to the graphics adapter in the VirtualBox configuration. 8MB will give you up to 1600x1200 in 32 colors. Going beyond that is mostly useful if you use 3D.
answered Nov 24 '11 at 1:44
Gilles
522k12610401570
522k12610401570
Thank you - marked as the correct answer as installing the VirtualBox Guest additions seems to have solved my problem. See my note above if you don't have the installation CDs.
– Aaron Newton
Nov 24 '11 at 1:55
1
I just followed this answer to fix the same problem with CentOS 7. I had to install kernel headers beforeautorun.sh
in the Guest Additions cd would work. The error message fromautorun.sh
gives the names of the packages to install withyum
. After installing Guest Additions, I just restarted the VM, and the problem is magically fixed.
– Michael Hoffmann
Nov 30 '17 at 18:20
add a comment |
Thank you - marked as the correct answer as installing the VirtualBox Guest additions seems to have solved my problem. See my note above if you don't have the installation CDs.
– Aaron Newton
Nov 24 '11 at 1:55
1
I just followed this answer to fix the same problem with CentOS 7. I had to install kernel headers beforeautorun.sh
in the Guest Additions cd would work. The error message fromautorun.sh
gives the names of the packages to install withyum
. After installing Guest Additions, I just restarted the VM, and the problem is magically fixed.
– Michael Hoffmann
Nov 30 '17 at 18:20
Thank you - marked as the correct answer as installing the VirtualBox Guest additions seems to have solved my problem. See my note above if you don't have the installation CDs.
– Aaron Newton
Nov 24 '11 at 1:55
Thank you - marked as the correct answer as installing the VirtualBox Guest additions seems to have solved my problem. See my note above if you don't have the installation CDs.
– Aaron Newton
Nov 24 '11 at 1:55
1
1
I just followed this answer to fix the same problem with CentOS 7. I had to install kernel headers before
autorun.sh
in the Guest Additions cd would work. The error message from autorun.sh
gives the names of the packages to install with yum
. After installing Guest Additions, I just restarted the VM, and the problem is magically fixed.– Michael Hoffmann
Nov 30 '17 at 18:20
I just followed this answer to fix the same problem with CentOS 7. I had to install kernel headers before
autorun.sh
in the Guest Additions cd would work. The error message from autorun.sh
gives the names of the packages to install with yum
. After installing Guest Additions, I just restarted the VM, and the problem is magically fixed.– Michael Hoffmann
Nov 30 '17 at 18:20
add a comment |
up vote
4
down vote
I had the same problems with different setup:
Host OS: Linux Mint 17 Cinnamon 64-bit
Guest OS: Centos 6.6
Virtualbox: Oracle VM VirtualBox Manager 4.3.10_Ubuntu
Solution which worked for me:
Install Virtualbox --> Devices, Insert Guest Additions CD image
[root@centos6 ~]# cd /media/VBOXADDITIONS_4.3.10_93012/
./VBoxLinuxAdditions.runget custom resolution string:
[root@centos6 ~]$ cvt 1600 900
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsyncset custom resolution string:
[root@centos6 ~]$ xrandr
Screen 0: minimum 64 x 64, current 1024 x 768, maximum 16384 x 16384
VBOX0 connected 1024x768+0+0 0mm x 0mm
1024x768 60.0*+ 60.0*
1600x1200 60.0
1440x1050 60.0
1280x960 60.0
800x600 60.0
640x480 60.0
[root@centos6 ~]$ xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
[root@centos6 ~]$ xrandr --addmode VBOX0 "1600x900_60.00"use normal system administration config dialog to change resolution to 1600 x 900 which was not available before.
HTH,
Magnus
Please set your profile name, and remove the signature under your answer, that is the recommended way to "identify" yourself on this site. (I.e. keep Answers and Questions crisp)
– Anthon
Jan 3 '15 at 19:43
in centos 6 - after restarting the guest additional size options appeared and were made available to use successfully without adding a custom resolution.
– Ross
Dec 31 '15 at 4:57
add a comment |
up vote
4
down vote
I had the same problems with different setup:
Host OS: Linux Mint 17 Cinnamon 64-bit
Guest OS: Centos 6.6
Virtualbox: Oracle VM VirtualBox Manager 4.3.10_Ubuntu
Solution which worked for me:
Install Virtualbox --> Devices, Insert Guest Additions CD image
[root@centos6 ~]# cd /media/VBOXADDITIONS_4.3.10_93012/
./VBoxLinuxAdditions.runget custom resolution string:
[root@centos6 ~]$ cvt 1600 900
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsyncset custom resolution string:
[root@centos6 ~]$ xrandr
Screen 0: minimum 64 x 64, current 1024 x 768, maximum 16384 x 16384
VBOX0 connected 1024x768+0+0 0mm x 0mm
1024x768 60.0*+ 60.0*
1600x1200 60.0
1440x1050 60.0
1280x960 60.0
800x600 60.0
640x480 60.0
[root@centos6 ~]$ xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
[root@centos6 ~]$ xrandr --addmode VBOX0 "1600x900_60.00"use normal system administration config dialog to change resolution to 1600 x 900 which was not available before.
HTH,
Magnus
Please set your profile name, and remove the signature under your answer, that is the recommended way to "identify" yourself on this site. (I.e. keep Answers and Questions crisp)
– Anthon
Jan 3 '15 at 19:43
in centos 6 - after restarting the guest additional size options appeared and were made available to use successfully without adding a custom resolution.
– Ross
Dec 31 '15 at 4:57
add a comment |
up vote
4
down vote
up vote
4
down vote
I had the same problems with different setup:
Host OS: Linux Mint 17 Cinnamon 64-bit
Guest OS: Centos 6.6
Virtualbox: Oracle VM VirtualBox Manager 4.3.10_Ubuntu
Solution which worked for me:
Install Virtualbox --> Devices, Insert Guest Additions CD image
[root@centos6 ~]# cd /media/VBOXADDITIONS_4.3.10_93012/
./VBoxLinuxAdditions.runget custom resolution string:
[root@centos6 ~]$ cvt 1600 900
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsyncset custom resolution string:
[root@centos6 ~]$ xrandr
Screen 0: minimum 64 x 64, current 1024 x 768, maximum 16384 x 16384
VBOX0 connected 1024x768+0+0 0mm x 0mm
1024x768 60.0*+ 60.0*
1600x1200 60.0
1440x1050 60.0
1280x960 60.0
800x600 60.0
640x480 60.0
[root@centos6 ~]$ xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
[root@centos6 ~]$ xrandr --addmode VBOX0 "1600x900_60.00"use normal system administration config dialog to change resolution to 1600 x 900 which was not available before.
HTH,
Magnus
I had the same problems with different setup:
Host OS: Linux Mint 17 Cinnamon 64-bit
Guest OS: Centos 6.6
Virtualbox: Oracle VM VirtualBox Manager 4.3.10_Ubuntu
Solution which worked for me:
Install Virtualbox --> Devices, Insert Guest Additions CD image
[root@centos6 ~]# cd /media/VBOXADDITIONS_4.3.10_93012/
./VBoxLinuxAdditions.runget custom resolution string:
[root@centos6 ~]$ cvt 1600 900
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsyncset custom resolution string:
[root@centos6 ~]$ xrandr
Screen 0: minimum 64 x 64, current 1024 x 768, maximum 16384 x 16384
VBOX0 connected 1024x768+0+0 0mm x 0mm
1024x768 60.0*+ 60.0*
1600x1200 60.0
1440x1050 60.0
1280x960 60.0
800x600 60.0
640x480 60.0
[root@centos6 ~]$ xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
[root@centos6 ~]$ xrandr --addmode VBOX0 "1600x900_60.00"use normal system administration config dialog to change resolution to 1600 x 900 which was not available before.
HTH,
Magnus
edited Jan 24 at 20:52
Community♦
1
1
answered Jan 3 '15 at 19:26
user96914
411
411
Please set your profile name, and remove the signature under your answer, that is the recommended way to "identify" yourself on this site. (I.e. keep Answers and Questions crisp)
– Anthon
Jan 3 '15 at 19:43
in centos 6 - after restarting the guest additional size options appeared and were made available to use successfully without adding a custom resolution.
– Ross
Dec 31 '15 at 4:57
add a comment |
Please set your profile name, and remove the signature under your answer, that is the recommended way to "identify" yourself on this site. (I.e. keep Answers and Questions crisp)
– Anthon
Jan 3 '15 at 19:43
in centos 6 - after restarting the guest additional size options appeared and were made available to use successfully without adding a custom resolution.
– Ross
Dec 31 '15 at 4:57
Please set your profile name, and remove the signature under your answer, that is the recommended way to "identify" yourself on this site. (I.e. keep Answers and Questions crisp)
– Anthon
Jan 3 '15 at 19:43
Please set your profile name, and remove the signature under your answer, that is the recommended way to "identify" yourself on this site. (I.e. keep Answers and Questions crisp)
– Anthon
Jan 3 '15 at 19:43
in centos 6 - after restarting the guest additional size options appeared and were made available to use successfully without adding a custom resolution.
– Ross
Dec 31 '15 at 4:57
in centos 6 - after restarting the guest additional size options appeared and were made available to use successfully without adding a custom resolution.
– Ross
Dec 31 '15 at 4:57
add a comment |
up vote
1
down vote
You need Virtual Box guest extensions.
In order to install them you first need the RPMForge repository added for yum, follow these instructions:
http://wiki.centos.org/AdditionalResources/Repositories/RPMForge#head-5aabf02717d5b6b12d47edbc5811404998926a1b
Then run this command in a terminal:
yum install dkms
Thank you, but I already marked this as the answer last November.
– Aaron Newton
May 2 '13 at 12:49
3
@AaronNewton, I totally understand. I just had to go through more research to get it working for me. If I have to do that, I usually post. Not to answer your question as much to maybe help out someone else that comes along and has the same questions with the accepted answer as I did.
– Beachhouse
May 2 '13 at 15:17
add a comment |
up vote
1
down vote
You need Virtual Box guest extensions.
In order to install them you first need the RPMForge repository added for yum, follow these instructions:
http://wiki.centos.org/AdditionalResources/Repositories/RPMForge#head-5aabf02717d5b6b12d47edbc5811404998926a1b
Then run this command in a terminal:
yum install dkms
Thank you, but I already marked this as the answer last November.
– Aaron Newton
May 2 '13 at 12:49
3
@AaronNewton, I totally understand. I just had to go through more research to get it working for me. If I have to do that, I usually post. Not to answer your question as much to maybe help out someone else that comes along and has the same questions with the accepted answer as I did.
– Beachhouse
May 2 '13 at 15:17
add a comment |
up vote
1
down vote
up vote
1
down vote
You need Virtual Box guest extensions.
In order to install them you first need the RPMForge repository added for yum, follow these instructions:
http://wiki.centos.org/AdditionalResources/Repositories/RPMForge#head-5aabf02717d5b6b12d47edbc5811404998926a1b
Then run this command in a terminal:
yum install dkms
You need Virtual Box guest extensions.
In order to install them you first need the RPMForge repository added for yum, follow these instructions:
http://wiki.centos.org/AdditionalResources/Repositories/RPMForge#head-5aabf02717d5b6b12d47edbc5811404998926a1b
Then run this command in a terminal:
yum install dkms
answered May 1 '13 at 16:38
Beachhouse
13519
13519
Thank you, but I already marked this as the answer last November.
– Aaron Newton
May 2 '13 at 12:49
3
@AaronNewton, I totally understand. I just had to go through more research to get it working for me. If I have to do that, I usually post. Not to answer your question as much to maybe help out someone else that comes along and has the same questions with the accepted answer as I did.
– Beachhouse
May 2 '13 at 15:17
add a comment |
Thank you, but I already marked this as the answer last November.
– Aaron Newton
May 2 '13 at 12:49
3
@AaronNewton, I totally understand. I just had to go through more research to get it working for me. If I have to do that, I usually post. Not to answer your question as much to maybe help out someone else that comes along and has the same questions with the accepted answer as I did.
– Beachhouse
May 2 '13 at 15:17
Thank you, but I already marked this as the answer last November.
– Aaron Newton
May 2 '13 at 12:49
Thank you, but I already marked this as the answer last November.
– Aaron Newton
May 2 '13 at 12:49
3
3
@AaronNewton, I totally understand. I just had to go through more research to get it working for me. If I have to do that, I usually post. Not to answer your question as much to maybe help out someone else that comes along and has the same questions with the accepted answer as I did.
– Beachhouse
May 2 '13 at 15:17
@AaronNewton, I totally understand. I just had to go through more research to get it working for me. If I have to do that, I usually post. Not to answer your question as much to maybe help out someone else that comes along and has the same questions with the accepted answer as I did.
– Beachhouse
May 2 '13 at 15:17
add a comment |
up vote
0
down vote
In my case (virtualbox 5
+ centos 7
), all I did is install the "Guest additional cd image", then restart the vm, and make it full screen when start, it automatically take the biggest resolution.
I think u might forget to reboot or didn't full screen it via host + F
.
add a comment |
up vote
0
down vote
In my case (virtualbox 5
+ centos 7
), all I did is install the "Guest additional cd image", then restart the vm, and make it full screen when start, it automatically take the biggest resolution.
I think u might forget to reboot or didn't full screen it via host + F
.
add a comment |
up vote
0
down vote
up vote
0
down vote
In my case (virtualbox 5
+ centos 7
), all I did is install the "Guest additional cd image", then restart the vm, and make it full screen when start, it automatically take the biggest resolution.
I think u might forget to reboot or didn't full screen it via host + F
.
In my case (virtualbox 5
+ centos 7
), all I did is install the "Guest additional cd image", then restart the vm, and make it full screen when start, it automatically take the biggest resolution.
I think u might forget to reboot or didn't full screen it via host + F
.
answered Oct 30 '15 at 16:44
Eric Wang
18418
18418
add a comment |
add a comment |
up vote
0
down vote
My virtual machine suddenly no longer supported full-screen.
Eventually, the fix was easy: I had to update to the newest version of VirtualBox, then re-install the newest version of Guest Additions. After doing that then restarting my VM, the resolution was automatically the correct (full-screen) size.
add a comment |
up vote
0
down vote
My virtual machine suddenly no longer supported full-screen.
Eventually, the fix was easy: I had to update to the newest version of VirtualBox, then re-install the newest version of Guest Additions. After doing that then restarting my VM, the resolution was automatically the correct (full-screen) size.
add a comment |
up vote
0
down vote
up vote
0
down vote
My virtual machine suddenly no longer supported full-screen.
Eventually, the fix was easy: I had to update to the newest version of VirtualBox, then re-install the newest version of Guest Additions. After doing that then restarting my VM, the resolution was automatically the correct (full-screen) size.
My virtual machine suddenly no longer supported full-screen.
Eventually, the fix was easy: I had to update to the newest version of VirtualBox, then re-install the newest version of Guest Additions. After doing that then restarting my VM, the resolution was automatically the correct (full-screen) size.
answered Nov 7 '17 at 23:17
marmot 1333
213
213
add a comment |
add a comment |
up vote
0
down vote
on CentOS 7.5 on VirtualBox 5.2.22 the solution was:
- install VirtualBox Additions
create a kernel module configuration file for the module "vboxvideo". Without the "modeset" parameter the module fails to load.
echo "options vboxvideo modeset=1" > /etc/modprobe.d/vboxvideo.conf
- reboot
New contributor
add a comment |
up vote
0
down vote
on CentOS 7.5 on VirtualBox 5.2.22 the solution was:
- install VirtualBox Additions
create a kernel module configuration file for the module "vboxvideo". Without the "modeset" parameter the module fails to load.
echo "options vboxvideo modeset=1" > /etc/modprobe.d/vboxvideo.conf
- reboot
New contributor
add a comment |
up vote
0
down vote
up vote
0
down vote
on CentOS 7.5 on VirtualBox 5.2.22 the solution was:
- install VirtualBox Additions
create a kernel module configuration file for the module "vboxvideo". Without the "modeset" parameter the module fails to load.
echo "options vboxvideo modeset=1" > /etc/modprobe.d/vboxvideo.conf
- reboot
New contributor
on CentOS 7.5 on VirtualBox 5.2.22 the solution was:
- install VirtualBox Additions
create a kernel module configuration file for the module "vboxvideo". Without the "modeset" parameter the module fails to load.
echo "options vboxvideo modeset=1" > /etc/modprobe.d/vboxvideo.conf
- reboot
New contributor
New contributor
answered Nov 20 at 16:34
sleif
11
11
New contributor
New contributor
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f25236%2fincreasing-screen-size-resolution-on-a-virtualbox-instance-of-centos%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
How much video memory have you allocated to the graphics card in VB? Have you installed guest additions?
– Gilles
Nov 23 '11 at 23:42
According to the Device Manager it's the VirtualBox Graphics Adapter - looking into this now. EDIT - it looks like it may be an option under the Guest Additions (virtualbox.org/manual/ch04.html#idp11274368), so I'm looking into that now - thank you for the tip.
– Aaron Newton
Nov 23 '11 at 23:45
This seems to have solved my problem. For those looking for the ISO it is available here as VBoxGuestAdditions_4.1.6.iso - download.virtualbox.org/virtualbox/4.1.6. I mounted this using the VirtualBox Devices > CD/DVD > Choose DVD Disk File menu and ran "sh VboxLinuxAdditions.run" from the media/<nameofdisk> directory
– Aaron Newton
Nov 24 '11 at 1:31