From owner-freebsd-current@FreeBSD.ORG Fri Aug 3 22:36:14 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A17C106566C for ; Fri, 3 Aug 2012 22:36:14 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 29CC78FC0C for ; Fri, 3 Aug 2012 22:36:13 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so985761wgb.31 for ; Fri, 03 Aug 2012 15:36:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dq5Yw/g9IWL8Go549aLZ7Fg8+hJ16zQ4GBv2fVfoAVU=; b=kg6lGb4RHoG22vQtNzQL3unOUblZxDwNu2ol8R1kurSU6/OwNccl2Y1CKThHKJZY0r ad40S33Mr19F9mKpGSTnsL9Nn6wYdAsFUTgJDIGAdYXjKMPhG5+0dXUwjJX9C7uzdeEK CUcI2bB9AM7Gb7wRPoyBAj5GB7CThzz0P0W86G4M3A+hwjM+O8rg8dCPEX/OwdA6SVu/ 1MIO+XqYl2DbD2P46c1bodh67itUluTyQMEUlAkOKy882sNFgRd6sX+qKLjgLOTLn6Dp UJ7Jyc6bL42tWPp60+L9IA3hopdkuzbZKtgkwhd2ij5G6/oMcVf7tiQO38uArphvDH91 9noQ== MIME-Version: 1.0 Received: by 10.180.82.164 with SMTP id j4mr7638671wiy.18.1344033373277; Fri, 03 Aug 2012 15:36:13 -0700 (PDT) Received: by 10.223.60.147 with HTTP; Fri, 3 Aug 2012 15:36:13 -0700 (PDT) In-Reply-To: <20120803134123.GA52965@onelab2.iet.unipi.it> References: <501A323E.6000106@zedat.fu-berlin.de> <1343972667.4952.5.camel@Nokia-N900-42-11> <20120803134123.GA52965@onelab2.iet.unipi.it> Date: Fri, 3 Aug 2012 15:36:13 -0700 Message-ID: From: Kevin Oberman To: Luigi Rizzo Content-Type: text/plain; charset=UTF-8 Cc: Bernhard Fr?hlich , FreeBSD Current , "Hartmann, O." Subject: Re: VirtualBox: Eating up 100% CPU, freezing Windows 7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2012 22:36:14 -0000 On Fri, Aug 3, 2012 at 6:41 AM, Luigi Rizzo wrote: > On Fri, Aug 03, 2012 at 07:44:27AM +0200, Bernhard Fr?hlich wrote: >> On Fr.,?? 3. Aug. 2012 06:18:33 CEST, Kevin Oberman wrote: >> >> > On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O. >> > wrote: >> > > I discover that when running Windows 7 in a VirtualBox On FreeBSD 10 >> > > (r238968: Wed Aug 1 14:26:40 CEST 2012), VBox is most recent from the >> > > ports, that the VirtualBox eats up 100% CPU time and freezes Windows 7 >> > > for more than a minute. For a minute or so, I can work, then, the >> > > freeze occurs again. >> > > >> > > I can't see this behaviour with a Ubuntu Guest on the same box. Is >> > > there Windows 7 specifica to be aware of? >> > >> > I am seeing the same thing. Also Win7 guest with Windows showing idle >> > process at 99%, but my system is showing VB at 100%. The VM is only >> > running a single CPU, so FreeBSD is still running OK, but the Win7 >> > system seems to freeze up periodically. >> > >> > 9.1-PRERELEASE on amd64 updated yesterday (though it has been this way >> > since VB was updated to 4.1.18. Guest additions for 4.1.18 >> > installed.All ports current. I'm thinking of backing off to 4.1.16. >> >> Can someone confirm that this is a regression in 4.1.18? Then I could talk to upstream and see if I can get that adressed. > > Could it be a case of kernel and virtualbox modules out of sync ? > I do see occasional crashes with virtualbox in both the host and guest, > but a reinstall of in-sync kernel and modules usually fixes them. Nope. To be really, really sure I just re-built the module and rebooted. VB still eats 100% CPU (out of 400%) continually. Thanks for the suggestion, though. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com