[one-users] issue with connection from C to OpenNebula
Hello
Here is my code:
string const serverUrl("http://IP:2633/RPC2;);
string const methodName("one.user.info");
xmlrpc_c::clientSimple myClient;
xmlrpc_c::value result;
myClient.call(serverUrl, methodName, "ss", ,
"oneadmin","one_admin_pass");
in oned.log : i'm getting:
Tue Jun 7 10:15:56 2016 [Z0][ReM][D]: Req:1120 UID:0 UserInfo invoked , "
one_admin_pass "
Tue Jun 7 10:15:56 2016 [Z0][ReM][E]: Req:1120 UID:0 UserInfo result
FAILURE [UserInfo] User couldn't be authenticated, aborting call.
Any one have example code ? or can any one help with it ? how pass to server
RPC2 login and password from C ?
Thx
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Issue with Gluster DataStore
Hi, What is the content of /var/lib/one//datastores/0/53/deployment.0. Can you also post the settigns of the Gluster Datastore. Vincent On 2014-12-09 04:16, Alexey Shalin wrote: Hello I added Gluster DS via docs: http://docs.opennebula.org/4.6/administration/storage/gluster_ds.html#glusterfs-volume-configuration It's attached without any issues, but when i tried start VM i got error: Mon Dec 8 09:25:47 2014 [VMM][I]: error: Failed to create domain from /var/lib/one//datastores/0/53/deployment.0 Mon Dec 8 09:25:47 2014 [VMM][I]: error: internal error unknown protocol type 'gluster' on node3 .. gluster volume already mounted --- node1:/opennebula 280G 14G 266G 5% /var/lib/one --- Can you please help me to resolve this issue ? --- Старший Системный Администратор Алексей Шалин ОсОО Хостер kg - http://www.hoster.kg ул. Ахунбаева 123 (здание БГТС) h...@hoster.kg ___ 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] Issue with Gluster DataStore
Hello I added Gluster DS via docs: http://docs.opennebula.org/4.6/administration/storage/gluster_ds.html#glusterfs-volume-configuration It's attached without any issues, but when i tried start VM i got error: Mon Dec 8 09:25:47 2014 [VMM][I]: error: Failed to create domain from /var/lib/one//datastores/0/53/deployment.0 Mon Dec 8 09:25:47 2014 [VMM][I]: error: internal error unknown protocol type 'gluster' on node3 .. gluster volume already mounted --- node1:/opennebula 280G 14G 266G 5% /var/lib/one --- Can you please help me to resolve this issue ? --- Старший Системный Администратор Алексей Шалин ОсОО Хостер kg - http://www.hoster.kg ул. Ахунбаева 123 (здание БГТС) h...@hoster.kg ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Issue with adding CDROM and boot it
Hello I set up a cluster of 3 nodes Opennebula and NFS. deployment.0 domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' nameone-38/name cputune shares1024/shares /cputune memory1048576/memory os type arch='x86_64'hvm/type boot dev='cdrom'/ /os devices emulator/usr/bin/kvm/emulator disk type='file' device='cdrom' source file='/var/lib/one//datastores/0/38/disk.0'/ target dev='hda'/ readonly/ driver name='qemu' type='raw' cache='none'/ /disk disk type='file' device='cdrom' source file='/var/lib/one//datastores/0/38/disk.1'/ target dev='hdb'/ readonly/ driver name='qemu' type='raw'/ /disk interface type='bridge' source bridge='br0'/ mac address='02:00:b0:7e:a5:86'/ /interface graphics type='vnc' listen='0.0.0.0' port='5938'/ /devices features acpi/ /features /domain /var/lib/one//datastores/0/38/disk.0 - points to iso file I do not know, why in deployment.0 having 2 cdroms, in the template only 1 disk added because of it .. i can not boot VM via CDROM --- Старший Системный Администратор Алексей Шалин ОсОО Хостер kg - http://www.hoster.kg ул. Ахунбаева 123 (здание БГТС) h...@hoster.kg ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Issue with adding CDROM and boot it
Alexey Shalin c...@hoster.kg writes: Hello I set up a cluster of 3 nodes Opennebula and NFS. [...] /var/lib/one//datastores/0/38/disk.0 - points to iso file I do not know, why in deployment.0 having 2 cdroms, in the template only 1 disk added because of it .. i can not boot VM via CDROM The second CDROM is CONTEXT. We report an issue[1] to avoid adding TARGET=hda on boot ISO. Regards. Footnotes: [1] http://dev.opennebula.org/issues/3158 -- Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF signature.asc Description: PGP signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Issue with Cloud View
Hi Daniel, I was going to ask you if we can add this ability in Sunstone, However as you informed that it going to be in next release then I will get my hands dirty when it is released :) Thanks Kiran Ranjane On Fri, Feb 21, 2014 at 3:37 PM, Daniel Molina dmol...@opennebula.orgwrote: Hi Kiran, The problem is how you define the view for the new group. In the sunstone-views.yaml you can define views in three different ways, per user, per group and the default one; and they will be selected in that order: https://github.com/OpenNebula/one/blob/master/src/sunstone/models/SunstoneViews.rb#L51 Therefore you have three sections in the sunstone-view.yaml: groups: users: default: inside the groups and users section you can define more than one user or group groups: developers: testers: users: dev_admin: dev_user: and inside each user, group or default key you have to add the views available: groups: developers: - admin testers: - cloud users: dev_admin: - admin dev_user: - user default: - user Hope this helps. We are changing this behaviour for the next release, and you will be able to assign views from sunstone when you create a new group or user. Cheers On 18 February 2014 16:57, kiran ranjane kiran.ranj...@gmail.com wrote: Hi Everyone, It seems that the document is not updated or I am missing something while configuring Cloud View in Sunstone. I followed this link to setup cloud view and it do not work, there are few things missing on the document http://docs.opennebula.org/stable/administration/sunstone_gui/cloud_view.html If I open the file sunstone-views.yaml, there seems to be a group called as default and it that the user view. When I create a new group and give that view cloud view in the above file, then restart sunstone, create new user and add that user to the new group created and login with the new user By Default it goes to USER VIEW Example of the entry groups: oneadmin: - admin - vdcadmin - user - cloud default: - user clouduser - cloud Now when I remove -user from the default view and add cloud in there and then login with the new user it goes to cloud view. -- I have added the new user to clouduser group and removed user group from new user, restarted sunstone and still it goes to user view. I tried above document 2 twice and it seems that there is something missing in the document and something has changed between 4.0 to 4.4 version. Thanks and Regards Kiran Ranjane ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- -- Daniel Molina Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Issue with Cloud View
Hi Everyone, It seems that the document is not updated or I am missing something while configuring Cloud View in Sunstone. I followed this link to setup cloud view and it do not work, there are few things missing on the document http://docs.opennebula.org/stable/administration/sunstone_gui/cloud_view.html If I open the file sunstone-views.yaml, there seems to be a group called as default and it that the user view. When I create a new group and give that view cloud view in the above file, then restart sunstone, create new user and add that user to the new group created and login with the new user By Default it goes to USER VIEW Example of the entry groups: oneadmin: - admin - vdcadmin - user - cloud default: - user clouduser - cloud Now when I remove -user from the default view and add cloud in there and then login with the new user it goes to cloud view. -- I have added the new user to clouduser group and removed user group from new user, restarted sunstone and still it goes to user view. I tried above document 2 twice and it seems that there is something missing in the document and something has changed between 4.0 to 4.4 version. Thanks and Regards Kiran Ranjane ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Issue with picking up proper ulimits during contextualization
Hi Richard, did you manage to get it working? regards, Jaime On Fri, Jul 26, 2013 at 3:00 PM, Jon three1...@gmail.com wrote: Hello Richard, What you are running into is the difference between an interactive shell (e.g. an ssh session) and a non-interactive shell (e.g. a startup shell). [Depending on the distro] A default profile will check if your shell is interactive, and if so, load bashrc. From the first line of my /etc/profile (ubuntu 13.04): if [ $PS1 ]; then So when your context script is executed, your .bashrc is never loaded. In the past, I've had trouble with upstart jobs not starting Catalyst websites properly because the environment variables weren't being loaded. The solution there was to use sudo instead of sudo: Instead of su foo -l -c starman /some/app.psgi I used: sudo -u foo -i starman /some/app.psgi Also, I recently ran into something similar in my day job, where I was attempting to execute a script over ssh: ssh root@hostname sudo somescript.pl The problem I was running into was the environment variables were not being loaded (because the shell detected it was running non-interactively), so I invoked bash directly, which loaded the environment variables, so my ssh command became: ssh -t x0319t62 '/usr/bin/bash -l -c /usr/local/bin/sudo -u foo /path/to/somescript.pl ' As Tino said, adding your directives to /etc/profile would cause them to be loaded whenever someone logs in. Based on your e-mail, I don't think that's exactly what you are looking for (correct me if I'm wrong), so I think one of the above solutions might work for you. e.g.: Instead of: su tomcatA -l -c /var/jakarta-tomcatA/bin/startup.sh try: sudo -u tomcatA -i /var/jakarta-tomcatA/bin/startup.sh or: bash -l -c 'sudo tomcatA -l /var/jakarta-tomcatA/bin/startup.sh' Anyway, hope that helps. Best Regards, Jon A On Fri, Jul 26, 2013 at 11:43 AM, Richard Bettridge rbettri...@blackberry.com wrote: I'll give it a shot, still a little confused about why it doesn't work in the contextualization's shell but works with an ssh login. Kind of new at this stuff. Richard -Original Message- From: Tino Vazquez [mailto:cvazq...@c12g.com] Sent: Friday, July 26, 2013 12:40 PM To: Richard Bettridge Cc: users@lists.opennebula.org Subject: Re: [one-users] Issue with picking up proper ulimits during contextualization Hi Richard, Reading .bashrc with 'su' (even with -l) can be sometimes a difficult task. Any chance of setting it in /etc/profile? Regards, -Tino -- Constantino Vázquez Blanco, PhD, MSc Senior Infrastructure Architect at C12G Labs www.c12g.com | @C12G | es.linkedin.com/in/tinova -- Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the To and cc box). They are the property of C12G Labs S.L.. Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On Fri, Jul 26, 2013 at 5:11 PM, Richard Bettridge rbettri...@blackberry.com wrote: Hey, I'm having an issue where the ulimit for open files isn't being set properly when I spin up a process for a user during contextualization. Upon start up of the non-persistent ubuntu 12 image, I am setting limits.conf to what I want and I'm explicitly adding ulimit -n 65536 to the user's .bashrc. However at the end of my 90_tomcat script when I execute the tomcat process the ulimit is not being picked up and is set to 1024 instead As a test in my 90_tomcat script I'm running ulimit -a /tmp/tomcatsu.txt root@host002:/mnt# cat 90_tomcat |grep su tomcatA su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt So this gets run at the end of 90_tomcat: su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt su tomcatA -l -c /var/jakarta-tomcatA/bin/startup.sh When I cat the txt file it says 1024: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 1024 But when I log in manually as root and run /mnt/90_tomcat by hand I end up getting the proper ulimit: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 65536 Not sure what the issue but I'd appreciate any input. Thanks, Richard Bettridge Systems Engineering Specialist BlackBerry - This transmission (including any attachments) may
Re: [one-users] Issue with picking up proper ulimits during contextualization
Thanks, I did try sudo with those args instead of su with no luck. I also put the ulimit in /etc/profile outside of the if statements all together with no luck. Pretty confused, possible I'm over looking something obvious. In the mean time my colleague added ulimits in init.sh of our contextualization and that seems to have actually worked. Not sure if I like that as a solution permanently however. I think I should continue to do some investigation, I'll mess around in one of our labs and see if I can document the changes and results for each suggestion. Thanks, Richard From: users-boun...@lists.opennebula.org [mailto:users-boun...@lists.opennebula.org] On Behalf Of Jaime Melis Sent: Monday, July 29, 2013 9:30 AM To: Jon Cc: users@lists.opennebula.org Subject: Re: [one-users] Issue with picking up proper ulimits during contextualization Hi Richard, did you manage to get it working? regards, Jaime On Fri, Jul 26, 2013 at 3:00 PM, Jon three1...@gmail.commailto:three1...@gmail.com wrote: Hello Richard, What you are running into is the difference between an interactive shell (e.g. an ssh session) and a non-interactive shell (e.g. a startup shell). [Depending on the distro] A default profile will check if your shell is interactive, and if so, load bashrc. From the first line of my /etc/profile (ubuntu 13.04): if [ $PS1 ]; then So when your context script is executed, your .bashrc is never loaded. In the past, I've had trouble with upstart jobs not starting Catalyst websites properly because the environment variables weren't being loaded. The solution there was to use sudo instead of sudo: Instead of su foo -l -c starman /some/app.psgi I used: sudo -u foo -i starman /some/app.psgi Also, I recently ran into something similar in my day job, where I was attempting to execute a script over ssh: ssh root@hostname sudo somescript.plhttp://somescript.pl The problem I was running into was the environment variables were not being loaded (because the shell detected it was running non-interactively), so I invoked bash directly, which loaded the environment variables, so my ssh command became: ssh -t x0319t62 '/usr/bin/bash -l -c /usr/local/bin/sudo -u foo /path/to/somescript.plhttp://somescript.pl ' As Tino said, adding your directives to /etc/profile would cause them to be loaded whenever someone logs in. Based on your e-mail, I don't think that's exactly what you are looking for (correct me if I'm wrong), so I think one of the above solutions might work for you. e.g.: Instead of: su tomcatA -l -c /var/jakarta-tomcatA/bin/startup.sh try: sudo -u tomcatA -i /var/jakarta-tomcatA/bin/startup.sh or: bash -l -c 'sudo tomcatA -l /var/jakarta-tomcatA/bin/startup.sh' Anyway, hope that helps. Best Regards, Jon A On Fri, Jul 26, 2013 at 11:43 AM, Richard Bettridge rbettri...@blackberry.commailto:rbettri...@blackberry.com wrote: I'll give it a shot, still a little confused about why it doesn't work in the contextualization's shell but works with an ssh login. Kind of new at this stuff. Richard -Original Message- From: Tino Vazquez [mailto:cvazq...@c12g.commailto:cvazq...@c12g.com] Sent: Friday, July 26, 2013 12:40 PM To: Richard Bettridge Cc: users@lists.opennebula.orgmailto:users@lists.opennebula.org Subject: Re: [one-users] Issue with picking up proper ulimits during contextualization Hi Richard, Reading .bashrc with 'su' (even with -l) can be sometimes a difficult task. Any chance of setting it in /etc/profile? Regards, -Tino -- Constantino Vázquez Blanco, PhD, MSc Senior Infrastructure Architect at C12G Labs www.c12g.comhttp://www.c12g.com | @C12G | es.linkedin.com/in/tinovahttp://es.linkedin.com/in/tinova -- Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the To and cc box). They are the property of C12G Labs S.L.. Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at ab...@c12g.commailto:ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On Fri, Jul 26, 2013 at 5:11 PM, Richard Bettridge rbettri...@blackberry.commailto:rbettri...@blackberry.com wrote: Hey, I'm having an issue where the ulimit for open files isn't being set properly when I spin up a process for a user during contextualization. Upon start up of the non-persistent ubuntu 12 image, I am setting limits.conf to what I want and I'm explicitly adding ulimit -n 65536 to the user's .bashrc. However at the end of my 90_tomcat script when I execute the tomcat process the ulimit is not being picked up
[one-users] Issue with picking up proper ulimits during contextualization
Hey, I'm having an issue where the ulimit for open files isn't being set properly when I spin up a process for a user during contextualization. Upon start up of the non-persistent ubuntu 12 image, I am setting limits.conf to what I want and I'm explicitly adding ulimit -n 65536 to the user's .bashrc. However at the end of my 90_tomcat script when I execute the tomcat process the ulimit is not being picked up and is set to 1024 instead As a test in my 90_tomcat script I'm running ulimit -a /tmp/tomcatsu.txt root@host002:/mnt# cat 90_tomcat |grep su tomcatA su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt So this gets run at the end of 90_tomcat: su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt su tomcatA -l -c /var/jakarta-tomcatA/bin/startup.sh When I cat the txt file it says 1024: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 1024 But when I log in manually as root and run /mnt/90_tomcat by hand I end up getting the proper ulimit: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 65536 Not sure what the issue but I'd appreciate any input. Thanks, Richard Bettridge Systems Engineering Specialist BlackBerry - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Issue with picking up proper ulimits during contextualization
Hi Richard, Reading .bashrc with 'su' (even with -l) can be sometimes a difficult task. Any chance of setting it in /etc/profile? Regards, -Tino -- Constantino Vázquez Blanco, PhD, MSc Senior Infrastructure Architect at C12G Labs www.c12g.com | @C12G | es.linkedin.com/in/tinova -- Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the To and cc box). They are the property of C12G Labs S.L.. Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On Fri, Jul 26, 2013 at 5:11 PM, Richard Bettridge rbettri...@blackberry.com wrote: Hey, I’m having an issue where the ulimit for open files isn’t being set properly when I spin up a process for a user during contextualization. Upon start up of the non-persistent ubuntu 12 image, I am setting limits.conf to what I want and I’m explicitly adding ulimit –n 65536 to the user’s .bashrc. However at the end of my 90_tomcat script when I execute the tomcat process the ulimit is not being picked up and is set to 1024 instead As a test in my 90_tomcat script I’m running ulimit –a /tmp/tomcatsu.txt root@host002:/mnt# cat 90_tomcat |grep su tomcatA su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt So this gets run at the end of 90_tomcat: su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt su tomcatA -l -c /var/jakarta-tomcatA/bin/startup.sh When I cat the txt file it says 1024: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 1024 But when I log in manually as root and run /mnt/90_tomcat by hand I end up getting the proper ulimit: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 65536 Not sure what the issue but I’d appreciate any input. Thanks, Richard Bettridge Systems Engineering Specialist BlackBerry - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ 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] Issue with picking up proper ulimits during contextualization
I'll give it a shot, still a little confused about why it doesn't work in the contextualization's shell but works with an ssh login. Kind of new at this stuff. Richard -Original Message- From: Tino Vazquez [mailto:cvazq...@c12g.com] Sent: Friday, July 26, 2013 12:40 PM To: Richard Bettridge Cc: users@lists.opennebula.org Subject: Re: [one-users] Issue with picking up proper ulimits during contextualization Hi Richard, Reading .bashrc with 'su' (even with -l) can be sometimes a difficult task. Any chance of setting it in /etc/profile? Regards, -Tino -- Constantino Vázquez Blanco, PhD, MSc Senior Infrastructure Architect at C12G Labs www.c12g.com | @C12G | es.linkedin.com/in/tinova -- Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the To and cc box). They are the property of C12G Labs S.L.. Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On Fri, Jul 26, 2013 at 5:11 PM, Richard Bettridge rbettri...@blackberry.com wrote: Hey, I'm having an issue where the ulimit for open files isn't being set properly when I spin up a process for a user during contextualization. Upon start up of the non-persistent ubuntu 12 image, I am setting limits.conf to what I want and I'm explicitly adding ulimit -n 65536 to the user's .bashrc. However at the end of my 90_tomcat script when I execute the tomcat process the ulimit is not being picked up and is set to 1024 instead As a test in my 90_tomcat script I'm running ulimit -a /tmp/tomcatsu.txt root@host002:/mnt# cat 90_tomcat |grep su tomcatA su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt So this gets run at the end of 90_tomcat: su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt su tomcatA -l -c /var/jakarta-tomcatA/bin/startup.sh When I cat the txt file it says 1024: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 1024 But when I log in manually as root and run /mnt/90_tomcat by hand I end up getting the proper ulimit: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 65536 Not sure what the issue but I'd appreciate any input. Thanks, Richard Bettridge Systems Engineering Specialist BlackBerry - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Issue with picking up proper ulimits during contextualization
Hello Richard, What you are running into is the difference between an interactive shell (e.g. an ssh session) and a non-interactive shell (e.g. a startup shell). [Depending on the distro] A default profile will check if your shell is interactive, and if so, load bashrc. From the first line of my /etc/profile (ubuntu 13.04): if [ $PS1 ]; then So when your context script is executed, your .bashrc is never loaded. In the past, I've had trouble with upstart jobs not starting Catalyst websites properly because the environment variables weren't being loaded. The solution there was to use sudo instead of sudo: Instead of su foo -l -c starman /some/app.psgi I used: sudo -u foo -i starman /some/app.psgi Also, I recently ran into something similar in my day job, where I was attempting to execute a script over ssh: ssh root@hostname sudo somescript.pl The problem I was running into was the environment variables were not being loaded (because the shell detected it was running non-interactively), so I invoked bash directly, which loaded the environment variables, so my ssh command became: ssh -t x0319t62 '/usr/bin/bash -l -c /usr/local/bin/sudo -u foo /path/to/somescript.pl ' As Tino said, adding your directives to /etc/profile would cause them to be loaded whenever someone logs in. Based on your e-mail, I don't think that's exactly what you are looking for (correct me if I'm wrong), so I think one of the above solutions might work for you. e.g.: Instead of: su tomcatA -l -c /var/jakarta-tomcatA/bin/startup.sh try: sudo -u tomcatA -i /var/jakarta-tomcatA/bin/startup.sh or: bash -l -c 'sudo tomcatA -l /var/jakarta-tomcatA/bin/startup.sh' Anyway, hope that helps. Best Regards, Jon A On Fri, Jul 26, 2013 at 11:43 AM, Richard Bettridge rbettri...@blackberry.com wrote: I'll give it a shot, still a little confused about why it doesn't work in the contextualization's shell but works with an ssh login. Kind of new at this stuff. Richard -Original Message- From: Tino Vazquez [mailto:cvazq...@c12g.com] Sent: Friday, July 26, 2013 12:40 PM To: Richard Bettridge Cc: users@lists.opennebula.org Subject: Re: [one-users] Issue with picking up proper ulimits during contextualization Hi Richard, Reading .bashrc with 'su' (even with -l) can be sometimes a difficult task. Any chance of setting it in /etc/profile? Regards, -Tino -- Constantino Vázquez Blanco, PhD, MSc Senior Infrastructure Architect at C12G Labs www.c12g.com | @C12G | es.linkedin.com/in/tinova -- Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the To and cc box). They are the property of C12G Labs S.L.. Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. On Fri, Jul 26, 2013 at 5:11 PM, Richard Bettridge rbettri...@blackberry.com wrote: Hey, I'm having an issue where the ulimit for open files isn't being set properly when I spin up a process for a user during contextualization. Upon start up of the non-persistent ubuntu 12 image, I am setting limits.conf to what I want and I'm explicitly adding ulimit -n 65536 to the user's .bashrc. However at the end of my 90_tomcat script when I execute the tomcat process the ulimit is not being picked up and is set to 1024 instead As a test in my 90_tomcat script I'm running ulimit -a /tmp/tomcatsu.txt root@host002:/mnt# cat 90_tomcat |grep su tomcatA su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt So this gets run at the end of 90_tomcat: su tomcatA -l -c ulimit -a /tmp/tomcatsu.txt su tomcatA -l -c /var/jakarta-tomcatA/bin/startup.sh When I cat the txt file it says 1024: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 1024 But when I log in manually as root and run /mnt/90_tomcat by hand I end up getting the proper ulimit: root@host002:/etc/pam.d# cat /tmp/tomcatsu.txt |grep open open files (-n) 65536 Not sure what the issue but I'd appreciate any input. Thanks, Richard Bettridge Systems Engineering Specialist BlackBerry - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public
Re: [one-users] Issue
Hello Hutson, Actually that's the expected behaviour of the 8021Q network drivers. We decided to keep the bridge and the physical device with the vlan tag in the host for the following reasons: 1) It doesn't hurt to leave the bridge and the tagged interface. It won't eat up system's resources. 2) If another VM with the same network ID is launched in the same host, you don't need to create it again, therefore (slightly) speeding up boot times Do you agree with this? Do you think the default behaviour should be to remove the bridge and tagged interface? Of course this behaviour can be modified by enhancing the clean script [1]. Take a look at the ebtables clean script [2]. You will probably need to develop a deactivate method in the ruby class that handles the 8021q network drivers [3]. [1] https://github.com/OpenNebula/one/blob/master/src/vnm_mad/remotes/802.1Q/clean [2] https://github.com/OpenNebula/one/blob/master/src/vnm_mad/remotes/ebtables/clean [3] https://github.com/OpenNebula/one/blob/master/src/vnm_mad/remotes/802.1Q/HostManaged.rb Regards, Jaime On Wed, Dec 14, 2011 at 10:54 PM, Hutson Betts hut...@tamu.edu wrote: I have been testing Host-managed VLANs, but I'm having an issue with cleanup. After creating a VNET and VM, I have the following: oneadmin@opennebula-server:~$ onevm show 5 VIRTUAL MACHINE 5 INFORMATION ID : 5 NAME: vm-example USER: oneadmin GROUP : oneadmin STATE : ACTIVE LCM_STATE : RUNNING HOSTNAME: 10.1.0.101 START TIME : 12/14 15:40:51 END TIME: - DEPLOY ID : one-5 VIRTUAL MACHINE MONITORING NET_TX : 0 NET_RX : 390 USED MEMORY : 524288 USED CPU: 66 VIRTUAL MACHINE TEMPLATE CPU=1 DISK=[ CLONE=YES, DISK_ID=0, IMAGE=Machine A, IMAGE_ID=1, READONLY=NO, SAVE=NO, SOURCE=/var/lib/one/images/643c79fb423c71730ffb84b1a88f06d0, TARGET=hda, TYPE=DISK ] MEMORY=512 NAME=vm-example NIC=[ BRIDGE=onebr2, IP=192.168.0.1, MAC=02:00:c0:a8:00:01, NETWORK=VLAN Test, NETWORK_ID=2, PHYDEV=eth2 ] OS=[ INITRD=/initrd.img, KERNEL=/vmlinuz, ROOT=sda ] VMID=5 oneadmin@opennebula-server:~$ onevnet show 2 VIRTUAL NETWORK 2 INFORMATION ID : 2 USER : oneadmin GROUP : oneadmin PUBLIC : No USED LEASES: 1 VIRTUAL NETWORK TEMPLATE BRIDGE=onebr2 NAME=VLAN Test NETWORK_ADDRESS=192.168.0.0 NETWORK_SIZE=C PHYDEV=eth2 TYPE=RANGED LEASES INFORMATION LEASE=[ IP=192.168.0.1, MAC=02:00:c0:a8:00:01, USED=1, VID=5 ] On the host system, I have the following, created as a result of the Host-managed VLAN script: eth2.502 Link encap:Ethernet HWaddr 00:1b:21:b8:cf:3d inet6 addr: fe80::21b:21ff:feb8:cf3d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:390 (390.0 B)\ onebr2Link encap:Ethernet HWaddr 00:1b:21:b8:cf:3d inet6 addr: fe80::9820:dff:fe31:9aab/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:390 (390.0 B) vnet1 Link encap:Ethernet Next, I proceed to delete the VM and VNET using the following: oneadmin@opennebula-server:~$ onevm delete 5 oneadmin@opennebula-server:~$ onevnet delete 2 The vnet0 tap was removed along with the VM, but the bridge and VLAN-tagged virtual interface are still there. Am I missing a configuration step to insure that those are removed when all remnants of the VM and VNET are deleted? -- Hutson Betts Computer Science and Engineering Texas AM University ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] issue with LVM storage
Hello Prakhar,
are you still experiencing this issue? It looks like a system setup problem.
Do you have any further information on this problem?
Regards,
Jaime
On Tue, Jun 21, 2011 at 5:28 PM, Prakhar Srivastava
prakhar@gmail.comwrote:
Hi,
When I try to create to VM on a cluster node using tm_lvm mode. I get the
following error.
Tue Jun 21 19:50:24 2011 [DiM][I]: New VM state is ACTIVE.
Tue Jun 21 19:50:24 2011 [LCM][I]: New VM state is PROLOG.
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh:
iCloud:/srv/cloud/one/var//images/56cee3989f620fc82e2af24ed4aeffcdc84b125b
192.168.145.105:/srv/cloud/one/var//211/images/disk.0
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: DST:
/srv/cloud/one/var//211/images/disk.0
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Creating directory
/srv/cloud/one/var//211/images
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Executed /usr/bin/ssh
192.168.145.105 mkdir -p /srv/cloud/one/var//211/images.
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Creating LV lv-one-211-0
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Executed /usr/bin/ssh
192.168.145.105 /usr/bin/sudo /sbin/lvcreate -L1G -n lv-one-211-0 one-data.
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Executed /usr/bin/ssh
192.168.145.105 ln -s /dev/one-data/lv-one-211-0
/srv/cloud/one/var//211/images/disk.0.
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Dumping Image
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Executed eval cat
/srv/cloud/one/var//images/56cee3989f620fc82e2af24ed4aeffcdc84b125b |
/usr/bin/ssh 192.168.145.105 /usr/bin/sudo /bin/dd
of=/dev/one-data/lv-one-211-0 bs=64k.
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Creating 1024Mb image in
/srv/cloud/one/var//211/images/disk.1
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh
192.168.145.105 mkdir -p /srv/cloud/one/var//211/images.
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh
192.168.145.105 /bin/dd if=/dev/zero
of=/srv/cloud/one/var//211/images/disk.1 bs=1 count=1 seek=1024M.
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Initializing swap space
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh
192.168.145.105 /sbin/mkswap /srv/cloud/one/var//211/images/disk.1.
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh
192.168.145.105 chmod a+w /srv/cloud/one/var//211/images/disk.1.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed mkdir -p
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed cp -R
/srv/cloud/one/var/211/context.sh
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed cp -R
/home/cloud/opennebula/images/init.sh
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed cp -R
/root/.ssh/id_dsa.pub
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed /usr/bin/mkisofs
-o /srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/disk.2 -J -R
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed /usr/bin/scp
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/disk.2 192.168.145.105:
/srv/cloud/one/var//211/images/disk.2.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed rm -rf
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71.
Tue Jun 21 20:04:06 2011 [LCM][I]: New VM state is BOOT
Tue Jun 21 20:04:06 2011 [VMM][I]: Generating deployment file:
/srv/cloud/one/var/211/deployment.0
Tue Jun 21 20:04:19 2011 [VMM][I]: Command execution fail: 'if [ -x
/var/tmp/one/vmm/xen/deploy ]; then /var/tmp/one/vmm/xen/deploy
/srv/cloud/one/var//211/images/deployment.0; else
exit 42; fi'
Tue Jun 21 20:04:19 2011 [VMM][I]: STDERR follows.
Tue Jun 21 20:04:19 2011 [VMM][I]: Error: Device 51712 (vbd) could not be
connected. /dev/dm-0 does not exist.
Tue Jun 21 20:04:19 2011 [VMM][I]: ExitCode: 1
*Tue Jun 21 20:04:19 2011 [VMM][E]: Error deploying virtual machine:
Error: Device 51712 (vbd) could not be connected. /dev/dm-0 does not exist.
*
Tue Jun 21 20:04:19 2011 [DiM][I]: New VM state is FAILED
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: LOG - 211 tm_delete.sh: Deleting
remote LVs
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: LOG - 211 tm_delete.sh: Executed
/usr/bin/ssh 192.168.145.105 /usr/bin/sudo /sbin/lvremove -f $(echo
one-data/$(/usr/bin/sudo /sbin/lvs --noheadings one-data|awk '{print
$1}'|grep lv-one-211)).
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: LOG - 211 tm_delete.sh: Deleting
/srv/cloud/one/var//211/images
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: LOG - 211 tm_delete.sh: Executed
/usr/bin/ssh 192.168.145.105 rm -rf /srv/cloud/one/var//211/images.
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: TRANSFER SUCCESS 211 -
When I check the cluster node
[one-users] issue with LVM storage
Hi,
When I try to create to VM on a cluster node using tm_lvm mode. I get the
following error.
Tue Jun 21 19:50:24 2011 [DiM][I]: New VM state is ACTIVE.
Tue Jun 21 19:50:24 2011 [LCM][I]: New VM state is PROLOG.
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh:
iCloud:/srv/cloud/one/var//images/56cee3989f620fc82e2af24ed4aeffcdc84b125b
192.168.145.105:/srv/cloud/one/var//211/images/disk.0
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: DST:
/srv/cloud/one/var//211/images/disk.0
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Creating directory
/srv/cloud/one/var//211/images
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Executed /usr/bin/ssh
192.168.145.105 mkdir -p /srv/cloud/one/var//211/images.
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Creating LV lv-one-211-0
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Executed /usr/bin/ssh
192.168.145.105 /usr/bin/sudo /sbin/lvcreate -L1G -n lv-one-211-0 one-data.
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Executed /usr/bin/ssh
192.168.145.105 ln -s /dev/one-data/lv-one-211-0
/srv/cloud/one/var//211/images/disk.0.
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Dumping Image
Tue Jun 21 20:03:46 2011 [TM][I]: tm_clone.sh: Executed eval cat
/srv/cloud/one/var//images/56cee3989f620fc82e2af24ed4aeffcdc84b125b |
/usr/bin/ssh 192.168.145.105 /usr/bin/sudo /bin/dd
of=/dev/one-data/lv-one-211-0 bs=64k.
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Creating 1024Mb image in
/srv/cloud/one/var//211/images/disk.1
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh
192.168.145.105 mkdir -p /srv/cloud/one/var//211/images.
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh
192.168.145.105 /bin/dd if=/dev/zero
of=/srv/cloud/one/var//211/images/disk.1 bs=1 count=1 seek=1024M.
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Initializing swap space
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh
192.168.145.105 /sbin/mkswap /srv/cloud/one/var//211/images/disk.1.
Tue Jun 21 20:04:00 2011 [TM][I]: tm_mkswap.sh: Executed /usr/bin/ssh
192.168.145.105 chmod a+w /srv/cloud/one/var//211/images/disk.1.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed mkdir -p
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed cp -R
/srv/cloud/one/var/211/context.sh
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed cp -R
/home/cloud/opennebula/images/init.sh
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed cp -R
/root/.ssh/id_dsa.pub
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed /usr/bin/mkisofs
-o /srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/disk.2 -J -R
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/isofiles.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed /usr/bin/scp
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71/disk.2 192.168.145.105:
/srv/cloud/one/var//211/images/disk.2.
Tue Jun 21 20:04:06 2011 [TM][I]: tm_context.sh: Executed rm -rf
/srv/cloud/one/var/c1799edd687e76f8d944d8aaa4f4ff71.
Tue Jun 21 20:04:06 2011 [LCM][I]: New VM state is BOOT
Tue Jun 21 20:04:06 2011 [VMM][I]: Generating deployment file:
/srv/cloud/one/var/211/deployment.0
Tue Jun 21 20:04:19 2011 [VMM][I]: Command execution fail: 'if [ -x
/var/tmp/one/vmm/xen/deploy ]; then /var/tmp/one/vmm/xen/deploy
/srv/cloud/one/var//211/images/deployment.0; else
exit 42; fi'
Tue Jun 21 20:04:19 2011 [VMM][I]: STDERR follows.
Tue Jun 21 20:04:19 2011 [VMM][I]: Error: Device 51712 (vbd) could not be
connected. /dev/dm-0 does not exist.
Tue Jun 21 20:04:19 2011 [VMM][I]: ExitCode: 1
*Tue Jun 21 20:04:19 2011 [VMM][E]: Error deploying virtual machine: Error:
Device 51712 (vbd) could not be connected. /dev/dm-0 does not exist.*
Tue Jun 21 20:04:19 2011 [DiM][I]: New VM state is FAILED
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: LOG - 211 tm_delete.sh: Deleting
remote LVs
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: LOG - 211 tm_delete.sh: Executed
/usr/bin/ssh 192.168.145.105 /usr/bin/sudo /sbin/lvremove -f $(echo
one-data/$(/usr/bin/sudo /sbin/lvs --noheadings one-data|awk '{print
$1}'|grep lv-one-211)).
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: LOG - 211 tm_delete.sh: Deleting
/srv/cloud/one/var//211/images
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: LOG - 211 tm_delete.sh: Executed
/usr/bin/ssh 192.168.145.105 rm -rf /srv/cloud/one/var//211/images.
Tue Jun 21 20:04:31 2011 [TM][W]: Ignored: TRANSFER SUCCESS 211 -
When I check the cluster node for the /dev/dm-0, the device mapper for the
logical volume created during VM creation, it shows me that /dev/dm-0 is
present.
Hope someone could throw some light on this error.
Regards,
Prakhar
___
Users mailing list
Users@lists.opennebula.org
Re: [one-users] issue: VM can't boot up from network
Thanks Héctor. I will use onevm command firstly for further tests. -Original Message- From: Héctor Sanjuán [mailto:hsanj...@opennebula.org] Sent: Friday, March 11, 2011 6:22 PM To: GONG YONGJIE A Cc: users@lists.opennebula.org Subject: Re: [one-users] issue: VM can't boot up from network Hi, I think this is related to: http://dev.opennebula.org/issues/511 The OS Section is not being created properly in Sunstone. Therefore the BOOT option is not recognised and takes the default value in ONE. The patch is ready and should be available in the 2.2 branch soon. Héctor El 11/03/11 04:07, GONG YONGJIE A escribió: Hi, I just test to create one VM to boot from PXEbut fromdeployment.0thebootparameter is stillhd. Please correct me if my configuration is wrong. Thanks a lot. Logs: [root@cloudmanager images]# onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 14 root linux-0. runn 1512M 172.24.178.38 00 21:01:46 19 rootOMCP1 runn 10 2G 172.24.178.38 00 17:29:33 23 root CCP5 runn 13 2G 172.24.178.38 00 01:06:19 [root@cloudmanager images]# [root@cloudmanager images]# onevm show 23 VIRTUAL MACHINE 23 INFORMATION ID : 23 NAME : CCP5 STATE : ACTIVE LCM_STATE : RUNNING START TIME : 03/11 11:12:00 END TIME : - DEPLOY ID: : one-23 VIRTUAL MACHINE MONITORING USED MEMORY: 2097152 USED CPU : 13 NET_TX : 0 NET_RX : 0 VIRTUAL MACHINE TEMPLATE ARCH=i686 BOOT=network CPU=1 EMULATOR=/usr/libexec/qemu-kvm GRAPHICS=[ LISTEN=127.0.0.1, PORT=5915, TYPE=vnc ] MEMORY=2048 NAME=CCP5 NIC=[ BRIDGE=br0, MAC=08:80:42:03:17:8a, MODEL=e1000 ] NIC=[ BRIDGE=br1, MAC=08:80:42:03:18:8a, MODEL=e1000 ] VCPU=1 VMID=23 = [root@host1 /]# cat /var/lib/one/23/images/deployment.0 domain type='kvm' nameone-23/name vcpu1/vcpu memory2097152/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator interface type='bridge' source bridge='br0'/ mac address='08:80:42:03:17:8a'/ model type='e1000'/ /interface interface type='bridge' source bridge='br1'/ mac address='08:80:42:03:18:8a'/ model type='e1000'/ /interface graphics type='vnc' listen='127.0.0.1' port='5915'/ /devices features acpi/ /features /domain === [root@cloudmanager images]# cat vm-CCP5.conf NAME = CCP5 MEMORY = 2048 CPU = 1 VCPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = network NIC = [ MAC = 08:80:42:03:17:8a, MODEL =e1000, BRIDGE = br0 ] NIC = [ MAC = 08:80:42:03:18:8a, MODEL =e1000, BRIDGE = br1 ] GRAPHICS = [ TYPE = vnc, LISTEN = 127.0.0.1, PORT = 5915 ] ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Héctor Sanjuan OpenNebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] issue: VM can't boot up from network
Hi, I think this is related to: http://dev.opennebula.org/issues/511 The OS Section is not being created properly in Sunstone. Therefore the BOOT option is not recognised and takes the default value in ONE. The patch is ready and should be available in the 2.2 branch soon. Héctor El 11/03/11 04:07, GONG YONGJIE A escribió: Hi, I just test to create one VM to boot from PXEbut from“deployment.0”the“boot”parameter is still“hd”. Please correct me if my configuration is wrong. Thanks a lot. Logs: [root@cloudmanager images]# onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 14 root linux-0. runn 1512M 172.24.178.38 00 21:01:46 19 rootOMCP1 runn 10 2G 172.24.178.38 00 17:29:33 23 root CCP5 runn 13 2G 172.24.178.38 00 01:06:19 [root@cloudmanager images]# [root@cloudmanager images]# onevm show 23 VIRTUAL MACHINE 23 INFORMATION ID : 23 NAME : CCP5 STATE : ACTIVE LCM_STATE : RUNNING START TIME : 03/11 11:12:00 END TIME : - DEPLOY ID: : one-23 VIRTUAL MACHINE MONITORING USED MEMORY: 2097152 USED CPU : 13 NET_TX : 0 NET_RX : 0 VIRTUAL MACHINE TEMPLATE ARCH=i686 BOOT=network CPU=1 EMULATOR=/usr/libexec/qemu-kvm GRAPHICS=[ LISTEN=127.0.0.1, PORT=5915, TYPE=vnc ] MEMORY=2048 NAME=CCP5 NIC=[ BRIDGE=br0, MAC=08:80:42:03:17:8a, MODEL=e1000 ] NIC=[ BRIDGE=br1, MAC=08:80:42:03:18:8a, MODEL=e1000 ] VCPU=1 VMID=23 = [root@host1 /]# cat /var/lib/one/23/images/deployment.0 domain type='kvm' nameone-23/name vcpu1/vcpu memory2097152/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator interface type='bridge' source bridge='br0'/ mac address='08:80:42:03:17:8a'/ model type='e1000'/ /interface interface type='bridge' source bridge='br1'/ mac address='08:80:42:03:18:8a'/ model type='e1000'/ /interface graphics type='vnc' listen='127.0.0.1' port='5915'/ /devices features acpi/ /features /domain === [root@cloudmanager images]# cat vm-CCP5.conf NAME = CCP5 MEMORY = 2048 CPU = 1 VCPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = network NIC = [ MAC = 08:80:42:03:17:8a, MODEL =e1000, BRIDGE = br0 ] NIC = [ MAC = 08:80:42:03:18:8a, MODEL =e1000, BRIDGE = br1 ] GRAPHICS = [ TYPE = vnc, LISTEN = 127.0.0.1, PORT = 5915 ] ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Héctor Sanjuan OpenNebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] issue: sunstone can't attach OS disk
Hi, so far we haven't been able to reproduce this or to find the cause. Is it possible that you simply forgot to click on the add button after you filled in the fields in the add disk/image section of the kvm wizard, so the disk appears in the current disks box? Héctor El 10/03/11 07:53, GONG YONGJIE A escribió: Hi Hector, I didn't use advanced mode but just Wizard KVM, snapshot attached in the mail. Please correct me if my operation is wrong. Following are onevm command and no disk argument included. [root@cloudmanager images]# onevm show 16 VIRTUAL MACHINE 16 INFORMATION ID : 16 NAME : test-OMCP STATE : ACTIVE LCM_STATE : RUNNING START TIME : 03/10 15:56:14 END TIME : - DEPLOY ID: : one-16 VIRTUAL MACHINE MONITORING USED MEMORY: 524288 USED CPU : 12 NET_TX : 0 NET_RX : 0 VIRTUAL MACHINE TEMPLATE ARCH=i686 BOOT=hd CPU=1 GRAPHICS=[ LISTEN=172.24.178.38, PORT=5923, TYPE=vnc ] MEMORY=512 NAME=test-OMCP RAW=[ TYPE=kvm ] VCPU=1 VMID=16 = [root@cloudmanager one]# cat 16.log Thu Mar 10 15:56:44 2011 [DiM][I]: New VM state is ACTIVE. Thu Mar 10 15:56:44 2011 [LCM][I]: New VM state is PROLOG. Thu Mar 10 15:56:44 2011 [VM][I]: Virtual Machine has no context Thu Mar 10 15:56:44 2011 [LCM][I]: New VM state is BOOT Thu Mar 10 15:56:44 2011 [VMM][I]: Generating deployment file: /var/lib/one/16/deployment.0 Thu Mar 10 15:56:44 2011 [LCM][I]: New VM state is RUNNING Thu Mar 10 15:57:05 2011 [VMM][D]: Monitor Information: CPU : 14 Memory: 524288 Net_TX: -1 Net_RX: -1 === [root@host1 ~]# cat /var/lib/one/16/images/deployment.0 domain type='kvm' nameone-16/name vcpu1/vcpu memory524288/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator graphics type='vnc' listen='172.24.178.38' port='5923'/ /devices features acpi/ /features /domain -Original Message- From: Héctor Sanjuán [mailto:hsanj...@opennebula.org] Sent: Wednesday, March 09, 2011 5:19 PM To: GONG YONGJIE A Cc: users@lists.opennebula.org Subject: Re: [one-users] issue: sunstone can't attach OS disk Hi, I understand that you created the first VM pasting the template in the advanced mode tab for VM creation in sunstone. (or did you use the kvm wizard?) In order to look better into it, I would need the Opennebula templates showing up on both machines after you run: onevm show VMID or from the VM information panel in Sunstone. I could also be helpful if you attach the full VM logs (they are as well on the information panel in Sunstone). Hector El 09/03/11 04:27, GONG YONGJIE A escribió: Hi, I encountered one problem during VM creation tests. Problem: VM machine created bysunstonewith registeredOS imageis running without disk image. Workaround: useonevm createinsteadly. From deployment file,no disk argument existed. === VM created by sunstoneweb interface== [root@host1 bin]# cat /var/lib/one/6/images/deployment.0 domain type='kvm' nameone-6/name vcpu1/vcpu memory524288/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator graphics type='vnc' listen='172.24.178.38' port='5905'/ /devices features acpi/ /features /domain === VM created by onevm command== [root@host1 bin]# cat /var/lib/one/7/images/deployment.0 domain type='kvm' nameone-7/name memory524288/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' source file='/var/lib/one//7/images/disk.0'/ target dev='hda'/ driver name='qemu' type='raw'/ /disk /devices features acpi/ /features /domain Some info: [root@cloudmanager images]# onevmlist ID USER NAME STAT CPU MEMHOSTNAME
Re: [one-users] issue: can't specify NIC hardware type duirng VM creating
Hi there, There's a typo in your template, you are using MODLE instead of MODEL. Regards, Carlos -- Carlos Martín, MSc Project Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org On 10 March 2011 08:02, GONG YONGJIE A yongjie.a.g...@alcatel-sbell.com.cnwrote: Hi, I’d like to create one VM with “e1000” hardware type for Ethernet interface. But after VM boots up, it still use default “realtek” type. From “deployment.0”, there is no “model=e1000” parameter for NIC. Could you help me check this or correct me if my configuration isn ’t right. Thanks. Logs: [root@cloudmanager one]# onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 12 rootOMCP1 runn 7 2G 172.24.178.38 00 22:00:52 14 root linux-0. runn 1512M 172.24.178.38 00 00:47:07 16 root test-OMC runn 12512M 172.24.178.38 00 00:07:26 [root@cloudmanager one]# [root@cloudmanager one]# onevm show 12 VIRTUAL MACHINE 12 INFORMATION ID : 12 NAME : OMCP1 STATE : ACTIVE LCM_STATE : RUNNING START TIME : 03/09 18:02:48 END TIME : - DEPLOY ID: : one-12 VIRTUAL MACHINE MONITORING USED MEMORY: 2097152 USED CPU : 7 NET_TX : 0 NET_RX : 0 VIRTUAL MACHINE TEMPLATE ARCH=i686 BOOT=hd CPU=1 DISK=[ CLONE=NO, DISK_ID=0, IMAGE=OMCP1, IMAGE_ID=3, READONLY=NO, SAVE=YES, SAVE_AS=3, SOURCE=/srv/cloud/var/images/de0d6ef4e05642f928c8eae5a5a0a7b4201cfba5, TARGET=hda, TYPE=DISK ] EMULATOR=/usr/libexec/qemu-kvm GRAPHICS=[ LISTEN=127.0.0.1, PORT=5913, TYPE=vnc ] MEMORY=2048 NAME=OMCP1 NIC=[ BRIDGE=br0, MAC=08:80:42:03:17:86, MODLE=e1000 ] NIC=[ BRIDGE=br1, MAC=08:80:42:03:18:86, MODLE=e1000 ] VCPU=1 VMID=12 [root@cloudmanager one]# [root@cloudmanager one]# pwd /var/log/one [root@cloudmanager one]# cat /srv/cloud/var/images/vm- vm-linux-0.2.conf vm-OMCP1.conf [root@cloudmanager one]# cat /srv/cloud/var/images/vm-OMCP1.conf NAME = OMCP1 MEMORY = 2048 CPU = 1 VCPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = hd DISK = [ IMAGE= OMCP1 ] NIC = [ MAC = 08:80:42:03:17:86, MODLE =e1000, BRIDGE = br0 ] NIC = [ MAC = 08:80:42:03:18:86, MODLE =e1000, BRIDGE = br1 ] GRAPHICS = [ TYPE = vnc, LISTEN = 127.0.0.1, PORT = 5913 ] [root@cloudmanager one]# [root@host1 ~]# cat /var/lib/one/12/images/deployment.0 domain type='kvm' nameone-12/name vcpu1/vcpu memory2097152/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' source file='/var/lib/one//12/images/disk.0'/ target dev='hda'/ driver name='qemu' type='raw'/ /disk interface type='bridge' source bridge='br0'/ mac address='08:80:42:03:17:86'/ /interface interface type='bridge' source bridge='br1'/ mac address='08:80:42:03:18:86'/ /interface graphics type='vnc' listen='127.0.0.1' port='5913'/ /devices features acpi/ /features /domain [root@host1 ~]# ___ 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] issue: can't specify NIC hardware type duirng VM creating
Ooops.. I will try it later J Thanks for great support. From: Carlos Martín Sánchez [mailto:cmar...@opennebula.org] Sent: Thursday, March 10, 2011 4:26 PM To: GONG YONGJIE A Cc: users@lists.opennebula.org Subject: Re: [one-users] issue: can't specify NIC hardware type duirng VM creating Hi there, There's a typo in your template, you are using MODLE instead of MODEL. Regards, Carlos -- Carlos Martín, MSc Project Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org mailto:cmar...@opennebula.org On 10 March 2011 08:02, GONG YONGJIE A yongjie.a.g...@alcatel-sbell.com.cn wrote: Hi, I'd like to create one VM with e1000 hardware type for Ethernet interface. But after VM boots up, it still use default realtek type. From deployment.0, there is no model=e1000 parameter for NIC. Could you help me check this or correct me if my configuration isn't right. Thanks. Logs: [root@cloudmanager one]# onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 12 rootOMCP1 runn 7 2G 172.24.178.38 00 22:00:52 14 root linux-0. runn 1512M 172.24.178.38 00 00:47:07 16 root test-OMC runn 12512M 172.24.178.38 00 00:07:26 [root@cloudmanager one]# [root@cloudmanager one]# onevm show 12 VIRTUAL MACHINE 12 INFORMATION ID : 12 NAME : OMCP1 STATE : ACTIVE LCM_STATE : RUNNING START TIME : 03/09 18:02:48 END TIME : - DEPLOY ID: : one-12 VIRTUAL MACHINE MONITORING USED MEMORY: 2097152 USED CPU : 7 NET_TX : 0 NET_RX : 0 VIRTUAL MACHINE TEMPLATE ARCH=i686 BOOT=hd CPU=1 DISK=[ CLONE=NO, DISK_ID=0, IMAGE=OMCP1, IMAGE_ID=3, READONLY=NO, SAVE=YES, SAVE_AS=3, SOURCE=/srv/cloud/var/images/de0d6ef4e05642f928c8eae5a5a0a7b4201cfba5, TARGET=hda, TYPE=DISK ] EMULATOR=/usr/libexec/qemu-kvm GRAPHICS=[ LISTEN=127.0.0.1, PORT=5913, TYPE=vnc ] MEMORY=2048 NAME=OMCP1 NIC=[ BRIDGE=br0, MAC=08:80:42:03:17:86, MODLE=e1000 ] NIC=[ BRIDGE=br1, MAC=08:80:42:03:18:86, MODLE=e1000 ] VCPU=1 VMID=12 [root@cloudmanager one]# [root@cloudmanager one]# pwd /var/log/one [root@cloudmanager one]# cat /srv/cloud/var/images/vm- vm-linux-0.2.conf vm-OMCP1.conf [root@cloudmanager one]# cat /srv/cloud/var/images/vm-OMCP1.conf NAME = OMCP1 MEMORY = 2048 CPU = 1 VCPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = hd DISK = [ IMAGE= OMCP1 ] NIC = [ MAC = 08:80:42:03:17:86, MODLE =e1000, BRIDGE = br0 ] NIC = [ MAC = 08:80:42:03:18:86, MODLE =e1000, BRIDGE = br1 ] GRAPHICS = [ TYPE = vnc, LISTEN = 127.0.0.1, PORT = 5913 ] [root@cloudmanager one]# [root@host1 ~]# cat /var/lib/one/12/images/deployment.0 domain type='kvm' nameone-12/name vcpu1/vcpu memory2097152/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' source file='/var/lib/one//12/images/disk.0'/ target dev='hda'/ driver name='qemu' type='raw'/ /disk interface type='bridge' source bridge='br0'/ mac address='08:80:42:03:17:86'/ /interface interface type='bridge' source bridge='br1'/ mac address='08:80:42:03:18:86'/ /interface graphics type='vnc' listen='127.0.0.1' port='5913'/ /devices features acpi/ /features /domain [root@host1 ~]# ___ 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] issue: VM instance can't shut down through sunstone command
Ok, My mistake, KVM driver is not plugging the VM off after the timeout occurs. var/remotes/vmm/kvm/shutdown: if [ $count -gt $TIMEOUT ] then echo Timeout reached 2 exit 1 fi ttylinux is just ignoring the shutdown signal, so the script fails with the Timeout reached message as expected. I guess the way to power off ttylinux is either using 'onevm cancel', modifying the poweroff script so it destroys the VM if the TIMEOUT is reached or getting the VM to understand the acpi poweroff signal. Héctor El 10/03/11 07:36, GONG YONGJIE A escribió: Thanks Hector. Just try to reproduce it. Status of VM becomes shutdown and then is recovered to running. Thu Mar 10 15:23:31 2011 [VMM][E]: Error shuting down VM, Timeout reached Thu Mar 10 15:23:31 2011 [LCM][I]: Fail to shutdown VM. Assuming that the VM is still RUNNING (will poll VM). [root@cloudmanager images]# cat vm-linux-0.2.conf NAME = linux-0.2 MEMORY = 512 CPU = 1 VCPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = hd DISK = [ IMAGE= linux-0.2 ] NIC = [ MAC = 05:80:42:03:17:86, MODLE =e1000, BRIDGE = br0 ] NIC = [ MAC = 05:80:42:03:18:86, MODLE =e1000, BRIDGE = br1 ] GRAPHICS = [ TYPE = vnc, LISTEN = 127.0.0.1, PORT = 5914 ] -Original Message- From: Héctor Sanjuán [mailto:hsanj...@opennebula.org] Sent: Wednesday, March 09, 2011 5:08 PM To: GONG YONGJIE A Cc: users@lists.opennebula.org Subject: Re: [one-users] issue: VM instance can't shut down through sunstone command Hi, Shutdown is a transitory state indicating that the shutdown script has started. This script tries to send and shutdown ACPI signal to the VM and regularly checks if the VM has shut down until the TIMEOUT occurs (defined in the shutdown remotes script as far as i know). If the VM has not been shutdown after that time, the script will try to directly power off the VM. After that the VM is deleted [1] Does your VM stay in shutdown state indefinitely? If you are using ttylinux it might be ignoring the ACPI shutdown signal and therefore it would take the TIMEOUT to power it off. The stop state is meant to freeze a vm in running state by saving its state. Can you ellaborate on how onevm stop is failing? I hope it helps, if not you can send the full VM log and template. Hector [1] VM State diagram: http://opennebula.org/documentation:rel2.0:vm_guide El 09/03/11 04:58, GONG YONGJIE A escribió: Hi, I encountered another issue that after shutdown VM instance fromsunstone,the VM is still alive even status of this VM becomesSHUTDOWN. Also fromonevmcommand, itis failed to useonevm stop. [root@cloudmanager one]# onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 9 root test-8 shut 2512M 172.24.178.38 00 00:18:29 qemu 30740 1 2 07:35 ?00:00:24 /usr/libexec/qemu-kvm -S -M rhel6.0.0 -cpu qemu32 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name one-9 -uuid 064aecf7-a857-222f-8121-5d47facf5eef -nodefconfig -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/one-9.monitor,server,nowait -mon chardev=monitor,mode=control -rtc base=utc -boot c -drive file=/var/lib/one//9/images/disk.0,if=none,id=drive-ide0-0-0,boot=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=23,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:11:22:33:44:55,bus=pci.0,addr=0x3 -usb -vnc 127.0.0.1:8 -vga cirrus -devicevirtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 [root@cloudmanager one]# cat 9.log ... Wed Mar 9 12:01:55 2011 [LCM][I]: New VM state is SHUTDOWN [root@cloudmanager one]# rpm -qa | grep -i openNebula opennebula-2.1.80-1 [root@cloudmanager one]# cat /etc/one/oned.conf #*** # OpenNebula Configuration file #*** #*** # Daemon configuration attributes #--- # MANAGER_TIMER: Time in seconds the core uses to evaluate periodical functions. # HOST_MONITORING_INTERVAL and VM_POLLING_INTERVAL can not have smaller values # than MANAGER_TIMER. # # HOST_MONITORING_INTERVAL: Time in seconds between host monitorization. # # VM_POLLING_INTERVAL: Time in seconds between virtual machine monitorization. # (use 0 to disable VM monitoring). # # VM_DIR: Remote path to store the VM images, it should be shared between all # the cluster nodes to perform live migrations. This variable is the default # for all the hosts in the cluster. VM_DIR IS ONLY FORTHE NODES AND *NOT* THE # FRONT-END
Re: [one-users] issue: VM instance can't shut down through sunstone command
Hi Héctor, Got it. Thanks very much :) -Original Message- From: Héctor Sanjuán [mailto:hsanj...@opennebula.org] Sent: Thursday, March 10, 2011 6:49 PM To: GONG YONGJIE A Cc: users@lists.opennebula.org Subject: Re: [one-users] issue: VM instance can't shut down through sunstone command Ok, My mistake, KVM driver is not plugging the VM off after the timeout occurs. var/remotes/vmm/kvm/shutdown: if [ $count -gt $TIMEOUT ] then echo Timeout reached 2 exit 1 fi ttylinux is just ignoring the shutdown signal, so the script fails with the Timeout reached message as expected. I guess the way to power off ttylinux is either using 'onevm cancel', modifying the poweroff script so it destroys the VM if the TIMEOUT is reached or getting the VM to understand the acpi poweroff signal. Héctor El 10/03/11 07:36, GONG YONGJIE A escribió: Thanks Hector. Just try to reproduce it. Status of VM becomes shutdown and then is recovered to running. Thu Mar 10 15:23:31 2011 [VMM][E]: Error shuting down VM, Timeout reached Thu Mar 10 15:23:31 2011 [LCM][I]: Fail to shutdown VM. Assuming that the VM is still RUNNING (will poll VM). [root@cloudmanager images]# cat vm-linux-0.2.conf NAME = linux-0.2 MEMORY = 512 CPU = 1 VCPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = hd DISK = [ IMAGE= linux-0.2 ] NIC = [ MAC = 05:80:42:03:17:86, MODLE =e1000, BRIDGE = br0 ] NIC = [ MAC = 05:80:42:03:18:86, MODLE =e1000, BRIDGE = br1 ] GRAPHICS = [ TYPE = vnc, LISTEN = 127.0.0.1, PORT = 5914 ] -Original Message- From: Héctor Sanjuán [mailto:hsanj...@opennebula.org] Sent: Wednesday, March 09, 2011 5:08 PM To: GONG YONGJIE A Cc: users@lists.opennebula.org Subject: Re: [one-users] issue: VM instance can't shut down through sunstone command Hi, Shutdown is a transitory state indicating that the shutdown script has started. This script tries to send and shutdown ACPI signal to the VM and regularly checks if the VM has shut down until the TIMEOUT occurs (defined in the shutdown remotes script as far as i know). If the VM has not been shutdown after that time, the script will try to directly power off the VM. After that the VM is deleted [1] Does your VM stay in shutdown state indefinitely? If you are using ttylinux it might be ignoring the ACPI shutdown signal and therefore it would take the TIMEOUT to power it off. The stop state is meant to freeze a vm in running state by saving its state. Can you ellaborate on how onevm stop is failing? I hope it helps, if not you can send the full VM log and template. Hector [1] VM State diagram: http://opennebula.org/documentation:rel2.0:vm_guide El 09/03/11 04:58, GONG YONGJIE A escribió: Hi, I encountered another issue that after shutdown VM instance fromsunstone,the VM is still alive even status of this VM becomesSHUTDOWN. Also fromonevmcommand, itis failed to useonevm stop. [root@cloudmanager one]# onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 9 root test-8 shut 2512M 172.24.178.38 00 00:18:29 qemu 30740 1 2 07:35 ?00:00:24 /usr/libexec/qemu-kvm -S -M rhel6.0.0 -cpu qemu32 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name one-9 -uuid 064aecf7-a857-222f-8121-5d47facf5eef -nodefconfig -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/one-9.monitor,server,nowait -mon chardev=monitor,mode=control -rtc base=utc -boot c -drive file=/var/lib/one//9/images/disk.0,if=none,id=drive-ide0-0-0,boot=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=23,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:11:22:33:44:55,bus=pci.0,addr=0x3 -usb -vnc 127.0.0.1:8 -vga cirrus -devicevirtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 [root@cloudmanager one]# cat 9.log ... Wed Mar 9 12:01:55 2011 [LCM][I]: New VM state is SHUTDOWN [root@cloudmanager one]# rpm -qa | grep -i openNebula opennebula-2.1.80-1 [root@cloudmanager one]# cat /etc/one/oned.conf #*** # OpenNebula Configuration file #*** #*** # Daemon configuration attributes #--- # MANAGER_TIMER: Time in seconds the core uses to evaluate periodical functions. # HOST_MONITORING_INTERVAL and VM_POLLING_INTERVAL can not have smaller values # than MANAGER_TIMER. # # HOST_MONITORING_INTERVAL: Time in seconds between host monitorization. # # VM_POLLING_INTERVAL: Time in seconds between virtual machine
[one-users] issue: VM can't boot up from network
Hi, I just test to create one VM to boot from PXE but from deployment.0 the boot parameter is still hd. Please correct me if my configuration is wrong. Thanks a lot. Logs: [root@cloudmanager images]# onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 14 root linux-0. runn 1512M 172.24.178.38 00 21:01:46 19 rootOMCP1 runn 10 2G 172.24.178.38 00 17:29:33 23 root CCP5 runn 13 2G 172.24.178.38 00 01:06:19 [root@cloudmanager images]# [root@cloudmanager images]# onevm show 23 VIRTUAL MACHINE 23 INFORMATION ID : 23 NAME : CCP5 STATE : ACTIVE LCM_STATE : RUNNING START TIME : 03/11 11:12:00 END TIME : - DEPLOY ID: : one-23 VIRTUAL MACHINE MONITORING USED MEMORY: 2097152 USED CPU : 13 NET_TX : 0 NET_RX : 0 VIRTUAL MACHINE TEMPLATE ARCH=i686 BOOT=network CPU=1 EMULATOR=/usr/libexec/qemu-kvm GRAPHICS=[ LISTEN=127.0.0.1, PORT=5915, TYPE=vnc ] MEMORY=2048 NAME=CCP5 NIC=[ BRIDGE=br0, MAC=08:80:42:03:17:8a, MODEL=e1000 ] NIC=[ BRIDGE=br1, MAC=08:80:42:03:18:8a, MODEL=e1000 ] VCPU=1 VMID=23 = [root@host1 /]# cat /var/lib/one/23/images/deployment.0 domain type='kvm' nameone-23/name vcpu1/vcpu memory2097152/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator interface type='bridge' source bridge='br0'/ mac address='08:80:42:03:17:8a'/ model type='e1000'/ /interface interface type='bridge' source bridge='br1'/ mac address='08:80:42:03:18:8a'/ model type='e1000'/ /interface graphics type='vnc' listen='127.0.0.1' port='5915'/ /devices features acpi/ /features /domain === [root@cloudmanager images]# cat vm-CCP5.conf NAME = CCP5 MEMORY = 2048 CPU = 1 VCPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = network NIC = [ MAC = 08:80:42:03:17:8a, MODEL =e1000, BRIDGE = br0 ] NIC = [ MAC = 08:80:42:03:18:8a, MODEL =e1000, BRIDGE = br1 ] GRAPHICS = [ TYPE = vnc, LISTEN = 127.0.0.1, PORT = 5915 ] ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] issue: sunstone can't attach OS disk
Hi, I understand that you created the first VM pasting the template in the advanced mode tab for VM creation in sunstone. (or did you use the kvm wizard?) In order to look better into it, I would need the Opennebula templates showing up on both machines after you run: onevm show VMID or from the VM information panel in Sunstone. I could also be helpful if you attach the full VM logs (they are as well on the information panel in Sunstone). Hector El 09/03/11 04:27, GONG YONGJIE A escribió: Hi, I encountered one problem during VM creation tests. Problem: VM machine created by“sunstone”with registeredOS imageis running without disk image. Workaround: use“onevm create”insteadly. From deployment file,no disk argument existed. === VM created by sunstoneweb interface== [root@host1 bin]# cat /var/lib/one/6/images/deployment.0 domain type='kvm' nameone-6/name vcpu1/vcpu memory524288/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator graphics type='vnc' listen='172.24.178.38' port='5905'/ /devices features acpi/ /features /domain === VM created by onevm command== [root@host1 bin]# cat /var/lib/one/7/images/deployment.0 domain type='kvm' nameone-7/name memory524288/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' source file='/var/lib/one//7/images/disk.0'/ target dev='hda'/ driver name='qemu' type='raw'/ /disk /devices features acpi/ /features /domain Some info: [root@cloudmanager images]# onevmlist ID USER NAME STAT CPU MEMHOSTNAMETIME 6 root test-5 runn 12512M 172.24.178.38 00 00:11:12 7 root test-6 pend 0 0K 00 00:00:03 [root@cloudmanager images]# [root@cloudmanager images]# oneimage list ID USER NAME TYPE REGTIME PUB PER STAT #VMS 2 root test_image_register_ OS Mar 09, 2011 02:38 Yes No used 1 [root@cloudmanager images]# [root@cloudmanager images]# rpm -qa | grep -i openNe opennebula-2.1.80-1 [root@cloudmanager images]# cat vmtest.conf NAME = test-6 MEMORY = 512 CPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = hd DISK = [ IMAGE= test_image_register_ttylinux ] ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Héctor Sanjuan OpenNebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] issue: VM instance can't shut down through sunstone command
Thanks Hector. Just try to reproduce it. Status of VM becomes shutdown and then is recovered to running. Thu Mar 10 15:23:31 2011 [VMM][E]: Error shuting down VM, Timeout reached Thu Mar 10 15:23:31 2011 [LCM][I]: Fail to shutdown VM. Assuming that the VM is still RUNNING (will poll VM). [root@cloudmanager images]# cat vm-linux-0.2.conf NAME = linux-0.2 MEMORY = 512 CPU = 1 VCPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = hd DISK = [ IMAGE= linux-0.2 ] NIC = [ MAC = 05:80:42:03:17:86, MODLE =e1000, BRIDGE = br0 ] NIC = [ MAC = 05:80:42:03:18:86, MODLE =e1000, BRIDGE = br1 ] GRAPHICS = [ TYPE = vnc, LISTEN = 127.0.0.1, PORT = 5914 ] -Original Message- From: Héctor Sanjuán [mailto:hsanj...@opennebula.org] Sent: Wednesday, March 09, 2011 5:08 PM To: GONG YONGJIE A Cc: users@lists.opennebula.org Subject: Re: [one-users] issue: VM instance can't shut down through sunstone command Hi, Shutdown is a transitory state indicating that the shutdown script has started. This script tries to send and shutdown ACPI signal to the VM and regularly checks if the VM has shut down until the TIMEOUT occurs (defined in the shutdown remotes script as far as i know). If the VM has not been shutdown after that time, the script will try to directly power off the VM. After that the VM is deleted [1] Does your VM stay in shutdown state indefinitely? If you are using ttylinux it might be ignoring the ACPI shutdown signal and therefore it would take the TIMEOUT to power it off. The stop state is meant to freeze a vm in running state by saving its state. Can you ellaborate on how onevm stop is failing? I hope it helps, if not you can send the full VM log and template. Hector [1] VM State diagram: http://opennebula.org/documentation:rel2.0:vm_guide El 09/03/11 04:58, GONG YONGJIE A escribió: Hi, I encountered another issue that after shutdown VM instance fromsunstone,the VM is still alive even status of this VM becomesSHUTDOWN. Also fromonevmcommand, itis failed to useonevm stop. [root@cloudmanager one]# onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 9 root test-8 shut 2512M 172.24.178.38 00 00:18:29 qemu 30740 1 2 07:35 ?00:00:24 /usr/libexec/qemu-kvm -S -M rhel6.0.0 -cpu qemu32 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name one-9 -uuid 064aecf7-a857-222f-8121-5d47facf5eef -nodefconfig -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/one-9.monitor,server,nowait -mon chardev=monitor,mode=control -rtc base=utc -boot c -drive file=/var/lib/one//9/images/disk.0,if=none,id=drive-ide0-0-0,boot=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=23,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:11:22:33:44:55,bus=pci.0,addr=0x3 -usb -vnc 127.0.0.1:8 -vga cirrus -devicevirtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 [root@cloudmanager one]# cat 9.log ... Wed Mar 9 12:01:55 2011 [LCM][I]: New VM state is SHUTDOWN [root@cloudmanager one]# rpm -qa | grep -i openNebula opennebula-2.1.80-1 [root@cloudmanager one]# cat /etc/one/oned.conf #*** # OpenNebula Configuration file #*** #*** # Daemon configuration attributes #--- # MANAGER_TIMER: Time in seconds the core uses to evaluate periodical functions. # HOST_MONITORING_INTERVAL and VM_POLLING_INTERVAL can not have smaller values # than MANAGER_TIMER. # # HOST_MONITORING_INTERVAL: Time in seconds between host monitorization. # # VM_POLLING_INTERVAL: Time in seconds between virtual machine monitorization. # (use 0 to disable VM monitoring). # # VM_DIR: Remote path to store the VM images, it should be shared between all # the cluster nodes to perform live migrations. This variable is the default # for all the hosts in the cluster. VM_DIR IS ONLY FORTHE NODES AND *NOT* THE # FRONT-END # # SCRIPTS_REMOTE_DIR: Remote path to store the monitoring and VM management # scripts. # # PORT: Port where oned will listen for xmlrpc calls. # # DB: Configuration attributes for the database backend # backend : can be sqlite or mysql (default is sqlite) # server : (mysql) host name or an IP address for the MySQL server # port: (mysql) port for the connection to the server. # If set to 0, the default port is used. # user: (mysql) user's MySQL login ID # passwd : (mysql) the password for user # db_name : (mysql) the database name
Re: [one-users] issue: sunstone can't attach OS disk
Hi Hector, I didn't use advanced mode but just Wizard KVM, snapshot attached in the mail. Please correct me if my operation is wrong. Following are onevm command and no disk argument included. [root@cloudmanager images]# onevm show 16 VIRTUAL MACHINE 16 INFORMATION ID : 16 NAME : test-OMCP STATE : ACTIVE LCM_STATE : RUNNING START TIME : 03/10 15:56:14 END TIME : - DEPLOY ID: : one-16 VIRTUAL MACHINE MONITORING USED MEMORY: 524288 USED CPU : 12 NET_TX : 0 NET_RX : 0 VIRTUAL MACHINE TEMPLATE ARCH=i686 BOOT=hd CPU=1 GRAPHICS=[ LISTEN=172.24.178.38, PORT=5923, TYPE=vnc ] MEMORY=512 NAME=test-OMCP RAW=[ TYPE=kvm ] VCPU=1 VMID=16 = [root@cloudmanager one]# cat 16.log Thu Mar 10 15:56:44 2011 [DiM][I]: New VM state is ACTIVE. Thu Mar 10 15:56:44 2011 [LCM][I]: New VM state is PROLOG. Thu Mar 10 15:56:44 2011 [VM][I]: Virtual Machine has no context Thu Mar 10 15:56:44 2011 [LCM][I]: New VM state is BOOT Thu Mar 10 15:56:44 2011 [VMM][I]: Generating deployment file: /var/lib/one/16/deployment.0 Thu Mar 10 15:56:44 2011 [LCM][I]: New VM state is RUNNING Thu Mar 10 15:57:05 2011 [VMM][D]: Monitor Information: CPU : 14 Memory: 524288 Net_TX: -1 Net_RX: -1 === [root@host1 ~]# cat /var/lib/one/16/images/deployment.0 domain type='kvm' nameone-16/name vcpu1/vcpu memory524288/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator graphics type='vnc' listen='172.24.178.38' port='5923'/ /devices features acpi/ /features /domain -Original Message- From: Héctor Sanjuán [mailto:hsanj...@opennebula.org] Sent: Wednesday, March 09, 2011 5:19 PM To: GONG YONGJIE A Cc: users@lists.opennebula.org Subject: Re: [one-users] issue: sunstone can't attach OS disk Hi, I understand that you created the first VM pasting the template in the advanced mode tab for VM creation in sunstone. (or did you use the kvm wizard?) In order to look better into it, I would need the Opennebula templates showing up on both machines after you run: onevm show VMID or from the VM information panel in Sunstone. I could also be helpful if you attach the full VM logs (they are as well on the information panel in Sunstone). Hector El 09/03/11 04:27, GONG YONGJIE A escribió: Hi, I encountered one problem during VM creation tests. Problem: VM machine created bysunstonewith registeredOS imageis running without disk image. Workaround: useonevm createinsteadly. From deployment file,no disk argument existed. === VM created by sunstoneweb interface== [root@host1 bin]# cat /var/lib/one/6/images/deployment.0 domain type='kvm' nameone-6/name vcpu1/vcpu memory524288/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator graphics type='vnc' listen='172.24.178.38' port='5905'/ /devices features acpi/ /features /domain === VM created by onevm command== [root@host1 bin]# cat /var/lib/one/7/images/deployment.0 domain type='kvm' nameone-7/name memory524288/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' source file='/var/lib/one//7/images/disk.0'/ target dev='hda'/ driver name='qemu' type='raw'/ /disk /devices features acpi/ /features /domain Some info: [root@cloudmanager images]# onevmlist ID USER NAME STAT CPU MEMHOSTNAMETIME 6 root test-5 runn 12512M 172.24.178.38 00 00:11:12 7 root test-6 pend 0 0K 00 00:00:03 [root@cloudmanager images]# [root@cloudmanager images]# oneimage list ID USER NAME TYPE REGTIME PUB PER STAT #VMS 2 root test_image_register_ OS Mar 09, 2011
[one-users] issue: can't specify NIC hardware type duirng VM creating
Hi, I'd like to create one VM with e1000 hardware type for Ethernet interface. But after VM boots up, it still use default realtek type. From deployment.0, there is no model=e1000 parameter for NIC. Could you help me check this or correct me if my configuration isn't right. Thanks. Logs: [root@cloudmanager one]# onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 12 rootOMCP1 runn 7 2G 172.24.178.38 00 22:00:52 14 root linux-0. runn 1512M 172.24.178.38 00 00:47:07 16 root test-OMC runn 12512M 172.24.178.38 00 00:07:26 [root@cloudmanager one]# [root@cloudmanager one]# onevm show 12 VIRTUAL MACHINE 12 INFORMATION ID : 12 NAME : OMCP1 STATE : ACTIVE LCM_STATE : RUNNING START TIME : 03/09 18:02:48 END TIME : - DEPLOY ID: : one-12 VIRTUAL MACHINE MONITORING USED MEMORY: 2097152 USED CPU : 7 NET_TX : 0 NET_RX : 0 VIRTUAL MACHINE TEMPLATE ARCH=i686 BOOT=hd CPU=1 DISK=[ CLONE=NO, DISK_ID=0, IMAGE=OMCP1, IMAGE_ID=3, READONLY=NO, SAVE=YES, SAVE_AS=3, SOURCE=/srv/cloud/var/images/de0d6ef4e05642f928c8eae5a5a0a7b4201cfba5, TARGET=hda, TYPE=DISK ] EMULATOR=/usr/libexec/qemu-kvm GRAPHICS=[ LISTEN=127.0.0.1, PORT=5913, TYPE=vnc ] MEMORY=2048 NAME=OMCP1 NIC=[ BRIDGE=br0, MAC=08:80:42:03:17:86, MODLE=e1000 ] NIC=[ BRIDGE=br1, MAC=08:80:42:03:18:86, MODLE=e1000 ] VCPU=1 VMID=12 [root@cloudmanager one]# [root@cloudmanager one]# pwd /var/log/one [root@cloudmanager one]# cat /srv/cloud/var/images/vm- vm-linux-0.2.conf vm-OMCP1.conf [root@cloudmanager one]# cat /srv/cloud/var/images/vm-OMCP1.conf NAME = OMCP1 MEMORY = 2048 CPU = 1 VCPU = 1 EMULATOR = /usr/libexec/qemu-kvm ARCH = i686 BOOT = hd DISK = [ IMAGE= OMCP1 ] NIC = [ MAC = 08:80:42:03:17:86, MODLE =e1000, BRIDGE = br0 ] NIC = [ MAC = 08:80:42:03:18:86, MODLE =e1000, BRIDGE = br1 ] GRAPHICS = [ TYPE = vnc, LISTEN = 127.0.0.1, PORT = 5913 ] [root@cloudmanager one]# [root@host1 ~]# cat /var/lib/one/12/images/deployment.0 domain type='kvm' nameone-12/name vcpu1/vcpu memory2097152/memory os type arch='i686'hvm/type boot dev='hd'/ /os devices emulator/usr/libexec/qemu-kvm/emulator disk type='file' device='disk' source file='/var/lib/one//12/images/disk.0'/ target dev='hda'/ driver name='qemu' type='raw'/ /disk interface type='bridge' source bridge='br0'/ mac address='08:80:42:03:17:86'/ /interface interface type='bridge' source bridge='br1'/ mac address='08:80:42:03:18:86'/ /interface graphics type='vnc' listen='127.0.0.1' port='5913'/ /devices features acpi/ /features /domain [root@host1 ~]# ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
