问题

在Windows Server 2016（AHV-VM）中显示分辨率粘在1280x1024

d
Userlevel 1
徽章 +2
  • didi7
  • 开拓者
  • 18个答复

好的，昨天，我们的众多Nutanix群集之一被升级为5.15 LTS，我开始使用UEFI-Configuration创建一个新的Windows Server 2016模板。

现在，我被困在1280x1024的显示分辨率上，并且不可能进行更改，因为它已变成灰色。安装了5.15 LTS和Virtio 1.1.5的Nutanix宾客工具。

这个错误是否已知，是否存在工作？

5.16 STS呢？它在那里固定了吗？

感谢您的任何答复。

问候，

didi7

Ok, yesterday one of our many Nutanix clusters was upgraded to 5.15 LTS and I started to create a new Windows Server 2016 template using UEFI-configuration.<\/p>

\u00a0<\/p>

Now I am stuck at display resolution of 1280x1024 and change is not possible, because it is grayed out. Nutanix Guest Tools from 5.15 LTS and VirtIO 1.1.5 are installed.<\/p>

\u00a0<\/p>

Is this bug known and does there exist a work-around?<\/p>

\u00a0<\/p>

What about 5.16 STS? Is it fixed there?<\/p>

\u00a0<\/p>

Thanks for any reply.<\/p>

\u00a0<\/p>

Regards,<\/p>

Didi7<\/p>

\u00a0<\/p>","quoteUsername":"Didi7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

13个答复

阿罗纳
秩
UserLevel 6
徽章 +5

嗨didi7，

为了确保我们在同一页面上，这是该选项被弄清楚的地方吗？

Hi Didi7,<\/p>

\u00a0<\/p>

To make sure we\u2019re on the same page is this where the option is greyed out?<\/p>

\"//www.jhbzcj.com/next/server-virtualization-27/\"<\/figure>

\u00a0<\/p>","quoteUsername":"Alona","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

d
Userlevel 1
徽章 +2

您好Alona，不，它不在UEFI配置之内，您会陷入Windows OS内的Display分辨率1280x1024。

Hello Alona, no it is not within the UEFI configuration, you are stuck at display resolution 1280x1024 within Windows OS.<\/p>

\u00a0<\/p>","quoteUsername":"Didi7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

d
Userlevel 1
徽章 +2

在UEFI-CONFIGURATION中的分辨率发生变化是可能的，但在安装过程中没有效果。Windows VM的整个安装过程只能使用1280x1024完成，因此您被迫使用大型监视器来成功安装Windows Server 2016，并且由于您无法在安装过程中更改分辨率，因此您也被困在1280x1024时，Windows已完全安装，Nutanix宾客工具以及安装了Virtio驱动程序。

确实，这很烦人，确实对客户没有共鸣。

不知道的Nutanix展示驱动程序可能可以解决吗？

在Windows Server 2016的安装过程中，使用非EUFI VM会导致同一监视器和显示驱动程序，但您可以更改分辨率。

是否有Nutanix的解决方案，还是这是已知的错误？

是否存在工作？

Changing resolution within UEFI-configuration is possible but has no effect during installation. The whole installation process of a Windows VM can only be done with 1280x1024, so you are forced to use big monitors to succeed with the installation of Windows Server 2016 and as you cannot change the resolution during installation, you are also stuck at 1280x1024, when Windows is fully installed and Nutanix Guest Tools, as well as VirtIO drivers are installed.<\/p>

\u00a0<\/p>

Really, that\u2019s so annoying and really not resonable to customers.<\/p>

\u00a0<\/p>

Might be fixable with an Nutanix display driver, don\u2019t know?<\/p>

\u00a0<\/p>

Using non-UEFI VMs during installatation of Windows Server 2016 results in the same Monitor and display driver, but you can change resolutions.<\/p>

\u00a0<\/p>

Is there a solution from Nutanix available or is this a known bug?<\/p>

\u00a0<\/p>

Does there exist a work-around?<\/p>","quoteUsername":"Didi7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

阿罗纳
秩
UserLevel 6
徽章 +5

可以说，您正在遇到的问题是在Prism中使用“启动控制台”功能连接到VM时？使用“启动控制台”时，从UEFI设置中拾取了屏幕分辨率，Windows驱动程序无法更改该设置。因此，您需要更改UEFI中的分辨率设置，以影响VNC连接分辨率。

