Hi,
I'm about to setup a CentOS4 server to install VmWare Server on it. Then I'll run 2 main guest OS, Microsoft SBS 2003, and a CentOS development LAMP server.
Except from the clock settings, is there any problems/comments?
Regards,
Ugo
Quoting Ugo Bellavance ugob@camo-route.com:
Hi,
I'm about to setup a CentOS4 server to install VmWare Server on it. Then I'll run 2 main guest OS, Microsoft SBS 2003, and a CentOS development LAMP server.
Except from the clock settings, is there any problems/comments?
I had it running on VmWare Workstation and ESX. Nothing special other than the clock problems. If I remember correctly, after updating the kernel and rebooting, you'll need to re-run vmware-config.pl script in the guest.
You'd probably want to download and install latest version of vmware tools on the guest. Latest version of vmware tools has kernel modules that load perfectly into CentOS 4 kernel (if you attempt to install too old version of vmware tools, you'd need to recompile the modules).
On Mon, Oct 16, 2006 at 03:08:27PM -0500, Aleksandar Milivojevic wrote:
Quoting Ugo Bellavance ugob@camo-route.com:
Hi,
I'm about to setup a CentOS4 server to install VmWare Server on it. Then I'll run 2 main guest OS, Microsoft SBS 2003, and a CentOS development LAMP server.
Except from the clock settings, is there any problems/comments?
I had it running on VmWare Workstation and ESX. Nothing special other than the clock problems. If I remember correctly, after updating the kernel and rebooting, you'll need to re-run vmware-config.pl script in the guest.
I'm running VmWare Workstation on two centos 4.4 machines (one, at home, an Athlon 32bit where Centos 4.4 was an upgrade from earlier version running VmWare 5.5.1, and one at work which is a P4 2.26ghz HP Proliant DL320-G2 server, VmWare 5.5.2).
But I don't know what this "clock problem" is that's mentioned here. Can someone enlighten me, and perhaps even describe what one does to cure it?
Thanks!
You'd probably want to download and install latest version of vmware tools on the guest. Latest version of vmware tools has kernel modules that load perfectly into CentOS 4 kernel (if you attempt to install too old version of vmware tools, you'd need to recompile the modules).
-- NOTICE: If you are not intended recipient, you are hereby notified that by reading this message you agreed not to disturb frogs during mating season. For more info, visit http://www.8-P.ca/
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
fredex wrote:
But I don't know what this "clock problem" is that's mentioned here. Can someone enlighten me, and perhaps even describe what one does to cure it?
When running 2.6 kernels in the guests, clock either runs way too slow or gains time very fast. The problem exists for almost all Linux distributions that use 2.6 kernels. Ntpd won't save you since system clock in the guest is way too unstable for it to work. There's couple of workarounds, the most common is to use clock=pit on kernel boot line and to use vmware-tools to synchronize guest's clock with the host clock (the host's clock can be synced using ntpd to outside source).
On Mon, 2006-10-16 at 21:02 -0500, Aleksandar Milivojevic wrote:
fredex wrote:
But I don't know what this "clock problem" is that's mentioned here. Can someone enlighten me, and perhaps even describe what one does to cure it?
When running 2.6 kernels in the guests, clock either runs way too slow or gains time very fast. The problem exists for almost all Linux distributions that use 2.6 kernels. Ntpd won't save you since system clock in the guest is way too unstable for it to work. There's couple of workarounds, the most common is to use clock=pit on kernel boot line and to use vmware-tools to synchronize guest's clock with the host clock (the host's clock can be synced using ntpd to outside source).
I may just be lucky, but as long as I am able to install vmware-tools, my clock has been fairly stable on vmware server version 1.0.1 build-29996.
That is using an i386 host (on x86_64 machines) ... then installing either i386 or x86_64 clients.
If I can't install vware-tools on the client and set the client to sync time from the host, the clock is pretty much shot, even with clock=pit. At least that is my experience.
Thanks, Johnny Hughes
Quoting Ugo Bellavance ugob@camo-route.com:
Johnny Hughes wrote:
That is using an i386 host (on x86_64 machines) ... then installing either i386 or x86_64 clients.
Regarding this, the host system is a dual-core Opteron... Should I use the x86_64 distro of Centos 4 or x86?
Depending on the type and version of VmWare you have. Some support x86_64 guests, some don't. For example, you'd need to have latest update to have x86_64 guests in ESX 3. Check VmWare's web site for details about the type and version of VmWare you have.
On Wed, 2006-10-18 at 15:14 -0400, Ugo Bellavance wrote:
Johnny Hughes wrote:
That is using an i386 host (on x86_64 machines) ... then installing either i386 or x86_64 clients.
Regarding this, the host system is a dual-core Opteron... Should I use the x86_64 distro of Centos 4 or x86?
Regards,
Ugo
What I normally do is this (with the free vmware server 1.0.1):
I install a minimal i386 on the host, install vmware, and do nothing on it except create the clients.
The vmware server requires the i686 glibc and other files to run even on x86_64, so I just make the host i386.
There might be some performance degradation wrt i386 instead of x86_64, but I have not really noticed a difference after trying a vmware x86_64 host on one machine.
You can install either x86_64 or i386 distros as a client OS on a machine with an i386 vmware host installed (again, I am specifically talking about the free server version).
Johnny Hughes escribió:
On Wed, 2006-10-18 at 15:14 -0400, Ugo Bellavance wrote:
Johnny Hughes wrote:
That is using an i386 host (on x86_64 machines) ... then installing either i386 or x86_64 clients.
Regarding this, the host system is a dual-core Opteron... Should I use the x86_64 distro of Centos 4 or x86?
Regards,
Ugo
What I normally do is this (with the free vmware server 1.0.1):
I install a minimal i386 on the host, install vmware, and do nothing on it except create the clients.
The vmware server requires the i686 glibc and other files to run even on x86_64, so I just make the host i386.
There might be some performance degradation wrt i386 instead of x86_64, but I have not really noticed a difference after trying a vmware x86_64 host on one machine.
You can install either x86_64 or i386 distros as a client OS on a machine with an i386 vmware host installed (again, I am specifically talking about the free server version).
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
But with a minimal instalation of CentOS, (with vmware server 1.0.1) don't you need X11 if you install a windows guest operative system??
sorry about my english!!!
Lazo
On Thu, 19 Oct 2006, Ing. Manuel Lazo wrote:
But with a minimal instalation of CentOS, (with vmware server 1.0.1) don't you need X11 if you install a windows guest operative system??
sorry about my english!!!
Lazo
Not if you access the vmware image from another box.
------------------------------------------------------------------------ Jim Wildman, CISSP, RHCE jim@rossberry.com http://www.rossberry.com "Society in every state is a blessing, but Government, even in its best state, is a necessary evil; in its worst state, an intolerable one." Thomas Paine
-
Aleksandar Milivojevic -
fredex -
Ing. Manuel Lazo -
Jim Wildman -
Johnny Hughes -
Ugo Bellavance