Guido Günther wrote:
I'm using the same setup and it works fine here.
On Tue, Dec 30, 2008 at 12:22:04PM -0600, Miguel Enrique Cobá Martínez wrote:
unix_sock_group = "libvirt"
unix_sock_rw_perms = "0770"
auth_unix_ro = "none"
auth_unix_rw = "none"
It seems you can't access the rw socket.
You can also try:
cat /var/run/libvirt/libvirt-sock
It should give "cat: /var/run/libvirt/libvirt-sock-ro: No such device or
address" not "permission denied".
[..snip..]
Verify that the libvirtd daemon is running with the default config:
# ps ax| grep libvirtd
No output here? This is wrong.
[..snip..]
You can only see the VMs (R/O mode: monitoring VM status only). That is,
you cannot start/stop/pause the VM (R/W mode: full VM management). In
the previous version you could.
Now, as root, and using virsh you can start and stop the VM:
laptop:~# virsh start WindowsXP
Domain WindowsXP started
laptop:~# virsh shutdown WindowsXP
Domain WindowsXP is being shutdown
The VM start and stop correctly and I can view it and use it with
virt-manager (in R/O mode)
But as normal user you can't start it:
mig...@laptop:~$ virsh start WindowsXP
Cannot set group when not running as root
libvir: QEMU error : Domain not found
libvir: QEMU error : Domain not found
error: failed to get domain 'WindowsXP'
Try "virsh -c qemu:///system".
Another thing I noticed, the previous version used to start the dnsmasq
automatically (I had ENABLED=0 in /etc/default/dnsmasq). This versión
doesn't start dnsmasq and therefore denies network capabilities to the VMs.
This again is an indication that you're mixing access to qemu:///system
and qemu:///session.
Please make sure you use either --connect=qemu:///system (connect to
daemon started via /etc/init.d/libvirt-bin) or --connect=qemu:///session
(started as user) and retest with virsh and virt-manager.
Which version of virt-manager is this? I'm using 0.6.0-6.
Cheers,
-- Guido
I have temporaly enabled unstable (sid) on my /etc/apt/sources.list and
installed virt-manager from sid with:
laptop:~# aptitude install -tsid virt-manager
This installed
virt-manager 0.6.0-6
virtinst 0.400.0-7
using this versión of virt-manager, all worked right.
Maybe the versión from testing (lenny) has some kind of incompatibility
with the libvirtd version 0.4.6-10.
So it appears that fast tracking virt-manager 0.4.6-10 from sid to lenny
solves this problem.
I continue testing for further problems, but in the meantime I can
start/stop/pause the VM without problem.
Thank you very much Guido.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
