We have installed VyOS version 1.1.6 as a Xen Para-Virtualized guest. When we enter configure mode, we get the following error message:
vyos@vyos:~$ configure fuse: failed to open /dev/fuse: Permission denied  vyos@vyos#
We can make changes to the config, but, when trying to commit the changes, the VyOS virtual machine freezes with the following output (not reachable via SSH anymore, and Xen console freezes).
vyos@vyos:~$ configure fuse: failed to open /dev/fuse: Permission denied  vyos@vyos# set system host-name edge-acn2.iciti.av  vyos@vyos# commit [ service ssh ] Stopping OpenBSD Secure Shell server: sshd. [ system package repository community ] Removing entry from /etc/apt/sources.list... [ system syslog ] Can't use an undefined value as an ARRAY reference at /opt/vyatta/sbin/vyatta_update_syslog.pl line 96. [ system login ] All login methods can not be deleted delete [ system login ] failed [ system ntp ] Stopping NTP server: ntpd. [ system console device hvc0 ] Warning: Access to system console is unconfigured [ system console device ttyS0 ] Warning: Access to system console is unconfigured
The vyos user is part of the fuse group, but when looking at the permissions of /dev/fuse we can see that, even though the group is set to fuse, there are no group read/write permissions on the file.
vyos@vyos:~$ groups users adm disk sudo dip quaggavty vyattacfg fuse vyos@vyos:~$ ls -l /dev/fuse crw------- 1 root fuse 10, 229 Nov 4 06:32 /dev/fuse vyos@vyos:~$
If we manually change the permissions of /dev/fuse to group read/write, then we are able to enter configure mode and commit. But on reboot, the permissions of /dev/fuse revert, and the problems with configure and commit re-present themselves.
The procedure we followed to create the Xen VM with VyOS is the following:
We have tried variations of the above procedure where we omitted installation of the Xen Tools package, this did not help. Another variation was to omit the last step of conversion from Xen HVM (fully virtualized) to Xen PV (para-virtualized) virtual machine, this did help. The problem seems to present itself only when VyOS is running as a Xen PV guest, but not when running as a Xen HVM guest, or on physical hardware (same VyOS version 1.1.6).
Does anyone know of any solutions or workarounds?