Processor-setting problem for VMWare player on Ubuntu

Topic

New Reply

The latest version of Ubuntu running the latest version of VMWare Player and VMWare tools. I copied over a VM to use and it had been set to use 4 processors so I was going to change it to one, which was the proper number for this particular elderly statesman in the computer household.
The problem is that no matter what I did, I could not set the number to 1. I could set it to 2, to 4 again, even to 8, but not to 1.
I only resolved the matter by going back to the original VM on a Windows system and adjusting the processor count there to 1 and then copying over the 50some GB VM to the Ubuntu system again.

I’m not very familiar with Ubuntu so I was wondering if this was a bug, a fluke or if there was something else I had to do to make it work as it should have.

Secondly, a little research has led me to believe that in order to view the Ubuntu desktop remotely on a Windows system I need to install one of the flavors of VNC on that Windows system, and that all the tools for allowing the Ubuntu system to be a remote desktop server are already available (I just need to find them : ) ). Is that true? If so, I’m pretty familiar with UltraVNC; is that as good a choice as any?

Reply | Quote

Replies

Sorry I don’t know the answer to your first question as I have no experience with VMWare on Ubuntu.

VNC is indeed the default remote desktop; and the default flavor is Vino. You activate/configure it in system settings/remote desktop. There is a lot of traffic saying Vino security is not very good, but I use it only for local connections so I think it is OK for that. I have used both RealVNC and TightVNC viewers and they work fine, but have never tried UltraVNC.

Jock

Reply | Quote

Thanks, yea I only want to get it working for local network access.

Once I got the configuration correct so the VM would run, I’ve been using it remotely for a day or so without any further issues so overall its working very well.

Reply | Quote

Coolest use of Ubuntu I’ve found so far…a NAS started beeping and the error light was on…no access.
Removed the drive, put it in a USB toaster and plugged into the Ubuntu box, recognized right away, understood the file system and I was able to locate the data files and a few hundred gigs of data are being copied over to another NAS until/if I can figure out what exactly is wrong with the faulty NAS.
First time LINUX saved me some time (unless GParted counts). :p

Reply | Quote