问题是，VNC旨在进行故障排除，调试，而不是作为所有时间访问工具。

当您通过RDP发布安装时，问题是否会出现？RDP使用其他驱动程序，因此您应该能够根据需要调整屏幕。

您是否考虑过从图像部署VM？这样，您可以完全跳过安装阶段并到达初始设置。我建议在制作图像之前先进行操作系统。AFAIK，SYSPREP将分辨率默认为1024 x 768 - 要记住的东西。

这是一个KB，描述了您特别遇到的问题KB-4792 AHV |如何在UEFI模式下运行的Windows VM上更改显示分辨率。

Would it be correct to say that the issue you are experiencing is when connecting to the VM by using \u201cLaunch console\u201d feature in Prism? When using \u201cLaunch console\u201d screen resolution is picked up from UEFI settings and Windows driver does not have the ability to change that setting. Therefore, you would need to change the resolution settings in UEFI in order to affect VNC connection resolution.<\/p>

The thing is, VNC is intended for troubleshooting, debugging and such rather then as a all time access tool.<\/p>

Does the issue appear when you connect via RDP post the installation? RDP is using a different driver hence you should be able to adjust the screen as required.<\/p>

Have you considered deploying VMs from an image? This way you can skip the installation phase entirely and arrive at initial set up. I would recommend to sysprep the OS prior to making an image out of it. AFAIK, sysprep defaults the resolution to 1024 x 768 \u2013 something to keep in mind.<\/p>

Here is a KB describing the issue that you encountered specifically KB-4792 AHV | How to change display resolution on Windows VMs running in UEFI mode.<\/a><\/p>","quoteUsername":"Alona","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

d
Userlevel 1
徽章 +2

Quote：说您正在遇到的问题是通过在PRISM中使用“启动控制台”功能连接到VM时正确的吗？

是的，绝对可以，但是只要没有网络连接，一个人就被迫使用VNC控制台，直到设置所有内容，我在谈论VM-Template生成，那里没有可用的网络连接，因为它们保持了断开连接。更新（例如Windows Server 2016中的累积更新）是通过ISO媒体完成的。在SYSPREPING和克隆这些VM-Template之后，它们将连接到网络，然后使用RDP。

I really know a lot of Hypervisor platforms and have 15 years of experience with VMware and the likes, but never had any problems to change the display resolution via the console, even if it’s only 640x480 and a change to 800x600 is only possible, but that I am forced to change the display resolution in the UEFI-firmware and that display resolution change within Windows is no longer possible, is unique to Nutanix AHV VMs imho!

当然，如果您使用RDP，客户端定义了分辨率，那不是我最初遇到的问题。

是的，在生成这些模板（没有任何网络连接）并完全配置以进行进一步分发之后，使用SYSPREP和广义关闭这些VM！

我决定目前继续创建非UEFI-Firmware Windows VM-Templates，因为此显示分辨率问题很烦人。不幸的是，我被迫将一些Hyper-V一代VM转移到Nutanix AHV上，在那里我将尝试将默认的分辨率设置为UEFI-FIRMWARE中的​​1024x768，但是IIRC对Windows设置的显示解决方案没有影响，但是由于我不确定，我会再次尝试。

问候，

didi7

Quote: Would it be correct to say that the issue you are experiencing is when connecting to the VM by using \u201cLaunch console\u201d feature in Prism?<\/p>

\u00a0<\/p>

Yes absolutely, but as long as there is no network connection, one is forced to use the VNC Console until everything is setup and I am talking about VM-template generation, where there are no network connections availaible, as here they stay disconnected. Updates, like Cumulative Updates in Windows Server 2016 are done via ISO medias. After syspreping and cloning those VM-templates, they get connected to networks and then RDP is used of course.<\/p>

\u00a0<\/p>

I really know a lot of Hypervisor platforms and have 15 years of experience with VMware and the likes, but never had any problems to change the display resolution via the console, even if it\u2019s only 640x480 and a change to 800x600 is only possible, but that I am forced to change the display resolution in the UEFI-firmware and that display resolution change within Windows is no longer possible, is unique to Nutanix AHV VMs imho!<\/p>

