<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[VM Display Resolution]]></title><description><![CDATA[<p dir="auto">So i was trying out a new Linux distro Umarchy and had issues with the screen resolution.</p>
<p dir="auto">Looks like this can be done by creating new vm templates with this UEFI setting preset.</p>
<p dir="auto">Is that something Vates and work on when pushing new templates?</p>
<p dir="auto">Checked the official docs — short version: there's no supported way to change the OVMF default. It's per-VM only, done inside the guest's UEFI setup, and XCP-ng/XO expose no pool setting, template field, or xe parameter for it.</p>
<p dir="auto">What the official docs actually say<br />
<a href="http://docs.xcp-ng.org/vms/" target="_blank" rel="noopener noreferrer nofollow ugc">docs.xcp-ng.org/vms/</a> has a "Manage screen resolution" section, but it only covers the OS layer:</p>
<p dir="auto">BIOS VM — set it in the guest OS (Display settings).<br />
UEFI VM — install the XCP-ng Standard VGA Display Driver (part of the Windows Guest Tools package); after that the guest OS controls resolution normally.<br />
The OVMF Platform Configuration menu itself isn't documented there. On the forum, Vates support (Darkbeldin) answered the exact question you're asking with "to my knowledge it's not possible inside the template." That's still the state of things.</p>
<p dir="auto">Setting it per VM<br />
Device Manager → OVMF Platform Configuration → Change Preferred → pick resolution → F10 to save → Esc back out → Reset (a full reboot; it does not apply to the current boot).</p>
<p dir="auto">Getting into setup is the annoying part since boot wait is 0s — either spam Esc at the Tianocore logo, or from the GRUB screen press c and type fwsetup.</p>
<p dir="auto">Making new VMs come up at 1024x768+<br />
The practical workaround, since the setting lives in the VM's UEFI NVRAM (varstored) and NVRAM is part of the VM record:</p>
<p dir="auto">Build one VM, set the OVMF preferred resolution, shut it down.<br />
Convert it to a template.<br />
VMs cloned from that template inherit the NVRAM, including the resolution.<br />
Caveats: this won't help VMs created from XCP-ng's built-in templates, and there are reports of guest UEFI NVRAM not persisting in some cases, so verify on a clone before rolling it out.</p>
<p dir="auto">Related knob worth checking first<br />
Separate from the OVMF preference, the emulated adapter caps what modes are available:</p>
<p dir="auto">xe vm-param-set uuid=$UUID platform:vga=std<br />
xe vm-param-set uuid=$UUID platform:videoram=16<br />
In XO these are the VGA toggle and Video RAM field on the VM's Advanced tab. 16 MiB is the max and is what people use for 1080p and above — with the default low videoram the higher modes may not even be offered in the OVMF menu.</p>
<p dir="auto">Sources:</p>
<p dir="auto">Virtual Machines (VMs) | XCP-ng Documentation<br />
Set default resolution for UEFI | XCP-ng forum<br />
VGA on Xen Orchestra | XCP-ng forum<br />
Guest VM UEFI NVRAM not saved / not persistent | XCP-ng forum<br />
How to set screen size for UEFI VMs on XCP-NG | TechOverflow</p>
]]></description><link>https://xcp-ng.org/forum/topic/12435/vm-display-resolution</link><generator>RSS for Node</generator><lastBuildDate>Tue, 25 Aug 2026 22:39:40 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/12435.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 25 Aug 2026 20:54:38 GMT</pubDate><ttl>60</ttl></channel></rss>