Thanks for the report, we need to add that indeed the moment we have something reliable by upstream I've added the upstream bug tracker https://gitlab.com/qemu-project/qemu/-/issues/3065
Implementation looks like being worked on since https://mail.gnu.org/archive/html/qemu-devel/2025-08/msg04984.html With iterations on feedback and fixes like https://mail.gnu.org/archive/html/qemu-devel/2025-10/msg08521.html https://mail.gnu.org/archive/html/qemu-devel/2025-11/msg00043.html Recently got some more attention by us and Fedora picking up and seeing the same https://mail.gnu.org/archive/html/qemu-devel/2025-12/msg00468.html @Heinrich do you think we need to rush glossing over it by using the incomplete versions in resolute until the final one is out. No risc there yet, but this isn't exclusive to risc - that is just more common to run emulated. Or can we wait until they have it finalized (either way before resolute release we should have it in R but also in SRU that we expect to run resolute binaries. ** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #3065 https://gitlab.com/qemu-project/qemu/-/issues/3065 ** Also affects: qemu via https://gitlab.com/qemu-project/qemu/-/issues/3065 Importance: Unknown Status: Unknown ** Also affects: qemu (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Resolute) Importance: High Status: Confirmed ** Also affects: qemu (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Questing) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Questing) Status: New => Confirmed ** Changed in: qemu (Ubuntu Plucky) Status: New => Confirmed ** Changed in: qemu (Ubuntu Noble) Status: New => Confirmed ** Changed in: qemu (Ubuntu Jammy) Status: New => Confirmed ** Changed in: qemu (Ubuntu Questing) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu Plucky) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu Noble) Importance: Undecided => High ** Changed in: qemu (Ubuntu Jammy) Importance: Undecided => Low -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/2133804 Title: QEMU does not emulate IOCTL TCGETS2 Status in QEMU: Unknown Status in qemu package in Ubuntu: Confirmed Status in qemu source package in Jammy: Confirmed Status in qemu source package in Noble: Confirmed Status in qemu source package in Plucky: Confirmed Status in qemu source package in Questing: Confirmed Status in qemu source package in Resolute: Confirmed Bug description: In Ubuntu 25.10 we moved to glibc 2.42. Here glibc has changed the implementation of isatty(). It now uses IOCTL TCGETS2 instead of TCGETS. TCGETS2 is not emulated by static QEMU (qemu-riscv64, qemu- arm64, ...). This leads to failures in containers for foreign architectures. E.g. no console prompt is displayed. A detailed analysis is contained in LP #2133188. A proper implementation of the missing IOCTLs will include: Functions: in linux-user/syscall.c: host_to_target_termios2() target_to_host_termios2() print_termios2() Definitions: in linux-user/syscall.c #define termios2 host_termios2 in linux-user/syscall_types.h STRUCT_SPECIAL(termios2) in linux-user/ioctls.h: IOCTL(TCGETS2, IOC_R, MK_PTR(MK_STRUCT(STRUCT_termios2))) IOCTL(TCSETS2, IOC_W, MK_PTR(MK_STRUCT(STRUCT_termios2))) IOCTL(TCSETSF2, IOC_W, MK_PTR(MK_STRUCT(STRUCT_termios2))) IOCTL(TCSETSW2, IOC_W, MK_PTR(MK_STRUCT(STRUCT_termios2))) in linux-user/user-internals.h: void print_termios2(void *arg); To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/2133804/+subscriptions
