VirtualBox gave me the following error:
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).


Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


I could mess around with BIOS settings, but not tonight.

On Sun, Aug 5, 2018 at 11:19 PM Richard Klein <rich@richardklein.org> wrote:
I'm not sure VMs are a good solution on my hardware.  I can't enable Hyper-V in Windows because the processors don't support SLAT.  I'll give it a shot with VirtualBox, though.

On Sun, Aug 5, 2018 at 10:27 PM John Stoffel <john@stoffel.org> wrote:

Richard> This is old hardware.  It's a dual-Xeon Dell Precision 490. 
Richard> The Dell support page says warranty coverage began on July
Richard> 10, 2007, so it's no spring chicken.  It has some Nvidia
Richard> video card that's old, but newer than the computer, but I use
Richard> Plex to stream to a Roku or XBox, so the video card is kind
Richard> of a moot point.  Also, I live alone, so I don't have to
Richard> worry about anyone rebooting the computer on me (aside from
Richard> hardware and power failures).  I'd really like to build
Richard> something quieter and more efficient for a Plex server, but
Richard> that's a pretty low relative priority.

Richard> I've used Debian, Mint, Ubuntu, and OpenSUSE in the past. 
Richard> They were all good.  I kind of wanted to try something new,
Richard> but right now I'm leaning toward Mint.

So try Fedora for a while and see how you like it... it's not my
personal favorite, but I'm also not happy with systemd either, but all
the distros are going that way.  I can understand the
advantages... but the interface is done by the same guys who did the
Sun/Oracle Virtual hosts tools, and the linux 'virsh' tools.
Basically high on crack and their own world view and not actually
thinking of the common man.

But I'll stop there...

but I will say it should be easy enough to fire up VirtManager and to
try out a couple of distros before you actually commit.

John