Missing emulation for epoll_create syscall

[Matteo Mattei]

Binary package hint: qemu-kvm

Looking at bootstrap.log after rootstock (bzr revision 126) I see this crash in qemu when it try to setup the console-setup package:

Setting up console-setup (1.34ubuntu15) ...
qemu: Unsupported syscall: 250
plymouth: ply-event-loop.c:466: ply_event_loop_new: Assertion `loop->epoll_fd >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted
update-initramfs: deferring update (trigger activated)

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: qemu-kvm-extras-static 0.12.3+noroms-0ubuntu9.2
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Wed Sep 22 09:19:50 2010
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
Lsusb:
 Bus 002 Device 002: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdLine: root=UUID=d2ea5f7c-cdb5-4565-bae8-94ec26df00ee ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LANGUAGE=
SourcePackage: qemu-kvm
dmi.bios.date: 09/18/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/18/2009:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

[Serge Hallyn (serge-hallyn)]

Thanks for reporting this bug and helping to make Ubuntu better.

Could you tell us the precise rootstock command you used, how you
subsequently started up the image (full kvm commandline), and attach
the bootstrap.log?

[Matteo Mattei (matteo-mattei)]

This is the rootstock command I use:

sudo ./rootstock \
        --fqdn NGP \
        --login myuser \
        --password mypassword \
        --imagesize 1G \
        --serial ttyS2 \
        --doswap \
        --swapsize 256 \
        --script ${HOME}/rootstock/setup.sh \
        --mirror http://localhost/ubuntu-armel \
        --manifest ${HOME}/rootstock/manifest.txt \
        --extra-mirror http://localhost/my-custom-packages \
        --locale en_US.UTF-8

where:
    setup.sh is a file with my customization
    http://localhost/ubuntu-armel is my local repository (mirrored with apt-mirror to the ubuntu official one)
    http://localhost/my-custom-packages is a local repository with some custom packages

The final images is generated w/o problem during the output (attached) but in the bootstrap.log (it is attached too) I see some errors:

Unsupported ioctl: cmd=0xc020660b <---- repeted more times

and

Setting up console-setup (1.34ubuntu15) ...
qemu: Unsupported syscall: 250
plymouth: ply-event-loop.c:466: ply_event_loop_new: Assertion `loop->epoll_fd >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted
update-initramfs: deferring update (trigger activated)

Anyway, I have never started up the image using qemu... I only need the ubuntu archive image to install in my board but looking in /var/log/bootstrap.log I saw those errors...

Again, using my generated built image, sometimes I experience a lot of "Segmentation fault" or "Illegal instruction" running some common tools like "top, grep, ps, ls etc...", should it be related to the error above?

[Launchpad Janitor (janitor)]

[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.]

[Zygmunt Krynicki (zyga)]

This occurred while configuring the same package using linaro headless 20110208 with identical error messages:

qemu: Unsupported syscall: 250
plymouth: ply-event-loop.c:466: ply_event_loop_new: Assertion `loop->epoll_fd >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted

[Loïc Minier (lool)]

I reproduce this with:
sudo qemu-debootstrap --arch armel natty natty-armel http://ports.ubuntu.com/ubuntu-ports
sudo chroot natty-armel /bin/bash
echo 'deb http://ports.ubuntu.com/ubuntu-ports natty main' > /etc/apt/sources.list
apt-get update
apt-get install --reinstall console-setup
[...]
Unpacking replacement console-setup ...
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up console-setup (1.57ubuntu5) ...
qemu: Unsupported syscall: 250
plymouth: ply-event-loop.c:466: ply_event_loop_new: Assertion `loop->epoll_fd >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted (core dumped)
Unknown name $sun_t6_custom

I think plymouth does some epoll_create, that returns ENOSYS or fails or another reason, so it aborts.

I'm moving this to qemu-linaro as to implement epoll_create -- I think we do have this on ARM nowadays.

[Peter Maydell (pmaydell)]

I have what seems to be a working implementation of the epoll syscalls; still need to test it on the qemu-debootstrap test case and submit upstream.

[Peter Maydell (pmaydell)]

Patch tested on the qemu-debootstrap test case, submitted upstream:
  http://patchwork.ozlabs.org/patch/83279/
(I'll put it into qemu-linaro 2011.03 anyway even if it hasn't made it into upstream git by then)

With the new qemu, Loic's testcase no longer aborts in plymouth. (dpkg doesn't successfully configure console-setup because "setupcon --force -k" returns a non-zero exit status, but that is clearly not the same problem as this bug.)

[Steve Langasek (vorlon)]

qemu-linaro 2011.03 is included in natty, so marking this bug as fixed in the package. Please let us know if you still experience this issue.

[Ira Rosen (irar)]

I am out of the office until 17/04/2011.

Note: This is an automated response to your message "[Bug 644961] Re:
Missing emulation for epoll_create syscall" sent on 12/4/11 8:32:28.

This is the only notification you will receive while this person is away.