From: arne@vajhoej.dk   
      
   On 11/26/2024 12:54 PM, Arne Vajhøj wrote:   
   > On 11/26/2024 12:46 PM, Arne Vajhøj wrote:   
   >> On 11/26/2024 11:41 AM, John Reagan wrote:   
   >>> On 11/25/2024 10:06 AM, Arne Vajhøj wrote:   
   >>>> And dev systems is different. VirtualBox, Player/WorkStation,   
   >>>> KVM etc..   
   >>>>   
   >>>> (I know VirtualBox has been pushed a lot for this, but given   
   >>>> peoples experience on both Windows and Linux has been very painful,   
   >>>> then VSI should probably consider dropping that)   
   >>>   
   >>> All I use is VirtualBox on Windows10 and Windows11 systems.  Works   
   >>> great out of the box on W10.  It took a few W11 changes to avoid VB   
   >>> and HyperV from bumping into each other but once I made those   
   >>> changes, VB works fine on my W11 laptop.  There are several of us   
   >>> internal folks that use VB.   
   >>   
   >> Not everyone can get rid of anything Hyper-V as other stuff may require   
   >> Hyper-V.   
   >>   
   >> There has been several with problems using VirtualBox on Windows   
   >> due to Hyper-V conflict.   
   >   
   > For those that want to mess with it then VSI do have a page   
   > about it:   
   >   
   > https://wiki.vmssoftware.com/   
   > Windows_host_compatibility_settings_for_OpenVMS_on_x86_VirtualBox_guests   
      
   And a couple of new threads today including:   
      https://forum.vmssoftware.com/viewtopic.php?f=22&t=9321   
   which has link to a long instruction on how to get rid of   
   Hyper-V.   
      
   Arne   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)