On Tue, 04 Oct 2016 15:50:30 +0100, Andrew May wrote:
The idea of dual booting has never appealed to me other than with test
rigs when the chosen OS really, really must be installed directly onto
the hardware so when I was experimenting (again!) with Ubuntu 10.04 and
12.04 (IIRC) some 3 to 4 years ago, I decided to try out Oracle's
VirtualBox (version 4.xxx AFAICR) with win2k and winXP VMs. I was
pleasantly impressed with the results especially considering the hardware
(a micro ATX AM2+ MoBo with on-board Nvidia graphics with 2 or 4 GB of
DDR2 ram and a single core Semperon).
I knew I'd be radically upgrading my win2k desktop machine some 2 to 3
years later and was anticipating the need to finally retire win2k as a
host OS. With subsequent MSFT windows versions only going from bad to
worse with each "upgrade", I was pretty certain I'd be using a 'modern'
Linux distro as the host OS and being able to still run the few 'Must
Have' windows only app software was an important consideration in my next
planned upgrade.
At the time of testing, I was able to get a usb connected film scanner
to work in the winXP VM (despite claims on the box that the minimum
windows version it could be run in was win2k, the truth of the matter was
that it needed winXP so I couldn't use it with my win2k desktop machine
anyway). Encouraged by this, I also installed and tested the Quake2 and
Unreal games which ran surprisingly well, considering the hardware spec
(certainly more than 'just playable' in an 800 by 600 resolution - a nod
of acknowledgement to the limitations of the on-board graphics).
As per my expectations, the games performed better in the win2k VM but
when it finally came to the actual upgrade a year last April using Linux
Mint Rebecca KDE 64 ver 17.1 with a 3.8GHz clocked quad core AMD 4300 and
8GB of DDR3 ram, this performance difference became switched around. :-(
However, after some considerable fettling of the VMs I was able to see a
threefold performance boost when running MpegStreamClip in the winXP VM
to convert the m2t PS files recorded by Kaffeine into mpg PS files for
archiving onto the NAS box. Considering that the earlier hardware wasn't
too shabby for its time (it included a dual core 3.1GHz clocked Phenom
and 3GB of DDR2 ram and an Intel 180GB SSD (plus a couple of HDDs)), I
was quite pleased with the overall result (I'd limited the VMs to 2 cores
and 2GB for the win2k and 3 GB for the winXP VMs).
For me, hosting VirtualBox on a Linux distro with winXP and win2k VMs
has worked out rather nicely. The only major downside being the rather
shabby support for 3D driver support of the not too shabby EN 8400 GS
graphics adapter inherited from the previous hardware setup. However,
eliminating the need to inflict antivirus and antimalware on the machine
was a major bonus and the main justification to quit MSFT's world of pain
(little did I realise at the time *just* how much worse *this* was going
to become with win 10 - turns out my decision was even better than I'd
originally thought it was!).
Anyway, you can run VirtualBox (or its alternatives) under windows and
setup Linux VMs if 3D graphics performance is vital to your needs and
you're accepting of the need to install the necessary AV and antimalware,
anti-spyware tools. If you decide to try the virtualisation route, the
choice as to which way round you want to arrange this is entirely yours
(I've never tried hosting guest VMs under windows - it just seems so
wrong to me).
Dual booting with a modern desktop PC blessed with a quad core cpu on-
board and 8+GB of ram just seems a waste of resources to me. Modern multi-
cored cpu based systems seem to be just crying out to be used for
virtualisation imo. Oracle's VirtualBox represent the cheapest way to
experiment with virtualisation. It may not be the best virtualisation
software out there but it's not too far behind the commercial
alternatives costing hundreds or even thousands of pounds. If you can
spare the time to experiment, it's well worth trying it out with a
suitable Linux distro.
Any VirtualBox created guest VMs can be used either directly or imported
into more expensive alternative Hypervisor or virtualisation solutions so
your efforts needn't be wasted if you do decide to 'upgrade' later on. In
any case, the principles remain pretty well much the same with all
virtualisation software so the experience alone will prove useful even if
you land up having to recreate your guest VMs all over again.
Of course, there's always the hypervisor hosted option where every
desktop machine is a guest VM without a Linux or windows host in sight
but this tends to be the most expensive route. The last time I looked,
there were only commercial hypervisor solutions available to eliminate
the question of choosing between windows or a *nix host OS. For all I
know, this may have changed by now (but I rather doubt it).
--
Johnny B Good