9:33 a.m.
2010/4/30 Tim McLeod <tim.mcleod(a)simulamen.eu>:
Requesting urgent assistance if I may?
Attempting to connect to an Ubuntu machine using an MinMG compiled virsh on
a Windows Vista machine. Using insecure TCP simply to prove a concept to a
client. However, cannot connect; situation as follows:
Edited /etc/libvirt/libvirt.conf as follows:
listen_tcp = 1
auth_tcp = "none"
Edited /etc/default//libvirt-bin as follows:
libvirt-opts="-d -l"
Did you restart libvirtd after the changes and checked that it's
started successfully?
listen_tls defaults to 1 in /etc/libvirt/libvirt.conf, in combination
with the -l flag (short for --listen) libvirtd requires properly
configured SSL certificates. If libvirtd can't find the certificates
or fails to validate them then it won't start up.
You can disable TLS in /etc/libvirt/libvirt.conf by setting listen_tls
= 0 and restart libvirtd.
Running virsh on Vista client fails as follows:
$ virsh -c qemu+tcp://192.168.1.101/system
error: unable to connect to libvirtd at '192.168.1.101': errno=10061
error: failed to connect to the hypervisor
Running virsh on Ubuntu server fails as follows:
$ virsh -c qemu+tcp:///system
Connecting to uri: qemu+tcp:///system
error: unable to connect to libvirtd at 'localhost': Connection refused
error: failed to connect to the hypervisor
Once libvirtd is running and configured properly for TCP transport
then remote and local TCP access to libvirtd works for me.
Indeed, with libvirt-opts="-d -l" in
etc/default//libvirt-bin the 'default'
command also fails:
$ virsh -c qemu:///system
Connecting to uri: qemu:///system
error: unable to connect to 'var/run/libvirt/libvirt-sock': Connection
refused
error: failed to connect to the hypervisor
Local access to libvirtd using qemu:///system requires properly
configured polkit, or running virsh as root. This is independent from
the -d and -l flags.
Matthias
9:44 p.m.
New subject: [libvirt-users] Windows Vista Client Fails to Connect to Ubuntu libvirtd
Matthias,
Excellent! Now up and running. I believe the crucial element was
listen_tls = 0
Once again, thank you very much for your help...
Tim
-----Original Message-----
From: libvirt-users-bounces(a)redhat.com [mailto:libvirt-users-bounces@redhat.com] On Behalf
Of Matthias Bolte
Sent: 01 May 2010 08:33
To: tim.mcleod(a)simulamen.eu
Cc: libvirt-users(a)redhat.com
Subject: Re: [libvirt-users] Windows Vista Client Fails to Connect to Ubuntu libvirtd
2010/4/30 Tim McLeod <tim.mcleod(a)simulamen.eu>:
Requesting urgent assistance if I may?
Attempting to connect to an Ubuntu machine using an MinMG compiled virsh on
a Windows Vista machine. Using insecure TCP simply to prove a concept to a
client. However, cannot connect; situation as follows:
Edited /etc/libvirt/libvirt.conf as follows:
listen_tcp = 1
auth_tcp = "none"
Edited /etc/default//libvirt-bin as follows:
libvirt-opts="-d -l"
Did you restart libvirtd after the changes and checked that it's
started successfully?
listen_tls defaults to 1 in /etc/libvirt/libvirt.conf, in combination
with the -l flag (short for --listen) libvirtd requires properly
configured SSL certificates. If libvirtd can't find the certificates
or fails to validate them then it won't start up.
You can disable TLS in /etc/libvirt/libvirt.conf by setting listen_tls
= 0 and restart libvirtd.
Running virsh on Vista client fails as follows:
$ virsh -c qemu+tcp://192.168.1.101/system
error: unable to connect to libvirtd at '192.168.1.101': errno=10061
error: failed to connect to the hypervisor
Running virsh on Ubuntu server fails as follows:
$ virsh -c qemu+tcp:///system
Connecting to uri: qemu+tcp:///system
error: unable to connect to libvirtd at 'localhost': Connection refused
error: failed to connect to the hypervisor
Once libvirtd is running and configured properly for TCP transport
then remote and local TCP access to libvirtd works for me.
Indeed, with libvirt-opts="-d -l" in
etc/default//libvirt-bin the 'default'
command also fails:
$ virsh -c qemu:///system
Connecting to uri: qemu:///system
error: unable to connect to 'var/run/libvirt/libvirt-sock': Connection
refused
error: failed to connect to the hypervisor
Local access to libvirtd using qemu:///system requires properly
configured polkit, or running virsh as root. This is independent from
the -d and -l flags.
Matthias
_______________________________________________
libvirt-users mailing list
libvirt-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
5353
days inactive
5355
days old
1 comments
2 participants
participants (2)
-
Development -
Matthias Bolte