Qubes 4.3 upgrage hangs stage 4

User Support
1

Hi all,

Inplace qubes 4.2 to qubes 4.3 upgrade hangs on stage 4. It hangs on

INFO: Please wait while running pre-check…

I am using sys-firewall for updatevm if this is important

I control-c and it went a step further but is now stuck upgrading a template to R4.3 repository

Any help on how to proceed is highly appreciated

This is the step stuck right now

—> (STAGE 4) Upgrade templates and standalone VMs to R4.3 repository…
----> upgrading cdebian-13-minimal…

It did start the template and I do see some cpu usage but it just stays there forever

2

Usb qubes show only unknown stuff and I don’t think the sys-net is even picking up my ethernet card which would explain the hang. I can’t connect to any qubes as they can’t show anything at all!

1 Like
3

I decided to re install qubes os 4.3 and import my templates / appvms from backup. This will be hell to debug

4

I think it would be really excellent if you could indicate as much detail as possible about your hardware…

… maybe there are others with similar setups who could have the same trouble!

Edit:
An extra question: Did you have sys-net or sys-usb based on -minimal or Debian templates? Or any other “non-default” settings.

And another:
Were you seeing running qubes, but no windows were appearing from them?

(I didn’t try 4.3 yet on any important computers. Feeling slightly nervous about it! It is time to check my backups, again.)

5

I don’t think I have a complex setup. AMD Ryzen 9 6900hx that runs qubes os just fine. sys-net, sys-firewall and sys-usb all based on fedora-42. The in place upgrade just didn’t work for me. Wish I could help more but since I used this as my daily driver, I had no time to debug or document what went wrong

Once stage 1-3 completed and I rebooted the system, I could not launch a terminal in sys-net to debug networking. No gui app would show

6

Thank you. Maybe it is just something special about your system… we will see if there are more cases.

The symptom of “no windows, but the qubes are running” makes me think of another recent report, where qubes-gui-daemon was uninstalled.