\u00a0<\/p>

Of course, if you use RDP, the client defines the resolution, that\u2019s not the question I originally had.<\/p>

\u00a0<\/p>

And yes, after those templates are generated (without any network connection) and completely configured for further distribution, those VMs are shutdown with sysprep and generalized!<\/p>

\u00a0<\/p>

I decided to continue to create non UEFI-firmware Windows VM-templates at the moment, because this display resolution problem is annoying. Unfortunately I am forced to transfer some Hyper-V Generation 2 VMs to Nutanix AHV and there I will try to set the default resolution to 1024x768 in UEFI-firmware, but iirc this had no effect to how the Windows setup display resolution came up, but as I am unsure, I will give it another try.<\/p>

\u00a0<\/p>

Regards,<\/p>

Didi7<\/p>

\u00a0<\/p>","quoteUsername":"Didi7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

d
Userlevel 1
徽章 +2

好的，我继续对基于UEFI-FIRMWARE的Windows 2016 VM进行测试，并最终发现，该测试仅在Windows 2016 VMS中显示分辨率，仅在更改UEFI-FIRMWARE中的​​默认分辨率时才更改，并且仅当您在重新启动后输入UEFI-FIRMWARE配置时才显示分辨率。和退出。显示分辨率更改为您在UEFI-Firmware中选择的分辨率。

一旦您再次关闭Windows Server 2016 VM供电，显示分辨率将再次返回到1280x1024，并且无法在Windows中更改。如果您重新启动（不关闭）Windows 2016 VM，请输入使用F2的UEFI-FIRMWARE并再次退出，显示分辨率再次更改为您在Nutanix Uefi-Firmware设置中选择的分辨率。

这就是我所说的烦人，应该尽快从nutanix上改变，但是也许我是唯一一个声称这很烦人的人，至少在我们公司中，有几个用户觉得这很烦人。

欢迎Nutanix的任何评论！

问候，

didi7

Ok, I continued my tests on UEFI-firmware based Windows 2016 VMs and finally found out, that display resolution in Windows 2016 VMs only changes, when changing the default resolution in UEFI-firmware and only if you enter UEFI-firmware configuration after a reboot and exit. The display resolution changes to the one you choose in UEFI-firmware.<\/p>

\u00a0<\/p>

As soon as you power off the Windows Server 2016 VM again, the display resolution returns to 1280x1024 again and cannot be changed within Windows. If you reboot (not power off) the Windows 2016 VM, enter UEFI-firmware with F2 and exit again, the display resolution changes again to the one you chose in Nutanix UEFI-firmware settings.<\/p>

\u00a0<\/p>

That\u2019s what I call annoying and should be changed from Nutanix asap, but maybe I am the only one claiming it\u2019s annoying, at least in our company several users find it annoying.<\/p>

\u00a0<\/p>

Any comments from Nutanix are welcome!<\/p>

\u00a0<\/p>

Regards,<\/p>

Didi7<\/p>

\u00a0<\/p>","quoteUsername":"Didi7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

sudhir9
UserLevel 2
徽章 +4

@didi7

我了解您的关注点，并在我的AHV20170830.395的AOS 5.15实验室中对此进行了测试。这确实是一个必要的功能，在Hyper-V和VMware中效果很好。正如您提到的，其特定于UEFI和Legacy VM并未显示出行为。这是因为，要更改显示分辨率，基于VGA标准的旧图形卡通过VGA BIOS暴露了其助手例程。操作系统驱动程序将提出一个BIOS，以中断INT 10H，以调用相应的VGA BIOS例程，这反过来又会呼叫固件助手，以通过特定的分辨率驱动卡。
使用UEFI，没有VGA。所有符合UEFI的卡都提供GOP协议处理程序，以相应地驱动卡以更改显示分辨率。
为了完全实现动态分辨率更改功能，OS驱动程序必须在运行时（使用VGA或GOP）在平台固件（BIOS或UEFI）中调用。请注意，在没有分辨率更改功能的情况下，来宾操作系统将不得不继承固件在启动处设置显示器时最初设置的任何分辨率（因此是FrameSbuffer大小）。

