Template migration to Qubes-testing

I’m trying to migrate a windows Template + AppVM from a stable installation to a testing instance.

The backup restore on the testing machine works well, but then the Qube does not boot.

The Qube only shows a black screen and does not even load the windows bootloader. Any ideas on how to troubleshoot this ?

Thanks !

1 Like

Do you get seabios output saying it will try to boot from disk or not even that? what is the qubes version difference between the two systems?

1 Like

No I only get a black screen, without any activity. I haven’t found any errors in the logs.

I’m migrating from R4.2.4 to R4.3-alpha.

1 Like

I’ve set the net qube of this Win template to none.
Here are the logs in dom0 using journalct -f -n0

journalctl
pierre@dom0:~$ journalctl -f -n0
Jul 11 10:11:24 dom0 qubesd[2658]: vm.win11-dev: Starting win11-dev
Jul 11 10:11:24 dom0 dmeventd[1382]: No longer monitoring thin pool qubes_dom0-vm--pool-tpool.
Jul 11 10:11:24 dom0 dmeventd[1382]: Monitoring thin pool qubes_dom0-vm--pool-tpool.
Jul 11 10:11:24 dom0 dmeventd[1382]: No longer monitoring thin pool qubes_dom0-vm--pool-tpool.
Jul 11 10:11:24 dom0 dmeventd[1382]: Monitoring thin pool qubes_dom0-vm--pool-tpool.
Jul 11 10:11:25 dom0 kernel: int3472-discrete INT3472:0c: cannot find GPIO chip INTC10D1:00, deferring
Jul 11 10:11:25 dom0 kernel: int3472-discrete INT3472:0c: cannot find GPIO chip INTC10D1:00, deferring
Jul 11 10:11:25 dom0 kernel: int3472-discrete INT3472:0c: cannot find GPIO chip INTC10D1:00, deferring
Jul 11 10:11:25 dom0 kernel: int3472-discrete INT3472:0c: cannot find GPIO chip INTC10D1:00, deferring
Jul 11 10:11:25 dom0 kernel: int3472-discrete INT3472:0c: cannot find GPIO chip INTC10D1:00, deferring
Jul 11 10:11:25 dom0 kernel: int3472-discrete INT3472:0c: cannot find GPIO chip INTC10D1:00, deferring
Jul 11 10:11:25 dom0 kernel: xen-blkback: backend/vbd/24/51712: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Jul 11 10:11:25 dom0 kernel: xen-blkback: backend/vbd/24/51728: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Jul 11 10:11:25 dom0 kernel: xen-blkback: backend/vbd/24/51744: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Jul 11 10:11:26 dom0 qubesd[2658]: vm.win11-dev: Setting Qubes DB info for the VM
Jul 11 10:11:26 dom0 qubesd[2658]: vm.win11-dev: Starting Qubes DB
Jul 11 10:11:26 dom0 audit[21047]: CRED_ACQ pid=21047 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 kernel: audit: type=1103 audit(1752221486.399:1489): pid=21047 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 runuser[21047]: pam_unix(runuser:session): session opened for user pierre(uid=1000) by (uid=0)
Jul 11 10:11:26 dom0 kernel: audit: type=1105 audit(1752221486.409:1490): pid=21047 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 audit[21047]: USER_START pid=21047 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 runuser[21047]: pam_unix(runuser:session): session closed for user pierre
Jul 11 10:11:26 dom0 audit[21047]: USER_END pid=21047 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 audit[21047]: CRED_DISP pid=21047 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 kernel: audit: type=1106 audit(1752221486.418:1491): pid=21047 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 kernel: audit: type=1104 audit(1752221486.418:1492): pid=21047 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 qubesd[2658]: vm.win11-dev: Activating the win11-dev VM
Jul 11 10:11:26 dom0 audit[21050]: CRED_ACQ pid=21050 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 kernel: audit: type=1103 audit(1752221486.438:1493): pid=21050 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 runuser[21050]: pam_unix(runuser:session): session opened for user pierre(uid=1000) by (uid=0)
Jul 11 10:11:26 dom0 kernel: audit: type=1105 audit(1752221486.448:1494): pid=21050 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 audit[21050]: USER_START pid=21050 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 runuser[21050]: pam_unix(runuser:session): session closed for user pierre
Jul 11 10:11:26 dom0 audit[21050]: USER_END pid=21050 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 audit[21050]: CRED_DISP pid=21050 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 kernel: audit: type=1106 audit(1752221486.457:1495): pid=21050 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 kernel: audit: type=1104 audit(1752221486.457:1496): pid=21050 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 audit[21056]: CRED_ACQ pid=21056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 kernel: audit: type=1103 audit(1752221486.470:1497): pid=21056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 runuser[21056]: pam_unix(runuser:session): session opened for user pierre(uid=1000) by (uid=0)
Jul 11 10:11:26 dom0 kernel: audit: type=1105 audit(1752221486.479:1498): pid=21056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:11:26 dom0 audit[21056]: USER_START pid=21056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'


BLACK SCREEN HERE, NO BOOT PROCESS

Jul 11 10:12:03 dom0 dbus-daemon[4270]: [session uid=1000 pid=4270] Activating service name='org.xfce.Xfconf' requested by ':1.49' (uid=1000 pid=5063 comm="xfce4-terminal")
Jul 11 10:12:03 dom0 dbus-daemon[4270]: [session uid=1000 pid=4270] Successfully activated service 'org.xfce.Xfconf'
Jul 11 10:12:07 dom0 runuser[21056]: pam_unix(runuser:session): session closed for user pierre
Jul 11 10:12:07 dom0 kernel: audit: type=1106 audit(1752221527.247:1499): pid=21056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:12:07 dom0 kernel: audit: type=1104 audit(1752221527.247:1500): pid=21056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:12:07 dom0 audit[21056]: USER_END pid=21056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jul 11 10:12:07 dom0 audit[21056]: CRED_DISP pid=21056 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="pierre" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'


NOTIF "QUBE HAS STARTED" popped up


NOTHING


The only peculiar lines are

Jul 11 10:11:25 dom0 kernel: int3472-discrete INT3472:0c: cannot find GPIO chip INTC10D1:00, deferring

But they also appear at the boot of other qubes.

I welcome any troubleshooting advice.

Updating dom0 solved the issue. The backup made on 4.2 can be booted directly on 4.3 (testing).