On 7/23/19 10:03 AM, Daniel P. Berrangé wrote:
The virtxend daemon will be responsible for providing the libxl API
Written that way, with the 'xen' and 'd' squashed together, revives nightmares of another thing with similar name :-). However I agree it is the correct name to use here and the 'virt' prefix helps settle my stomach.
driver functionality. The libxl driver is still loaded by the main libvirtd daemon at this stage, so virtxend must not be running at the same time.
This naming is slightly different than other drivers. With the libxl driver, the user still has a 'xen:///system' URI, and we provide it in a libvirt-daemon-xen RPM, which pulls in a libvirt-daemon-driver-libxl RPM.
Arguably we could rename the libxl driver to "xen" since it is the only xen driver we have these days, and that matches how we expose it to users in the URI naming.
Nod. And the contents of xenconfig directory could likely be moved under it. Regards, Jim