mhbell, on 20 April 2017 - 09:57 PM, said:
I will address this mostly to Raymac because he uses Mint the same as I do, but anyone else can chime in. Here are my questions.
1. Are you or anyone else running VBox in Windows 10?
2. What are the spec's of the computer you are running win 10 and Vbox on?
3. What Linux Distro are you running Vbox on?
4. How big a hard drive or ssd are you using, and how much memory?
5. What CPU are you running?
6. How well does the VM work in Windows 10?
7. How well does windows 10 work running in a VM?
I am thinking of setting up a VM in Windows 10 and in Linux Mint 18.1. I would be using a 250 GB SSD Disk. I have 16 GB ram and a AMD 3.1 Ghz cpu. Any help or advise appreciated.
3. Lubuntu (all machines)
4. 256GB Intel(?) SSD on main rig, with 1TB SATA for /home and another 1TB SATA for backup; 64GB Patriot Torch SSD on media rig, with 2TB SATA for /home and 2TB HD in external caddy for backup
5. Intel® Core i7-4770 CPU @ 3.40GHz in main rig; AMD FX-6200 in media rig
7. I have a Win10VM and Win7VM on main rig, with Win7VM and WinXPVM on media rig; all run just fine. FWIW, I think WinXP and Win7 run better in a VM than they do on metal, and they're certainly easier to work with, IMO. As long as you backup regularly (I do!), there is no reason to spend hours troubleshooting a Windows issue...unless you choose to....as it is simply so much easier to just restore a snapshot or (in the event of a massively buggered-up system) to just import your backup VM. In 5-10 minutes, you are back up and running as if it never happened. I can't compare Win10VM to bare metal, as I've only used Win10 in a VM.
I had Win10 Technical Preview on my media rig (which was my main rig until about 6 months ago), but I had activated it for an "official" license. When I built my new rig and migrated all my data, including VMs, I "lost" my official Windows status as I learned through MUCH trial & error that Win10 licenses are tied to hardware UUIDs, a combination of motherboards, hard drives, etc...and when I switched the Win10VM from an AMD-based motherboard and AMD-FX CPU and ATI discrete card to my NEW rig, with an Intel-compatible motherboard, Intel i7 CPU and integrated GPU, Win10 just wouldn't activate. I ended up downloading and installing a new Win10 Technical Preview, but I can't activate it. I can install other software on it (anti-virus, browsers, etc...) and it works just fine. I have to keep it fairly updated (especially when I get a notification from Windows Insider that a new Tech Preview was released), but it seems the only penalty from not being able to activate is that I can't change my themes/appearances. I can live with that trade-off for a VM. At some point in the future, I may even purchase a Win10 license so that I can activate and therefore, migrate to another machine in the future. Until then...no biggie for me.
I WHOLEHEARTEDLY endorse WinVMs! Unfortunately, we live in a world where sometimes you HAVE TO use Windows to do something, and it sure is nice to click on Virtualbox, click on Windows and have it available like your browser, or e-mail, or music player.....do what you need to, then click close>save settings and move on to your next task. The next time you need Windows, your VM will fire up IMMEDIATELY and restore the last Windows session exactly as you left it! No more waiting on boot-ups, or the lengthy dual-boot process. The only downside to VMs that I can think of is the "splitting of resources" between the host & guest, i.e. CPU cores, RAM, etc... Recommended best practices is to make sure that host has 50% plus, while guest receives less than 50%; but with a machine like yours, that shouldn't be any problem whatsoever.
I'll echo others advice in this thread...a good rule of thumb for VMs is 2 cores or less for CPU, maximum 128MB for video, and 2GB for RAM. I haven't experienced any VMs struggling with those resources, FWIW. Sometimes, I'll only allocate a single core to CPU and/or 1GB or less of RAM, just to see how a "low-resource" distro actually performs with low resources! For Windows10 in a VM, I might suggest 2 cores and bump the RAM to 4GB, and it should run just fine for you. If it doesn't, something isn't configured properly, such as forgetting to "enable I/O apic" in VM settings....or not enough video memory, etc...
Lastly, Win10 will require 25GB+ for installation, so you should probably provide it a 50GB+ virtual disk to allow for other software and updates, and "dynamic" disk size. GOOD LUCK!