Hi;
After several days of intense googling with no solution, am forced to ask for help.
I am attempting to use my host bluetooth via /run/dbus using this as a guide: linux - Qemu share folder - 9pnet_virtio: no channels available for device - Super User and, receiving same errors
I have used home assistant OS buildroot to add the necessary haos kernel variables (linked in above link, may submit a pull request to make part of hassos, if succeed):
CONFIG_NET_9P=y CONFIG_NET_9P_VIRTIO=y CONFIG_NET_9P_DEBUG=y (Optional) CONFIG_9P_FS=y CONFIG_9P_FS_POSIX_ACL=y CONFIG_PCI=y CONFIG_VIRTIO_PCI=y CONFIG_PCI=y CONFIG_VIRTIO_PCI=y CONFIG_PCI_HOST_GENERIC=y (only needed for the QEMU Arm 'virt' board)
my host qemu-system-aarch64 invocation contains this:
-virtfs local,path=/run/dbus,mount_tag=dbus,security_model=mapped-xattr,readonly=on,multidevs=warn
and my mount command is:
mount -t 9p -o trans=virtio,version=9p2000.L,ro dbus /run/dbus (in Advanced SSH & Web Terminal). Suspect I should be mounting it in (read only) homeassistant container - how?
With a failure message on dmesg:
9pnet_virtio: no channels available for device dbus
mount | grep dbus returns
“dbus on /run/dbus type 9p (ro,sync,dirsync,relatime,access=client,trans=virtio)”
bluetoothctl returns:
Waiting to connect to bluetoothd...dbus[422]: arguments to dbus_connection_get_object_path_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5969. This is normally a bug in some application using the D-Bus library.
Not sure what the problem is? Anyone managed to passthrough host /run/dbus using qemu? Is there a better way? Cannot use virtualbox since it only supports X86_64
Am reluctant to use a supervised docker installation on host, since I have complex network setup, not using network-manager (pre-requisite for superviesd docker install)
Thanks;
Bill