virt February 2008

virt@lists.centos.org

15 participants
7 discussions

Re: CentOS-virt Digest, Vol 6, Issue 11
by chanms 27 Feb '08

27 Feb '08

I apologize, but it appears that I was missing one digest in my email box(issue 9). Hence I though my submission never went through to the list, thus resent my email to the list. I'll go to the list archive and check out the missing replies. M. Chan > From: Elliot Lee <elliot(a)vmware.com> > Subject: Re: [CentOS-virt] Fwd: Fast clock under VMWare > To: Discussion about the virtualization on CentOS > <centos-virt(a)centos.org> > Message-ID: <C3E9B88C.5B99%elliot(a)vmware.com> > Content-Type: text/plain; charset="US-ASCII" > > On 2/26/08 12:28 PM, "chanms" <chanms(a)gmail.com> wrote: > > > What other things I can do in order to fix this? > > Hi, > > There were a few replies to your post on Friday. Please follow up on them. > > Best, > -- Elliot

1 0

Fast clock under VMWare
by chanms 26 Feb '08

26 Feb '08

Hi everyone, I have been struggling with having the clock of Linux VM's (including CentOS 4.6 and 5.1) running very fast under VMWare, no matter what I have tried. My platform: - AMD Turion X2 TL-60 - AMD 690 chipset with integrated Radeon x1250 (probably doesn't concern in this case) - Windows Vista Ultimate x64, all Windows Update patches loaded (no SP1 yet) - 4GB RAM - VMWare Workstation 6.0.2 - BIOS has no options to disable power management, etc. On my host PC - C:\ProgramData\VMware\VMware Workstation\Config.ini, put in host.cpukHz = "2000000", host.noTSC = "TRUE", ptsc.noTSC = "TRUE" - AMD's dual core optimizer loaded On CentOS 5.1 VM - use kernel options "noapic nolapic nosmp clocksource=acpi_pm" - use "divider=10" option in the regular kernel - try the vm version of the kernel in centos-plus with the same kernel options in first line No matter what I try, the CentOS clocks are still fast - at a rate of almost 2 seconds for every 1 real second. What other things I can do in order to fix this? M. Chan

5 6

Issue with dom0 xen ballooning
by Frederic SOULIER 21 Feb '08

21 Feb '08

Hi all, I'm having issue with my Centos 5.1 /Xen installation. I'm having some dom0 running 2.6.18-53.1.6.el5xen (x86_64). On the dom0 where the load is high (more than 70% of total system memory consumed by dom0 and domU) we have a lot of "memory squeeze ". The result is that the domU seems to be blocked (no network/no disk acces/ etc....). Looking for a solution in xen user list, it seems the problem come from dom0 xen ballooning. With this option the dom0 attempt to use the maximum of the system memory and "balloon" is memory when new domU needs memory. To resolve it, we have to fix the dom0 memory usage to avoid dom0 ballooning and crash in our production environnemnt. The solution seems to pass a parameter at xen boot time (in grub) to limit dom0 memory usage : " dom0_mem=256M " As anyone encounter this type of problems ? Is there any other solution than limitting dom0 memory usage ? Regards -- Frederic Soulier Administrateur Reseau Centre de Ressources Informatiques Université Toulouse 1 Sciences Sociales 2 RUE DU DOYEN GABRIEL MARTY 31042 TOULOUSE CEDEX 9 Tel : +33 5 61 63 39 98 / +33 5 61 63 39 98 Fax : +33 5 61 63 37 98 Bureau : AR38 bis http://cri.univ-tlse1.fr/

3 3

CentOS 5.1 guide for VMware Fusion
by Bradley Sepos 19 Feb '08

19 Feb '08

Hello all, I recently created a VM running CentOS 5.1 x86-64 for development purposes. Along the way, I found a number of fixes to various issues one can experience under VMware and decided to turn my documentation into a general guide that others might benefit from. I have not found any guides for VMware Fusion on OS X, so I figured it is a worthwhile endeavor. It is likely that most or all of this guide applies to VMware Workstation as well. I welcome any additions or corrections. I am open to reposting on the wiki. Look forward to your replies... Cheers. Bradley~ (See the attached text document.)

3 3

VMWare Server -- Which Kernel is Best
by John Thomas 09 Feb '08

09 Feb '08

I read http://bugs.centos.org/view.php?id=2189 Summary: CentOS is not getting optimal performance in a virtualized environment and on slow cpus but I am not sure I understand the current best practice. Your thoughts would be appreciated. Options as I see them: 1. Run kernel-vm-2.6.18-53.1.4.el5 with clocksource=pit until the excellent CentOS team builds the latest kernel into a VM kernel (This is working for me now). 2. Run kernel-2.6.18-53.1.6.el5 with divider=10 and hope the clock does not go fast (I have not tried this). -- Sincerely, John Thomas

2 1

Build VirtualBox OSE for CentOS?
by Johnny Hughes 04 Feb '08

04 Feb '08

Is there any need for CentOS to build and distribute the OSE version of VirtualBox? The differences between the versions are here: http://www.virtualbox.org/wiki/Editions The reason I ask is that the Full version is free for personal use and the restrictions (especially no USB or RDP) make the OSE version fairly crippled, so I am not sure there is enough benefit to design and keep updated the OSE RPM packages. What does everyone think? Thanks, Johnny Hughes

3 3

Xen performance (very slow) problem with 4GB of RAM.
by Michael Olson 03 Feb '08

03 Feb '08

I just took the x64 CentOS 5.1/Xen system I've been working on and upgraded from 2GB to 4GB of memory. Fresh minimal install of the OS (to remove some 3.2 stuff I had done trying to make PCI passthrough work). No special options, just a flat out default install. Dom0 is incredibly slow, I haven't tried DomU's yet to see if they are affected. X in particular is impressively slow (you can watch the screen be filled in one little block at a time, with several seconds between blocks) but it's not just video apps, it takes a considerable amount of time for the Xend daemon to start during boot. Before worrying about it I updated everything, same problem. Nothing interesting looking in dmesg or /var/log/messages. I tried out the vanilla kernel and it booted/ran well, no sign of the problem. Next, I tried Dom0 limited to 1.5GB (kernel /xen.gz-2.6.18-53.1.6.el5 dom0_mem=1536M), and it performed well. This workaround is probably adequate for me, I haven't found what the boundary conditions are on the problem and I haven't tested DomU performance yet. A Google and BugTracker search didn't turn this problem described elsewhere, is this known or is this something unique to me? Thanks -- Michael

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt February 2008