... could it be the source of the 'virsh cannot find suitable emulator
for x86_64' thing I've encountered many times before?
On Fri, 2016-04-29 at 17:59 +0000, Peters, Brad T wrote:
Here's the problem - You are attempting to install two different
kernel types (3 native and 1 kvm);
the clr-specialized-updaters (CSU) kernel_updater script was codded
assuming only 1 kernel type would
ever be installed per system. So if you look at your ls output, the 3
native kernels (releases 193, 200 and 201)
are getting installed, while the kvm kernel (at release 159) is
considered older than the other three,
and is cleaned up rather than installed.
This is an interesting edge case, and since installing different
kernel types is indeed something we want to
support, we'll look at patching CSU to treat different kernel types
Thanks for bringing this to our attention
On Fri, Apr 29, 2016 at 9:38 AM, Douglas, William <william.douglas@in
> On Fri, Apr 29, 2016 at 9:29 AM, fb.dev.clx <fb.dev.clx(a)gmail.com>
> > Hi all,
> > Since at least releases 7730 and 7770, `swupd verify --fix`
> > intents to fix missing kernel 4.5.1-159 related files.
> > Each time the command is run, a "Fix successful" message is
> > at the end, but without any real change:
> > ```
> > $ ls -d /usr/lib/modules/4.5.1-159/
> > ls: cannot access '/usr/lib/modules/4.5.1-159/': No such file or
> > directory
> > ```
> So it sounds like the kernel update scripts are detecting 4.5.1-159
> somehow (something sitting in /boot probably) and attempting to
> restore files in /boot but since you don't have the files (in
> /usr/lib/kernel btw is where these are pulled from) it doesn't
> We could possibly have something going wrong with detection/cleanup
> here though Brad would know best.
> > Can anyone check this?
> > -- FB
> > _______________________________________________
> > Dev mailing list
> > Dev(a)lists.clearlinux.org
> > https://lists.clearlinux.org/mailman/listinfo/dev