On Mon, May 22, 2017 at 2:10 PM, Unman <[email protected]> wrote:
> 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. > Many thanks Unman for trying so hard to help me :-)) > > 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". > > It is the first one, in the heading, the second is just syntax that you properly corrected, but even after the correction and after running qvm-prefs without errors, then trying to start the VM I fall again to the first 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 > > It seems the end of your paragraph is lacking. > Can you check that you have done this If you mean rebooting, yes I rebooted many times. > and then try to explicitly start > from a terminal the upstream proxies ? > I do not know what upstream proxies are, but if you means something like qvm-start <VM-name> then I always get the heading error, unless the VM is not connected to network. In this last case it starts normally. > If I haven't understood exactly what your current problem is please can > you explain in more detail. Unman, the problem is that in the past it was easy to fix this error simply pointing each VM to a different kernel, on the contrary now this workaround does NOT work anymore. Worse than that I cannot even make dom0 recognize that I plugged in some USB stick, so even taking a backup (that luckily finished successfully) out of dom0 is problem. > and perhaps provide the output from > qvm-start? > > qvm-start sys-net ERROR: VM kernel does not exist: /var/lib/qubes/vm-kernels/4.4.38-11/vmlinuz qvm-start personal --> Starting NetVM sys-firewall --> Starting NetVM sys-net ERROR: VM kernel does not exist: /var/lib/qubes/vm-kernels/4.4.38-11/vmlinuz result: nothing started But many thanks again for your strong patience > 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. > -- 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-qD3ZQXHaMzoSWNWZW3Jb7iX5000CqsCZnX6L0W5rux4Dg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
