A start job is running for Start Qubes VM sys-net. FOREVER.

Fabrizio Romano Genovese

unread,

Mar 16, 2021, 11:49:21 AM3/16/21

to qubes-users

As the title says. I've upgraded to the latest kernel (5.11) on qubes 4.0 and now boot is stuck. How do I get out of this? :)

Fab

haaber

unread,

Mar 16, 2021, 12:05:36 PM3/16/21

to qubes...@googlegroups.com

On 3/16/21 4:49 PM, Fabrizio Romano Genovese wrote:
> As the title says. I've upgraded to the latest kernel (5.11) on qubes
> 4.0 and now boot is stuck. How do I get out of this? :)
>

you go back: boot a life linux, mount your UEFI partition, search for
/efi/EFI/qubes/xen.cfg or /efi/EFI/BOOT/xen.cfg and edit the first
line, by copying one of the available kernel-names from list below. It's
straightforward. Use nano editor, for example. Crtl-k cuts a line,
crtl-u pastes it back. A second crtl-u gives a clean second copy. that
way you avoid typing errors. good luck

Manuel Amador (Rudd-O)

unread,

Mar 16, 2021, 12:29:53 PM3/16/21

to qubes...@googlegroups.com

You can mask the unit in the GRUB kernel command line with the parameter:

systemd.mask=qube...@sys-net.service

And then you will be able to log in and fix the kernel issue (without networking, of course).

You can also choose the older kernel in the GRUB menu.

On 16/03/2021 16.49, Fabrizio Romano Genovese wrote:

As the title says. I've upgraded to the latest kernel (5.11) on qubes 4.0 and now boot is stuck. How do I get out of this? :)

Fab

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com.

-- 
    Rudd-O
    https://rudd-o.com/

OpenPGP_signature

Fabrizio Romano Genovese

unread,

Mar 16, 2021, 7:13:26 PM3/16/21

to qubes-users

Booting from a live version and switching to the old kernel solved it. Has anyone else experienced something similar with kernel 5.11 or it is just myself? I had a boot fuckup with kernel 5.10 as well a few weeks ago, but I just waited for the next release and that solved it. I'd like to understand if the situation is similar here or if it's a problem of my machine, in which case I'll investigate deeper.

haaber

unread,

Mar 17, 2021, 3:11:03 AM3/17/21

to qubes...@googlegroups.com

On 3/17/21 12:13 AM, Fabrizio Romano Genovese wrote:
> Booting from a live version and switching to the old kernel solved it.
> Has anyone else experienced something similar with kernel 5.11 or it is
> just myself? I had a boot fuckup with kernel 5.10 as well a few weeks
> ago, but I just waited for the next release and that solved it. I'd like
> to understand if the situation is similar here or if it's a problem of
> my machine, in which case I'll investigate deeper.

there are several issues. Like

https://github.com/QubesOS/qubes-issues/issues/6446
https://github.com/QubesOS/qubes-issues/issues/6397

but they might be unrelated, as well.

>
> On Tuesday, March 16, 2021 at 5:29:53 PM UTC+1 rud...@rudd-o.com wrote:
>
> You can mask the unit in the GRUB kernel command line with the
> parameter:
>
> systemd.mask=qube...@sys-net.service
>
> And then you will be able to log in and fix the kernel issue
> (without networking, of course).
>
> You can also choose the older kernel in the GRUB menu.
>
> On 16/03/2021 16.49, Fabrizio Romano Genovese wrote:
>> As the title says. I've upgraded to the latest kernel (5.11) on
>> qubes 4.0 and now boot is stuck. How do I get out of this? :)
>>
>> Fab
>> --
>> 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...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com

>> <https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
>
> --
> Rudd-O
> https://rudd-o.com/ <https://rudd-o.com/>

>
> --
> 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...@googlegroups.com

> <mailto:qubes-users...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/qubes-users/772e2a89-da21-4f87-8977-0e171526978fn%40googlegroups.com
> <https://groups.google.com/d/msgid/qubes-users/772e2a89-da21-4f87-8977-0e171526978fn%40googlegroups.com?utm_medium=email&utm_source=footer>.

Fabrizio Romano Genovese

unread,

Mar 17, 2021, 5:53:54 AM3/17/21

to qubes-users

These are not directly related to kernel 5.11. My problem started when I upgraded from 5.10 to 5.11.

Ulrich Windl

unread,

Mar 27, 2021, 7:20:28 PM3/27/21

to qubes...@googlegroups.com

On 3/16/21 4:49 PM, Fabrizio Romano Genovese wrote:

> As the title says. I've upgraded to the latest kernel (5.11) on qubes
> 4.0 and now boot is stuck. How do I get out of this? :)

Last time I had this (outside of Qubes OS) was when I had configured a
disk device that did not exist. For some reason Xen tried again and
again instead of quitting. I found the problem by inspecting the Xen logs.
Anyway I'd guess systemd will timeout the VM start at some time
(allowing the boot to continue). Did you try to be patient?

>
> Fab
>
> --
> 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...@googlegroups.com
> <mailto:qubes-users...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com
> <https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com?utm_medium=email&utm_source=footer>.

Ulrich Windl

unread,

Mar 27, 2021, 7:30:58 PM3/27/21

to qubes...@googlegroups.com

On 3/16/21 5:29 PM, Manuel Amador (Rudd-O) wrote:
> You can mask the unit in the GRUB kernel command line with the parameter:
>
> systemd.mask=qube...@sys-net.service

I think this should go into the Qubes OS FAQ (like "boot parameters for
troubleshooting")!

>
> And then you will be able to log in and fix the kernel issue (without
> networking, of course).
>
> You can also choose the older kernel in the GRUB menu.
>
> On 16/03/2021 16.49, Fabrizio Romano Genovese wrote:
>> As the title says. I've upgraded to the latest kernel (5.11) on qubes
>> 4.0 and now boot is stuck. How do I get out of this? :)
>>
>> Fab
>> --
>> 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...@googlegroups.com

>> <mailto:qubes-users...@googlegroups.com>.

>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com
>> <https://groups.google.com/d/msgid/qubes-users/7ba1ae0f-4037-4a47-9bf4-aa9eae652a7dn%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
>
> --
> Rudd-O
> https://rudd-o.com/
>

> --
> 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...@googlegroups.com

> <mailto:qubes-users...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/qubes-users/bbc147a8-4fa0-2f74-9227-23f24b1a19ce%40rudd-o.com
> <https://groups.google.com/d/msgid/qubes-users/bbc147a8-4fa0-2f74-9227-23f24b1a19ce%40rudd-o.com?utm_medium=email&utm_source=footer>.

Reply all

Reply to author

Forward