Hello Community Members,
After finally able to setup OpenNebula 3.4.1 in standalone mode on
Fedora 14, I tried to create a VM from a template but I get errors:
---
Fri Jun 1 13:10:17 2012 [DiM][I]: New VM state is ACTIVE.
Fri Jun 1 13:10:17 2012 [LCM][I]: New VM state is PROLOG.
Looks like opennebula user does not have permission to do this:
scp -r /srv/cloud/one3/var/remotes//. 127.0.0.1:/var/tmp/one
Check that /var/tmp/one has the correct permissions so that oneadmin can
write to it.
Hector
En Fri, 01 Jun 2012 13:20:15 +0200, Piyush Harsh piyush.ha...@inria.fr
So... can you ssh to 127.0.0.1 as oneadmin?
Fri Jun 1 13:13:00 2012 [VMM][I]: Command execution fail: scp -r
/srv/cloud/one3/var/remotes//. 127.0.0.1:/var/tmp/one
Fri Jun 1 13:13:00 2012 [VMM][I]: scp: /var/tmp/one/./scripts_common.**rb:
Permission denied
Regards
--
Carlos Martín, MSc
Project
Yes I can to a passwordless ssh to 127.0.0.1
Regards,
Piyush.
On Fri 01 Jun 2012 01:25:46 PM CEST, Carlos Martín Sánchez wrote:
So... can you ssh to 127.0.0.1 as oneadmin?
Fri Jun 1 13:13:00 2012 [VMM][I]: Command execution fail: scp -r
/srv/cloud/one3/var/remotes//. 127.0.0.1:/var/tmp/one
Hi Hector,
The tmp directory /var/tmp/one is used by my opennebula 2.2.1 standalone
installation, I changed the tmp path in 3.4.1 setup to /var/tmp/one3 and
gave permissions to oneadmin3 user to write to it.
How do I sync up this folder so that it contains all monitoring scripts
and
restarting opennebula would probably be enough, also you can run 'onehost
sync' and the scripts will be copied in the next monitorization round.
Hector
En Fri, 01 Jun 2012 15:10:43 +0200, Piyush Harsh piyush.ha...@inria.fr
escribió:
Hi Hector,
The tmp directory /var/tmp/one is used by
Hi Hector,
Thank you for your response, now I get new errors, seems qemu dependent:
Fri Jun 1 15:17:48 2012 [DiM][I]: New VM state is ACTIVE.
Fri Jun 1 15:17:48 2012 [LCM][I]: New VM state is PROLOG.
Fri Jun 1 15:17:48 2012 [VM][I]: Virtual Machine has no context
Fri Jun 1 15:20:32 2012
Hi Hector,
I changed the dynamic ownership flag in qemu conf to 0 and now I get a
slightly different type of error
Fri Jun 1 16:34:45 2012 [DiM][I]: New VM state is ACTIVE.
Fri Jun 1 16:34:45 2012 [LCM][I]: New VM state is PROLOG.
Fri Jun 1 16:34:45 2012 [VM][I]: Virtual Machine has no
