How do I adjust the screen resolution for my Debian 8.1 64-bit VirtualBox machine?Setting Framebuffer splash...
Was US film used in Luna 3?
What rules turn any attack that hits a given target into a critical hit?
Why can't a country print its own money to spend it only abroad?
5V/12V load balance of 3.5'' HDD?
The seven story archetypes. Are they truly all of them?
What is "ass door"?
Killing a star safely
How does mathematics work?
If I have the Armor of Shadows Eldritch Invocation do I know the Mage Armor spell?
Extrapolation v. Interpolation
Can I pay with HKD in Macau or Shenzhen?
Why did computer video outputs go from digital to analog, then back to digital?
On the history of Haar measure
Is it OK to accept a job opportunity while planning on not taking it?
Why are Oscar, India, and X-Ray (O, I, and X) not used as taxiway identifiers?
How can Kazakhstan perform MITM attacks on all HTTPS traffic?
Adding one more column to a table
Short story where a flexible reality hardens to an unchanging one
What is the best word describing the nature of expiring in a short amount of time, connoting "losing public attention"?
Why do people say "I am broke" instead of "I am broken"?
ExactlyOne extension method
Can't understand how static works exactly
How could Barty Crouch Jr. have run out of Polyjuice Potion at the end of the Goblet of Fire movie?
Is an easily guessed plot twist a good plot twist?
How do I adjust the screen resolution for my Debian 8.1 64-bit VirtualBox machine?
Setting Framebuffer splash resolution when exiting XScreen resolution problem in Fedora 17 on Oracle VirtualBox 4.2Fedora 18 VirtualBox Resolution Guest AdditionsAccessing file from the Windows host in a VirtualBox virtual machineHow do I write a Bash script to autoadjust the screen resolution of Enlightenment 20 running under VirtualBox?Bad secondary monitor resolutionCentOS7 server VirtualBox guest on Ubuntu 15.10 screen issueAdjust screen resolution scaling in Lumina desktop of TrueOSTrying to install Guest Additions in Fedora 24Alpine Linux VirtualBox VM With xfce4 Desktop Not Able to Use Full Screen Resolution
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I would like to adjust the screen resolution for my Debian 8.1 Virtual Machine (running in VirtualBox 5 on 64-bit Windows 10) from 1024x768 to 1366x768 (which for me would be full screen). Neither "Seamless Mode" nor "Auto-resize Guest Display" options are allowed under the, "View" drop-down menu. I have six other Virtual machines installed on my PC, for each of the following OSs (each 64-bit):
- Fedora 22
- Linux Mint 17.2
- Mageia 5
- Manjaro Linux 0.8.13.1
- openSUSE 13.2
- Sabayon Linux 15.08
all but the Fedora 22 machine runs seamless mode just fine (i.e., full screen occupies all 1366x768 pixels of my screen and not just 1024x768 of it). Fedora 22 has the same issue as Debian: it runs 1024x768 screen resolution, when it is supposed to be occupying the whole screen. I have attempted to change the screen resolution from within the guest machine itself, but I notice for both Debian and Fedora 1024x768 is the largest display they are allowing. If you are wondering why I am mentioning this Fedora glitch, it is in case it helps you in solving my problem with my Debian machine, this question is just about the Debian machine (although if your answer is applicable to the Fedora machine too a brief mention of this fact would be appreciated). I have installed the Oracle VM VirtualBox Extension Pack (version 5.0.0r101573), if you are wondering. I have enabled 3D acceleration and bidirectional clipboard (although the clipboard does not appear to be working for either machine) with 64 MB display memory, 4096 MB RAM, 64 GB HDD (for Debian, that is; Fedora is using 128 GB) and any other helpful detail I will be happy to provide. Keep in mind my programming and technical knowledge is limited, so please keep the technical discourse in your answer to a minimum.
debian virtualbox resolution display-settings
add a comment |
I would like to adjust the screen resolution for my Debian 8.1 Virtual Machine (running in VirtualBox 5 on 64-bit Windows 10) from 1024x768 to 1366x768 (which for me would be full screen). Neither "Seamless Mode" nor "Auto-resize Guest Display" options are allowed under the, "View" drop-down menu. I have six other Virtual machines installed on my PC, for each of the following OSs (each 64-bit):
- Fedora 22
- Linux Mint 17.2
- Mageia 5
- Manjaro Linux 0.8.13.1
- openSUSE 13.2
- Sabayon Linux 15.08
all but the Fedora 22 machine runs seamless mode just fine (i.e., full screen occupies all 1366x768 pixels of my screen and not just 1024x768 of it). Fedora 22 has the same issue as Debian: it runs 1024x768 screen resolution, when it is supposed to be occupying the whole screen. I have attempted to change the screen resolution from within the guest machine itself, but I notice for both Debian and Fedora 1024x768 is the largest display they are allowing. If you are wondering why I am mentioning this Fedora glitch, it is in case it helps you in solving my problem with my Debian machine, this question is just about the Debian machine (although if your answer is applicable to the Fedora machine too a brief mention of this fact would be appreciated). I have installed the Oracle VM VirtualBox Extension Pack (version 5.0.0r101573), if you are wondering. I have enabled 3D acceleration and bidirectional clipboard (although the clipboard does not appear to be working for either machine) with 64 MB display memory, 4096 MB RAM, 64 GB HDD (for Debian, that is; Fedora is using 128 GB) and any other helpful detail I will be happy to provide. Keep in mind my programming and technical knowledge is limited, so please keep the technical discourse in your answer to a minimum.
debian virtualbox resolution display-settings
add a comment |
I would like to adjust the screen resolution for my Debian 8.1 Virtual Machine (running in VirtualBox 5 on 64-bit Windows 10) from 1024x768 to 1366x768 (which for me would be full screen). Neither "Seamless Mode" nor "Auto-resize Guest Display" options are allowed under the, "View" drop-down menu. I have six other Virtual machines installed on my PC, for each of the following OSs (each 64-bit):
- Fedora 22
- Linux Mint 17.2
- Mageia 5
- Manjaro Linux 0.8.13.1
- openSUSE 13.2
- Sabayon Linux 15.08
all but the Fedora 22 machine runs seamless mode just fine (i.e., full screen occupies all 1366x768 pixels of my screen and not just 1024x768 of it). Fedora 22 has the same issue as Debian: it runs 1024x768 screen resolution, when it is supposed to be occupying the whole screen. I have attempted to change the screen resolution from within the guest machine itself, but I notice for both Debian and Fedora 1024x768 is the largest display they are allowing. If you are wondering why I am mentioning this Fedora glitch, it is in case it helps you in solving my problem with my Debian machine, this question is just about the Debian machine (although if your answer is applicable to the Fedora machine too a brief mention of this fact would be appreciated). I have installed the Oracle VM VirtualBox Extension Pack (version 5.0.0r101573), if you are wondering. I have enabled 3D acceleration and bidirectional clipboard (although the clipboard does not appear to be working for either machine) with 64 MB display memory, 4096 MB RAM, 64 GB HDD (for Debian, that is; Fedora is using 128 GB) and any other helpful detail I will be happy to provide. Keep in mind my programming and technical knowledge is limited, so please keep the technical discourse in your answer to a minimum.
debian virtualbox resolution display-settings
I would like to adjust the screen resolution for my Debian 8.1 Virtual Machine (running in VirtualBox 5 on 64-bit Windows 10) from 1024x768 to 1366x768 (which for me would be full screen). Neither "Seamless Mode" nor "Auto-resize Guest Display" options are allowed under the, "View" drop-down menu. I have six other Virtual machines installed on my PC, for each of the following OSs (each 64-bit):
- Fedora 22
- Linux Mint 17.2
- Mageia 5
- Manjaro Linux 0.8.13.1
- openSUSE 13.2
- Sabayon Linux 15.08
all but the Fedora 22 machine runs seamless mode just fine (i.e., full screen occupies all 1366x768 pixels of my screen and not just 1024x768 of it). Fedora 22 has the same issue as Debian: it runs 1024x768 screen resolution, when it is supposed to be occupying the whole screen. I have attempted to change the screen resolution from within the guest machine itself, but I notice for both Debian and Fedora 1024x768 is the largest display they are allowing. If you are wondering why I am mentioning this Fedora glitch, it is in case it helps you in solving my problem with my Debian machine, this question is just about the Debian machine (although if your answer is applicable to the Fedora machine too a brief mention of this fact would be appreciated). I have installed the Oracle VM VirtualBox Extension Pack (version 5.0.0r101573), if you are wondering. I have enabled 3D acceleration and bidirectional clipboard (although the clipboard does not appear to be working for either machine) with 64 MB display memory, 4096 MB RAM, 64 GB HDD (for Debian, that is; Fedora is using 128 GB) and any other helpful detail I will be happy to provide. Keep in mind my programming and technical knowledge is limited, so please keep the technical discourse in your answer to a minimum.
debian virtualbox resolution display-settings
debian virtualbox resolution display-settings
asked Aug 12 '15 at 3:37
BH2017BH2017
1,5605 gold badges28 silver badges60 bronze badges
1,5605 gold badges28 silver badges60 bronze badges
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
The issue was essentially the result of my misunderstanding of how to properly install VirtualBox guest modules. I thought everything was done on the host, I did not realize these systems required me to follow a guide like this on the guest OS too. After I followed this guide (with slight adjustments for the Debian system as the guide is for Red Hat-based systems using the yum/DNF package management system) both guest systems were able to run seamless mode no-problem. To provide an example of how I'd like answers to my questions here to be formatted I am going to give the details of what exactly I did.
Debian
I first signed into the administrative (root) account by running:
su
then I ran Host+D
(to insert the guest additions ISO), after adding a blank disk to my virtual machine. I then ran:
mkdir /media/VirtualBoxGuestAdditions
mount -r /dev/cdrom /media/VirtualBoxGuestAdditions
export KERN_DIR=/usr/src/kernels/`uname -r`
cd /media/VirtualBoxGuestAdditions
./VBoxLinuxAdditions.run
For Fedora 22 I merely added the line:
dnf install gcc kernel-devel kernel-headers dkms make bzip2 perl
before the 4th line (i.e., the cd
line).
add a comment |
I know this question realtes to different versions but it might be usefull for someone that has installed the latest version of VirtualBox (5.2)
My setup:
- VirtualBox 5.2.0 r118431
- Host OS: Windows 10
- Guest OS: Linux Debian 9.2.1 with XFCE
- Guest Additions ISO: VBoxGuestAdditions_5.2.1-118447 (please note that this is not the ISO you get with the default installer, there is a note on virtualbox site to download a newer version)
The following commands must be run in super user mode on guest OS rebooted:
mkdir -p /lib/modules/$(uname -r)/build/include/drm
touch /lib/modules/$(uname -r)/build/include/drm/drm_rect.h
The VBoxLinuxAdditions.run
must be executed again, and then guest OS need a reboot
There is also a newer Guest Additions ISO in the development downloads which should fix this problem Virtualbox Test builds
Credits:
- Ticket #17203
- vboxvideo build is skipped, Debian 9.2, GA 5.2.1-r118447
UPDATE (11/4/2017):
New version VBoxGuestAdditions_5.2.1-118918.iso has been linked on the VirtualBox download page
I getPermission denied
if I try to executeVBoxLinuxAdditions.run
as root
– binaryBigInt
Mar 18 '18 at 9:52
add a comment |
This is an old question but I still couldn't get it to work using the virtual box guest addition's so here's a different way to go about it: change the resolution in the GRUB2 bootloader.
- In Debian log into root
Run
cd /etc/default/
Open the file grub with permissions with you favorite editor ie:
sudo nano grub
Look for the GRUB_GFXMODE line then replace it with the following:
GRUB_GFXMODE=DesiredResolution
GRUB_GFXPAYLOAD_LINUX=keep
In my case DesiredResolution=1280x1024. The resolution here must be a supported resolution. You can find a list of supported resolution by booting up to grub, running the grub shell then executing the vbeinfo command.
Run
update-grub
Restart your machine.
- done
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f222659%2fhow-do-i-adjust-the-screen-resolution-for-my-debian-8-1-64-bit-virtualbox-machin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
The issue was essentially the result of my misunderstanding of how to properly install VirtualBox guest modules. I thought everything was done on the host, I did not realize these systems required me to follow a guide like this on the guest OS too. After I followed this guide (with slight adjustments for the Debian system as the guide is for Red Hat-based systems using the yum/DNF package management system) both guest systems were able to run seamless mode no-problem. To provide an example of how I'd like answers to my questions here to be formatted I am going to give the details of what exactly I did.
Debian
I first signed into the administrative (root) account by running:
su
then I ran Host+D
(to insert the guest additions ISO), after adding a blank disk to my virtual machine. I then ran:
mkdir /media/VirtualBoxGuestAdditions
mount -r /dev/cdrom /media/VirtualBoxGuestAdditions
export KERN_DIR=/usr/src/kernels/`uname -r`
cd /media/VirtualBoxGuestAdditions
./VBoxLinuxAdditions.run
For Fedora 22 I merely added the line:
dnf install gcc kernel-devel kernel-headers dkms make bzip2 perl
before the 4th line (i.e., the cd
line).
add a comment |
The issue was essentially the result of my misunderstanding of how to properly install VirtualBox guest modules. I thought everything was done on the host, I did not realize these systems required me to follow a guide like this on the guest OS too. After I followed this guide (with slight adjustments for the Debian system as the guide is for Red Hat-based systems using the yum/DNF package management system) both guest systems were able to run seamless mode no-problem. To provide an example of how I'd like answers to my questions here to be formatted I am going to give the details of what exactly I did.
Debian
I first signed into the administrative (root) account by running:
su
then I ran Host+D
(to insert the guest additions ISO), after adding a blank disk to my virtual machine. I then ran:
mkdir /media/VirtualBoxGuestAdditions
mount -r /dev/cdrom /media/VirtualBoxGuestAdditions
export KERN_DIR=/usr/src/kernels/`uname -r`
cd /media/VirtualBoxGuestAdditions
./VBoxLinuxAdditions.run
For Fedora 22 I merely added the line:
dnf install gcc kernel-devel kernel-headers dkms make bzip2 perl
before the 4th line (i.e., the cd
line).
add a comment |
The issue was essentially the result of my misunderstanding of how to properly install VirtualBox guest modules. I thought everything was done on the host, I did not realize these systems required me to follow a guide like this on the guest OS too. After I followed this guide (with slight adjustments for the Debian system as the guide is for Red Hat-based systems using the yum/DNF package management system) both guest systems were able to run seamless mode no-problem. To provide an example of how I'd like answers to my questions here to be formatted I am going to give the details of what exactly I did.
Debian
I first signed into the administrative (root) account by running:
su
then I ran Host+D
(to insert the guest additions ISO), after adding a blank disk to my virtual machine. I then ran:
mkdir /media/VirtualBoxGuestAdditions
mount -r /dev/cdrom /media/VirtualBoxGuestAdditions
export KERN_DIR=/usr/src/kernels/`uname -r`
cd /media/VirtualBoxGuestAdditions
./VBoxLinuxAdditions.run
For Fedora 22 I merely added the line:
dnf install gcc kernel-devel kernel-headers dkms make bzip2 perl
before the 4th line (i.e., the cd
line).
The issue was essentially the result of my misunderstanding of how to properly install VirtualBox guest modules. I thought everything was done on the host, I did not realize these systems required me to follow a guide like this on the guest OS too. After I followed this guide (with slight adjustments for the Debian system as the guide is for Red Hat-based systems using the yum/DNF package management system) both guest systems were able to run seamless mode no-problem. To provide an example of how I'd like answers to my questions here to be formatted I am going to give the details of what exactly I did.
Debian
I first signed into the administrative (root) account by running:
su
then I ran Host+D
(to insert the guest additions ISO), after adding a blank disk to my virtual machine. I then ran:
mkdir /media/VirtualBoxGuestAdditions
mount -r /dev/cdrom /media/VirtualBoxGuestAdditions
export KERN_DIR=/usr/src/kernels/`uname -r`
cd /media/VirtualBoxGuestAdditions
./VBoxLinuxAdditions.run
For Fedora 22 I merely added the line:
dnf install gcc kernel-devel kernel-headers dkms make bzip2 perl
before the 4th line (i.e., the cd
line).
edited Aug 12 '15 at 8:53
answered Aug 12 '15 at 8:03
BH2017BH2017
1,5605 gold badges28 silver badges60 bronze badges
1,5605 gold badges28 silver badges60 bronze badges
add a comment |
add a comment |
I know this question realtes to different versions but it might be usefull for someone that has installed the latest version of VirtualBox (5.2)
My setup:
- VirtualBox 5.2.0 r118431
- Host OS: Windows 10
- Guest OS: Linux Debian 9.2.1 with XFCE
- Guest Additions ISO: VBoxGuestAdditions_5.2.1-118447 (please note that this is not the ISO you get with the default installer, there is a note on virtualbox site to download a newer version)
The following commands must be run in super user mode on guest OS rebooted:
mkdir -p /lib/modules/$(uname -r)/build/include/drm
touch /lib/modules/$(uname -r)/build/include/drm/drm_rect.h
The VBoxLinuxAdditions.run
must be executed again, and then guest OS need a reboot
There is also a newer Guest Additions ISO in the development downloads which should fix this problem Virtualbox Test builds
Credits:
- Ticket #17203
- vboxvideo build is skipped, Debian 9.2, GA 5.2.1-r118447
UPDATE (11/4/2017):
New version VBoxGuestAdditions_5.2.1-118918.iso has been linked on the VirtualBox download page
I getPermission denied
if I try to executeVBoxLinuxAdditions.run
as root
– binaryBigInt
Mar 18 '18 at 9:52
add a comment |
I know this question realtes to different versions but it might be usefull for someone that has installed the latest version of VirtualBox (5.2)
My setup:
- VirtualBox 5.2.0 r118431
- Host OS: Windows 10
- Guest OS: Linux Debian 9.2.1 with XFCE
- Guest Additions ISO: VBoxGuestAdditions_5.2.1-118447 (please note that this is not the ISO you get with the default installer, there is a note on virtualbox site to download a newer version)
The following commands must be run in super user mode on guest OS rebooted:
mkdir -p /lib/modules/$(uname -r)/build/include/drm
touch /lib/modules/$(uname -r)/build/include/drm/drm_rect.h
The VBoxLinuxAdditions.run
must be executed again, and then guest OS need a reboot
There is also a newer Guest Additions ISO in the development downloads which should fix this problem Virtualbox Test builds
Credits:
- Ticket #17203
- vboxvideo build is skipped, Debian 9.2, GA 5.2.1-r118447
UPDATE (11/4/2017):
New version VBoxGuestAdditions_5.2.1-118918.iso has been linked on the VirtualBox download page
I getPermission denied
if I try to executeVBoxLinuxAdditions.run
as root
– binaryBigInt
Mar 18 '18 at 9:52
add a comment |
I know this question realtes to different versions but it might be usefull for someone that has installed the latest version of VirtualBox (5.2)
My setup:
- VirtualBox 5.2.0 r118431
- Host OS: Windows 10
- Guest OS: Linux Debian 9.2.1 with XFCE
- Guest Additions ISO: VBoxGuestAdditions_5.2.1-118447 (please note that this is not the ISO you get with the default installer, there is a note on virtualbox site to download a newer version)
The following commands must be run in super user mode on guest OS rebooted:
mkdir -p /lib/modules/$(uname -r)/build/include/drm
touch /lib/modules/$(uname -r)/build/include/drm/drm_rect.h
The VBoxLinuxAdditions.run
must be executed again, and then guest OS need a reboot
There is also a newer Guest Additions ISO in the development downloads which should fix this problem Virtualbox Test builds
Credits:
- Ticket #17203
- vboxvideo build is skipped, Debian 9.2, GA 5.2.1-r118447
UPDATE (11/4/2017):
New version VBoxGuestAdditions_5.2.1-118918.iso has been linked on the VirtualBox download page
I know this question realtes to different versions but it might be usefull for someone that has installed the latest version of VirtualBox (5.2)
My setup:
- VirtualBox 5.2.0 r118431
- Host OS: Windows 10
- Guest OS: Linux Debian 9.2.1 with XFCE
- Guest Additions ISO: VBoxGuestAdditions_5.2.1-118447 (please note that this is not the ISO you get with the default installer, there is a note on virtualbox site to download a newer version)
The following commands must be run in super user mode on guest OS rebooted:
mkdir -p /lib/modules/$(uname -r)/build/include/drm
touch /lib/modules/$(uname -r)/build/include/drm/drm_rect.h
The VBoxLinuxAdditions.run
must be executed again, and then guest OS need a reboot
There is also a newer Guest Additions ISO in the development downloads which should fix this problem Virtualbox Test builds
Credits:
- Ticket #17203
- vboxvideo build is skipped, Debian 9.2, GA 5.2.1-r118447
UPDATE (11/4/2017):
New version VBoxGuestAdditions_5.2.1-118918.iso has been linked on the VirtualBox download page
edited Nov 4 '17 at 20:14
answered Nov 1 '17 at 18:59
Sebastian WidzSebastian Widz
1214 bronze badges
1214 bronze badges
I getPermission denied
if I try to executeVBoxLinuxAdditions.run
as root
– binaryBigInt
Mar 18 '18 at 9:52
add a comment |
I getPermission denied
if I try to executeVBoxLinuxAdditions.run
as root
– binaryBigInt
Mar 18 '18 at 9:52
I get
Permission denied
if I try to execute VBoxLinuxAdditions.run
as root– binaryBigInt
Mar 18 '18 at 9:52
I get
Permission denied
if I try to execute VBoxLinuxAdditions.run
as root– binaryBigInt
Mar 18 '18 at 9:52
add a comment |
This is an old question but I still couldn't get it to work using the virtual box guest addition's so here's a different way to go about it: change the resolution in the GRUB2 bootloader.
- In Debian log into root
Run
cd /etc/default/
Open the file grub with permissions with you favorite editor ie:
sudo nano grub
Look for the GRUB_GFXMODE line then replace it with the following:
GRUB_GFXMODE=DesiredResolution
GRUB_GFXPAYLOAD_LINUX=keep
In my case DesiredResolution=1280x1024. The resolution here must be a supported resolution. You can find a list of supported resolution by booting up to grub, running the grub shell then executing the vbeinfo command.
Run
update-grub
Restart your machine.
- done
add a comment |
This is an old question but I still couldn't get it to work using the virtual box guest addition's so here's a different way to go about it: change the resolution in the GRUB2 bootloader.
- In Debian log into root
Run
cd /etc/default/
Open the file grub with permissions with you favorite editor ie:
sudo nano grub
Look for the GRUB_GFXMODE line then replace it with the following:
GRUB_GFXMODE=DesiredResolution
GRUB_GFXPAYLOAD_LINUX=keep
In my case DesiredResolution=1280x1024. The resolution here must be a supported resolution. You can find a list of supported resolution by booting up to grub, running the grub shell then executing the vbeinfo command.
Run
update-grub
Restart your machine.
- done
add a comment |
This is an old question but I still couldn't get it to work using the virtual box guest addition's so here's a different way to go about it: change the resolution in the GRUB2 bootloader.
- In Debian log into root
Run
cd /etc/default/
Open the file grub with permissions with you favorite editor ie:
sudo nano grub
Look for the GRUB_GFXMODE line then replace it with the following:
GRUB_GFXMODE=DesiredResolution
GRUB_GFXPAYLOAD_LINUX=keep
In my case DesiredResolution=1280x1024. The resolution here must be a supported resolution. You can find a list of supported resolution by booting up to grub, running the grub shell then executing the vbeinfo command.
Run
update-grub
Restart your machine.
- done
This is an old question but I still couldn't get it to work using the virtual box guest addition's so here's a different way to go about it: change the resolution in the GRUB2 bootloader.
- In Debian log into root
Run
cd /etc/default/
Open the file grub with permissions with you favorite editor ie:
sudo nano grub
Look for the GRUB_GFXMODE line then replace it with the following:
GRUB_GFXMODE=DesiredResolution
GRUB_GFXPAYLOAD_LINUX=keep
In my case DesiredResolution=1280x1024. The resolution here must be a supported resolution. You can find a list of supported resolution by booting up to grub, running the grub shell then executing the vbeinfo command.
Run
update-grub
Restart your machine.
- done
edited 18 mins ago
Rafael
32 bronze badges
32 bronze badges
answered Aug 11 '16 at 21:06
user3286166user3286166
111 bronze badge
111 bronze badge
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f222659%2fhow-do-i-adjust-the-screen-resolution-for-my-debian-8-1-64-bit-virtualbox-machin%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