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 <w41...@gmail.com> 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.
