Hi All; I'll try and answer all the questions: Why are you expecting stability when the host OS you are using is betaware? Use CentOS as your host OS and you might get better results. I use Fedora for the eye-candy, and the fact that the stuff I most often use just works. I understand that it's a beta but I don't want to go to a centos desktop. Basically I want it all and I want it now, and most of the time Fedora delivers for me What VM's do you need, e.g., do you need to run Windows or just
linux VM's? Is there are reason to rule out VirtualBox and
lightweight tools (LXC -- Docker, LXD, etc)?
I run mostly Linux VM's although I do have a couple of mac VM's and one windows VM for clients that force me to use VPN's that I can only get running on mac or windows. I'm actually testing virtualbox as we speak. However I may be stuck with VMware to keep the mac VM's running - The
issue of it breaking every 2-3 kernel updates is a little vague;
though this might simply be the outdatedness of an older instance
of VMware Tools in the VM. Simply keeping VMware Workstation up
to date, and periodically ensuring your VM's get updated
(consistent with the version of VMware Workstation) and that their
internal VMware Tools also get updated will likely reduce the
frequency of this problem, again, assuming it is kernel version to
VMware Tools version related.
The current issue is that VMware workstation
12.5 Pro does not start with kernel 4.9 (the latest update).
Luckily I caught it before I updated my laptop but I see this
somewhat often and sometimes there is a patch and sometimes I just
have to wait but I use these VM's for testing day to day so I need
to do what I can to ensure they are runningI know I'm wanting the moon, looking for a possible replacement cause I want a fully patched laptop and my VM's to work. Just poking around t see if there is a better plan. Thanks for all the feedback |
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx