On Fri, Aug 23, 2019 at 05:11:18PM +, Jim Fehlig wrote:
> On 8/8/19 9:10 AM, Daniel P. Berrangé wrote:
> > 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.
>
> While thi
On 8/8/19 9:10 AM, Daniel P. Berrangé wrote:
> 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.
While thinking about this today I realized it is actually quite a rat hole. I
st
The virtxend daemon will be responsible for providing the libxl API
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 u
