Running with debug enabled shows that it actually runs fine until it tries to create a temp directory:
Something around systemd-coredump does not sound good.
autopkgtest-virt-qemu: DBG: execute-timeout: /tmp/autopkgtest-qemu.us495jpz/runcmd true
autopkgtest-virt-qemu: DBG: can connect to autopkgtest sh in VM
autopkgtest-virt-qemu: DBG: determine_normal_user: got user "systemd-coredump"
autopkgtest-virt-qemu: DBG: auxverb = ['/tmp/autopkgtest-qemu.us495jpz/runcmd'], downtmp = None
autopkgtest-virt-qemu: DBG: execute-timeout: /tmp/autopkgtest-qemu.us495jpz/runcmd mktemp --directory --tmpdir autopkgtest.XXXXXX
In this state I can't login anymore at all
I found a few processes like these:
$ /usr/bin/python3 /tmp/autopkgtest-qemu.us495jpz/runcmd mktemp --directory --tmpdir autopkgtest.XXXXXX
Which seem to be the host counterpart to the hanging guest processes I think.
Running with debug enabled shows that it actually runs fine until it tries to create a temp directory:
Something around systemd-coredump does not sound good.
autopkgtest- virt-qemu: DBG: execute-timeout: /tmp/autopkgtes t-qemu. us495jpz/ runcmd true virt-qemu: DBG: can connect to autopkgtest sh in VM virt-qemu: DBG: determine_ normal_ user: got user "systemd-coredump" virt-qemu: DBG: auxverb = ['/tmp/ autopkgtest- qemu.us495jpz/ runcmd' ], downtmp = None virt-qemu: DBG: execute-timeout: /tmp/autopkgtes t-qemu. us495jpz/ runcmd mktemp --directory --tmpdir autopkgtest.XXXXXX
autopkgtest-
autopkgtest-
autopkgtest-
autopkgtest-
In this state I can't login anymore at all
I found a few processes like these: t-qemu. us495jpz/ runcmd mktemp --directory --tmpdir autopkgtest.XXXXXX
$ /usr/bin/python3 /tmp/autopkgtes
Which seem to be the host counterpart to the hanging guest processes I think.
This makes this even less working :-/