Your message dated Thu, 21 May 2020 17:27:54 +0900 (JST)
with message-id <20200521.172754.446228688745625701.ryutaroh@???>
and subject line Re: bug#461: autopkgtest-virt-qemu always fails with <VirtSubproc>: failure: timed out on client shared directory setup
has caused the Devuan bug report #461,
regarding autopkgtest-virt-qemu always fails with <VirtSubproc>: failure: timed out on client shared directory setup
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@???
immediately.)


--
461: https://bugs.devuan.org/cgi/bugreport.cgi?bug=461
Devuan Bug Tracking System
Contact owner@??? with problems
Package: autopkgtest
Version: 5.13.1
Severity: grave
Tags: beowulf ceres
Justification: renders package unusable
Control: found -1 5.10

Dear Maintainer,

After building a testbed by
autopkgtest-build-qemu ceres /var/tmp/ceres-amd64.img http://deb.devuan.org/merged
and adjust /etc/inittab in the testbed so that it accepts login
from /dev/ttyS[01],

autopkgtest -U -B thunderbird -o /var/tmp/autopkgtest-thunderbird1 -- qemu --ram-size=2048 /var/tmp/ceres-amd64.img
autopkgtest [15:57:43]: starting date: 2020-05-16
autopkgtest [15:57:43]: version 5.13.1
autopkgtest [15:57:43]: host devuan; command line: /usr/bin/autopkgtest -U -B thunderbird -o /var/tmp/autopkgtest-thunderbird1 -- qemu --ram-size=2048 /var/tmp/ceres-amd64.img
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
qemu-system-x86_64: terminating on signal 15 from pid 12727 (/usr/bin/python3)
<VirtSubproc>: failure: timed out on client shared directory setup
autopkgtest [15:58:20]: ERROR: testbed failure: cannot send to testbed: [Errno 32] Broken pipe

This issue is found in package versions 5.13.1 and 5.10.
This issue is observed both Beowulf and Ceres qemu images.

Best regards, Ryutaroh Matsumoto

-- System Information:
Distributor ID:    Debian
Description:    Devuan GNU/Linux 3 (beowulf)
Release:    3
Codename:    beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages autopkgtest depends on:
ii  apt-utils       1.8.2.1
ii  libdpkg-perl    1.19.7
ii  procps          2:3.3.15-2+devuan1
ii  python3         3.7.3-1
ii  python3-debian  0.1.35

Versions of packages autopkgtest recommends:
ii autodep8 0.18

Versions of packages autopkgtest suggests:
pn  lxc               <none>
pn  lxd               <none>
ii  ovmf              0~20181115.85588389-3+deb10u1
pn  qemu-efi-aarch64  <none>
pn  qemu-efi-arm      <none>
pn  qemu-system       <none>
ii  qemu-utils        1:3.1+dfsg-8+deb10u5
pn  schroot           <none>
ii  vmdb2             0.13.2+git20190215-1

-- no debconf information
At the upstream report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960800
I was told that "/bin/sh" should be used in place of /sbin/getty for ttyS1 in /etc/inittab
in the qemu image. This issue is resolved also on Devuan Chimaera by that trick.
I close #461 Ryutaroh