Windows 10: Can setting up a VM cause damage to main system

Hi,

It's many years since I looked at setting up a VM so memory is a bit hazy

If you set one up wrongly can it mess anything up on your PC

I am assuming the worst that can happen is if you allocate RAM wrongly you main machine will possibly crash but a reboot would fix this

Thanks

:)

 

Can I dual boot Windows 10 and Ubuntu on the same drive without partitioning

Up until now I have been using a VM running off of Hyper-V however I avoid putting my VMs on my main drive (Had bad experiences with VMs and Windows accessing the same drive at the same time).

 

How to install Windows XP on Hyper-V virtual machine?

The Media menu is in the VM Window not the Hyper-V manager Window, Select the previously created VM in the main panel of Manager and lower right you will find Connect. This opens the VM monitor Window without actually starting the VM. You can the insert
the CD image and "turn on" the VM.

 

I haven't heard anything like that.


But then again I haven't run a VM for years lol. Don't trust my advice.

 

You should be fine, you would have to work very hard to break anything using virtualbox. It is pretty straightforward too.

 

I agree.. I've never had an issue with VMWare.

 

Thanks for replies, didn't think there was but wanted to check

Have VMware installed, just need to wait for a time when I can download 10 to install

 

Yes, under certain circumstances if you're not vigilant. Say your OS resides on a 120GB SSD, and with a handful of other programs on there you have 60GB free. When setting up your VM in VMWare the default installation path is C: so if you create a virtual machine that will ever be allowed to reach that size you would have a problem. It would be easily sorted by simply deleting the VM, but if you have spent time setting it up you won't want to be doing that.

If you do set it up correctly though, as others have said, it can't affect your main machine.

 

I don't quite understand how the VM uses resources. During set up it asks how much Memory to allocate. If my system has 4GB and I allocate 2GB to the VM does that mean my main system will now only have 2GB to work with? Or can I give it everything and it will use what it needs with no effect on the host?

Someone said I should install the 32-bit version of Win 10 as a VM even though I have a 64-bit system because it will perform better with less memory. So I assumed the above reason was why.

 

You have it right. If you allocate 2GB to the VM, then you'll have that much less RAM for your main system. It's best on a system with only 4GB of RAM to stick with 32-bit for guest OSes.

 

The RAM assigned to vm is taken from the total amount of RAM available on your host. As the host still needs some of it to run, you cannot assign all of your host RAM to a vm. In your case you can assign a maximum of 2.5 to 2.8 GB to a vm out of 4 GB total, depending on the virtualization program you are using.

Some virtualization programs allow using so called Dynamic RAM. When Dynamic RAM is selected, the vm uses at any given moment only as much RAM as it needs though at least a set minimum, and never more than the set maximum. This example from Hyper-V virtualization, my Windows 10 Tech Preview vm:




Dynamic RAM enabled (yellow highlight), the VM starts with 1024 MB (#1) and is allowed to decrease and increase the amount of RAM it uses as it sees fit, though always using a minimum of 512 MB and never exceeding 4096 MB (#2).

 

Thanks to both of you for the excellent explanation.

 

Hope and am not going to get major issues trying to get 10 working

Just spent 12 hours downloading the 64-bit version and I only have 4GB RAM, currently on 8 i am at 41% RAM used so hopefully have enough to spare

Thanks for tip, will remember that for the future

 

You'll only be able to allocate 2GB (at most) to the VM. 64-bit Win 10 should install in 2GB but probably won't run optimally.

 

If host has 4 GB, Hyper-V allows you to assign 2.8 GB of that to vm, although it leaves so little RAM to host that you can only run the vm if you have at least 3.2 GB free RAM when vm is launched.

Here a screenshot from a 4 GB system. I try to assign all RAM (4 GB) to vm (#1), system warns me and tells what's the maximum (#2):