a16f01fd0f
Conflicts: BuildingArchlinuxTemplate.md BuildingNonFedoraTemplate.md ContributingHowto.md HCLR1.md InstallNvidiaDriver.md InstallationIsoBuilding.md LinuxHVMTips.md Mutt.md Qrexec.md Qrexec3.md Qrexec3Implementation.md QubesBuilder.md QubesBuilderDetails.md QubesDevelopers.md QubesFirewall.md SecurityCriticalCode.md SystemDoc/VMInterface.md UserDoc/SplitGpg.md VMSudo.md VPN.md WindowsDebugging.md
1.6 KiB
| layout | title | permalink | redirect_from |
|---|---|---|---|
| doc | LinuxHVMTips | /doc/LinuxHVMTips/ | /wiki/LinuxHVMTips/ |
Tips for Linux in HVM domain
Screen resolution
Some kernel/Xorg combination use only 640x480 in HVM, which is quite small. To enable maximum resolution, some changes in Xorg configuration are needed:
- Force "vesa" video driver
- Provide wide horizontal synchronization range
To achieve it (all commands run as root):
-
Generate XOrg configuratio (if you don't have it):
{% highlight trac-wiki %} X -configure :1 && mv ~/xorg.conf.new /etc/X11/xorg.conf {% endhighlight %}
-
Add HorizSync line to Monitor section, it should look something like:
{% highlight trac-wiki %} Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" HorizSync 30.0 - 60.0 EndSection {% endhighlight %}
-
Change driver to "vesa" in Device section:
{% highlight trac-wiki %} Section "Device" # (...) Identifier "Card0" Driver "vesa" VendorName "Technical Corp." BoardName "Unknown Board" BusID "PCI:0:2:0" EndSection {% endhighlight %}
Now you should get at least 1280x1024 and be able to choose other modes.
Qubes agents
Linux Qubes agents are written with PV domain in mind, but it looks to be possible to run them also in HVM domain. However some work is required to achieve it. Check this thread.