Only dom0 is running after logging in

User Support
1

hello fsflover,

  1. my Qubes just started booting weird after i tried updating fedora32 template. It was running fine since June 2020. I am running a NitroPad x230 from NitroKey.

  2. only dom0 is running after logging in.

  3. i am not able to export log from AppVM.

I would be grateful for any advice.

:slight_smile:

2

Hi @kraken! Welcome to the community! I created a separated topic for you.

This is strange, since it’s only a template and should not affect dom0 at all.

Why you can’t do it? What’s preventing you? Could you take a picture of your screen with logs? Same with dom0 by running journalctl.

3

i manage to take a photo of the error pop-up.

https://mudamzjamx.joplinusercontent.com/shares/PT9ORaeohIjW1l8eVwOwwMA5iDF6NquC

4

Unfortunately, this is not enough. More detailed error description should be in the logs, which you can access from Qube Manager (right click on the qube → Logs) and, for dom0, in its terminal after running journalctl -r (ideally, just after booting).

Maybe someone else can suggest more places to check.

5

2 photos of the log on dom0 by running journalctl.

https://mudamzjamx.joplinusercontent.com/shares/fCLaiZoU3ebqfjclyY7tFKk1LCdRf5aE

https://mudamzjamx.joplinusercontent.com/shares/TK4K84DfcJDDrhANaIorEroW6nPMsZ03

6

These logs have dates “May 22” as you may see in the beginning of each line. You forgot “-r” after “journalctl” to show the latest lines first.

7

journalctl -r

2 photos taken of log:

https://mudamzjamx.joplinusercontent.com/shares/xXEVVbcOKZ039MtYo6LodcCFBFqq3vqh

https://mudamzjamx.joplinusercontent.com/shares/EkKWwkKxQOv7NkmjwBg1oxNJtPtWTNhE

1 Like
8

i tried updating fedora32 template.

Let’s start with a description of what that means:

  1. did you attempt to do an in-place upgrade?
  2. did you download the new templates and switch your qubes to it?

If it was 1) and that process failed, this basically leaves you without a functioning template which would explain no qube starting and consequently also no network.

Did you make a clone of the template before starting the upgrade?

Just tell us step by step what you did – that’ll be much faster then trying to guess.

2 Likes
9

went to Qube Setttings of Template fedora-32, Basic Tab, changed Networking from default (none) to sys-firewall. click apply.

launched software of Template fedora-32, went to update and downloaded fedora 33.

update was not successful.

10

Hi Sven,

i think you got it right.

  1. and that process failed, this basically leaves you without a functioning template which would explain no qube starting and consequently also no network.
11

I had similar problems trying to upgrade templates from 4.04 to 4.1b. The fedora template got corrupted and nothing attached to it could start. I restored a debian template from backup and got qubes to start again.

2 Likes
12

@kraken there are two options to upgrade Fedora templates:

  1. Download the new templates and switch all your qubes over to the new template. This means that if you had customized your templates you will have to redo those customization (e.g. install additional software).

  2. Do an “in-place” upgrade as you attempted. But there are Qubes OS specific instructions that you should have followed.

1 Like
13

@Sven thank you for your advice.

I went with option 1 and am now able to run Qubes normally.

I am grateful to all who have responded to this thread. Thank you :grin: