Re: [one-users] Run bash script in vm on spin-up
Hello Kerry, I am having the same problem. I think I discovered why your test.sh script doesn't get executed: !!! Opennebula completely disregards the INIT_SCRIPTS=test.sh entry in your CONTEXT=[...] section of the template !!! How to verify? After your VM spins up, login and mount the CONTEXT image like so: mount -t iso9660 /dev/sr0 /mnt Enter /mnt and you will find your test.sh file there. So far so good. There is one more file there - context.sh. You can see that it contains the variables from your CONTEXT=[...] section of the template. You can see that it contains an entry like FILES_DS='...' or FILES='/var/lib/one/datastores/2/test.sh' that mentions your script. HOWEVER, it does NOT contain an entry like INIT_SCRIPTS=test.sh. OK, so now open /etc/one-context.d/99-execute-scripts. That script is responsible for executing your custom scripts. Here it is: #!/bin/bash MOUNT_DIR=/mnt TMP_DIR=/tmp/one-context-tmp if [ -z $INIT_SCRIPTS ]; then if [ -f $MOUNT_DIR/init.sh ]; then INIT_SCRIPTS=init.sh fi fi mkdir -p $TMP_DIR cd $MOUNT_DIR for f in $INIT_SCRIPTS; do cp $f $TMP_DIR chmod +x $TMP_DIR/$f $TMP_DIR/$f done In the beginning it checks to see if there is an environment variableINIT_SCRIPTS defined. It is never defined, no matter whether you put INIT_SCRIPTS=test.sh in your CONTEXT=[...] or not because, as it seems, Opennebula silently disregards it. So, in that case the 99-execute-scripts script continues with the default, which is init.sh. TL; DR; Name your script init.sh and it will be executed. Opennebula devs, please, fix this! P.S.: Kerry, you say: / I have created test.sh and put it into the files datastore on the//head node./ Please, explain how you did it, because I can't seem to find a step-by-step explanation about this in the documentation. Thanks, -- Pavel Tankov On 12.09.2014 02:28, kerryhall . wrote: Hi Valentin, I appreciate the help! I managed to create a new CONTEXT image, which copied my test.sh to the datastore successfully, and I updated my template to include those two lines you specified. However, it looks like test.sh is not executing on vm spin up. Currently all it does is touch /root/test.tmp to confirm execution. However when I booted my vm, this file was not created. Also tried doing useradd tmp as well, with no luck. test.sh has executable flag set for user, group, and other. I also tried setting permissions of test.sh to 777, still no luck. Thanks!! Kerry On Mon, Sep 8, 2014 at 11:27 PM, Valentin Bud valentin@gmail.com mailto:valentin@gmail.com wrote: Hello Kerry, Do you have a registered image of type CONTEXT with the name of `test.sh` in the files datastore? The file you specify in FILES_DS can be found in the contextualization CDROM on the VM (/dev/disk/by-label/CONTEXT). The following would run a `test.sh` script when the VM is spun up at the end of the contextualization routine [1]. CONTEXT = [ FILES_DS=$FILE[IMAGE=\test.sh\], INIT_SCRIPTS=test.sh, ... ] [1]: https://github.com/OpenNebula/addon-context-linux/blob/master/base/etc/one-context.d/99-execute-scripts Best, Valentin On Mon, Sep 8, 2014 at 11:09 PM, kerryhall . kerryh...@gmail.com mailto:kerryh...@gmail.com wrote: Thanks! I'm still having issues here unfortunately. I tried putting: FILES_DS=$FILE[IMAGE=\test.sh\] into my template context section, but I get: User 0 does not own an image with name: test.sh I'm not trying to include an image, I just want test.sh (a file in my file datastore) to get copied to anywhere on my vm's filesystem. (And eventually, I want test.sh to get run on vm creation, or failing that, every time the vm starts) Thanks!! On Fri, Jul 25, 2014 at 11:18 PM, Valentin Bud valentin@gmail.com mailto:valentin@gmail.com wrote: Hello Kerry, Under Defining Context [1] there is an example how to use FILES_DS. FILES_DS=$FILE[IMAGE=\test.sh\] [1]: http://docs.opennebula.org/4.6/user/virtual_machine_setup/cong.html Best, Valentin On Fri, Jul 25, 2014 at 11:29 PM, kerryhall . kerryh...@gmail.com mailto:kerryh...@gmail.com wrote: Hi folks, I am trying to run a bash script on a vm as it gets spun up. I've read: http://docs.opennebula.org/4.6/user/virtual_machine_setup/cong.html but there isn't too much to go on there. I have created test.sh and put it into the files datastore on the head node. The issue I am having is that the syntax in the Defining Context section of http://docs.opennebula.org/4.6/user
Re: [one-users] Run bash script in vm on spin-up
OK, it seems I wasn't right. Opennebula DOES honor the INIT_SCRIPTS entry. I am sorry for blaming you! Why I got confused, though? Well, I was testing with a VM and its template. With every new change that I made to the template I went to the VM (via Sunstone GUI) and chose from the toolbar the button that says Delete recreate, thinking that it will do what it says - namely it will delete the VM and then recreate it. Appears that wasn't quite the case. When I clicked the rightmost red button and chose Delete and then deployed the template again, the changes that I had made to the template actually took effect. Question: Why Delete recreate doesn't do just like when you manually delete the VM and then re-deploy from template? P.S.: Kerry, I discovered how to create CONTEXT files and put them to the files datastore, don't need to answer me. There is a nice menu in Sunstone called Files Kernels which I somehow kept skipping. :) About your problem with test.sh - see if you have fallen in the same trap as me - try to first manually delete the VM and then re-deploy it from template for your changes to take effect. Other than that, all settings work like expected. Thanks, Pavel Tankov On 28.11.2014 12:44, Pavel Tankov wrote: Hello Kerry, I am having the same problem. I think I discovered why your test.sh script doesn't get executed: !!! Opennebula completely disregards the INIT_SCRIPTS=test.sh entry in your CONTEXT=[...] section of the template !!! How to verify? After your VM spins up, login and mount the CONTEXT image like so: mount -t iso9660 /dev/sr0 /mnt Enter /mnt and you will find your test.sh file there. So far so good. There is one more file there - context.sh. You can see that it contains the variables from your CONTEXT=[...] section of the template. You can see that it contains an entry like FILES_DS='...' or FILES='/var/lib/one/datastores/2/test.sh' that mentions your script. HOWEVER, it does NOT contain an entry like INIT_SCRIPTS=test.sh. OK, so now open /etc/one-context.d/99-execute-scripts. That script is responsible for executing your custom scripts. Here it is: #!/bin/bash MOUNT_DIR=/mnt TMP_DIR=/tmp/one-context-tmp if [ -z $INIT_SCRIPTS ]; then if [ -f $MOUNT_DIR/init.sh ]; then INIT_SCRIPTS=init.sh fi fi mkdir -p $TMP_DIR cd $MOUNT_DIR for f in $INIT_SCRIPTS; do cp $f $TMP_DIR chmod +x $TMP_DIR/$f $TMP_DIR/$f done In the beginning it checks to see if there is an environment variableINIT_SCRIPTS defined. It is never defined, no matter whether you put INIT_SCRIPTS=test.sh in your CONTEXT=[...] or not because, as it seems, Opennebula silently disregards it. So, in that case the 99-execute-scripts script continues with the default, which is init.sh. TL; DR; Name your script init.sh and it will be executed. Opennebula devs, please, fix this! P.S.: Kerry, you say: / I have created test.sh and put it into the files datastore on the//head node./ Please, explain how you did it, because I can't seem to find a step-by-step explanation about this in the documentation. Thanks, -- Pavel Tankov On 12.09.2014 02:28, kerryhall . wrote: Hi Valentin, I appreciate the help! I managed to create a new CONTEXT image, which copied my test.sh to the datastore successfully, and I updated my template to include those two lines you specified. However, it looks like test.sh is not executing on vm spin up. Currently all it does is touch /root/test.tmp to confirm execution. However when I booted my vm, this file was not created. Also tried doing useradd tmp as well, with no luck. test.sh has executable flag set for user, group, and other. I also tried setting permissions of test.sh to 777, still no luck. Thanks!! Kerry On Mon, Sep 8, 2014 at 11:27 PM, Valentin Bud valentin@gmail.com mailto:valentin@gmail.com wrote: Hello Kerry, Do you have a registered image of type CONTEXT with the name of `test.sh` in the files datastore? The file you specify in FILES_DS can be found in the contextualization CDROM on the VM (/dev/disk/by-label/CONTEXT). The following would run a `test.sh` script when the VM is spun up at the end of the contextualization routine [1]. CONTEXT = [ FILES_DS=$FILE[IMAGE=\test.sh\], INIT_SCRIPTS=test.sh, ... ] [1]: https://github.com/OpenNebula/addon-context-linux/blob/master/base/etc/one-context.d/99-execute-scripts Best, Valentin On Mon, Sep 8, 2014 at 11:09 PM, kerryhall . kerryh...@gmail.com mailto:kerryh...@gmail.com wrote: Thanks! I'm still having issues here unfortunately. I tried putting: FILES_DS=$FILE[IMAGE=\test.sh\] into my template context section, but I get: User 0 does not own an image with name: test.sh I'm not trying to include an image, I just want test.sh (a file in my file datastore) to get copied to anywhere on my
Re: [one-users] Users can't create VMs with large capacity (in the cloud view)
OK, I understand it now. Then, does Opennebula support any kind of overcommitting or something? Pavel Tankov On 11/03/2014 07:29 PM, Carlos Martín Sánchez wrote: Hi, On Tue, Oct 28, 2014 at 1:06 PM, Pavel Tankov pavel.tan...@strategyobject.com mailto:pavel.tan...@strategyobject.com wrote: Does host 0 have enough capacity? Those numbers refer to the allocated capacity, as can be seen in sunstone or the onehost show output. Well, capacity could mean many things. I am not sure. See the attached screen shot. The hosts have 2 kinds of capacity: real and allocated. Real is the cpu/mem as reported by the monitoring probes. Allocated is the amount of cpu/mem requested by the VMs running on this host. This is the one used for scheduling. In your case, the new VM requests 400 cpu. But the host has already allocated 500 out of 800, this is why the scheduler decides that it doesn't fit. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.OpenNebula.org | cmar...@opennebula.org mailto:cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebulamailto:cmar...@opennebula.org On Tue, Oct 28, 2014 at 1:06 PM, Pavel Tankov pavel.tan...@strategyobject.com mailto:pavel.tan...@strategyobject.com wrote: That's strange. You should have the following message: Sched Message: No host with enough capacity to deploy the VM I understand, but there is nothing there. Absolutely empty. Does host 0 have enough capacity? Those numbers refer to the allocated capacity, as can be seen in sunstone or the onehost show output. Well, capacity could mean many things. I am not sure. See the attached screen shot. Pavel Tankov On 10/28/2014 12:06 PM, Carlos Martín Sánchez wrote: Hi, On Mon, Oct 27, 2014 at 1:17 PM, Pavel Tankov pavel.tankov@strategyobject.__com mailto:pavel.tan...@strategyobject.com mailto:pavel.tankov@__strategyobject.com mailto:pavel.tan...@strategyobject.com wrote: Admins and advanced users can see the scheduler error messages in sunstone, under the placement VM tab. That's what I meant when I said there are no logs. That's strange. You should have the following message: Sched Message: No host with enough capacity to deploy the VM On the other hand, I didn't know about /var/log/one/sched.log. Here is what I found there: Mon Oct 27 14:15:52 2014 [Z0][VM][D]: Pending/rescheduling VM and capacity requirements: VM CPU Memory System DS Image DS --__-- 110 400 2097152 10240 DS 1: 0 Mon Oct 27 14:15:52 2014 [Z0][HOST][D]: Discovered Hosts (enabled): 0 Mon Oct 27 14:15:52 2014 [Z0][SCHED][D]: VM 110: Host 0 filtered out. Not enough capacity. Mon Oct 27 14:15:52 2014 [Z0][SCHED][I]: Scheduling Results: and it keeps repeating. Pavel Tankov Does host 0 have enough capacity? Those numbers refer to the allocated capacity, as can be seen in sunstone or the onehost show output. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org mailto:cmar...@opennebula.org mailto:cmar...@opennebula.org mailto:cmar...@opennebula.org__ | @OpenNebula http://twitter.com/opennebula__mailto:cmartin@opennebula.__org mailto:cmar...@opennebula.org _ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/__listinfo.cgi/users-opennebula.__org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] How to protect a virtual network from being used by users?
That's exactly what I had done. The problem is that users are able to change the network when they instantiate the template. They can add/remove networks at will. Pavel Tankov On 10/27/2014 11:11 PM, Hamada, Ondrej wrote: Hi Pavel, Create two templates - first one uses the public network and all users are allowed to instantiate this template. The second template uses the restricted network and is allowed to be used only by admins. Ondra -Original Message- From: Pavel Tankov [mailto:pavel.tan...@strategyobject.com] Sent: Monday, October 27, 2014 11:16 AM To: Hamada, Ondrej; users@lists.opennebula.org Subject: Re: [one-users] How to protect a virtual network from being used by users? I don't understand what is to solve the network separation on template level. Could you, please, clarify? Pavel Tankov On 10/24/2014 05:18 PM, Hamada, Ondrej wrote: Hi Pavel, Well, I suppose it is the default. I was also struggling with it and finally I had to replace the default ACLs with more strict ones. You can try to solve the network separation on template level if you don't want to play with ACLs. Ondra -Original Message- From: Pavel Tankov [mailto:pavel.tan...@strategyobject.com] Sent: Friday, October 24, 2014 4:01 PM To: Hamada, Ondrej; users@lists.opennebula.org Subject: Re: [one-users] How to protect a virtual network from being used by users? Hello Ondra, You are right, I just saw the ACLs. They are by default created like this: $ oneacl list ID USER RES_VHNIUTGDCOZ RID OPE_UMAC ZONE 0 @1 V-NI-T---O- * ---c#0 1* --Z * u--- * 2 @1 -H- * -m--#0 3 @1 --ND--- * u---#0 (or see the attached screen shot) The group named users is denoted by @1. So, it looks like in the very first ALC (ID 0) the group @1 (users) is granted a CREATE permission on all Virtual Networks (Resource ID *). Which may be OK or not, it depends what you want. But then ACL (ID 3) grants the group @1 (users) the permission to use any Virtual Network (RID *). The ACLs have permissive nature so once granted I can't restrict it with a later rule. I could only re-write the default ACLs completely, which I am not quite willing to try. The documentation says (http://docs.opennebula.org/4.8/administration/users_and_groups/manage_acl.html): Please note: the ACL rules is an advanced mechanism. For most use cases, you should be able to rely on the built-in resource permissions and the ACL Rules created automatically when a group is created, and when a resource provider is added. But it looks like *all* Vritual Networks are meant to be used by *anyone* by default and there is not much I can do about it with the normal means, namely with the resource permissions. Is that so, indeed, or where am I wrong? Pavel Tankov On 10/24/2014 04:33 PM, Hamada, Ondrej wrote: Hi Pavel, Have you checked ACLs as well? I guess that one of the default ACL grants all users the 'use' permission for all 'networks'. Ondra -Original Message- From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of Pavel Tankov Sent: Friday, October 24, 2014 12:09 PM To: users@lists.opennebula.org Subject: [one-users] How to protect a virtual network from being used by users? Hello, I (as oneadmin) have configured two virtual networks: - one named default for use by regular users to deploy disposable test VMs - one named SPECIAL for use by the admin to create servers that will not be disposable but will stay always ON Both networks have different IP ranges so that you could easily tell whether it's a server or a disposable test VM by looking at it's IP address. I have set up Opennebula with LDAP authentication. LDAP users authenticate just fine and are able to create themselves VMs using those templates that the admin has allowed for them. Now, I'd like to make so that only default virtual network is exposed to regular users, and SPECIAL is not seen by them. Currently, both networks have the following permissions: - Owner: use, manage - Group none - Other: none Users still can use both of these when they deploy a test VM although permissions clearly state they shouldn't be able to see any of them. What is wrong with the permissions? -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding
Re: [one-users] Users can't create VMs with large capacity (in the cloud view)
That's strange. You should have the following message: Sched Message: No host with enough capacity to deploy the VM I understand, but there is nothing there. Absolutely empty. Does host 0 have enough capacity? Those numbers refer to the allocated capacity, as can be seen in sunstone or the onehost show output. Well, capacity could mean many things. I am not sure. See the attached screen shot. Pavel Tankov On 10/28/2014 12:06 PM, Carlos Martín Sánchez wrote: Hi, On Mon, Oct 27, 2014 at 1:17 PM, Pavel Tankov pavel.tan...@strategyobject.com mailto:pavel.tan...@strategyobject.com wrote: Admins and advanced users can see the scheduler error messages in sunstone, under the placement VM tab. That's what I meant when I said there are no logs. That's strange. You should have the following message: Sched Message: No host with enough capacity to deploy the VM On the other hand, I didn't know about /var/log/one/sched.log. Here is what I found there: Mon Oct 27 14:15:52 2014 [Z0][VM][D]: Pending/rescheduling VM and capacity requirements: VM CPU Memory System DS Image DS --__-- 110 400 2097152 10240 DS 1: 0 Mon Oct 27 14:15:52 2014 [Z0][HOST][D]: Discovered Hosts (enabled): 0 Mon Oct 27 14:15:52 2014 [Z0][SCHED][D]: VM 110: Host 0 filtered out. Not enough capacity. Mon Oct 27 14:15:52 2014 [Z0][SCHED][I]: Scheduling Results: and it keeps repeating. Pavel Tankov Does host 0 have enough capacity? Those numbers refer to the allocated capacity, as can be seen in sunstone or the onehost show output. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org mailto:cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebulamailto:cmar...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] How to connect to a guest with an external VNC client?
Hello Community, Is it possible to connect to a guest with an external VNC client and how? Thanks! -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] How to connect to a guest with an external VNC client?
Wow, that worked! Sweet! Thank you very much. How come that's nowhere mentioned in the docs... Pavel Tankov On 10/28/2014 03:53 PM, Jose Angel Diaz wrote: It's very easy, locate te node where start the machine (ex. node1) and connect to the IP_node1 and here is the trick: The port for VNC is 5900+VM_Number. Example Instantiate 4 machines (100, 101, 102, 103) on the nodes node1 (100) node2 (101) noder3(100) node4(101) You must connect with your external VNC Client on the node1:6000 for machine 1 You must connect with your external VNC Client on the node2:6001 for machine 2 and so on... ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] How to protect a virtual network from being used by users?
I don't understand what is to solve the network separation on template level. Could you, please, clarify? Pavel Tankov On 10/24/2014 05:18 PM, Hamada, Ondrej wrote: Hi Pavel, Well, I suppose it is the default. I was also struggling with it and finally I had to replace the default ACLs with more strict ones. You can try to solve the network separation on template level if you don't want to play with ACLs. Ondra -Original Message- From: Pavel Tankov [mailto:pavel.tan...@strategyobject.com] Sent: Friday, October 24, 2014 4:01 PM To: Hamada, Ondrej; users@lists.opennebula.org Subject: Re: [one-users] How to protect a virtual network from being used by users? Hello Ondra, You are right, I just saw the ACLs. They are by default created like this: $ oneacl list ID USER RES_VHNIUTGDCOZ RID OPE_UMAC ZONE 0 @1 V-NI-T---O- * ---c#0 1* --Z * u--- * 2 @1 -H- * -m--#0 3 @1 --ND--- * u---#0 (or see the attached screen shot) The group named users is denoted by @1. So, it looks like in the very first ALC (ID 0) the group @1 (users) is granted a CREATE permission on all Virtual Networks (Resource ID *). Which may be OK or not, it depends what you want. But then ACL (ID 3) grants the group @1 (users) the permission to use any Virtual Network (RID *). The ACLs have permissive nature so once granted I can't restrict it with a later rule. I could only re-write the default ACLs completely, which I am not quite willing to try. The documentation says (http://docs.opennebula.org/4.8/administration/users_and_groups/manage_acl.html): Please note: the ACL rules is an advanced mechanism. For most use cases, you should be able to rely on the built-in resource permissions and the ACL Rules created automatically when a group is created, and when a resource provider is added. But it looks like *all* Vritual Networks are meant to be used by *anyone* by default and there is not much I can do about it with the normal means, namely with the resource permissions. Is that so, indeed, or where am I wrong? Pavel Tankov On 10/24/2014 04:33 PM, Hamada, Ondrej wrote: Hi Pavel, Have you checked ACLs as well? I guess that one of the default ACL grants all users the 'use' permission for all 'networks'. Ondra -Original Message- From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of Pavel Tankov Sent: Friday, October 24, 2014 12:09 PM To: users@lists.opennebula.org Subject: [one-users] How to protect a virtual network from being used by users? Hello, I (as oneadmin) have configured two virtual networks: - one named default for use by regular users to deploy disposable test VMs - one named SPECIAL for use by the admin to create servers that will not be disposable but will stay always ON Both networks have different IP ranges so that you could easily tell whether it's a server or a disposable test VM by looking at it's IP address. I have set up Opennebula with LDAP authentication. LDAP users authenticate just fine and are able to create themselves VMs using those templates that the admin has allowed for them. Now, I'd like to make so that only default virtual network is exposed to regular users, and SPECIAL is not seen by them. Currently, both networks have the following permissions: - Owner: use, manage - Group none - Other: none Users still can use both of these when they deploy a test VM although permissions clearly state they shouldn't be able to see any of them. What is wrong with the permissions? -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. ___ Users mailing list Users
Re: [one-users] Users can't create VMs with large capacity (in the cloud view)
Admins and advanced users can see the scheduler error messages in sunstone, under the placement VM tab. That's what I meant when I said there are no logs. On the other hand, I didn't know about /var/log/one/sched.log. Here is what I found there: Mon Oct 27 14:15:52 2014 [Z0][VM][D]: Pending/rescheduling VM and capacity requirements: VM CPU Memory System DS Image DS 110 400 2097152 10240 DS 1: 0 Mon Oct 27 14:15:52 2014 [Z0][HOST][D]: Discovered Hosts (enabled): 0 Mon Oct 27 14:15:52 2014 [Z0][SCHED][D]: VM 110: Host 0 filtered out. Not enough capacity. Mon Oct 27 14:15:52 2014 [Z0][SCHED][I]: Scheduling Results: and it keeps repeating. Pavel Tankov On 10/24/2014 07:21 PM, Carlos Martín Sánchez wrote: Hi Pavel, On Fri, Oct 24, 2014 at 3:49 PM, Pavel Tankov pavel.tan...@strategyobject.com mailto:pavel.tan...@strategyobject.com wrote: Hello, CentOS6.5 - KVM - Opennebula 4.8 My users log in to the cloud view. I have prepared templates for them. They can instantiate VMs with the default capacity, but if they decide to choose anything other than the default, e.g. Change Capacity -- small-x2 or medium-x2 or whatever, the VM never boots up, it stays in PENDING and there are no logs. What could be the problem? Is it some quota that exists by default for regular users? I have not set up restrictions deliberately. Thanks, Pavel Tankov The problem is not the quota, because in that case the users would not be able to even create the VM. When a VM stays in pending, it's because the scheduler can't find where to deploy it. Admins and advanced users can see the scheduler error messages in sunstone, under the placement VM tab. This information is not available to cloud users, since they are not supposed to know about the underlying infrastructure. You will find more detailed information in /var/log/one/sched.log. If the reason is not clear in there, paste the output and we'll try to help deciphering it. Regards. -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org mailto:cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebulamailto:cmar...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] How to protect a virtual network from being used by users?
Hello, I (as oneadmin) have configured two virtual networks: - one named default for use by regular users to deploy disposable test VMs - one named SPECIAL for use by the admin to create servers that will not be disposable but will stay always ON Both networks have different IP ranges so that you could easily tell whether it's a server or a disposable test VM by looking at it's IP address. I have set up Opennebula with LDAP authentication. LDAP users authenticate just fine and are able to create themselves VMs using those templates that the admin has allowed for them. Now, I'd like to make so that only default virtual network is exposed to regular users, and SPECIAL is not seen by them. Currently, both networks have the following permissions: - Owner: use, manage - Group none - Other: none Users still can use both of these when they deploy a test VM although permissions clearly state they shouldn't be able to see any of them. What is wrong with the permissions? -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Users can't create VMs with large capacity (in the cloud view)
Hello, CentOS6.5 - KVM - Opennebula 4.8 My users log in to the cloud view. I have prepared templates for them. They can instantiate VMs with the default capacity, but if they decide to choose anything other than the default, e.g. Change Capacity -- small-x2 or medium-x2 or whatever, the VM never boots up, it stays in PENDING and there are no logs. What could be the problem? Is it some quota that exists by default for regular users? I have not set up restrictions deliberately. Thanks, Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] How to protect a virtual network from being used by users?
Hello Ondra, You are right, I just saw the ACLs. They are by default created like this: $ oneacl list ID USER RES_VHNIUTGDCOZ RID OPE_UMAC ZONE 0 @1 V-NI-T---O- * ---c#0 1* --Z * u--- * 2 @1 -H- * -m--#0 3 @1 --ND--- * u---#0 (or see the attached screen shot) The group named users is denoted by @1. So, it looks like in the very first ALC (ID 0) the group @1 (users) is granted a CREATE permission on all Virtual Networks (Resource ID *). Which may be OK or not, it depends what you want. But then ACL (ID 3) grants the group @1 (users) the permission to use any Virtual Network (RID *). The ACLs have permissive nature so once granted I can't restrict it with a later rule. I could only re-write the default ACLs completely, which I am not quite willing to try. The documentation says (http://docs.opennebula.org/4.8/administration/users_and_groups/manage_acl.html): Please note: the ACL rules is an advanced mechanism. For most use cases, you should be able to rely on the built-in resource permissions and the ACL Rules created automatically when a group is created, and when a resource provider is added. But it looks like *all* Vritual Networks are meant to be used by *anyone* by default and there is not much I can do about it with the normal means, namely with the resource permissions. Is that so, indeed, or where am I wrong? Pavel Tankov On 10/24/2014 04:33 PM, Hamada, Ondrej wrote: Hi Pavel, Have you checked ACLs as well? I guess that one of the default ACL grants all users the 'use' permission for all 'networks'. Ondra -Original Message- From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of Pavel Tankov Sent: Friday, October 24, 2014 12:09 PM To: users@lists.opennebula.org Subject: [one-users] How to protect a virtual network from being used by users? Hello, I (as oneadmin) have configured two virtual networks: - one named default for use by regular users to deploy disposable test VMs - one named SPECIAL for use by the admin to create servers that will not be disposable but will stay always ON Both networks have different IP ranges so that you could easily tell whether it's a server or a disposable test VM by looking at it's IP address. I have set up Opennebula with LDAP authentication. LDAP users authenticate just fine and are able to create themselves VMs using those templates that the admin has allowed for them. Now, I'd like to make so that only default virtual network is exposed to regular users, and SPECIAL is not seen by them. Currently, both networks have the following permissions: - Owner: use, manage - Group none - Other: none Users still can use both of these when they deploy a test VM although permissions clearly state they shouldn't be able to see any of them. What is wrong with the permissions? -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] LDAP Authentication with TLS
OK, I figured it out. For the record: You should be able to use SSL uncommenting the line: :encryption: :simple_tls Well, no. Actually, in order to get it, you should have: :auth_method: :simple AND :encryption: :simple_tls -- Pavel Tankov On 10/17/2014 06:59 PM, Javier Fontan wrote: It seems I've forgot to delete that part from the documentation. Thanks for noticing. You should be able to use SSL uncommenting the line: :encryption: :simple_tls Cheers On Tue, Oct 14, 2014 at 4:47 PM, Pavel Tankov pavel.tan...@strategyobject.com wrote: Hello, I have Opennebula 4.8 and OpenLDAP 2.4.23 on a CentOS 6.5. I followed the doc [1] and succeeded in getting LDAP users to log on the Sunstone UI. Then I made my OpenLDAP accept TLS connections only and can't connect anymore. The documentation [1] says: Considerations Limitations LDAP auth driver has a bug that does not let it connect to TLS LDAP instances. A patch is available in the bug issue [2] to fix this. The fix will be applied in future releases. However, the bug [2] is fixed by Javi Fontan almost 2 years ago. He said in his commit message: I've applied the patch mostly verbatim. Thanks! So, is the documentation for 4.8 wrong or is this limitation still valid now? Thanks! [1] http://docs.opennebula.org/4.8/administration/authentication/ldap.html [2] http://dev.opennebula.org/issues/1171 -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] LDAP Authentication with TLS
Hello, I have Opennebula 4.8 and OpenLDAP 2.4.23 on a CentOS 6.5. I followed the doc [1] and succeeded in getting LDAP users to log on the Sunstone UI. Then I made my OpenLDAP accept TLS connections only and can't connect anymore. The documentation [1] says: Considerations Limitations LDAP auth driver has a bug that does not let it connect to TLS LDAP instances. A patch is available in the bug issue [2] to fix this. The fix will be applied in future releases. However, the bug [2] is fixed by Javi Fontan almost 2 years ago. He said in his commit message: I've applied the patch mostly verbatim. Thanks! So, is the documentation for 4.8 wrong or is this limitation still valid now? Thanks! [1] http://docs.opennebula.org/4.8/administration/authentication/ldap.html [2] http://dev.opennebula.org/issues/1171 -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Cannot create a VM snapshot
opennebula-node package is installed: # rpm -qa | grep opennebula-node opennebula-node-kvm-4.8.0-1.x86_64 The command onehost sync returns this: # onehost sync No hosts are going to be updated. -- Pavel Tankov On 09/30/2014 11:06 AM, Hamada, Ondrej wrote: Maybe you have to run `onehost sync` against that node or install opennebula-node package. O. -Original Message- From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of Pavel Tankov Sent: Tuesday, September 30, 2014 9:03 AM To: users@lists.opennebula.org Subject: Re: [one-users] Cannot create a VM snapshot The 'snapshot_create' script is not available on /var/tmp/one/vmm/kvm/. The contents of this folder is: # ls -l /var/tmp/one/vmm/kvm/ total 32 -rwxr-xr-x 1 oneadmin oneadmin 1596 Aug 20 11:25 cancel -rwxr-xr-x 1 oneadmin oneadmin 1545 Aug 20 11:25 deploy -rw-r--r-- 1 oneadmin oneadmin 1790 Aug 20 11:25 kvmrc -rwxr-xr-x 1 oneadmin oneadmin 14255 Aug 20 11:25 poll -rwxr-xr-x 1 oneadmin oneadmin 2304 Aug 20 11:25 shutdown But isn't this a temporary folder. Is the script expected to be there? On the other hand: # find / -name snapshot_create /var/lib/one/remotes/vmm/sl/snapshot_create /var/lib/one/remotes/vmm/ec2/snapshot_create /var/lib/one/remotes/vmm/kvm/snapshot_create /var/lib/one/remotes/vmm/vmware/snapshot_create /var/lib/one/remotes/vmm/az/snapshot_create /var/lib/one/remotes/vmm/xen3/snapshot_create /var/lib/one/remotes/vmm/xen4/snapshot_create -- Pavel Tankov On 09/28/2014 05:04 PM, Ondrej Hamada wrote: Hi Pavel, this check has failed: if [ -x /var/tmp/one/vmm/kvm/snapshot_create ]; You should check that the 'snapshot_create' script is available on the host in the specified path and that it is executable by oneadmin user. Ondra On 09/24/2014 04:22 PM, Pavel Tankov wrote: Hello, I have Opennebula 4.8 on CentOS 6.5. I have installed from the Marketplace CentOS 7 - KVM - OpenNebula 4.8 I am able to instantiate it and it runs fine. However, when I click on the running VM -- Snapshots -- Take snapshot, It doesn't get created and in the log there is this: --- log begin --- Wed Sep 24 17:13:41 2014 [Z0][DiM][I]: New VM state is ACTIVE. Wed Sep 24 17:13:41 2014 [Z0][LCM][I]: New VM state is PROLOG. Wed Sep 24 17:13:42 2014 [Z0][LCM][I]: New VM state is BOOT Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/61/deployment.0 Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: ExitCode: 0 Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: Successfully execute network driver operation: pre. Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: ExitCode: 0 Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy. Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: ExitCode: 0 Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: Successfully execute network driver operation: post. Wed Sep 24 17:13:43 2014 [Z0][LCM][I]: New VM state is RUNNING Wed Sep 24 17:15:05 2014 [Z0][VMM][I]: Command execution fail: 'if [ -x /var/tmp/one/vmm/kvm/snapshot_create ]; then /var/tmp/one/vmm/kvm/snapshot_create one-61 0 61 localhost; else exit 42; fi' Wed Sep 24 17:15:05 2014 [Z0][VMM][I]: Warning: Permanently added 'localhost' (RSA) to the list of known hosts. Wed Sep 24 17:15:05 2014 [Z0][VMM][I]: ExitCode: 42 Wed Sep 24 17:15:05 2014 [Z0][VMM][E]: Error creating new VM Snapshot --- log end --- Please, note that the image is from the Marketplace and is supposed to be qcow2, e.g. to support snapshots. I tried both with the image set to Persistent: no and Persistent: yes. I tried with both the image set to Type: OS and Type: DATABLOCK. What could be the problem? Thanks! This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org
[one-users] Cannot create a VM snapshot
Hello, I have Opennebula 4.8 on CentOS 6.5. I have installed from the Marketplace CentOS 7 - KVM - OpenNebula 4.8 I am able to instantiate it and it runs fine. However, when I click on the running VM -- Snapshots -- Take snapshot, It doesn't get created and in the log there is this: --- log begin --- Wed Sep 24 17:13:41 2014 [Z0][DiM][I]: New VM state is ACTIVE. Wed Sep 24 17:13:41 2014 [Z0][LCM][I]: New VM state is PROLOG. Wed Sep 24 17:13:42 2014 [Z0][LCM][I]: New VM state is BOOT Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/61/deployment.0 Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: ExitCode: 0 Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: Successfully execute network driver operation: pre. Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: ExitCode: 0 Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy. Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: ExitCode: 0 Wed Sep 24 17:13:42 2014 [Z0][VMM][I]: Successfully execute network driver operation: post. Wed Sep 24 17:13:43 2014 [Z0][LCM][I]: New VM state is RUNNING Wed Sep 24 17:15:05 2014 [Z0][VMM][I]: Command execution fail: 'if [ -x /var/tmp/one/vmm/kvm/snapshot_create ]; then /var/tmp/one/vmm/kvm/snapshot_create one-61 0 61 localhost; else exit 42; fi' Wed Sep 24 17:15:05 2014 [Z0][VMM][I]: Warning: Permanently added 'localhost' (RSA) to the list of known hosts. Wed Sep 24 17:15:05 2014 [Z0][VMM][I]: ExitCode: 42 Wed Sep 24 17:15:05 2014 [Z0][VMM][E]: Error creating new VM Snapshot --- log end --- Please, note that the image is from the Marketplace and is supposed to be qcow2, e.g. to support snapshots. I tried both with the image set to Persistent: no and Persistent: yes. I tried with both the image set to Type: OS and Type: DATABLOCK. What could be the problem? Thanks! -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Where are the CentOS one-context-4.8.0-1.noarch rpm files?
Thank you for the response! I was just about to reply to my thread that I'd found the package and help other people but, fortunately, you were faster. I would have given false information. Anyway, please, see below how I got confused: I wasn't getting a response for a while and thought I was asking a too obvious question, so I went to re-read the documentation once again more carefully. The documentation here: (1) http://docs.opennebula.org/4.8/user/virtual_machine_setup/bcont.html says: Install from our repositories package one-context in Ubuntu/Debian or opennebula-context in CentOS/RedHat. Instructions to add the repository at the installation guide. where installation guide is a hyperlink to (2) http://docs.opennebula.org/4.8/design_and_installation/building_your_cloud/ignc.html#ignc However, (2) explains how to add the opennebula repo for CentOS and the link to the repo is: (3) http://downloads.opennebula.org/repo/4.8/CentOS/6/x86_64. But (3) DOES NOT have the contextualization rpm packages. On the other hand, (1) also says: Download and install the package for your distribution: DEB: Compatible with Ubuntu 11.10 to 14.04 and Debian 6/7 RPM: Compatible with CentOS and RHEL 6/7 where RPM is a hyperlink to (4) http://dev.opennebula.org/attachments/download/804/one-context_4.8.0.rpm which, apparently according to your mail, is not the latest version. Please, fix the documentation in (1) to mention http://dev.opennebula.org/projects/opennebula/files instead. -- Pavel Tankov On 09/23/2014 12:22 PM, Javier Fontan wrote: The images from the marketpace already come with the context packages installed. To download the packages you can go to one of these places: http://dev.opennebula.org/projects/opennebula/files https://github.com/OpenNebula/addon-context-linux/releases/tag/v4.8.1 On Fri, Sep 19, 2014 at 1:49 PM, Pavel Tankov pavel.tan...@strategyobject.com wrote: Hello, I am installing a CentOS 6.5 VM from scratch. I would like, of course, to contextualize it. Where can I download the one-context-4.8.0-1.noarch.rpm from? It is installed by default on a CentOS 6.5 VM that I deploy from the Marketplace. Thank you. -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] CentOS 7 - KVM - OpenNebula 4.8 from Marketplace doesn't start
Much appreciated! Works now. Only there's a message upon boot: Failed to access perfctr msr (MSR c1 is 0) but I suppose that's a pure OS issue. Other than that, it seems to be all OK. Thanks! On 09/02/2014 02:18 PM, Javier Fontan wrote: Hi, I've just uploaded a new version of the image with the correct format. On Tue, Aug 26, 2014 at 11:52 AM, Pavel Tankov pavel.tan...@strategyobject.com wrote: We are going to convert it to a more compatible version and reupload. Hello, guys. Any progress on that? Thanks. On 08/21/2014 04:23 PM, Javier Fontan wrote: We found a problem with the format of that image. It only works with qemu = 1.10. We are going to convert it to a more compatible version and reupload. In case you have a machine with a newer qemu version you can use this command to convert it: $ qemu-img convert -f qcow2 -O qcow2 -o compat=0.10 orig_image dest_image Sorry for the inconveniences. On Thu, Aug 21, 2014 at 10:16 AM, Pavel Tankov pavel.tan...@strategyobject.com wrote: Hello Users, I have the following setup: Physical host: CentOS 6.5 (64 bit, of course), KVM, all set up following the Quickstart Guide here: http://docs.opennebula.org/4.8/design_and_installation/quick_starts/qs_centos_kvm.html Opennebula 4.8.0 I got from the Marketplace the image named CentOS 7 - KVM - OpenNebula 4.8. Imported it and it and created the template automatically for me. I modified the template to add my ssl public key to be able to login as root, added a network and pretty much that was it. I tried to instantiate the template, but the VM keeps getting into the FAILED status. Do you have any idea why it wouldn't start? Thanks in advance. Here is the VM log: BEGIN LOG Wed Jul 30 18:00:53 2014 [DiM][I]: New VM state is ACTIVE. Wed Jul 30 18:00:53 2014 [LCM][I]: New VM state is PROLOG. Wed Jul 30 18:00:56 2014 [LCM][I]: New VM state is BOOT Wed Jul 30 18:00:56 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Wed Jul 30 18:00:56 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:56 2014 [VMM][I]: Successfully execute network driver operation: pre. Wed Jul 30 18:00:57 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:57 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Wed Jul 30 18:00:57 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:57 2014 [VMM][I]: Successfully execute network driver operation: post. Wed Jul 30 18:00:57 2014 [LCM][I]: New VM state is RUNNING Thu Jul 31 14:03:18 2014 [LCM][I]: New VM state is SHUTDOWN Thu Jul 31 14:03:51 2014 [VMM][I]: ExitCode: 0 Thu Jul 31 14:03:51 2014 [VMM][I]: Successfully execute virtualization driver operation: shutdown. Thu Jul 31 14:03:51 2014 [VMM][I]: ExitCode: 0 Thu Jul 31 14:03:51 2014 [VMM][I]: Successfully execute network driver operation: clean. Thu Jul 31 14:03:51 2014 [LCM][I]: New VM state is EPILOG Thu Jul 31 14:03:51 2014 [DiM][I]: New VM state is DONE Thu Aug 7 12:09:20 2014 [DiM][I]: New VM state is ACTIVE. Thu Aug 7 12:09:20 2014 [LCM][I]: New VM state is PROLOG. Thu Aug 7 12:09:21 2014 [LCM][I]: New VM state is BOOT Thu Aug 7 12:09:21 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Thu Aug 7 12:09:21 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:21 2014 [VMM][I]: Successfully execute network driver operation: pre. Thu Aug 7 12:09:22 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:22 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Thu Aug 7 12:09:22 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:22 2014 [VMM][I]: Successfully execute network driver operation: post. Thu Aug 7 12:09:22 2014 [LCM][I]: New VM state is RUNNING Thu Aug 7 12:24:05 2014 [LCM][I]: New VM state is SHUTDOWN Thu Aug 7 12:24:15 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:24:15 2014 [VMM][I]: Successfully execute virtualization driver operation: shutdown. Thu Aug 7 12:24:15 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:24:15 2014 [VMM][I]: Successfully execute network driver operation: clean. Thu Aug 7 12:24:15 2014 [LCM][I]: New VM state is EPILOG Thu Aug 7 12:24:16 2014 [DiM][I]: New VM state is DONE Tue Aug 19 16:03:52 2014 [DiM][I]: New VM state is ACTIVE. Tue Aug 19 16:03:52 2014 [LCM][I]: New VM state is PROLOG. Tue Aug 19 16:03:53 2014 [LCM][I]: New VM state is BOOT Tue Aug 19 16:03:53 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute network driver operation: pre. Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute network driver operation: post. Tue Aug 19 16:03:53 2014 [LCM][I]: New VM state is RUNNING Tue Aug 19 16:05:37 2014 [LCM][I]: New VM state is CLEANUP. Tue Aug 19 16:05:37 2014 [DiM][I]: New VM state
Re: [one-users] CentOS 7 - KVM - OpenNebula 4.8 from Marketplace doesn't start
We are going to convert it to a more compatible version and reupload. Hello, guys. Any progress on that? Thanks. On 08/21/2014 04:23 PM, Javier Fontan wrote: We found a problem with the format of that image. It only works with qemu = 1.10. We are going to convert it to a more compatible version and reupload. In case you have a machine with a newer qemu version you can use this command to convert it: $ qemu-img convert -f qcow2 -O qcow2 -o compat=0.10 orig_image dest_image Sorry for the inconveniences. On Thu, Aug 21, 2014 at 10:16 AM, Pavel Tankov pavel.tan...@strategyobject.com wrote: Hello Users, I have the following setup: Physical host: CentOS 6.5 (64 bit, of course), KVM, all set up following the Quickstart Guide here: http://docs.opennebula.org/4.8/design_and_installation/quick_starts/qs_centos_kvm.html Opennebula 4.8.0 I got from the Marketplace the image named CentOS 7 - KVM - OpenNebula 4.8. Imported it and it and created the template automatically for me. I modified the template to add my ssl public key to be able to login as root, added a network and pretty much that was it. I tried to instantiate the template, but the VM keeps getting into the FAILED status. Do you have any idea why it wouldn't start? Thanks in advance. Here is the VM log: BEGIN LOG Wed Jul 30 18:00:53 2014 [DiM][I]: New VM state is ACTIVE. Wed Jul 30 18:00:53 2014 [LCM][I]: New VM state is PROLOG. Wed Jul 30 18:00:56 2014 [LCM][I]: New VM state is BOOT Wed Jul 30 18:00:56 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Wed Jul 30 18:00:56 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:56 2014 [VMM][I]: Successfully execute network driver operation: pre. Wed Jul 30 18:00:57 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:57 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Wed Jul 30 18:00:57 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:57 2014 [VMM][I]: Successfully execute network driver operation: post. Wed Jul 30 18:00:57 2014 [LCM][I]: New VM state is RUNNING Thu Jul 31 14:03:18 2014 [LCM][I]: New VM state is SHUTDOWN Thu Jul 31 14:03:51 2014 [VMM][I]: ExitCode: 0 Thu Jul 31 14:03:51 2014 [VMM][I]: Successfully execute virtualization driver operation: shutdown. Thu Jul 31 14:03:51 2014 [VMM][I]: ExitCode: 0 Thu Jul 31 14:03:51 2014 [VMM][I]: Successfully execute network driver operation: clean. Thu Jul 31 14:03:51 2014 [LCM][I]: New VM state is EPILOG Thu Jul 31 14:03:51 2014 [DiM][I]: New VM state is DONE Thu Aug 7 12:09:20 2014 [DiM][I]: New VM state is ACTIVE. Thu Aug 7 12:09:20 2014 [LCM][I]: New VM state is PROLOG. Thu Aug 7 12:09:21 2014 [LCM][I]: New VM state is BOOT Thu Aug 7 12:09:21 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Thu Aug 7 12:09:21 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:21 2014 [VMM][I]: Successfully execute network driver operation: pre. Thu Aug 7 12:09:22 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:22 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Thu Aug 7 12:09:22 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:22 2014 [VMM][I]: Successfully execute network driver operation: post. Thu Aug 7 12:09:22 2014 [LCM][I]: New VM state is RUNNING Thu Aug 7 12:24:05 2014 [LCM][I]: New VM state is SHUTDOWN Thu Aug 7 12:24:15 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:24:15 2014 [VMM][I]: Successfully execute virtualization driver operation: shutdown. Thu Aug 7 12:24:15 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:24:15 2014 [VMM][I]: Successfully execute network driver operation: clean. Thu Aug 7 12:24:15 2014 [LCM][I]: New VM state is EPILOG Thu Aug 7 12:24:16 2014 [DiM][I]: New VM state is DONE Tue Aug 19 16:03:52 2014 [DiM][I]: New VM state is ACTIVE. Tue Aug 19 16:03:52 2014 [LCM][I]: New VM state is PROLOG. Tue Aug 19 16:03:53 2014 [LCM][I]: New VM state is BOOT Tue Aug 19 16:03:53 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute network driver operation: pre. Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute network driver operation: post. Tue Aug 19 16:03:53 2014 [LCM][I]: New VM state is RUNNING Tue Aug 19 16:05:37 2014 [LCM][I]: New VM state is CLEANUP. Tue Aug 19 16:05:37 2014 [DiM][I]: New VM state is DONE Tue Aug 19 16:05:37 2014 [VMM][W]: Ignored: LOG I 9 Driver command for 9 cancelled Tue Aug 19 16:05:38 2014 [VMM][W]: Ignored: LOG I 9 error: failed to get domain 'one-9' Tue Aug 19 16:05:38 2014 [VMM][W]: Ignored: LOG I 9 error: Domain not found: no domain with matching name 'one-9' Tue Aug 19 16:05:38 2014 [VMM][W]: Ignored: LOG I 9 ExitCode: 0 Tue Aug 19 16:05:38 2014
[one-users] CentOS 7 - KVM - OpenNebula 4.8 from Marketplace doesn't start
operation: tm_delete. Tue Aug 19 16:05:38 2014 [VMM][W]: Ignored: CLEANUP SUCCESS 9 Thu Aug 21 10:59:24 2014 [Z0][DiM][I]: New VM state is ACTIVE. Thu Aug 21 10:59:24 2014 [Z0][LCM][I]: New VM state is PROLOG. Thu Aug 21 10:59:25 2014 [Z0][LCM][I]: New VM state is BOOT Thu Aug 21 10:59:25 2014 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Thu Aug 21 10:59:25 2014 [Z0][VMM][I]: ExitCode: 0 Thu Aug 21 10:59:25 2014 [Z0][VMM][I]: Successfully execute network driver operation: pre. Thu Aug 21 10:59:26 2014 [Z0][VMM][I]: Command execution fail: cat EOT | /var/tmp/one/vmm/kvm/deploy '/var/lib/one//datastores/0/9/deployment.0' 'localhost' 9 localhost Thu Aug 21 10:59:26 2014 [Z0][VMM][I]: error: Failed to create domain from /var/lib/one//datastores/0/9/deployment.0 Thu Aug 21 10:59:26 2014 [Z0][VMM][I]: error: internal error process exited while connecting to monitor: qemu-kvm: -drive file=/var/lib/one//datastores/0/9/disk.0,if=none,id=drive-ide0-0-0,format=qcow2,cache=none: 'drive-ide0-0-0' uses a qcow2 feature which is not supported by this qemu version: QCOW version 3 Thu Aug 21 10:59:26 2014 [Z0][VMM][I]: qemu-kvm: -drive file=/var/lib/one//datastores/0/9/disk.0,if=none,id=drive-ide0-0-0,format=qcow2,cache=none: could not open disk image /var/lib/one//datastores/0/9/disk.0: Operation not supported Thu Aug 21 10:59:26 2014 [Z0][VMM][I]: Thu Aug 21 10:59:26 2014 [Z0][VMM][E]: Could not create domain from /var/lib/one//datastores/0/9/deployment.0 Thu Aug 21 10:59:26 2014 [Z0][VMM][I]: ExitCode: 255 Thu Aug 21 10:59:26 2014 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy. Thu Aug 21 10:59:26 2014 [Z0][VMM][E]: Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/0/9/deployment.0 Thu Aug 21 10:59:26 2014 [Z0][DiM][I]: New VM state is FAILED === END LOG = -- Pavel Tankov ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
