Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FireMarshal does not support being run out of a NFS-mounted directory #137

Open
jerryz123 opened this issue Feb 18, 2020 · 1 comment
Open

Comments

@jerryz123
Copy link
Contributor

Default runs of FireMarshal in a NFS-mounted directory will result in

Running: "guestmount --pid-file guestmount.pid -a /nscratch/jerryz/chipyard-proj/chipyard4/software/firemarshal/images/br-base.img -m /dev/sda /nscratch/jerryz/chipyard-proj/chipyard4/software/firemarshal/disk-mount" in /nscratch/jerryz/chipyard-proj/chipyard4/software/firemarshal
fusermount: failed to open mountpoint for reading: Permission denied
libguestfs: error: fuse_mount: /nscratch/jerryz/chipyard-proj/chipyard4/software/firemarshal/disk-mount: Operation not permitted
TaskError - taskid:/nscratch/jerryz/chipyard-proj/chipyard4/software/firemarshal/images/br-base.img

I'm not familiar with the details here, but there seems to be some issue with FUSE and NFS.

The workaround I am using is to set mnt-dir in wlutil.py to a local directory.

@NathanTP
Copy link
Contributor

I don't think generally fixing this is feasible. It's only an issue with setups that don't have sudo and it seems like a fundamental problem. Autodetecting this corner case and working around it also doesn't seem like it's worth the extra complexity.

I will make the manual workaround easier though by allowing the user to override mnt-dir in their config or with an environment variable.

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

No branches or pull requests

2 participants