From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 05ED0198005 for ; Mon, 4 Mar 2013 08:20:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 68813E072C; Mon, 4 Mar 2013 08:19:59 +0000 (UTC) Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.rwth-aachen.de [134.130.7.73]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E7F6AE061F for ; Mon, 4 Mar 2013 08:19:57 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-disposition: inline Content-type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Received: from mx-out-1.rwth-aachen.de ([134.130.5.186]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0MJ400820N584V70@mta-2.ms.rz.RWTH-Aachen.de> for gentoo-user@lists.gentoo.org; Mon, 04 Mar 2013 09:19:56 +0100 (CET) X-IronPort-AV: E=Sophos;i="4.84,777,1355094000"; d="scan'208";a="212791394" Received: from relay-2.ms.rz.rwth-aachen.de (HELO relay.rwth-aachen.de) ([134.130.7.75]) by mx-1.rz.rwth-aachen.de with ESMTP; Mon, 04 Mar 2013 09:19:57 +0100 Received: from numa-i.igpm.rwth-aachen.de (numa-i.igpm.rwth-aachen.de [134.130.161.252]) by relay.rwth-aachen.de (8.14.4+Sun/8.13.8/1) with ESMTP id r248JuDN024582 for ; Mon, 04 Mar 2013 09:19:56 +0100 (CET) Received: from numa-i (localhost [127.0.0.1]) by numa-i.igpm.rwth-aachen.de (Postfix) with ESMTP id DB83E2D98 for ; Mon, 04 Mar 2013 09:19:57 +0100 (CET) Date: Mon, 04 Mar 2013 09:19:57 +0100 From: Helmut Jarausch Subject: Re: [gentoo-user] Re: Be cautious about virtualbox-4.2.8 and Win7 guests To: gentoo-user@lists.gentoo.org References: <51324B16.6010701@gmail.com> <51334F5F.4090605@gmail.com> <1362318311.11226.0@numa-i> <51335843.9010101@gmail.com> In-reply-to: <51335843.9010101@gmail.com> X-Mailer: Balsa 2.4.91-7-g3440dfb Message-id: <1362385197.13357.1@numa-i> X-Archives-Salt: 40b6469b-18b0-44c7-a9e8-5e02009a23ec X-Archives-Hash: 49ef88d5acbe10960956a140541dcc5b On 03/03/2013 03:03:47 PM, walt wrote: > On 03/03/2013 05:45 AM, Helmut Jarausch wrote: > > On 03/03/2013 02:25:51 PM, walt wrote: > >> On 03/02/2013 10:55 AM, walt wrote: > >> > On 03/01/2013 10:34 PM, Nilesh Govindrajan wrote: > >> >> On Sat, Mar 2, 2013 at 2:06 AM, walt wrote: > >> >>> After updating vbox today I got crashes on login with two > different > >> >>> Win7 guests (gentoo ~amd64 host). > >> >>> > >> >>> Luckily, only the most recent snapshot crashed and I was able > to > >> >>> boot normally with the second most recent snapshot (both > guests). > >> >>> > >> >>> I didn't lose anything important because the only thing I use > >> >>> Windows for is to run Windows Update :) (know thine enemy, etc) > >> >>> > >> >>> Maybe if you have important stuff on a Win7 guest you should > make > >> >>> an extra snapshot just before you update to vbox-4.2.8 in case > you > >> >>> need to delete the last one. > >> >>> > >> >>> BTW, I had no problems with linux guests so far. > >> >>> > >> >>> > >> >> > >> >> What did the crashes say? > >> > > >> > The usual :) "Windows has encountered a problem and must > close..." > >> > > >> > Just now I updated a second gentoo machine that (I thought) is > the > >> > same as this one, but I didn't the crashes on that machine, so I > don't > >> > know what to think now. I hope nobody else has the same problem. > >> > >> Crap, I just noticed that virtualbox-modules-4.2.8 won't compile > against > >> the latest 3.8.x kernels : > > > > virtualbox-modules-4.2.8 builds just fine with gentoo-sources-3.8.1 > here > > Helmut. > > Good. Most days I'm running the latest kernel from Linus's git > repository > instead of gentoo-sources, so that's probably the cause of my recent > problem > and why virtualbox-modules-4.2.8 didn't install when I upgraded > virtualbox. > Shame on me for not noticing the build failure :( > No, that cannot be the reason for the failure on your machine. I have been following git-sources 3.8-rc 3..7 without any problems with virtualbox. Helmut.