Cole Robinson wrote:
On 04/07/2014 11:43 AM, Michal Privoznik wrote:
On 07.04.2014 17:12, Cole Robinson wrote:
On 04/04/2014 02:43 PM, Roman Bogorodskiy wrote:
Allow connection to bhyve using bhyve:///system URI.
---
virtManager/connect.py | 8 ++--
1 file changed, 6
On 07.04.2014 17:43, Michal Privoznik wrote:
On 07.04.2014 17:12, Cole Robinson wrote:
On 04/04/2014 02:43 PM, Roman Bogorodskiy wrote:
Allow connection to bhyve using bhyve:///system URI.
---
virtManager/connect.py | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git
On 04/07/2014 09:59 AM, Daniel P. Berrange wrote:
The more I think about it the more it makes me wonder if we should
learn libvirt return list of all supported/enabled drivers.
Something like:
char **virGetDrivers(virConnectPtr conn);
if conn == NULL, the client side drivers are returned,
Roman Bogorodskiy bogorods...@gmail.com writes:
Allow connection to bhyve using bhyve:///system URI.
---
virtManager/connect.py | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/virtManager/connect.py b/virtManager/connect.py
index b779c75..bc6d56d 100644
ACK.
Allow connection to bhyve using bhyve:///system URI.
---
virtManager/connect.py | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/virtManager/connect.py b/virtManager/connect.py
index b779c75..bc6d56d 100644
--- a/virtManager/connect.py
+++ b/virtManager/connect.py
@@