Hyper-V guest services: Difference between revisions

From Alpine Linux
(Added link for creating Xorg page)
 
(4 intermediate revisions by 4 users not shown)
Line 1: Line 1:
=How to install Hyper-V guest services=
== How to install Hyper-V guest services ==  


Hyper-V tools is nicely packaged, so the install is simple, as follows:
Hyper-V tools is nicely packaged, so the install is simple, as follows:


{{Cmd|apk add hvtools}}
{{Cmd|apk add hvtools}}
Then enable the services
{{Cmd|rc-service hv_fcopy_daemon start}}
{{Cmd|rc-service hv_kvp_daemon start}}
{{Cmd|rc-service hv_vss_daemon start}}
Then to ensure these services start on boot
{{Cmd|rc-update add hv_fcopy_daemon}}
{{Cmd|rc-update add hv_kvp_daemon}}
{{Cmd|rc-update add hv_vss_daemon}}
== Hyper-V Settings ==
* When creating the VHDX, use 1MB BlockSizeBytes (from the default 32MB) See [https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/best-practices-for-running-linux-on-hyper-v#tuning-linux-file-systems-on-dynamic-vhdx-files| Microsoft's official docs on running Hyper-V with Linux Guest VMs] . this will reduce host filesystem usage by 75-90%
{{cmd|New-VHD -Path C:\MyVHDs\test.vhdx -SizeBytes 127GB -Dynamic -BlockSizeBytes 1MB}}
* When using using Hyper-V, if [[Xorg]] refuses to start, blacklist the <code>hyperv_drm</code> module by adding it to the <code>/etc/modprobe.d/blacklist.conf</code> file.
[[category:Virtualization]]

Latest revision as of 05:45, 22 November 2024

How to install Hyper-V guest services

Hyper-V tools is nicely packaged, so the install is simple, as follows:

apk add hvtools

Then enable the services

rc-service hv_fcopy_daemon start

rc-service hv_kvp_daemon start

rc-service hv_vss_daemon start

Then to ensure these services start on boot

rc-update add hv_fcopy_daemon

rc-update add hv_kvp_daemon

rc-update add hv_vss_daemon

Hyper-V Settings

New-VHD -Path C:\MyVHDs\test.vhdx -SizeBytes 127GB -Dynamic -BlockSizeBytes 1MB

  • When using using Hyper-V, if Xorg refuses to start, blacklist the hyperv_drm module by adding it to the /etc/modprobe.d/blacklist.conf file.