On Sat, Jan 19, 2008 at 11:07:18PM +0100, Soren Hansen wrote:
> On Sat, Jan 19, 2008 at 06:29:52PM +, Daniel P. Berrange wrote:
> > So this patch adds support for LIBVIRT_DEFAULT_URI env variable which
> > will be used if the connect URI is NULL. If that variable is not set
> > it will still de
Daniel P. Berrange wrote:
Currently, if the app provides NULL as the connect URI, we always connect
to a Xen hypervisor.
virsh provides a VIR_DEFAULT_CONNECT_URI env var which can be used to
override this. virt-install/virt-manager never use NULL, and now try
to 'guess' a default URI based o
On Sat, Jan 19, 2008 at 06:29:52PM +, Daniel P. Berrange wrote:
> So this patch adds support for LIBVIRT_DEFAULT_URI env variable which
> will be used if the connect URI is NULL. If that variable is not set
> it will still default to Xen.
virsh needs to be made aware of this as well. Current
Currently, if the app provides NULL as the connect URI, we always connect
to a Xen hypervisor.
virsh provides a VIR_DEFAULT_CONNECT_URI env var which can be used to
override this. virt-install/virt-manager never use NULL, and now try
to 'guess' a default URI based on whether /dev/kvm or /proc/x
