On Sat, May 20, 2017 at 11:27:01PM -0300, Franz 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
Hello Fran It's not clear to me what error you are reporting. The error in the subject line arises because the recent upgrade deleted the kernel that you have allocated to a qube. The next error arose because you were using the qvm-prefs command incorrectly. And so I dont understand what you mean by "gives the same error". In you other post you say that you can start a VM when you set the networking to none - this makes me wonder if you have not yet reset the Can you check that you have done this and then try to explicitly start from a terminal the upstream proxies ? If I haven't understood exactly what your current problem is please can you explain in more detail. and perhaps provide the output from qvm-start? unman -- 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/20170522171007.GA10073%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
