autopkgtest-virt-qemu for sh4 guests

Hi everyone,

Several days ago here I reported that mmdebstrap'ping sh4 on an amd64 host
failed as cited at the bottom of this email, and now it succeeds with no problem!

By the way, I am proposing to adapt autopkgtest-virt-qemu to guest
architectures other than amd64 and i386, specifically to arm* and ppc64* at
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/100
which is a revised version of my previous MR.

The only problem in the latest autopkgtest-virt-qemu on gitlab
is that it assumes that a qemu VM has two serial ports, and tries to
attach two sockets on host to two serial ports of the guest.
On the other hand, arm* and ppc64* has only one serial port,
and the current autopkgtest-virt-qemu cannot attach two host sockets.

So I checked if the name of qemu-system-* is i386 or x86_64,
and attach one QEMU virtconsole to a guest unless i386 or x86_64 as
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/100/diffs

The QEMU sh4 virtual machine seems to have two serials in its guest VM.
So the current autopkgtest-virt-qemu on gitlab can theoretically work
on sh4 guests, and my proposal might break the functionality for sh4.
But I am unsure, because I do not have an sh4 QEMU disk image that can
boot without giving -kernel to qemu-system-sh4.

If you have any comments, please post them to
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/100

Best regards, Ryutaroh Matsumoto

From: Ryutaroh Matsumoto <[email protected]>
Subject: Re: mmdebstrap'ping sh4 failure on amd64 host
Date: Mon, 30 Nov 2020 11:12:16 +0900 (JST)

>> It will take two more days as there was a serious bug in the package
>> isc-dhcp [1] and the fix has been uploaded to the delayed queue [2].
>>> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957379
>>> [2] https://ftp-master.debian.org/deferred.html
> 
> Adrian, thanks for the info. I will re-check the situation maybe in the next
> weekend (Dec. 5). Ryutaroh