Windows 10: Vmware or virtualbox?

I have tested out vmware workstation and virtualbox and can't decide which is best, can you help me?

:)

 

BSOD when running VMWare Player after Creators Update

The minidump files showed a consistent Unknown bugcheck code (e0000001) that appears to be caused by the vmx86.sys.

The vmware-vmx.exe is the process that crashed.

As the vmx86.sys and vmware-vmx.exe are components of VMware there may have been a corruption in the installation if the VMware software was present during the upgrade.

In any event try uninstalling VMware.

Then apply the following update for Windows 10:

https://support.microsoft.com/en-us/help/4022716

The reinstall VMware.

If the issue persists consider posting on the VMware forums.

The Unknown bugcheck code (e0000001) with VMware has been reported before although it appears to be rare such as:

Bluescreen 0xe0000001 in vmx86.sys |VMware Communities

 

Ethernet problem after recent Win10 update

Those driver names suggest you are running Windows 10 in a VMWare Virtual Machine. If that's correct, the best place for this enquiry is on the VMWare Forums as it's clearly a VMWare software issue.

 

If you have tested both, then it will come down to personal preference. I find VMWare Player easier and more intuitive.

 

Hi there

BMW / Audi / Mercedes. Take your choice.

My own view is that VMware is far more robust - but I haven't really messed around with VBOX. Why not try both -- Installing W10 twice is no big deal and there are also converters around to convert from one vm system to another one. Uninstall VMware tools / vbox additions on your GUEST systems before switching vm systems though. There's no reason why you can't have vbox and VMware installed.

Note both these products don't run when HYPER-V is enabled. Similarly HYPER-V won't work unless you uninstall both VMware and Vbox.

Cheers
jimbo

 

VMWare all the way for me !

*Smile

 

Running on what? VirtualBox is always free. VMware you have to pay for on OSX but (limited Player version) is free on Windows and Linux. The Workstation VMWare is again chargeable.

If my host was Windows I'd use Hyper-V. As it isn't and I don't want to pay $60 I use VirtualBox.

 

But there is so much more you can do in VMware and you can activate yiur copy by using a key off youtube videos or google.

 

BS. Please tell me one thing possible with VMware but not possible with Hyper-V.

See Forum Rules:

 

Merc

 

I personally prefer Hyper-V. My main machine at home is high end MacBook Pro running Windows 8.1 Pro. I can't get the track pad to scroll with VMWare, but I can with Hyper-V. The guest OS is Windows 10 Tech Preview.

Okay that is not a comprehensive evaluation on my part. Perhaps there is a way to make the scroll work on VMWare. But I couldn't find any. And there are many other issues to compare other than basic track pad functionality. But the track pad is a deal breaker for me.

I haven't tried VirtualBox. I did a few years back and was underwhelmed.

Also the price of Hyper-V is better. It's free!

 

See Forum Rules:

Kari
Hi Kari

It works on Linux !!!! (Sorry had to say that one).

Using Linux though you can use an equivalent (XEN or my preference - especially on Red hat based systems KVM) which also work pretty well.

You might find though using HYPER-V that dynamically adding and removing devices on the VM (USB cameras, HDD's etc) is a bit more fiddly and in some cases using the RDP system (Remote desktop) for connection can sometimes seem slowish.

All these things are "fixable" I agree in HYPER-V but for people relatively new to VM's I wouldn't suggest they start with HYPER-V.

Another issue is that if you have BOTH LINUX and WINDOWS HOSTS you can run the SAME VM (whether VMware or VBOX) on BOTH HOSTS without change / conversion etc.

BTW you don't have to pay 65 USD for VMware player - that's for the commercial use. Home users can download a FREE copy which works just fine.

One other thing I did notice on HYPER-V is that NETWORK SHARING of devices is more problematic - in the RDP I think you have to enable local devices as well as sound if you want it.

HYPER-V IMO works best if the VM is not on the same physical host. I know it works on laptops but I think HYPER-V would be better with the VM's stored on a remote server / file system rather than the machine you are actually using. For purely local use (i.e VM on a laptop I'd still go for VMware or vbox). Just my 2c though - of course other people will have different reasons for choosing their system.

Cheers
jimbo

 

I discovered by accident that if you have Hyper-V enabled Virtual Toolbox of VMplayer don't work. I attempted VTB and the list of option of OS's of the VM machine only showed 32 bit choices. I attempted to install the 32 bit Technical Preview and got an error. When I tried to use VMplayer it gave me an error something like can't use if Hyper-V VM exists. So I decided to use Hyper-V which i installed and no wireless but I googled and found out I have to create A virtual switch and select the wireless card. That worked fine the the VM got corrupt and I tried to reinstall the VM and I had to set the virtual switch again but I could get it to work. SO I went back to VMplayer. I read the error again and I though maybe if i disable Hyper-V it will work. I disabled Hyper-V in windows and when went to Virtual toolbox it showed 64 bit and 32 bit in the dropdown. I installed but it would let me go above 1600 by 900. So then I decided to try VMPlayer and it's working fine. I've added all the new builds with no problems.

Then my laptop broke and I sent it back to repair so I replaced my Windows 7 boot SSD with an older and smaller SSD and I installed The technical preview build 9926 and it's working fine.

SO my choice is VMPlayer as everything runs well except my camera.

 

I used vBox for years but there were always little gremlins. Now I use VMware Player which works very well for me. Only the printing from a Linux distro is a problem. That may be a driver problem though.

 

Well you can take snapshots and share VMs, you can also pause the state of your vm instead of having to start ALL over again.