Skip to content

vm: enable inotify in guest kernels - #32

Open
zbarsky-openai wants to merge 1 commit into
hermeticbuild:mainfrom
zbarsky-openai:zbarsky/kernel-inotify
Open

zbarsky-openai wants to merge 1 commit into
hermeticbuild:mainfrom
zbarsky-openai:zbarsky/kernel-inotify

Conversation

@zbarsky-openai

Copy link
Copy Markdown

Node-based build actions that start a filesystem watcher fail inside the
VM:

Error: ENOSYS: function not implemented, watch
errno: -38
syscall: 'watch'
code: 'ENOSYS'

The compact kernels use allnoconfig, which omits the inotify system
calls. Enable CONFIG_INOTIFY_USER in both ARM64 and x86_64 kernel
configurations; it also selects the required CONFIG_FSNOTIFY support.

The ARM64 kernel builds and boots, and an unchanged Vite filesystem-watcher
test now passes inside the VM. Both resolved architecture configurations
contain CONFIG_INOTIFY_USER=y and CONFIG_FSNOTIFY=y.

Node-based build actions that start a filesystem watcher fail inside the
VM:

```text
Error: ENOSYS: function not implemented, watch
errno: -38
syscall: 'watch'
code: 'ENOSYS'
```

The compact kernels use `allnoconfig`, which omits the inotify system
calls. Enable `CONFIG_INOTIFY_USER` in both ARM64 and x86_64 kernel
configurations; it also selects the required `CONFIG_FSNOTIFY` support.

The ARM64 kernel builds and boots, and an unchanged Vite filesystem-watcher
test now passes inside the VM. Both resolved architecture configurations
contain `CONFIG_INOTIFY_USER=y` and `CONFIG_FSNOTIFY=y`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant