Farkas Levente wrote: >>> we did a quick test against this version and it's turn out the smp >>> guests are still not working. even if we start only one linux guest with >>> 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel >>> loading process (if we run more smp guests then they hang earlier, but >>> different random stage), but it's never reach the end of the kernel so >>> hang somewhere inside the kernel. and the cpu usage of these process >>> goes up to until the qemu-kvm processes eat all cpus (ie. 100%). t >>> >> What host cpu are you using? What guest kernel version? 32-bit or 64-bit? >> >> I have no problems running a 4-way Linux guest here. >> > > - host: > - Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz > - Intel S3000AHV > - 8GB RAM > - CentOS-5 > - kernel-2.6.18-8.1.14.el5 x86_64 64bit > - guest-1: > - CentOS-5 > - kernel-2.6.18-8.1.14.el5 i386 32bit > - guest-2: > - CentOS-5 > - kernel-2.6.18-8.1.14.el5 x86_64 64bit > - guest-3: > - Mandrake-9 > - kernel-2.4.19.16mdk-1-1mdk 32bit > - guest-4: > - Windows XP Professional 32bit > > start the first guest-1 with 4cpu produce the above hang. (and of course > using kvm-46:-) > >
Is it the only guest that hangs with -smp 4? Or all of them? -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
