From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 14 22:23:43 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 860151065672 for ; Sat, 14 Jul 2012 22:23:43 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 022238FC12 for ; Sat, 14 Jul 2012 22:23:42 +0000 (UTC) Received: by weyx56 with SMTP id x56so4358658wey.13 for ; Sat, 14 Jul 2012 15:23:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=from:reply-to:to:subject:x-mailer:references:in-reply-to :content-type:content-id:date:message-id:mime-version :content-transfer-encoding; bh=SqZPdQv1ZQODNQZewIgtDq5jylA+tJR8/B6iKgFQFvs=; b=ef4wDfGbeYDcLJ/js/lY5eGEyt4zFQ8osfzx76kWLj97zWVilI9p3Xsg39CNEoxrVG tMrIKlE7rtGs73Odqu8uG1+7Lm1IZZLOH7ezDuZ6y2w1tPQsZmgHdIxTnG+ZvV7XqCqf Zc9XjrHZBXDUzrn0dXqqdmeLO/VozaezPBnYk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:reply-to:to:subject:x-mailer:references:in-reply-to :content-type:content-id:date:message-id:mime-version :content-transfer-encoding:x-gm-message-state; bh=SqZPdQv1ZQODNQZewIgtDq5jylA+tJR8/B6iKgFQFvs=; b=V/GL3E4TJhgVR6sF5iJf0yAdDDhcPGbdvCz/axQmc7n0BSxytRXVUinxyhBslYtEGA KH6JkD0E3jn2SUlK6kO7w2McUVCbOuOWl1W8p+bqaGIAck2mztqvJAiA30FPcT/s0eql DE4yHMXGI1nGxLPmd+WuBLMKHIdBpN5CSZHnvxMuas1IuS/lwFLcY9vqpPFXqaZoVEGE YEAMFS9vwAwiqYVgER874HRBhHUM2iIXN5veC2jv/E1Wfp49bG6LOMC6xnWhEvwn/pli aG2H/ArWE/EGzN/ljv2fEayKpGkJ4DEuQecosWOSYMfqSaWYqrD2cwJx40Pd4d0EbeGK p29Q== Received: by 10.180.92.7 with SMTP id ci7mr9043053wib.1.1342304621781; Sat, 14 Jul 2012 15:23:41 -0700 (PDT) Received: from [10.37.82.177] (089144192238.atnat0001.highway.a1.net. [89.144.192.238]) by mx.google.com with ESMTPS id fr4sm17821231wib.8.2012.07.14.15.23.39 (version=SSLv3 cipher=OTHER); Sat, 14 Jul 2012 15:23:41 -0700 (PDT) From: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= To: Mike Meyer , freebsd-hackers@freebsd.org X-Mailer: Modest 3.90.7 References: <20120714061141.473cc8ee@bhuda.mired.org> In-Reply-To: <20120714061141.473cc8ee@bhuda.mired.org> Content-Type: text/plain; charset=utf-8 Content-ID: <1342304614.3162.1.camel@Nokia-N900-42-11> Date: Sun, 15 Jul 2012 00:23:35 +0200 Message-Id: <1342304615.3162.2.camel@Nokia-N900-42-11> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQnFQLMIABt2SFhGaaU/QkL0zwmLqpYm8YSAqYNSZMl0oqCUqS4edZ+NzGdOVR7DFAop6UI0 X-Mailman-Approved-At: Sat, 14 Jul 2012 22:29:55 +0000 Cc: Subject: Re: FreeBSD 8.3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2012 22:23:43 -0000 On Sa., 14. Jul. 2012 12:11:41 CEST, Mike Meyer wrote: > I just set up a system designed to handle lots of VBox VM's: a 6-core > SandyBridge processor with 32GB of ram on a FreeBSD 8.3-STABLE host. > > Unfortunately, once I got it set up, I found that VBox guest > performance simply sucks. The *mouse* isn't responsive. Linux guests > see lots of "CPU Locked" errors. Does the VM use multiple vCPUs? Does reducing to one vcpu help? I have seen a lot of instabilities and problems in the past when using more than one vcpu. Where is that cpu locked reported? You could also try to build the vbox port with debug option enabled and look at VBox.log which gives probably useful information in case there are soft errors that cause the slowdown or if some of the vt-x features were incorrectly detected and vbox had to fallback to the recompiler (=slow). > Googling turns up lots of problems with VBox on SandyBridge: Mac's > running on 64 bit kernels have this problem - running on 32 bit > kernels helps. Turning off Intel's SpeedStep has been reported to > help. Turning off VT-X in the guest - if it's a 32-bit guest - > helps. The last one is the only one that actually helped me. Just to be sure which vbox version are we talking about? You could try emulators/virtualbox-ose-legacy to verify if it is a regression of 4.1.x. > I was wondering if anyone here had run into and solved similar > problems? Or if they were running a similar system, and didn't run > into that problem? Especially anyone running 9.0 instead of 8.X I've not heard about that before so it wasn't reported at least.