On Mon, Jan 29, 2018 at 11:58:11AM +0100, Peter Krempa wrote:
> > Daniel P. Berrangé (10):
> > storage: move driver registration back to end of the file
> > storage: allow opening with storage:///system and storage:///session
> > URIs
> > network: move driver registration back to end of
On Mon, Jan 29, 2018 at 12:46:11PM +0100, Erik Skultety wrote:
> On Fri, Jan 26, 2018 at 01:35:27PM +, Daniel P. Berrangé wrote:
> > Currently the secondary drivers can only be used if you have a
> > connection to a primary hypervisor driver. This series introduces
> > explicit URIs that allow
On Mon, Jan 29, 2018 at 11:58:11AM +0100, Peter Krempa wrote:
> On Fri, Jan 26, 2018 at 13:35:27 +, Daniel Berrange wrote:
> > Currently the secondary drivers can only be used if you have a
> > connection to a primary hypervisor driver. This series introduces
> > explicit URIs that allow
On Fri, Jan 26, 2018 at 01:35:27PM +, Daniel P. Berrangé wrote:
> Currently the secondary drivers can only be used if you have a
> connection to a primary hypervisor driver. This series introduces
> explicit URIs that allow opening a connection that only talks to a
> specific secondary driver.
On Fri, Jan 26, 2018 at 13:35:27 +, Daniel Berrange wrote:
> Currently the secondary drivers can only be used if you have a
> connection to a primary hypervisor driver. This series introduces
> explicit URIs that allow opening a connection that only talks to a
> specific secondary driver. In
On 01/26/2018 02:35 PM, Daniel P. Berrangé wrote:
> Currently the secondary drivers can only be used if you have a
> connection to a primary hypervisor driver. This series introduces
> explicit URIs that allow opening a connection that only talks to a
> specific secondary driver. In the future
Currently the secondary drivers can only be used if you have a
connection to a primary hypervisor driver. This series introduces
explicit URIs that allow opening a connection that only talks to a
specific secondary driver. In the future these URIs will resolve to
individual daemons containing