Ubuntu Server 18.04 LTS cannot change resolution in Hyper-V
Clash Royale CLAN TAG#URR8PPP up vote
3
down vote
favorite
I am testing Ubuntu Server 18.04 LTS using a Hyper-V VM running from Windows 10 1709, but so far I have been unable to change the console resolution. I have already installed the virtual services, modified grub file, updated grub config, but it does not work, the resolution always stucks at 1152x864 pixels.
I have another VM running Server 16.04 LTS and there it works flawlessly.
This is all the config I have done
- Update repositories.
- Install linux-virtual, linux-cloud-tools-virtual, linux-tools-virtual
- Verify the hyper-v daemons are loaded with lsmod (they are)
- Modify the file /etc/default/grub with the following
GRUB_CMDLINE_LINUX_DEFAULT=video=hyperv_fb:1024x768and runningsudo update-grub - Reboot the VM.
I would be glad if someone can shed more light to know why it's not working or if there is a new trick to apply with this version.
server virtualization display-resolution hyper-v
asked Apr 30 at 19:18
badger_8007
9317
add a comment |Â
up vote
3
down vote
favorite
I am testing Ubuntu Server 18.04 LTS using a Hyper-V VM running from Windows 10 1709, but so far I have been unable to change the console resolution. I have already installed the virtual services, modified grub file, updated grub config, but it does not work, the resolution always stucks at 1152x864 pixels.
I have another VM running Server 16.04 LTS and there it works flawlessly.
This is all the config I have done
- Update repositories.
- Install linux-virtual, linux-cloud-tools-virtual, linux-tools-virtual
- Verify the hyper-v daemons are loaded with lsmod (they are)
- Modify the file /etc/default/grub with the following
GRUB_CMDLINE_LINUX_DEFAULT=video=hyperv_fb:1024x768and runningsudo update-grub - Reboot the VM.
I would be glad if someone can shed more light to know why it's not working or if there is a new trick to apply with this version.
server virtualization display-resolution hyper-v
asked Apr 30 at 19:18
badger_8007
9317
1
Make sure you have created a Generation 2 virtual machine.
– Michael Hampton
Apr 30 at 21:19
Thanks for the info but it is a Generation 2 VM indeed. So far I haven´t found aything documenting a change on this process, but knowing the underlying changes to other components (networking, etc.) made in this version, will not surprise me you have to modify aditional files or configure it in another way to get it working.
– badger_8007
May 1 at 15:19
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I am testing Ubuntu Server 18.04 LTS using a Hyper-V VM running from Windows 10 1709, but so far I have been unable to change the console resolution. I have already installed the virtual services, modified grub file, updated grub config, but it does not work, the resolution always stucks at 1152x864 pixels.
I have another VM running Server 16.04 LTS and there it works flawlessly.
This is all the config I have done
- Update repositories.
- Install linux-virtual, linux-cloud-tools-virtual, linux-tools-virtual
- Verify the hyper-v daemons are loaded with lsmod (they are)
- Modify the file /etc/default/grub with the following
GRUB_CMDLINE_LINUX_DEFAULT=video=hyperv_fb:1024x768and runningsudo update-grub - Reboot the VM.
I would be glad if someone can shed more light to know why it's not working or if there is a new trick to apply with this version.
server virtualization display-resolution hyper-v
asked Apr 30 at 19:18
badger_8007
9317
I am testing Ubuntu Server 18.04 LTS using a Hyper-V VM running from Windows 10 1709, but so far I have been unable to change the console resolution. I have already installed the virtual services, modified grub file, updated grub config, but it does not work, the resolution always stucks at 1152x864 pixels.
I have another VM running Server 16.04 LTS and there it works flawlessly.
This is all the config I have done
- Update repositories.
- Install linux-virtual, linux-cloud-tools-virtual, linux-tools-virtual
- Verify the hyper-v daemons are loaded with lsmod (they are)
- Modify the file /etc/default/grub with the following
GRUB_CMDLINE_LINUX_DEFAULT=video=hyperv_fb:1024x768and runningsudo update-grub - Reboot the VM.
I would be glad if someone can shed more light to know why it's not working or if there is a new trick to apply with this version.
server virtualization display-resolution hyper-v
asked Apr 30 at 19:18
badger_8007
9317
asked Apr 30 at 19:18
badger_8007
9317
asked Apr 30 at 19:18
badger_8007
9317
asked Apr 30 at 19:18
badger_8007
9317
9317
1
Make sure you have created a Generation 2 virtual machine.
– Michael Hampton
Apr 30 at 21:19
Thanks for the info but it is a Generation 2 VM indeed. So far I haven´t found aything documenting a change on this process, but knowing the underlying changes to other components (networking, etc.) made in this version, will not surprise me you have to modify aditional files or configure it in another way to get it working.
– badger_8007
May 1 at 15:19
add a comment |Â
1
Make sure you have created a Generation 2 virtual machine.
– Michael Hampton
Apr 30 at 21:19
Thanks for the info but it is a Generation 2 VM indeed. So far I haven´t found aything documenting a change on this process, but knowing the underlying changes to other components (networking, etc.) made in this version, will not surprise me you have to modify aditional files or configure it in another way to get it working.
– badger_8007
May 1 at 15:19
1
1
Make sure you have created a Generation 2 virtual machine.
– Michael Hampton
Apr 30 at 21:19
Make sure you have created a Generation 2 virtual machine.
– Michael Hampton
Apr 30 at 21:19
Thanks for the info but it is a Generation 2 VM indeed. So far I haven´t found aything documenting a change on this process, but knowing the underlying changes to other components (networking, etc.) made in this version, will not surprise me you have to modify aditional files or configure it in another way to get it working.
– badger_8007
May 1 at 15:19
Thanks for the info but it is a Generation 2 VM indeed. So far I haven´t found aything documenting a change on this process, but knowing the underlying changes to other components (networking, etc.) made in this version, will not surprise me you have to modify aditional files or configure it in another way to get it working.
– badger_8007
May 1 at 15:19
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
I changed both the CMD_LINE_DEFAULT and the next CMD_LINE with the same value (resolution I wanted), updated then rebooted, and it worked.
Like this:
GRUB_CMDLINE_LINUX_DEFAULT=video=hyperv_fb:1366×768
GRUB_CMDLINE_LINUX=video=hyperv_fb:1366×768
answered May 4 at 20:28
George
361
Actually you must runupdate-grubbefore to reboot.
– Emmanuel
May 20 at 0:43
Does not work for me, I constantly get a "package not found" error, can't install these components. the repositories seem to be removed or incompatible with current version of Ubuntu (no longer "xenial")
– verdy_p
May 29 at 9:09
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
I changed both the CMD_LINE_DEFAULT and the next CMD_LINE with the same value (resolution I wanted), updated then rebooted, and it worked.
Like this:
GRUB_CMDLINE_LINUX_DEFAULT=video=hyperv_fb:1366×768
GRUB_CMDLINE_LINUX=video=hyperv_fb:1366×768
answered May 4 at 20:28
George
361
Actually you must runupdate-grubbefore to reboot.
– Emmanuel
May 20 at 0:43
Does not work for me, I constantly get a "package not found" error, can't install these components. the repositories seem to be removed or incompatible with current version of Ubuntu (no longer "xenial")
– verdy_p
May 29 at 9:09
add a comment |Â
up vote
2
down vote
accepted
I changed both the CMD_LINE_DEFAULT and the next CMD_LINE with the same value (resolution I wanted), updated then rebooted, and it worked.
Like this:
GRUB_CMDLINE_LINUX_DEFAULT=video=hyperv_fb:1366×768
GRUB_CMDLINE_LINUX=video=hyperv_fb:1366×768
answered May 4 at 20:28
George
361
Actually you must runupdate-grubbefore to reboot.
– Emmanuel
May 20 at 0:43
Does not work for me, I constantly get a "package not found" error, can't install these components. the repositories seem to be removed or incompatible with current version of Ubuntu (no longer "xenial")
– verdy_p
May 29 at 9:09
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
I changed both the CMD_LINE_DEFAULT and the next CMD_LINE with the same value (resolution I wanted), updated then rebooted, and it worked.
Like this:
GRUB_CMDLINE_LINUX_DEFAULT=video=hyperv_fb:1366×768
GRUB_CMDLINE_LINUX=video=hyperv_fb:1366×768
answered May 4 at 20:28
George
361
I changed both the CMD_LINE_DEFAULT and the next CMD_LINE with the same value (resolution I wanted), updated then rebooted, and it worked.
Like this:
GRUB_CMDLINE_LINUX_DEFAULT=video=hyperv_fb:1366×768
GRUB_CMDLINE_LINUX=video=hyperv_fb:1366×768
answered May 4 at 20:28
George
361
answered May 4 at 20:28
George
361
answered May 4 at 20:28
George
361
answered May 4 at 20:28
George
361
361
Actually you must runupdate-grubbefore to reboot.
– Emmanuel
May 20 at 0:43
Does not work for me, I constantly get a "package not found" error, can't install these components. the repositories seem to be removed or incompatible with current version of Ubuntu (no longer "xenial")
– verdy_p
May 29 at 9:09
add a comment |Â
Actually you must runupdate-grubbefore to reboot.
– Emmanuel
May 20 at 0:43
Does not work for me, I constantly get a "package not found" error, can't install these components. the repositories seem to be removed or incompatible with current version of Ubuntu (no longer "xenial")
– verdy_p
May 29 at 9:09
Actually you must run
update-grub before to reboot.– Emmanuel
May 20 at 0:43
Actually you must run
update-grub before to reboot.– Emmanuel
May 20 at 0:43
Does not work for me, I constantly get a "package not found" error, can't install these components. the repositories seem to be removed or incompatible with current version of Ubuntu (no longer "xenial")
– verdy_p
May 29 at 9:09
Does not work for me, I constantly get a "package not found" error, can't install these components. the repositories seem to be removed or incompatible with current version of Ubuntu (no longer "xenial")
– verdy_p
May 29 at 9:09
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1030276%2fubuntu-server-18-04-lts-cannot-change-resolution-in-hyper-v%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
1
Make sure you have created a Generation 2 virtual machine.
– Michael Hampton
Apr 30 at 21:19
Thanks for the info but it is a Generation 2 VM indeed. So far I haven´t found aything documenting a change on this process, but knowing the underlying changes to other components (networking, etc.) made in this version, will not surprise me you have to modify aditional files or configure it in another way to get it working.
– badger_8007
May 1 at 15:19