@Unman,
On Mon, May 22, 2017 at 5:05 PM, Unman <[email protected]> wrote: > On Mon, May 22, 2017 at 04:39:50PM -0300, Franz wrote: > > 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 > > > > So this suggests that you have not yet changed the kernel for sys-net, > yet you say that the qvm-prefs command runs without errors. > 1. Run qvm-prefs sys-net kernel. > the above command is interesting because it gives 4.4.38-11 while Qubes Manager gives 4.4.67-12 > 2. Then qvm-prefs sys-net kernel -s <an installed kernel> > qvm-prefs sys-net kernel -s 4.4.67-12 3. Then qvm-prefs sys-net kernel. > Important change here: I get 4.4.67-12 > 4. Then qvm-start sys-net > > Hurrah!!! you dit it, it started. Now everything works again. So what means all that? 1. The kernel identification provided by Qubes Manager is not reliable and cannot be trusted 2. The qvm-prefs does work, but must be run for each VM, while when you first taught me to use it, I understood that it could be used once for all VMs. 3. When something like that happens the best thing to do is to look for the commands that may help: had I known that qvm-prefs sys-net kernel gives the actual kernel used I would had been able to find the answer. Simply trusting Qubes manager was not enough. I have no words to thank you Unman. You are methodical, one step after the other in the proper order, never loosing faith that a rational simple answer exists, even if we are perhaps thousands of kilometers far away. Many thanks Fran -- 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-qDdWre-HKT7XWvQig5EtipggJTHSVkJSaVURuCAHNZmGw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
