Error: VM Kernel does not exist:

[cooloutac]

I can't update one of the templates or start half the vms. After I did a dom0 update. What happened?

[cooloutac]

On Tuesday, April 18, 2017 at 6:54:58 PM UTC-4, cooloutac wrote:
> I can't update one of the templates or start half the vms. After I did a dom0 update. What happened?

Error: VM Kernel does not exist: /var/lib/qubes/vm-kernels/4.4.14-11/vmlinuz

[cooloutac]

the default sys vms work fine. all the templates including a debian clone work fine. All the untrusted red templates work mysteriously.

But all my other appvms, and a fedora-24 cloned template have the error.
Anyone know how to fix this. This is pretty devastating and catastrophic imo. I don't have any repos enabled except current.

I rebooted twice, no help.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Known bug: https://github.com/QubesOS/qubes-issues/issues/2757

Workaround (in dom0):

$ for VM in `qvm-ls --raw-list`; do qvm-prefs -s $VM kernel default; done

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJY9p0eAAoJENtN07w5UDAwLP8QAKRaS8ozA/75xLFvgLhFeqj8
43j7lGJX+UxB48CRCuRtEKGB2qKM87g5MLrWx2AdWBmMUVFwO0iP+UNY3B9t9xuy
cLxFOvt4kgyHDvSfbhXpDmRbR2VTQFm4aNVJ/jNSLIuav5hcO0dpj7Zptt9ygQ2Y
GejhDTABch88tEpOYOZ6Fymt0vY5QvV9aDkJMoj5jSPfYxSXz53pz5sMzN83q2Rd
STxzkePwwIxnS9NNh6y9xUqHxhpCp9ctZqR5LjmP7eGSL+5uSpeFlV8wTZHmOECT
fXMtm1yyUUvHkfr5TaPyddHeXU6cnASZHCDWasCXoUFsQ3fzzlBlWnqkxP5VKT5n
RnQj51ldXibi1rykTDuNpa9NIuMZTxmj4OS9QZjAWNtOwbLzkz8DT5YakgZkUNJY
ilprc35PUCSPAgvexol8bMCPJ63Lfde/hL7HHrKq12LTsTvGS4aVNUpTKgb1zlR4
p3N4jc0tPFy6uNfeTq6ZjyOeasofS5ZUnKG74ztmrv/+2qLze4VjKdhxz/iAUogl
RGiirzV93mB0qyVY+j2+sr1K/1CaNueLzLLXdWsI4laeFKhWFcsR79mruvDoBOdn
BmzDgUxm6l4o2H3b8J6W5wxNBcoH/w93hBZAlILfw+bxGf9dswOCGg5iSqknrRFA
GxGCp0YcGn79jvhmcute
=BFi3
-----END PGP SIGNATURE-----

[cooloutac]

oh tk goodness I was searching frantically and getting paranoid. I saw the kernel was removed and didn't know what to do. Thanks for prompt reply Andrew!!

[cooloutac]

a couple untrusted ones I created, the default dispvm, and anon-whonix were not affected.

So my 4 untrusted vms were not affected and what template they are based on seems not to matter. But every one of my other vms, all 15 of them, had the issue. Very strange.

[cooloutac]

On Tuesday, April 18, 2017 at 7:51:04 PM UTC-4, cooloutac wrote:
> a couple untrusted ones I created, the default dispvm, and anon-whonix were not affected.
>
> So my 4 untrusted vms were not affected and what template they are based on seems not to matter. But every one of my other vms, all 15 of them, had the issue. Very strange.

maybe I should of done the new Tor dom0 update? haha

[Markus Kilås]

On 04/19/2017 01:11 AM, Andrew David Wong wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2017-04-18 16:08, cooloutac wrote:
>> On Tuesday, April 18, 2017 at 6:55:31 PM UTC-4, cooloutac wrote:
>>> On Tuesday, April 18, 2017 at 6:54:58 PM UTC-4, cooloutac wrote:
>>>> I can't update one of the templates or start half the vms. After I did a dom0 update. What happened?
>>>
>>> Error: VM Kernel does not exist: /var/lib/qubes/vm-kernels/4.4.14-11/vmlinuz
>>
>> the default sys vms work fine. all the templates including a debian clone work fine. All the untrusted red templates work mysteriously.
>>
>> But all my other appvms, and a fedora-24 cloned template have the error.
>> Anyone know how to fix this. This is pretty devastating and catastrophic imo. I don't have any repos enabled except current.
>>
>> I rebooted twice, no help.
>>
>
> Known bug: https://github.com/QubesOS/qubes-issues/issues/2757
>
> Workaround (in dom0):
>
> $ for VM in `qvm-ls --raw-list`; do qvm-prefs -s $VM kernel default; done
>

I used the following workaround/fix before I saw the above:
1. For each affected VM, go into VM Settings -> Advanced and switch
Kernel from "default (4.4.55-11)" to "4.4.55-11" and click OK.
2. Then go back in again and switch back to "default (4.4.55-1) and
click OK.
Now it works again.

Cheers,
Markus

[Franz]

Interesting.  this workaround:

$ for VM in `qvm-ls --raw-list`; do qvm-prefs -s $VM kernel default; done

did NOT work for me. I got the same error.

But what Markus is suggesting does work.

Best

Fran

Cheers,
Markus

--
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 qubes-users+unsubscribe@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/90059f3d-6b4d-eaaf-6bf2-2d219cfeb3e3%40xn--kils-soa.se.

For more options, visit https://groups.google.com/d/optout.

[wordsw...@gmail.com]

> Known bug: https://github.com/QubesOS/qubes-issues/issues/2757
>
> Workaround (in dom0):
>
> $ for VM in `qvm-ls --raw-list`; do qvm-prefs -s $VM kernel default; done
>

The recent dom0 update caused this issue for me again (I've had it before), and it was quickly fixed by the command above.