From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [ANNOUNCE] kvm-46 release Date: Wed, 10 Oct 2007 13:28:30 +0200 Message-ID: <470CB75E.4000404@qumranet.com> References: <470C8D28.2060408@qumranet.com> <470CB672.4070209@bppiac.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Farkas Levente Return-path: In-Reply-To: <470CB672.4070209-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Farkas Levente wrote: > Avi Kivity wrote: > >> We've now switched to allocating guest memory in userspace rather than >> in the kernel. This is important if you have a mainframe, but also if >> you want to share memory between guests and implement nice features like >> swapping. >> > > 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. -- 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/