On Tue, 2014-06-24 at 16:24 -0600, Jim Fehlig wrote: > Ian Campbell wrote: > > On Fri, 2014-06-20 at 15:07 -0600, Jim Fehlig wrote: > > > >> The libxl driver currently sets the disk backend to > >> LIBXL_DISK_BACKEND_TAP when <driver name='file'> is specified > >> in the <disk> config. qdisk should be prefered with this > >> configuration, otherwise existing configuration such as the > >> following, which worked with the old Xen driver, will not work > >> with the libxl driver > >> > > > > OOI why not let libxl pick the most appropriate backend for (most of) > > these alternatives? > > > > I think the libvirt approach is to be a bit more explicit, instead of > relying on hypervisor defaults that might change over time. I'm quite > sure this is the approach danpb has always advocated. I thought that policy was more for guest visible things whereas the disk backend is transparent to the guest. But either way it's up to libvirt. Thanks, Ian. -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list