I used Opennebula from Ubuntu repository, so it is version 3.2.1-2.
I will try to upgrade it to version 3.4.
SSh transfer is vry slow (that is why I don't know if it
works yet ...), but definitely the issue is NFS in my case.
Which parameters has to be set?
Yes - of course, but by command /etc/init.d/apparmor reload
After that I tried to remove apparmor and from that moment I have
nothing in syslog but error message in oned.log changed to:
Wed Jun 20 17:51:03 2012 [LCM][I]: New VM state is BOOT
Wed Jun 20 17:51:03
Have you reloaded the apparmor conf?
service apparmor reload
On Wed, Jun 20, 2012 at 1:20 PM, Jan Benadik wrote:
> Maybe bingo?
>
> In /etc/apparmor.d/usr.sbin.libvirtd I have set (on ONE-server and host too):
> /var/lib/one/** lrwk,
>
> and /var/lib/syslog on host is saying (at deployment tim
Maybe bingo?
In /etc/apparmor.d/usr.sbin.libvirtd I have set (on ONE-server and host too):
/var/lib/one/** lrwk,
and /var/lib/syslog on host is saying (at deployment time):
Jun 20 15:10:16 opennebula-host kernel: [11202.067916] type=1400
audit(1340197816
Can you check that you are not getting apparmor error messages in
/var/log/syslog at the time of VM deployment?
On Wed, Jun 20, 2012 at 12:23 PM, Jan Benadik wrote:
>
> And of course - libvirtd daemon is restarted and running on both machines.
>
> oneadmin@opennebula-host:~$ ps aux|grep libv
> ro
And of course - libvirtd daemon is restarted and running on both
machines.
oneadmin@opennebula-host:~$ ps aux|grep libv
root 1010 0.0 0.0 852624 6612 ? Sl 12:03 0:00
/usr/sbin/libvirtd -d -l
106 1107 0.0 0.0 25964 992 ? S 1
