Problems after upgrading

[valvar]

The lastest upgrade has broken both the new installation of 3.8 as the 3.6 version that I had running in Virtualbox. I looks that the UFW is actively blocking some traffic and a failure to deal with the absence of GPUs.
Both happened after update/upgrade on VBox 5.1 and 5.2.
Also during the OS boot some errors appear (booterrors.png), please check the Images.zip attached.

I've been using this distribution for some years now for making slick and fast development vms and I have had no issues so far but I'm starting to have the feeling that this distribution is becoming bloated with all the whistles and bells that make good distributions suck. Do you agree ?

I think I'm going back to the old days of installing a server distribution and on top installing a window manager.

> > >

[ralphy]

I disagree.

[TheDead]

Hi,

I did not download and unzip your attachement.
Please post picture according to forum guidelines (i.e. using the picture icon when editing your post).


I used both 3.6 and 3.8, both upgraded and also clean installed wihout problems.
I use 32bits most of the time though. Maybe it's a kernel issue, try roling back to a previous version.

I would also suggest checking your virtual machine config, I'm pretty sure some settings can break an installation, especialy if kept between multiple VB upgrades.

Cheers!

[JohnyBeGood57]

Hello,

For me, it is the Linux updates that are killing my VM's.  It happened on a Windows server 2012 host, VBox 5.2.8 and now just happened on my Linux Lite workstation running VBox 5.1.34.

Both VM's were Linux Lite 3.6 64 bits.  They simply don't booth anymore.  Seems to be a Kernel issue...

My workstation is still running fine, but I am kind of scarred to run any updates...

Regards

[trinidad]

It's definitely not bloat. Don't feel too bad. I had similar issues on all my AMD machines with qemu and my own repairs led to segmentation faults and back again. It's most likely the new kernel's cpu channeling differences relative to the configurations of virtual environments of any kind that are not yet entirely programmable because of OEM microcode utilizing firmware that is simply not written for the changes that have been forced upon system admins lately. In your case it may make sense to run an older kernel.

TC

[TheDead]

I guess this would be a thread merging case


Some updates break the Linux Lite installation, but these can be put on hold...

See precisions here in this thread :
https://www.freecinema2022.gq/forums/other.../#msg39894


Cheers!