由于上述原因，您只能从UEFI固件菜单上更改Windows VM的默认引导分辨率https://portal.nutanix.com/page/documents/details/?targetID=AHV-ADMIN-GUIDE-V5_17%3Avmm-getting-familiar-with-euefi-uefi-firmware-firmware-c.html

我们为此提出了一个增强请求，我正在与工程学联系以获取更多更新。我会及时通知您此主题。

Sudhir
@Didi7<\/user-mention>\u00a0\u00a0<\/p>

I understand your concern and have tested the same in my lab on\u00a0AOS 5.15 with AHV20170830.395. This indeed is a necessary feature and works well in Hyper-V and VMWare. As you have mentioned its specific to UEFI and LEGACY VMs doesn't show the behaviour.\u00a0\u00a0It's because, to change the display resolution, legacy Graphics cards based on VGA standard exposed their helper routines via VGA BIOS. OS drivers would raise a BIOS to interrupt\u00a0INT 10H\u00a0for the respective VGA bios routine to be invoked, which would in turn call into the firmware helper for driving the card in a particular resolution.
With UEFI, there is no VGA. All UEFI-compliant cards provide GOP protocol handlers to drive the card accordingly for changing display resolution.
To fully implement dynamic resolution changing capabilities, the OS driver must be able to call into platform firmware (BIOS or UEFI) at runtime (using VGA or GOP). Note that in the absence of resolution change capability, the guest OS will have to inherit whatever resolution (and hence framebuffer size) the firmware had initially set for it while setting up the display device at boot.<\/p>

Due to the reason mentioned above, you can only\u00a0change the default boot resolution of your Windows VM from the UEFI firmware menu as described here\u00a0https:\/\/portal.nutanix.com\/page\/documents\/details\/?targetId=AHV-Admin-Guide-v5_17%3Avmm-getting-familiar-with-uefi-firmware-c.html<\/a>

We have an enhancement request in place for this and I am checking with engineering for more updates on that. I will keep you posted on this thread.<\/p>","quoteUsername":"Sudhir9","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

d
Userlevel 1
徽章 +2

嗨，苏迪尔，

有趣的！好吧，Hyper-V和VMware（例如Windows Server 2016下的UEFI-VMS）等其他管理程序没有显示分辨率的更改问题。

让我们看看Nutanix如何解决这个问题！

问候，

didi7

Hi Sudhir,<\/p>

\u00a0<\/p>

interesting! Well, other Hypervisors like Hyper-V and VMware have no display resolution change problems with UEFI-VMs under Windows Server 2016.<\/p>

\u00a0<\/p>

Lets see how Nutanix can fix that!<\/p>

\u00a0<\/p>

Regards,<\/p>

Didi7<\/p>","quoteUsername":"Didi7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

F

您可以在此增强上提供更新吗？

is there an update you can provide on this enhancement?<\/p>","quoteUsername":"Freddie","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
Userlevel 1
徽章 +2

从来没听说过 ：（

Not that I know of :(<\/p>","quoteUsername":"Didi7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
F

从来没听说过 ：（

凉爽的！感谢您引起他们的注意。我以前没有搜索过，没有真正的结果；我猜这次我输入了正确的搜索词。我进去并更新了该分辨率，现在可以使用。

\t

Not that I know of :(<\/p>\t<\/div><\/content-quote>

Cool!\u00a0 Thanks for bringing this to their attention.\u00a0 I had searched before with no real results; I guess this time I entered in the correct search words.\u00a0 I went in and updated the resolution, for now, it works.<\/p>","quoteUsername":"Freddie","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

d
Userlevel 1
徽章 +2

好吧，您可以更改UEFI-BIOS中的分辨率，但是一旦关闭VM，1280x1024的旧分辨率就会返回。

祝你好运！

Well, you can change the resolution in the UEFI-BIOS but as soon as you power off the VM the old resolution of 1280x1024 is back.<\/p>

Good luck!<\/p>","quoteUsername":"Didi7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

一个

嗨，有解决问题吗？与UEFI-BIO的Windows 2019数据中心服务器似乎相同。

谢谢

Hi is there a fix for this yet? It seems to be the same with a windows 2019 datacenter server with UEFI-BIOS.<\/p>

\u00a0<\/p>

Thanks<\/p>","quoteUsername":"apps_2","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu