there is no good way to get DTB working, have not looked at this to date, Viresh now has some cycles to look.
DTB, How do we limit guests to a subset of I2C devices for example? Arnd, assign one to one is my preference. Viresh i2c detect - pings all addresses to see if there is anything there, can't know what it is. Back end will not get the data sent to the guest OS’es, Arnd it has to be defined at guest creation. Alex on the guest side there is binding to **missed what ** host side which guest to which real HW. Alex for daemon you could have a magic shell script for now - Arnd we cant do that, shell script cant know, Alex, hardcoded ? Arnd yes if embedded.
Alex, perhaps scope a card to look at this, do have card on how to describe a system, Arnd who defines DT in QEMU ? Alex from QEMU it depends, only the virt machine cares. Arnd for fixed machine it is easier. Arnd assumed we would use virt machine. need format for any virtio device, currently assume it is a PCI device, or the outside of the device and not what's inside. MMIO we have virtio device in DTB. For cases of GPIO as an interrupt or I2C with slave device we need to come up with a solution.
QEMU wants the same information as the backend - Arnd - command line ?, Alex for embedded yes. What happens with large numbers of GPIOs, imagine the command line
Viresh - Xen testing on MachiatoBin, unable to boot Dom0 unless it gets firmware information, fix looks straightforward (Stefano) just needs to be done.
Mathieu - how to connect rustVMM to daemon, Alex QEMU in my case, rustVMM may not have stub support. vmm-ref is just a shim. Alternative hypervisors need to think about production deployment. Viresh used QEMU.
RustVMM - AJB: not sure how easy it would be to do a Xen crate for rust-vmm given the tight coupling between the xen libs and their userspace and the version of the hypervisor. Maybe we just end up with several versioned crates (e.g. xen-4.14, xen-4.15…)
Alex be nice to look at Gynya, and create a crate for that.