Re: Bare Metal VMS (Frame.Work Laptops) <<<< complete answer late

On 11/26/2024 5:35 PM, Dave Froble 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)
>
Arne
>
>

>
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.

 Yes, and I've played with it in the past.  Seemed to work Ok.
 But as recently mentioned, development is one thing, but critical operational environment might be a bit more demanding.  Do you have any opinions about VirtualBox in a critical operational environment.  Just curious.
 

My opinion is that you should read the official statements from VSI about support.  Nobody suggests using VB in a critical environment. Will it work?  I don't know.  It has never failed me for the things I do. I don't run a cluster.  I don't have shared storage.  I don't do things that a real system does. I'm just a poor compiler guy picking up rocks and pulling weeds in the field.
As for the network bounce at upgrade time, it hasn't been a problem for me.  I have PuTTY windows thru a WireGuard VPN back to VSI systems and they don't drop.  I've even been streaming a YouTube video and didn't see a problem (I'm sure something had to recover, refetch, etc. in the browser).