---------- Original Message ----------- From: Avi Kivity <avi@xxxxxxxxxx> To: Riccardo <andrighetto.riccardo@xxxxxxxxx> Cc: kvm@xxxxxxxxxxxxxxx Sent: Sun, 23 May 2010 16:30:06 +0300 Subject: Re: Gentoo guest with smp: emerge freeze while recompile world > On 05/23/2010 03:12 PM, Riccardo wrote: > > ---------- Original Message ----------- > > From: Avi Kivity<avi@xxxxxxxxxx> > > To: Riccardo<andrighetto.riccardo@xxxxxxxxx> > > Cc: kvm@xxxxxxxxxxxxxxx > > Sent: Sun, 23 May 2010 14:38:42 +0300 > > Subject: Re: Gentoo guest with smp: emerge freeze while recompile world > > > > > >> On 05/21/2010 07:47 PM, Riccardo wrote: > >> > >>> > >>>> If you are using kvm-clock, maybe try disabling that. > >>>> > >>>> > >>>> > >>> $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource > >>> hpet > >>> > >>> This is from server, not from VM (that have freeze). > >>> > >>> > >> What about the guest? > >> > >> -- > >> error compiling committee.c: too many arguments to function > >> > > ------- End of Original Message ------- > > > > # dmesg | grep clock > > [ 0.000000] kvm-clock: cpu 0, msr 0:1845bc1, boot clock > > [ 0.000000] kvm-clock: cpu 0, msr 0:28047bc1, primary cpu clock > > [ 0.000999] hpet clockevent registered > > [ 0.084027] kvm-clock: cpu 1, msr 0:28063bc1, secondary cpu clock > > [ 0.102059] kvm-clock: cpu 2, msr 0:2807fbc1, secondary cpu clock > > [ 0.120035] kvm-clock: cpu 3, msr 0:2809bbc1, secondary cpu clock > > [ 0.148051] kvm-clock: cpu 4, msr 0:280b7bc1, secondary cpu clock > > [ 0.173039] kvm-clock: cpu 5, msr 0:280d3bc1, secondary cpu clock > > # cat /sys/devices/system/clocksource/clocksource0/current_clocksource > > kvm-clock > > # cat /sys/devices/system/clocksource/clocksource0/available_clocksource > > kvm-clock tsc hpet acpi_pm > > > > > > Please try with kvmclock disabled. I have recompile gentoo-sources-2.6.34 without kvm-clock: # cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc # dmesg | grep clock [ 0.000000] hpet clockevent registered [ 0.661050] Switching to clocksource tsc And with this kernel all working fine! (emerge -e world) It's a problem in the kvm-clock for kernel >=2.6.32 > > Do you think it's a related issue with the system freeze under compiling with > > newer kernel? > > > > That's what we're trying to find out. > Ok, It's only a simple question :) Thanks for your support and to Brian Jackson -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
