Hi,
first of all thanks for your help, folks!
root@Arbeitsrechner:~# grep -vE '^($|#)' /etc/libvirt/qemu.conf
user = "oneadmin"
group = "oneadmin"
dynamic_ownership = 0
root@Arbeitsrechner:~# grep -vE '^($|#)' /etc/libvirt/libvirtd.conf
listen_tls = 0
listen_tcp = 1
mdns_adv = 0
unix_sock_group = "oneadmin"
unix_sock_rw_perms = "0777"
auth_unix_ro = "none"
auth_unix_rw = "none"
(root@Arbeitsrechner:~# grep -vE '^($|#)' /etc/default/libvirt-bin
start_libvirtd="yes"
libvirtd_opts="-d -l")
I did a complete computer-restart after that just to be sure ;)
oneadmin@Arbeitsrechner:~$ virsh -c qemu:///system nodeinfo
Fehler: Failed to connect socket to '/var/run/libvirt/libvirt-sock':
Datei oder Verzeichnis nicht gefunden
Fehler: Verbindung zum Hypervisor scheiterte
oneadmin@Arbeitsrechner:~$ /var/tmp/one/im/kvm.d/kvm.rb
Fehler: Failed to connect socket to '/var/run/libvirt/libvirt-sock':
Datei oder Verzeichnis nicht gefunden
Fehler: Verbindung zum Hypervisor scheiterte
That means "File or directory not found" "Connection to hypervisor failed"
Cheers,
Marco
Am 15.01.2013 12:40, schrieb Jaime Melis:
Hi Marco,
yes, just like Tobias says it should work. Can you configure the files
the same way Tobias said (and restart libvirtd) and run these commands
(as oneadmin in the worker node):
$ virsh -c qemu:///system nodeinfo
$ /var/tmp/one/im/kvm.d/kvm.rb
On Tue, Jan 15, 2013 at 12:30 PM, Tobias Honacker
<[email protected] <mailto:[email protected]>> wrote:
your config files must look like this: (works perfect for me)
[root@priv001 ~]# grep -vE '^($|#)' /etc/libvirt/qemu.conf
user = "oneadmin"
group = "oneadmin"
dynamic_ownership = 0
[root@priv001 ~]# grep -vE '^($|#)' /etc/libvirt/libvirtd.conf
listen_tls = 0
listen_tcp = 1
mdns_adv = 0
unix_sock_group = "oneadmin"
unix_sock_rw_perms = "0777"
auth_unix_ro = "none"
auth_unix_rw = "none"
there is no output in your command by executing
grep -vE '^($|#)' /etc/libvirt/qemu.conf
please check your qemu.conf file.
Am 15.01.2013 12:22, schrieb Marco Jagodzinska:
Hi Jaime,
this is my current configuration. (onehost is working, but onevm
isn't. But when I follow the KVM configuration
(http://opennebula.org/documentation:rel3.8:kvmg) onehost isn't
working any longer)
oneadmin@Arbeitsrechner:~$ grep -vE '^($|#)'
/etc/libvirt/libvirtd.conf
unix_sock_group = "libvirtd"
unix_sock_rw_perms = "0770"
auth_unix_ro = "none"
auth_unix_rw = "none"
oneadmin@Arbeitsrechner:~$ grep -vE '^($|#)' /etc/libvirt/qemu.conf
oneadmin@Arbeitsrechner:~$
oneadmin@Arbeitsrechner:~$ grep -vE '^($|#)'
/etc/apparmor.d/libvirt-qemu
grep: /etc/apparmor.d/libvirt-qemu: Datei oder Verzeichnis nicht
gefunden
That means "not found" ;)
But I put libvirt into complain mode:
root@Arbeitsrechner:~# aa-status
[...]
2 profiles are in complain mode.
/usr/lib/libvirt/virt-aa-helper
/usr/sbin/libvirtd
[..]
oneadmin@Arbeitsrechner:~$ virsh -c qemu:///system nodeinfo
CPU-Modell: x86_64
CPU(s): 4
CPU-Frequenz: 1199 MHz
CPU-Socket(s): 1
Kern(e) pro Socket: 2
Thread(s) pro Kern: 2
NUMA-Zelle(n): 1
Speichergrösse: 3911112 kB
Cheers,
Marco
Am 15.01.2013 12:02, schrieb Jaime Melis:
Hi Marco,
I'm a bit lost about your current configuration, can you do grep
-vE '^($|#)' on these files and pastebin them to this list?
- /etc/libvirt/libvirtd.conf
- /etc/libvirt/qemu.conf
- /etc/apparmor.d/libvirt-qemu
Also, what happens when you do (as oneadmin):
$ virsh -c qemu:///system nodeinfo
cheers,
Jaime
On Mon, Jan 14, 2013 at 4:16 PM, Marco Jagodzinska
<[email protected] <mailto:[email protected]>> wrote:
I'm working as oneadmin :)
sudo su oneadmin
Am 14.01.2013 16:09, schrieb Duverne, Cyrille:
Marco,
Just to be 100% sure, are you launching and using ONE as
oneadmin ?
Cheers
Cyrille
Lundi 14/01/2013 à 15:51 Marco Jagodzinska a écrit:
Hello again,
so you mean changing the two following two parts in
|/etc/libvirt/libvirtd.conf| ?/
unix_sock_group = "libvirt" -> unix_sock_group =
"oneadmin"///
and
/
//unix_sock_rw_perms = "0770" -> unix_sock_rw_perms =
"0777"
I tried it and it still isn't working.
But that strangest thing is: when I don't change
anything at all "onehost create" is working.
I thought because of later errors with "onevm create"
(see mail: [one-users] "Could not create domain" while
trying to start a vm, 9.1.), I have to follow the steps
for KVM configuration from the official site.
I dont want to believe that following the official
tutorial leads to errors you doesn't would have when
you do nothing ;)
Cheers,
Marco
/
Am 14.01.2013 14:54, schrieb Duverne, Cyrille:
> Hello again,
>
> As mentionned here as well :
>
http://lists.opennebula.org/pipermail/users-opennebula.org/2011-March/014614.html
>
> You have to run libvirt as oneadmin.
>
> Could you try again ?
>
> Cheers
> Cyrille
>
> Lundi 14/01/2013 à 14:50 Marco Jagodzinska a écrit:
>
> Hello Cyrille,
>
> thanks for your answer!
>
> I tried both.
>
> With "-l" the command "service libvirt-bin
restart" isn't longer
> working properly:
> root@Arbeitsrechner:/# service libvirt-bin restart
> stop: Unknown instance:
> libvirt-bin start/running, process 25471
>
> Without "-l" the restart is working fine:
> root@Arbeitsrechner:/# service libvirt-bin restart
> libvirt-bin stop/waiting
> libvirt-bin start/running, process 25673
>
> And "onehost create" fails in both cases...
>
> Cheers,
> Marco
>
>
>
> Am 14.01.2013 14:38, schrieb Duverne, Cyrille:
>> Hello Marco,
>>
>> Did you launch livirt with the -l option ?
>> As described in the tutorial :
>> "
>>
>> *
>> |/etc/libvirt/libvirtd.conf| : Uncomment “listen_tcp
= 1”.
>> Security configuration is left to the
admin's choice, file is
>> full of useful comments to achieve a correct
configuration.
>> As a tip, if you don't want to use TLS for
connections set
>> |listen_tls = 0|.
>>
>> *
>> |/etc/default/libvirt-bin| : add *-l* option to
|libvirtd_opts|
>>
>> "
>>
>> Just my 2 cents.
>>
>> Kind regards
>> CyD
>>
>>
>> Lundi 14/01/2013 à 14:20 Marco Jagodzinska a écrit:
>>
>> Hello again,
>>
>> next try, hoping for an answer ;)
>>
>> (I'm using Xubuntu 12.04 and the latest
OpenNebula 3.8.3)
>>
>> If I follow the tutorial for configuring KVM
>>
(http://opennebula.org/documentation:rel3.8:kvmg), I
receive
>> an error
>> message when I try to "onehost create
localhost -i im_kvm -v
>> vmm_kvm -n
>> dummy"
>>
>> The error (onehost show):
>>
>> ERROR=[
>> MESSAGE="Error monitoring host 4 :
MONITOR FAILURE 4 Error
>> executing
>> kvm.rb
>> ",
>> TIMESTAMP="Mon Jan 14 14:10:11 2013" ]
>>
>>
>>
>> It seems that the step leading to this error
is changing
>> qemu.conf so
>> that it reads as follows:
>>
>> $ grep -vE '^($|#)' /etc/libvirt/qemu.conf
>> user = "oneadmin"
>> group = "oneadmin"
>> dynamic_ownership = 0
>>
>>
>> Anybody able to help me?
>>
>> Cheers,
>> Marco
>>
>>
>> _______________________________________________
>> Users mailing list
>> [email protected]
<mailto:[email protected]>
<mailto:[email protected]>
<mailto:[email protected]>
>>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Jaime Melis
Project Engineer
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org <http://www.OpenNebula.org> |
[email protected] <mailto:[email protected]>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Jaime Melis
Project Engineer
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org <http://www.OpenNebula.org> | [email protected]
<mailto:[email protected]>
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
