On Sat, May 20, 2017 at 11:27 PM, Franz <[email protected]> wrote: > > > On Sat, May 20, 2017 at 7:49 PM, Unman <[email protected]> wrote: > >> On Sat, May 20, 2017 at 07:34:28PM -0300, Franz wrote: >> > On Sat, May 20, 2017 at 7:20 PM, Unman <[email protected]> >> wrote: >> > >> > > On Sat, May 20, 2017 at 04:27:24PM -0300, Franz wrote: >> > > > Hello, >> > > > >> > > > the usual trick of selecting other kernel in Qubes manager does not >> work >> > > > running >> > > > qvm-prefs -s kernel default >> > > > gives >> > > > A VM with the name 'kernel" does not exist in tne system >> > > > >> > > > ls /var/lib/qubes/vm-kernels/ >> > > > gives >> > > > 4.4.55-11 4.4.62-12 4.4.67-12 >> > > > >> > > > However one of the VMs does correctly starts. this one shows it is >> using >> > > > 4.4.55-11 >> > > > >> > > > Best >> > > > Fran >> > > >> > > You are supposed to include the name of the qube you want to work on >> > > when using qvm-prefs. >> > > If you want to run against a number of qubes just script it with a >> bash >> > > script iterating over the names. >> > > >> > > unman >> > > >> > >> > Many thanks Unman, following your suggestion I do not get errors with >> the >> > qvm-prefs command, but the same trying to start the VMs I get the same >> > error that makes the heading of this thread. >> > >> >> The recent update provided a new kernel - Qubes only maintains 3 >> recent kernels, so one has been deleted. That's why you get this error. >> (A number of people have reported this.) >> You should be able to set the default kernel as you have tried - if this >> doesn't work for you just set one of the kernels that you DO have >> explicitly. >> >> unman >> > > > this is the first thing that I tried using Qubes manager. It worked in the > past when after an update the same thing happened, But it is not working > anymore now as I reported in the first post. None of the available kernels > work. > > I even tried to create a standalone as a workaround, but it gives the same > error. > > best > Fran >
I found a strange workaround: if I deprive a VM of network connection (NetVM to none) that the kernel error issue does NOT appear. But of course I have no network :-(( Any idea what this may means? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAPzH-qAAbo9O5YXq5DV7-invKbcEcesCb_CGdPBWtse4nLxjqQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
