Re: [virt-tools-list] connection refused when connecting to a VM
If you autenticate (need to enter root password root password when
connecting), see if root password hasn't changed (type 'su -', without the
quotes, in terminal, enter root password and see if it works).
Also check if libvirtd is running. Type 'ps aux | grep libtvirt' in
terminal, see if there is any process with this name.
On Tue, Feb 8, 2011 at 5:46 AM, Tapas Mishra mightydre...@gmail.com wrote:
I have been regularly logging in to a virtualization setup of mine and
have been using it.
Today after noon I logged in as usual and typed virt-manager
I got following error
Unable to open a connection to the libvirt management daemon.
Libvirt URI is: qemu:///system
Verify that:
- The 'libvirt-bin' package is installed
- The 'libvirtd' daemon has been started
- That you have access to '/var/run/libvirt/libvirt-sock'
system':
unable to connect to '/var/run/libvirt/libvirt-sock': Connection refused
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/connection.py, line 896,
in _try_open
None], flags)
File /usr/lib/python2.6/dist-packages/libvirt.py, line 111, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: unable to connect to '/var/run/libvirt/libvirt-sock':
Connection refused
Any idea as what might be causing this problem and what should I check in
here?
--
___
virt-tools-list mailing list
virt-tools-list@redhat.com
https://www.redhat.com/mailman/listinfo/virt-tools-list
___
virt-tools-list mailing list
virt-tools-list@redhat.com
https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] connection refused when connecting to a VM
Hi Bruno,
what worked was
changing the permissions of
/var/run/libvirt/libvirt-sock
When this problem came I saw the permissions as
srwxrwx--- 1 root root 0 2011-02-08 15:54 libvirt-sock
I did 777 to above file and I find the permissions now
srwxrwx--- 1 root libvirtd 0 2011-02-08 15:54 libvirt-sock
and now the virt-manager is working fine.
I really do not have any idea as why this problem came.
Though I was doing an update on my Ubuntu server at that time.
Here is a problem which I just reported to Ubuntu server team
https://answers.launchpad.net/ubuntu/+question/144560
I feel this is related with my problem.
In case you have any idea for this let me know.
But right now this problem is fixed.
On Tue, Feb 8, 2011 at 4:54 PM, Bruno Lamps lam...@gmail.com wrote:
If you autenticate (need to enter root password root password when
connecting), see if root password hasn't changed (type 'su -', without the
quotes, in terminal, enter root password and see if it works).
Also check if libvirtd is running. Type 'ps aux | grep libtvirt' in
terminal, see if there is any process with this name.
On Tue, Feb 8, 2011 at 5:46 AM, Tapas Mishra mightydre...@gmail.com wrote:
I have been regularly logging in to a virtualization setup of mine and
have been using it.
Today after noon I logged in as usual and typed virt-manager
I got following error
Unable to open a connection to the libvirt management daemon.
Libvirt URI is: qemu:///system
Verify that:
- The 'libvirt-bin' package is installed
- The 'libvirtd' daemon has been started
- That you have access to '/var/run/libvirt/libvirt-sock'
system':
unable to connect to '/var/run/libvirt/libvirt-sock': Connection refused
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/connection.py, line 896,
in _try_open
None], flags)
File /usr/lib/python2.6/dist-packages/libvirt.py, line 111, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: unable to connect to '/var/run/libvirt/libvirt-sock':
Connection refused
Any idea as what might be causing this problem and what should I check in
here?
--
--
___
virt-tools-list mailing list
virt-tools-list@redhat.com
https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] How can I run virt-manager 0.8.5 and 0.8.6 at the same system?
Hi, Just found the software where I can see the error messages (the kernel-related ones). Package:kernel Latest Crash:Qua 02 Fev 2011 14:33:43 Command:not_applicable Reason: WARNING: at lib/list_debug.c:26 __list_add+0x3f/0x81() Comment:None Bug Reports: Package:kernel Latest Crash:Qua 02 Fev 2011 14:33:43 Command:not_applicable Reason: WARNING: at lib/list_debug.c:30 __list_add+0x68/0x81() Comment:None Bug Reports: But I'm not sure that this is a clue, really. =/ On Mon, Feb 7, 2011 at 3:22 PM, Bruno Lamps lam...@gmail.com wrote: Hi, sorry to be this late, things are a little messed up here. =D Fedora isn't showing me the kernel dump in gnome tray, where can I find it? I located a log in /var/log/libvirt/libvirtd.log, previously actived: 14:36:17.444: debug : qemuMonitorGetBalloonInfo:1001 : mon=0x7f1ac800ce80 14:36:17.444: debug : qemuMonitorCommandWithHandler:231 : Send command 'info balloon' for write with FD -1 14:36:20.203: debug : qemuMonitorCommandWithHandler:236 : Receive command reply ret=-1 errno=104 0 bytes '(null)' 14:36:20.276: debug : qemuMonitorIO:577 : Triggering EOF callback error? 1 14:36:20.277: error : qemuMonitorCommandWithHandler:255 : cannot send monitor command 'info balloon': Connection reset by peer 14:36:20.277: error : qemuMonitorTextGetBalloonInfo:555 : operation failed: could not query memory balloon allocation 14:36:20.287: debug : qemuMonitorClose:691 : mon=0x7f1ac800ce80 14:36:20.307: debug : qemuMonitorFree:200 : mon=0x7f1ac800ce80 14:36:20.957: error : qemudDomainGetVcpus:6044 : Requested operation is not valid: cannot list vcpu pinning for an inactive domain 14:36:29.782: debug : qemuMonitorOpen:668 : New mon 0x7f1ac8014560 fd =37 watch=11 14:36:29.782: debug : qemuMonitorSetCapabilities:902 : mon=0x7f1ac8014560 14:36:29.872: debug : qemuMonitorGetPtyPaths:1702 : mon=0x7f1ac8014560 14:36:29.874: debug : qemuMonitorCommandWithHandler:231 : Send command 'info chardev' for write with FD -1 14:36:29.876: debug : qemuMonitorCommandWithHandler:236 : Receive command reply ret=0 errno=0 102 bytes 'monitor: filename=unix:/var/lib/libvirt/qemu/stfcnc$ serial0: filename=pty:/dev/pts/2 ' 14:36:29.876: debug : qemuMonitorGetCPUInfo:982 : mon=0x7f1ac8014560 14:36:29.876: debug : qemuMonitorCommandWithHandler:231 : Send command 'info cpus' for write with FD -1 14:36:29.879: debug : qemuMonitorCommandWithHandler:236 : Receive command reply ret=0 errno=0 48 bytes '* CPU #0: pc=0x0000 thread_id=369 ' 14:36:29.879: debug : qemuMonitorTextGetCPUInfo:448 : vcpu=0 pid=369 14:36:29.879: debug : qemuMonitorSetBalloon:1113 : mon=0x7f1ac8014560 newmem=1048576 14:36:29.879: debug : qemuMonitorCommandWithHandler:231 : Send command 'balloon 1024' for write with FD -1 14:36:29.879: debug : qemuMonitorCommandWithHandler:236 : Receive command reply ret=0 errno=0 0 bytes '(null)' 14:36:29.879: debug : qemuMonitorStartCPUs:923 : mon=0x7f1ac8014560 14:36:29.879: debug : qemuMonitorCommandWithHandler:231 : Send command 'cont' for write with FD -1 14:36:29.880: debug : qemuMonitorCommandWithHandler:236 : Receive command reply ret=0 errno=0 0 bytes '(null)' 14:36:29.881: debug : qemuMonitorGetBalloonInfo:1001 : mon=0x7f1ac8014560 14:36:29.881: debug : qemuMonitorCommandWithHandler:231 : Send command 'info balloon' for write with FD -1 14:36:29.892: debug : qemuMonitorCommandWithHandler:236 : Receive command reply ret=0 errno=0 22 bytes 'balloon: actual=1024 Does this log help you guys? I tried windows 2003 and windows 7 isos, both installation processes stops right after HD formatting. On Thu, Feb 3, 2011 at 10:20 AM, Richard W.M. Jones rjo...@redhat.comwrote: On Wed, Feb 02, 2011 at 03:14:47PM -0300, Bruno Lamps wrote: But today I noticed that I'm not able to run (not even install) windows 2003 VMs. LOL I create the machine, boot the install cd, format the disk, and the machine goes down unexpectedly. Fedora gives me some crach report, saying that some kernel crach happened. Then I turn the VM on again, but the disk image isn't bootable, and if I try to run the win2003 install CD again, it crashes again, same way. We don't print these reports out for entertainment. Please post the full messages you see into a new bug. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df http://people.redhat.com/%7Erjones%0Avirt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] How do I set up spice with virt-manager-0.8.6?
On 02/04/2011 08:14 PM, sean darcy wrote: I've installed: rpm -qa | grep virt | sort libvirt-0.8.7-1.fc14.x86_64 libvirt-client-0.8.7-1.fc14.x86_64 libvirt-python-0.8.7-1.fc14.x86_64 ocaml-libvirt-0.6.1.0-7.fc13.x86_64 ocaml-libvirt-devel-0.6.1.0-7.fc13.x86_64 python-virtinst-0.500.5-1.fc14.noarch python-virtkey-0.50-8.fc14.x86_64 redland-virtuoso-1.0.12-1.fc14.x86_64 virt-manager-0.8.6-1.fc14.noarch virtuoso-opensource-6.1.2-1.fc14.x86_64 virt-viewer-0.2.1-1.fc13.x86_64 and rpm -qa | grep spice | sort spice-glib-0.5-1.fc14.x86_64 spice-gtk-0.5-1.fc14.x86_64 spice-gtk-python-0.5-1.fc14.x86_64 spice-protocol-0.7.0-2.fc14.noarch spice-server-0.7.2-1.fc14.x86_64 spice-vdagent-0.6.3-2.fc14.x86_64 On the server. But I can't connect to the vm using spicec or spicey from a remote. From the server host: spicec -h localhost -p 5930 Warning: failed to connect: Connection refused (111) Is there a way to have virt-manager to use spice, or do I need to edit the /etc/libvirt/qemu/*.xml by hand? If I need to edit by hand, is http://www.libvirt.org/formatdomain.html the correct guide? You can use virt-manager's 'Add Hardware' wizard to add a spice graphics device to your guest. You'll also want to make sure you have the latest qemu-system-x86 package as well (in fact, latest packages in fedora may still not be new enough for this to work with libvirt, so you may need to build from upstream). - Cole ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] How do I set up spice with virt-manager-0.8.6?
Will we have this capability in Fedora 15 without rebuilding from source? Or is that a bit further down the road? Thanks. -Kenny On Tue, Feb 8, 2011 at 10:31 AM, Cole Robinson crobi...@redhat.com wrote: On 02/04/2011 08:14 PM, sean darcy wrote: I've installed: rpm -qa | grep virt | sort libvirt-0.8.7-1.fc14.x86_64 libvirt-client-0.8.7-1.fc14.x86_64 libvirt-python-0.8.7-1.fc14.x86_64 ocaml-libvirt-0.6.1.0-7.fc13.x86_64 ocaml-libvirt-devel-0.6.1.0-7.fc13.x86_64 python-virtinst-0.500.5-1.fc14.noarch python-virtkey-0.50-8.fc14.x86_64 redland-virtuoso-1.0.12-1.fc14.x86_64 virt-manager-0.8.6-1.fc14.noarch virtuoso-opensource-6.1.2-1.fc14.x86_64 virt-viewer-0.2.1-1.fc13.x86_64 and rpm -qa | grep spice | sort spice-glib-0.5-1.fc14.x86_64 spice-gtk-0.5-1.fc14.x86_64 spice-gtk-python-0.5-1.fc14.x86_64 spice-protocol-0.7.0-2.fc14.noarch spice-server-0.7.2-1.fc14.x86_64 spice-vdagent-0.6.3-2.fc14.x86_64 On the server. But I can't connect to the vm using spicec or spicey from a remote. From the server host: spicec -h localhost -p 5930 Warning: failed to connect: Connection refused (111) Is there a way to have virt-manager to use spice, or do I need to edit the /etc/libvirt/qemu/*.xml by hand? If I need to edit by hand, is http://www.libvirt.org/formatdomain.html the correct guide? You can use virt-manager's 'Add Hardware' wizard to add a spice graphics device to your guest. You'll also want to make sure you have the latest qemu-system-x86 package as well (in fact, latest packages in fedora may still not be new enough for this to work with libvirt, so you may need to build from upstream). - Cole ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] How do I set up spice with virt-manager-0.8.6?
On 02/08/2011 10:41 AM, Kenneth Armstrong wrote: Will we have this capability in Fedora 15 without rebuilding from source? Or is that a bit further down the road? Thanks. -Kenny Fedora 15 spice need no special packages/building, and the plan is to use spice for new f15 guests. - Cole On Tue, Feb 8, 2011 at 10:31 AM, Cole Robinson crobi...@redhat.com wrote: On 02/04/2011 08:14 PM, sean darcy wrote: I've installed: rpm -qa | grep virt | sort libvirt-0.8.7-1.fc14.x86_64 libvirt-client-0.8.7-1.fc14.x86_64 libvirt-python-0.8.7-1.fc14.x86_64 ocaml-libvirt-0.6.1.0-7.fc13.x86_64 ocaml-libvirt-devel-0.6.1.0-7.fc13.x86_64 python-virtinst-0.500.5-1.fc14.noarch python-virtkey-0.50-8.fc14.x86_64 redland-virtuoso-1.0.12-1.fc14.x86_64 virt-manager-0.8.6-1.fc14.noarch virtuoso-opensource-6.1.2-1.fc14.x86_64 virt-viewer-0.2.1-1.fc13.x86_64 and rpm -qa | grep spice | sort spice-glib-0.5-1.fc14.x86_64 spice-gtk-0.5-1.fc14.x86_64 spice-gtk-python-0.5-1.fc14.x86_64 spice-protocol-0.7.0-2.fc14.noarch spice-server-0.7.2-1.fc14.x86_64 spice-vdagent-0.6.3-2.fc14.x86_64 On the server. But I can't connect to the vm using spicec or spicey from a remote. From the server host: spicec -h localhost -p 5930 Warning: failed to connect: Connection refused (111) Is there a way to have virt-manager to use spice, or do I need to edit the /etc/libvirt/qemu/*.xml by hand? If I need to edit by hand, is http://www.libvirt.org/formatdomain.html the correct guide? You can use virt-manager's 'Add Hardware' wizard to add a spice graphics device to your guest. You'll also want to make sure you have the latest qemu-system-x86 package as well (in fact, latest packages in fedora may still not be new enough for this to work with libvirt, so you may need to build from upstream). - Cole ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
[virt-tools-list] store vm xml files in another directory
I know that by default, vm xml files are in /etc/libvirt/qemu/vm-name.xml, but is there a configuration somewhere that I could point to another directory? For instance, have it on something like /srv/qemu/xml/vm-name.xml which would be a GFS2 filesystem (for HA purposes)? -Kenny ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
