On 15/06/2021 21.38, Larry Rainey wrote:

This explains a new problem On updated 43.x 15.0 and 15.1 to 15.2 to 15.3 when the new kernel came in the virtualbox guest no longer can be seen. Every machine that was like that - I had to boot to run level 3 and zypper in kernel-default-optional kernel-default-extra as they did not get updated via zypper up

There are two config settings that could cause that behaviour: grep -e solver.onlyRequires -e installRecommends \ /etc/zypp/zypp.conf /etc/zypp/zypper.conf

I remember that JeOS images used one of those to be leaner.

How was that problematic OS originally installed? Or did you set one of the options manually?

btw: usually KVM is much less troublesome for virtualization on Linux. With libvirt+virt-manager it is even decently user-friendly.

Ciao Bernhard M.

On 16/06/2021 08.48, Martin Wilck wrote:

On Di, 2021-06-15 at 14:38 -0500, Larry Rainey wrote:

...

Every machine that was like that - I had to boot to run level 3 and zypper in kernel-default-optional kernel-default-extra as they did not get updated via zypper up

If you update to a new Leap version (e.g. 15.2 -> 15.3), you need to use "zypper dup". That's well documented. Even then, the -extra and -optional packages will only be installed if you install recommended packages (which is the default).

Absolutely, it is crucial to use "zypper dup" when upgrading from one distribution to the next (or in Tumbleweed). Using "zypper up" for this job causes problems.

And having recommends disabled can bite you sometimes.

On Mi, 2021-06-16 at 07:19 -0500, Larry Len Rainey wrote:

Every upgrade was done with these 2 scripts as root - many machines are wifi only so it is download and then install softupd_applet is what calls packagekit in Mate desktop and can break an update. llr@LLR1:~> cat /a/u/do153  zypper mr -d 1 3 9 10  pkill softupd_applet  zypper -vvv --releasever 15.3 ref  zypper -vvv --releasever 15.3 dup --download-only --allow-vendor- change    llr@LLR1:~> cat /a/u/pt2  /sbin/init 3  sleep 2  zypper -vvv --releasever 15.3 --no-refresh dup --allow-vendor-change  llr@LLR1:~> Only these 3 repos active during the dup  7 | repo-non-oss                | openSUSE-Leap-15.3-Non- Oss                    | Yes     | (r ) Yes  | Yes   8 | repo-oss                    | openSUSE-Leap-15.3- Oss                        | Yes     | (r ) Yes  | Yes  11 | repo-update                 | openSUSE-Leap-15.3- Update                     | Yes     | (r ) Yes  | Yes

This should be fine for an update to Leap 15.3 GM, but for further updates you'll need repo-sle-update and repo-backports-update, too.

Not sure why this failed for you. I've done it on a couple of systems and got the -extra and -optinal packages installed. Are you using "solver.onlyRequires = true", perhaps? IF not, you may want to open a bug and provide additional material such as /var/log/zypp/history and the output of your zypper command.

Martin

Martin Wilck composed on 2021-06-15 13:37 (UTC):

On Di, 2021-06-15 at 08:27 -0500, Larry Len Rainey wrote:

...

I have had to lock these because they cause issues:   kernel-preempt virtualbox-kmp-preempt

...

Are these really needed and can they be uninstalled and or locked?  kernel-default-extra-5.3.18-59.5.2   kernel-default-optional-5.3.18-59.5.2

This is caused by "closing the Leap gap". As the same binary packages are shipped for SLE and Leap, but SUSE can't offer full enterprise- level support for the entire universe of Leap modules, the kernel package had to be split in parts.

kernel-default: kernel + supported modules in SLES (SUSE Linux Enterprise Server) kernel-default-extra: additional modules for SLED (SUSE Linux Enterprise Desktop) or SLE-WE (Workstation extension) kernel-default-optional: additional modules that are neither in SLES or SLED, but in Leap.

To bring your system to the full functionality your kernel-default package had in Leap 15.2, you'll have to install both -extra and  -optional.

OTOH, if you have standard hardware and no fancy other requirements, you may not actually *need* either of them. They have "Supplements" dependencies to the kernel-default package; thus they'll be installed unless you use --no-recommends.

None of my 15.3 installations with AMD or Intel graphics have needed neither of the two. All my NVidia graphics installations have needed -extra for KMS to work. Apparently the Nouveau kernel driver is not supported for SLES.