From b41887caf1057aacca68c30d229a042848b041be Mon Sep 17 00:00:00 2001 From: cieska <41318524+cieska@users.noreply.github.com> Date: Tue, 20 Feb 2024 21:27:12 +0000 Subject: [PATCH] Update virtuals.rst Note added to Hyper-V section when creating VM. --- source/manual/virtuals.rst | 19 +++++++------------ 1 file changed, 7 insertions(+), 12 deletions(-) diff --git a/source/manual/virtuals.rst b/source/manual/virtuals.rst index a31e9f03..ea74135f 100644 --- a/source/manual/virtuals.rst +++ b/source/manual/virtuals.rst @@ -48,9 +48,8 @@ HyperV ------ HyperV Generation 1 and 2 are supported out of the box, no additional drivers or tools are needed. -Secure Boot must not be enabled in the hardware settings for the VM. -.. image:: images/hyper-v_no-enable-sec-boot.png +* Secure Boot setting must be un-ticked in the Hardware > Security section for the VM. ------ KVM @@ -122,32 +121,28 @@ Common Issues Some common issues have been reported for different virtual environments. You can find known solutions to these problems below. -If you problem is not listed always try the General tips as mentioned in the +If your problem is not listed always try the General tips mentioned in the article first. ------------------- File copy failed during installation ------------------------------------- +------------ This issue is most likely caused by low memory setting. Make sure your virtual OPNsense installation has a minimum of 1 GB of RAM. ------------------- Disk Errors on VMware ------------------------ -This issue can be caused by a defective drive. Changing drive mode to IDE has +------------ +This issue can be caused by a defective drive. Changing the drive mode to IDE has been reported to help for certain ESXi versions. ------------------- NAT issues on XenServer ------------------------ +------------ This issue has been reported to be solved by disabling checksum offloading on both OPNsense domU and Vifs. ------------------- Traffic Shaper does not work on VMware --------------------------------------- +------------ If you are using vmxnet3 drivers try to switch to E1000.