On 3 October 2011 21:50, Mark Pryor <tlviewer@xxxxxxxxx> wrote:
> If virt-install can't connect to your xen install with or without the
> --connect flag,
The --debug option doesn't say nothing to me, even with the connect flag.
Here's the output:
Mon, 03 Oct 2011 21:53:56 DEBUG Requesting libvirt URI default
Mon, 03 Oct 2011 21:53:56 ERROR no connection driver available for
No connection for URI (null)
Mon, 03 Oct 2011 21:53:56 DEBUG Traceback (most recent call last):
File "/usr/bin/virt-install-2.7", line 995, in <module>
sys.exit(main())
File "/usr/bin/virt-install-2.7", line 975, in main
conn = cli.getConnection(options.connect)
File "/usr/lib64/python2.7/site-packages/virtinst/cli.py", line 327,
in getConnection
conn = open_connection(uri)
File "/usr/lib64/python2.7/site-packages/virtinst/cli.py", line 342,
in open_connection
open_flags)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 102, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: no connection driver available for No connection for URI (null)
> then perhaps
> /proc/xen is not mounted.
I think it is mounted:
# ls /proc/xen/
capabilities privcmd xenbus
--
Flavio
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|