"Invalid argument" on creating file in 9p filesystem (Linux) about v86 HOT 13 CLOSED

@SuperMaxusa regarding the node issue I mentioned earlier, nothing to worry about, it's #875 . I noticed it earlier but just confirming the same here.

from v86.

Yes this issue is fixed and works in debian trixie+ too.

We can close this issue now (or maybe after new release)

from v86.

I have a similar issue when trying to open node console on alpine. It gives me an error saying 'x' invalid argument found or something. Will add more details later. Please ignore if this is irrelevant.

from v86.

trying to open node console on alpine.

did you tried run node with script without repl (or node -e "console.log('hello')") or this is also not working?

from v86.

did you tried run node with script without repl (or node -e "console.log('hello')") or this is also not working?

Am able to run node scripts without issues. issue was for node console only. Will try node -e "console.log('hello')" too and update here.

from v86.

This also reproduces in Void Linux 2024-03-14, so it's problem of Linux kernel 6.6.x (or earlier), not just Alpine

from v86.

Issue in debian too :( with 9pfs

from v86.

How do we fix this? I can try but will need some guidance. Issue is reproducable in the provided debian docker build in this repo too.

from v86.

I have some thoughts about this commit in linux repo: torvalds/linux@3866584, but I'm not entirely sure. Because of that reason, probably, open() and statx() returns EINVAL about incorrect flags.

Issue is reproducable in the provided debian docker build in this repo too.

Can you provide which kernel version is installed in rootfs? Seems a Dockerfile created on Debian Buster, which linux-image-686 has latest version as 4.19, or it's automatically updates?

from v86.

Seems a Dockerfile created on Debian Buster, which linux-image-686 has latest version as 4.19

Its auto-updated so the current version in it is 6.6.15-686

However, I downloaded and installed linux-image 5.10.0 (5.10.0-0.deb10.28-686) kernel but trying to figure out where I can change the default kernel version when booting :(

I am trying to see if 9p mounted with 5.10.0 linux-image would resolve the problem if its due to compatibility like you mentioned.

from v86.

My above reply is wrong, I changed it to trixie earlier. Buster doesn't have the 9p issue, working perfectly fine.

from v86.

Will be fixed in 2ca82a5.

from v86.

Thanks, works for me on Linux 6.6 without any problems.

@farhan-ct can you try build v86 from wip branch and test on newer Alpine (3.18.6+) or Debian (trixie+) versions?

from v86.