[one-users] OCCI vm status indication
Hi, I am running opennebula 3.8.3 and OCCI self-service portal. My problem is that the VM indication is misleading. There 3 statuses - green, yellow, red. When I stop VM it turns to yellow, if anything is wrong red.. that is perfectly correct but the VM is indicated by green for shutdown, poweroff and all other statuses.. I was trying to fix compute.js, but it didnt worked out.. So I assume there is a deeper problem? Can you confirm that? Thank you, Milos ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] OpenNebula 3.8.3 and VMWare ESXi 5.0: internal error HTTP response code 403 for upload
Hi, On Wed, Apr 24, 2013 at 5:20 PM, chenxi...@aquala-tech.com wrote: Second try. I looked into disk.vmdk, and found the following: # Disk DescriptorFile version=1 encoding=UTF-8 CID=e451587b parentCID= isNativeSnapshot=no createType=vmfs # Extent description RW 16777216 VMFS CentOS-6.2.vmdk Obvious I did not have CentOS-6.2.vmdk, but I have CentOS-6.2-flat.vmdk. So, I manually edited that disk.vmdk, and changed CentOS-6.2.vmdk to CentOS-6.2-flat.vmdk. Then I instantiated a VM, that worked! Sure, the image had this issue indeed. We have fixed the image and uploaded it to the marketplace Thanks a lot for the feedback! Regards, -Tino Now I have CentOS 6.2 running.. Chen Xiang A lot of new things to learn. After getting ttylinux work with ESXi, I headed for CentOS 6.2 (also imported from Marketplace), and it did not work as expected. This time I already have a datastore with DS_MAD=vmware. I imported CentOS 6.2 from marketplace, and had the following in that datastore directory, which looked alright: oneadmin@opennebula:~/var/datastores/100/c5610951183fa21ac0900ce147a677b7$ ls -l total 8388616 -rw--- 1 oneadmin cloud 8589934592 Jul 2 2012 CentOS-6.2-flat.vmdk -rw--- 1 oneadmin cloud515 Jul 3 2012 disk.vmdk Then I instantiated a VM, but it failed to boot (prolog seemed to be OK). Below is the VM log: Wed Apr 24 22:40:41 2013 [DiM][I]: New VM state is ACTIVE. Wed Apr 24 22:40:41 2013 [LCM][I]: New VM state is PROLOG. Wed Apr 24 22:40:41 2013 [VM][I]: Virtual Machine has no context Wed Apr 24 22:47:36 2013 [TM][I]: clone: Cloning opennebula:/srv/cloud/one/var/datastores/100/c5610951183fa21ac0900ce147a677b7 in /vmfs/volumes/101/135/disk.0 Wed Apr 24 22:47:36 2013 [TM][I]: ExitCode: 0 Wed Apr 24 22:47:37 2013 [LCM][I]: New VM state is BOOT Wed Apr 24 22:47:37 2013 [VMM][I]: Generating deployment file: /srv/cloud/one/var/vms/135/deployment.1 Wed Apr 24 22:47:37 2013 [VMM][I]: ExitCode: 0 Wed Apr 24 22:47:37 2013 [VMM][I]: Successfully execute network driver operation: pre. Wed Apr 24 22:47:47 2013 [VMM][I]: Command execution fail: /srv/cloud/one/var/remotes/vmm/vmware/deploy /srv/cloud/one/var/vms/135/deployment.1 vmware01 135 vmware01 Wed Apr 24 22:47:47 2013 [VMM][D]: deploy: Successfully defined domain one-135. Wed Apr 24 22:47:47 2013 [VMM][E]: deploy: Error executing: virsh -c 'esx://vmware01/?no_verify=1auto_answer=1' start one-135 err: ExitCode: 1 Wed Apr 24 22:47:47 2013 [VMM][I]: out: Wed Apr 24 22:47:47 2013 [VMM][I]: error: Failed to start domain one-135 Wed Apr 24 22:47:47 2013 [VMM][I]: error: internal error Could not start domain: FileNotFound - File [101] 135/disk.0/disk.vmdk was not found Wed Apr 24 22:47:47 2013 [VMM][I]: Wed Apr 24 22:47:47 2013 [VMM][I]: ExitCode: 1 Wed Apr 24 22:47:47 2013 [VMM][I]: Failed to execute virtualization driver operation: deploy. Wed Apr 24 22:47:47 2013 [VMM][E]: Error deploying virtual machine Wed Apr 24 22:47:47 2013 [DiM][I]: New VM state is FAILED I double check on the ESXi box, File [101] 135/disk.0/disk.vmdk was actually there. /vmfs/volumes/5170ef35-aa800722-6bfa-80ee733ae308/135/disk.0 # ls -l -rw---1 oneadmin root 8589934592 Apr 24 14:47 CentOS-6.2-flat.vmdk -rw---1 oneadmin root515 Apr 24 14:47 disk.vmdk -rw-r--r--1 root root 0 Apr 24 14:47 one-135.vmsd -rw-r--r--1 root root875 Apr 24 14:47 one-135.vmx -rw-r--r--1 root root262 Apr 24 14:47 one-135.vmxf -rw-r--r--1 root root 38580 Apr 24 14:47 vmware.log So I looked into vmware.log, and found that it was looking for CentOS-6.2.vmdk. I did not have this file anywhere. 2013-04-24T14:47:35.839Z| vmx| DISK: OPEN scsi0:0 '/vmfs/volumes/5170ef35-aa800722-6bfa-80ee733ae308/135/disk.0/disk.vmdk' persistent R[] 2013-04-24T14:47:35.842Z| vmx| AIOGNRC: Failed to open '/vmfs/volumes/5170ef35-aa800722-6bfa-80ee733ae308/135/disk.0/CentOS-6.2.vmdk' : Could not find the file (60003) (0x2013). 2013-04-24T14:47:35.842Z| vmx| DISKLIB-VMFS : /vmfs/volumes/5170ef35-aa800722-6bfa-80ee733ae308/135/disk.0/CentOS-6.2.vmdk : failed to open (The system cannot find the file specified): AIOMgr_Open failed. Type 3 2013-04-24T14:47:35.842Z| vmx| DISKLIB-LINK : /vmfs/volumes/5170ef35-aa800722-6bfa-80ee733ae308/135/disk.0/disk.vmdk : failed to open (The system cannot find the file specified). 2013-04-24T14:47:35.842Z| vmx| DISKLIB-CHAIN : /vmfs/volumes/5170ef35-aa800722-6bfa-80ee733ae308/135/disk.0/disk.vmdk : failed to open (The system cannot find the file specified). 2013-04-24T14:47:35.842Z| vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/5170ef35-aa800722-6bfa-80ee733ae308/135/disk.0/disk.vmdk' with flags 0xa The system cannot find the file specified (25). 2013-04-24T14:47:35.842Z| vmx| Msg_Post: Error 2013-04-24T14:47:35.842Z| vmx|
Re: [one-users] Upgrade 4.0 Beta to 4.0 RC
Hi, The required gems should be installed by the packages or the install_gems script, so I've opened a ticket to see if we forgot about that one. Cheers [1] http://dev.opennebula.org/issues/1953 -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org On Wed, Apr 24, 2013 at 9:44 PM, Simon Boulet si...@nostalgeek.com wrote: Hi, I was struggling with the same issue updating from 3.9.80 (4.0 beta) to 3.9.90 (4.0 rc2). The onedb upgrade script would fail with a table user_pool is missing or empty.. If you're running OpenNebula with an sqlite DB make sure you have the sqlite3 ruby package installed (in my case libsqlite3-ruby) Simon On Sat, Apr 20, 2013 at 6:24 AM, Tao Craig t...@leadmesh.com wrote: Can you manually login to mysql by typing mysql at the command prompt (you may have to supply credentials)? If so, what happens if you do this: use opennebula; show tables; select * from user_pool; That should at least tell you if mysql is running, if that table exists and if it is populated. Also, be sure to Reply to All so others on this list can help. On Sat, Apr 20, 2013 at 2:52 AM, Ügyfélszolgálat (Manzol Kkt.) ugyfelszolga...@manzol.hu wrote: This is show me same... :S What do you think, that it can't connect mysql? 2013/4/20 Tao Craig t...@leadmesh.com Hi, Have you tried the following: onedb upgrade -v -S localhost -u oneadmin -p oneadmin -d opennebula That worked for me. On Sat, Apr 20, 2013 at 2:46 AM, Ügyfélszolgálat (Manzol Kkt.) ugyfelszolga...@manzol.hu wrote: Hi, I want to upgrade 4.0 Beta to 4.0 RC, and i read, that only run: # onedb -u opennebula -d opennebula But it don't work. It show me that: Database schema does not look to be created by OpenNebula: table user_pool is missing or empty. I checked manualy that the opennebula database have user_pool and other tables, and yes. I try it wrong password but it shows me like same. So i think it can't connect mysql. What should i do or what did i wrong? Thanks -- Manzol Kkt. Webtárhely Manzol http://www.webtarhely.manzol.hu/ 2117 Isaszeg, Mátyás király utca 29. Mobil: +36 30 543 7137 ___ 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 -- Ha elégedett szolgáltatásunkkal kérem pluszozza Google+ oldalunkat: https://plus.google.com/112673174823067308026/ (Jobb oldalt a térkép alatt) *Köszönjük!* * * *Tisztelettel,* *Ügyfélszolgálat* -- Manzol Kkt. Webtárhely Manzol http://www.webtarhely.manzol.hu/ 2117 Isaszeg, Mátyás király utca 29. Mobil: +36 30 543 7137 ___ 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 ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Relationship of cpu usages
Hello, HOST/CPU is the number of cores reported by the hypervisor x 100; 800 = 8 cpu cores. VM Template CPU is the number of Host CPU cores reserved for the VM. So cpu=0.5 means that the Host will allocate 50 from the CPU total for that VM. I have a new question about that. On http://opennebula.org/documentation:rel3.8:kvmg, I read about cgroups: So, thanks to cgroups a VM with CPU=0.5 will get half of the physical CPU cycles than a VM with CPU=1.0. How can a second VM get half of the physical CPU cycles of a first VM if the first VM is defined to use 100 % of the CPU cycles? Regards Christoph ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Cannot clone persistent image
From the log file I'm seeing that you are using shred drivers and I suppose you are using kvm. Can you check that in /var/lib/one/var/datastores/1 there are images that belong to oneadmin and other images which the owner is root? If this is the case check that your libvirt configuration has dynamic_ownership set to 0 and the correct user/group [1]: $ grep -vE '^($|#)' /etc/libvirt/qemu.conf user = oneadmin group = oneadmin dynamic_ownership = 0 [1] http://opennebula.org/documentation:rel3.8:kvmg#kvm_configuration On Thu, Apr 25, 2013 at 3:16 AM, Mohammad Fazli Ahmat Jalaluddin fazli@gmail.com wrote: Hi, I am new to OpenNebula. Currently the version of OpenNebula I am using is 3.8.3 I have some question regarding cloning persistent image: Why I cannot clone any persistent image (READY) and if I change the persistent image back to non-persistent, I still cannot clone it. Also, If I want to deploy a VM using a non-persistent image that was previously a persistent image, it FAILED with this error message: Error executing image transfer script: Error copying hpc-workstation1:/var/lib/one/ var/datastores/1/1a173d1d2b39cfd247a8438bfbbe4cae to onevmhost:/var/lib/one/var//datastores/0/116/disk.0 VM Log: Thu Apr 25 09:02:35 2013 [DiM][I]: New VM state is ACTIVE. Thu Apr 25 09:02:35 2013 [LCM][I]: New VM state is PROLOG. Thu Apr 25 09:02:36 2013 [TM][I]: Command execution fail: /var/lib/one/var/remotes/tm/shared/clone hpc-workstation1:/var/lib/one/var/datastores/1/1a173d1d2b39cfd247a8438bfbbe4cae onevmhost:/var/lib/one/var//datastores/0/116/disk.0 116 1 Thu Apr 25 09:02:36 2013 [TM][I]: clone: Cloning /var/lib/one/var/datastores/1/1a173d1d2b39cfd247a8438bfbbe4cae in onevmhost:/var/lib/one/var//datastores/0/116/disk.0 Thu Apr 25 09:02:36 2013 [TM][E]: clone: Command cd /var/lib/one/var/datastores/0/116; cp -r /var/lib/one/var/datastores/1/1a173d1d2b39cfd247a8438bfbbe4cae /var/lib/one/var/datastores/0/116/disk.0 failed: cp: cannot open `/var/lib/one/var/datastores/1/1a173d1d2b39cfd247a8438bfbbe4cae' for reading: Permission denied Thu Apr 25 09:02:36 2013 [TM][E]: Error copying hpc-workstation1:/var/lib/one/var/datastores/1/1a173d1d2b39cfd247a8438bfbbe4cae to onevmhost:/var/lib/one/var//datastores/0/116/disk.0 Thu Apr 25 09:02:36 2013 [TM][I]: ExitCode: 1 Thu Apr 25 09:02:36 2013 [TM][E]: Error executing image transfer script: Error copying hpc-workstation1:/var/lib/one/var/datastores/1/1a173d1d2b39cfd247a8438bfbbe4cae to onevmhost:/var/lib/one/var//datastores/0/116/disk.0 Thu Apr 25 09:02:36 2013 [DiM][I]: New VM state is FAILED Regards, Fazli ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Project Engineer OpenNebula - The Open Source Toolkit for Data Center Virtualization www.OpenNebula.org | jfon...@opennebula.org | @OpenNebula ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Sunstone buggy in RC 4.0
The new packages are uploaded since yesterday (3.9.90-2). We had some unforeseen problems that delayed the release. This release should fix the problems with sunstone from the previous packaging. Sorry for the delay. On Sat, Apr 20, 2013 at 11:06 AM, Jaime Melis jme...@opennebula.org wrote: Hi Tao and Alex, (joining Alex's thread into this one): As Daniel just mentioned this is an issue with Ruby 1.8.7, and since upgrading to Ruby 1.9 might be a bit cumbersome, what we're going to do is to release a new RC first thing next week (probably on Monday) fixing this bug with Ruby 1.8.7. For the moment we have removed the packages of the distributions which use Ruby 1.8.7. Thank you both for your quick feedback! http://dev.opennebula.org/issues/1936 cheers, Jaime On Sat, Apr 20, 2013 at 10:46 AM, Daniel Molina dmol...@opennebula.org wrote: Hi Tao, On 19 April 2013 19:43, Tao Craig t...@leadmesh.com wrote: Hi everybody, I just upgraded from 3.8.3 to 3.9.90 (CentOS) and my Sunstone interface is very unpredictable. When I first logged in, the Infrastructure tab was unresponsive and the Virtual Resources tab only displayed my datastores. After restarting oned and sunstone-server, my Infrastructure tab remains unresponsive and my Virtual Resources tab now only displays my images. All of my hosts, appear in oned.log as being successfully monitored however and I can not identify any errors. I have tried Firefox, Chrome, clearing my cache and private browsing. ... any ideas? Are you running ruby 1.8.7? There are some issues when using ruby 1.8.7 due to the way it handles Hashes. The tabs are loaded in a different order in this version and there are some dependencies among tabs that produce these errors.. Could you try upgrading ruby to 1.9? We will fix this for the final release. Cheers ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Daniel Molina Project Engineer OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula ___ 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 -- Javier Fontán Muiños Project Engineer OpenNebula - The Open Source Toolkit for Data Center Virtualization www.OpenNebula.org | jfon...@opennebula.org | @OpenNebula ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Upgrade 4.0 Beta to 4.0 RC
Try with these gems: sudo gem install sequel mysql Regards PS: Please reply to the mailing list -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org On Thu, Apr 25, 2013 at 11:38 AM, Webtárhely Manzol manzol...@gmail.comwrote: I am using mysql. So i don't know what is the problem... Carlos Martín Sánchez cmar...@opennebula.org wrote: Hi, The required gems should be installed by the packages or the install_gems script, so I've opened a ticket to see if we forgot about that one. Cheers [1] http://dev.opennebula.org/issues/1953 -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org On Wed, Apr 24, 2013 at 9:44 PM, Simon Boulet si...@nostalgeek.com wrote: Hi, I was struggling with the same issue updating from 3.9.80 (4.0 beta) to 3.9.90 (4.0 rc2). The onedb upgrade script would fail with a table user_pool is missing or empty.. If you're running OpenNebula with an sqlite DB make sure you have the sqlite3 ruby package installed (in my case libsqlite3-ruby) Simon On Sat, Apr 20, 2013 at 6:24 AM, Tao Craig t...@leadmesh.com wrote: Can you manually login to mysql by typing mysql at the command prompt (you may have to supply credentials)? If so, what happens if you do this: use opennebula; show tables; select * from user_pool; That should at least tell you if mysql is running, if that table exists and if it is populated. Also, be sure to Reply to All so others on this list can help. On Sat, Apr 20, 2013 at 2:52 AM, Ügyfélszolgálat (Manzol Kkt.) ugyfelszolga...@manzol.hu wrote: This is show me same... :S What do you think, that it can't connect mysql? 2013/4/20 Tao Craig t...@leadmesh.com Hi, Have you tried the following: onedb upgrade -v -S localhost -u oneadmin -p oneadmin -d opennebula That worked for me. On Sat, Apr 20, 2013 at 2:46 AM, Ügyfélszolgálat (Manzol Kkt.) ugyfelszolga...@manzol.hu wrote: Hi, I want to upgrade 4.0 Beta to 4.0 RC, and i read, that only run: # onedb -u opennebula -d opennebula But it don't work. It show me that: Database schema does not look to be created by OpenNebula: table user_pool is missing or empty. I checked manualy that the opennebula database have user_pool and other tables, and yes. I try it wrong password but it shows me like same. So i think it can't connect mysql. What should i do or what did i wrong? Thanks -- Manzol Kkt. Webtárhely Manzol http://www.webtarhely.manzol.hu/ 2117 Isaszeg, Mátyás király utca 29. Mobil: +36 30 543 7137 ___ 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 -- Ha elégedett szolgáltatásunkkal kérem pluszozza Google+ oldalunkat: https://plus.google.com/112673174823067308026/ (Jobb oldalt a térkép alatt) *Köszönjük!* * * *Tisztelettel,* *Ügyfélszolgálat* -- Manzol Kkt. Webtárhely Manzol http://www.webtarhely.manzol.hu/ 2117 Isaszeg, Mátyás király utca 29. Mobil: +36 30 543 7137 ___ 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 ___ 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] Problems with VM
Has anyone encountered such problems? I guess it's coming from Xen but I have no idea. If someone could help me it would be great. Best Regards Aridane 2013/4/24 Aridane Jesús Sarrionandia de León ajsa...@gmail.com Hi everyone, I've got open nebula installed and a server with Xen running and I have the following problem. I can create a VM with no problem, and reaches the state runn without error messages. The thing is that if I try to *stop *(onevm stop X) or *poweroff* (onevm poweroff X) it goes to *unk* state. This is the VM template I used (a lot of things are in comments until I get to solve the basic issues). CPU= 0.1 MEMORY = 64 DISK = [ #BUS=ide, IMAGE=ttylinux, #IMAGE_UNAME=oneadmin, READONLY=no#, #TARGET=xvda ] NIC= [ NETWORK=Small network] OS=[ KERNEL=/vmlinuz, INITRD=/initrd.img ] #RAW=[ DATA=builder = 'hvm' #shadow_memory = 8 # device_model = '/usr/lib/xen-default/bin/qemu-dm' # boot=\c\, # TYPE=xen ] TEMPLATE_ID=1 #CONTEXT = [ #hostname= $NAME, #ip_public = PUBLIC_IP, #files = /path/to/init.sh /path/to/id_dsa.pub, #target = hdc, #root_pubkey = id_dsa.pub, #username= opennebula, #user_pubkey = id_dsa.pub #] And this is the VM Log after the following commands: onevm create ttylinux_template.one onevm stop 13 onevm restart 13 onevm poweroff 13* *And this is the log*: * Wed Apr 24 16:36:20 2013 [DiM][I]: New VM state is ACTIVE. Wed Apr 24 16:36:20 2013 [LCM][I]: New VM state is PROLOG. Wed Apr 24 16:36:20 2013 [VM][I]: Virtual Machine has no context Wed Apr 24 16:36:21 2013 [TM][I]: clone: Cloning /var/lib/one/datastores/1/364fed6a7cfeeabca962d3fa160a8f60 in oneHost:/var/lib/one//datastores/0/13/disk.0 Wed Apr 24 16:36:21 2013 [TM][I]: ExitCode: 0 Wed Apr 24 16:36:21 2013 [LCM][I]: New VM state is BOOT Wed Apr 24 16:36:21 2013 [VMM][I]: Generating deployment file: /var/lib/one/vms/13/deployment.0 Wed Apr 24 16:36:21 2013 [VMM][I]: ExitCode: 0 Wed Apr 24 16:36:21 2013 [VMM][I]: Successfully execute network driver operation: pre. Wed Apr 24 16:36:23 2013 [VMM][D]: deploy: Credits set to 26 Wed Apr 24 16:36:23 2013 [VMM][I]: ExitCode: 0 Wed Apr 24 16:36:23 2013 [VMM][I]: Successfully execute virtualization driver operation: deploy. Wed Apr 24 16:36:23 2013 [VMM][I]: ExitCode: 0 Wed Apr 24 16:36:23 2013 [VMM][I]: Successfully execute network driver operation: post. Wed Apr 24 16:36:23 2013 [LCM][I]: New VM state is RUNNING Wed Apr 24 16:36:54 2013 [LCM][I]: New VM state is SAVE_STOP Wed Apr 24 16:36:54 2013 [VMM][I]: Command execution fail: /var/tmp/one/vmm/xen/save one-13 /var/lib/one//datastores/0/13/checkpoint oneHost 13 oneHost Wed Apr 24 16:36:54 2013 [VMM][E]: save: Command sudo /usr/sbin/xm save one-13 /var/lib/one//datastores/0/13/checkpoint failed: Error: xm save: Unable to create file /var/lib/one/datastores/0/13/checkpoi nt Wed Apr 24 16:36:54 2013 [VMM][E]: Could not save one-13 to /var/lib/one//datastores/0/13/checkpoint Wed Apr 24 16:36:54 2013 [VMM][I]: ExitCode: 1 Wed Apr 24 16:36:54 2013 [VMM][I]: Failed to execute virtualization driver operation: save. Wed Apr 24 16:36:54 2013 [VMM][E]: Error saving VM state: Could not save one-13 to /var/lib/one//datastores/0/13/checkpoint Wed Apr 24 16:36:54 2013 [LCM][I]: Fail to save VM state. Assuming that the VM is still RUNNING (will poll VM). Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-2-51712 but domain 2 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-3-51712 but domain 3 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-4-51712 but domain 4 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-5-51712 but domain 5 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-6-51712 but domain 6 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-7-768 but domain 7 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-8-768 but domain 8 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-9-768 but domain 9 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-2-51712 but domain 2 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-3-51712 but domain 3 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-4-51712 but domain 4 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-5-51712 but domain 5 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-6-51712 but domain 6 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-7-768 but domain 7 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-8-768 but domain 8 does not exist. Wed Apr 24 16:36:58 2013 [VMM][I]: Found interface tap-9-768 but domain 9 does not exist. Wed Apr 24 16:36:58
Re: [one-users] [one-ecosystem] Custom monitoring attributes in VM TEMPLATE
Hi Simon The criteria is that every thing to be consumed by OpenNebula should be in the Template, so the user can not modify it. Otherwise it may lead to OpenNebula incorrectly manage the object (e.g. remove or modify an attribute from the DISK section) or a security threat (e.g. a user modifying the SOURCE attribute to access someone else's image ) That is the main reason to place the system generated information in the TEMPLATE section, including monitoring info (you may bypass a billing system based on a probe). You are right that ERROR should be moved to USER TEMPLATE. The user may want to delete the error once she is notified... I've opened an issue for this [1] Now the other probes. This is for historical reasons. First versions of OpenNebula 1.0 (4 years ago!) did not have the functionality that we have now, and that lead to some inconsistencies in the data model. Probably CPU, NETRX... and the other probe results should be placed probably under a MONITOR section. During the development of the project we've opted to keep backwards compatibility over a more consistent data model. Probably we are wrong, but trying to keep the ecosystem and other adaption working from one release to other has been a priority for us. You've raised other interesting issue. First, we are sorry if we failed to engage in any discussion about the implementation of new issues. This is by no means because of a lack of interest but for the trillions of things we have to deal with. Your feedback is very valuable for us and always considered internally even if we fail to answer it. I'd say that comments to issues in redmine is a good place to link the discussions to specific features, new things and general aspects should go to the mailing list. However, this is probably not as fluent and agile as it should. We've done in the past IRC meetings that we may restore plan a regular hangout for example. We'll work on this and send a proposal to the mailing list. Thank you very much for feedback! [1] http://dev.opennebula.org/issues/1955 On Wed, Apr 24, 2013 at 4:24 PM, Simon Boulet si...@nostalgeek.com wrote: Hi, Custom monitoring attributes (extra attributes returned by the IM MONITOR or VMM POLL) are currently being added under the TEMPLATE section of the VM definition (from vm/VirtualMachine.cc:3165) Perhaps I'm wrong, but I am seeing the TEMPLATE section a block that containt the static definition of the VM (number of CPU, maximum memory, attached NICs, Disks, etc.). Ex. one could cache the information found in the TEMPLATE section on their frontend for a certain period of time. And it starts to make even more sense now that we have a USER_TEMPLATE section (since OpenNebula 4.0). Also errors are added under the TEMPLATE section. Wouldn't it make more sense if the custom monitoring attributes (and errors) were being reported directly under the VM section (just like the other monitoring attributes NETRX, NETTX, etc. are being reported). PS. Not sure if the ecosystem list is the right place for this. In the past I used the users list as well as the bug tracker to submit technical questions and discussions. And I find it difficult to be informed, sharing the vision and debating some implementations of upcoming features in OpenNebula. Simon ___ Ecosystem mailing list ecosys...@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/ecosystem-opennebula.org -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] [one-ecosystem] Custom monitoring attributes in VM TEMPLATE
Hi Ruben I like the idea of placing the monitoring information under a MONITOR section. I'm looking at scaling OpenNebula and adding some caching, having the TEMPLATE section to be static where the information would change only ex. when a VM resize operation is done (or at least, not being updated each time the VM is monitored). One could identify each sections lifetime ex. : USER_TEMPLATE = updated on vm.update or when a VM action fails (and the ERROR attribute is updated) TEMPLATE = updated on vm.resize, attach, detach, etc. operation MONITOR = updated on each poll (typically LASTPOLL + MONITORING_INTERVAL in oned.conf.. perhaps add a NEXTPOLL attribute to make caching lifetime easier) HISTORY_RECORDS = updated on VM state changes (one.vm.action) etc. Then perhaps vm.vmpool could return only the base VM attributes (nothing below the USER_TEMPLATE, TEMPLATE, MONITOR) and one would have to call one.vm.info to retrieve the full VM XML. I understand that would break backward compatibility. But I think it would be a huge improvement to ease caching of the OpenNebula information. I'd say that comments to issues in redmine is a good place to link the discussions to specific features, new things and general aspects should go to the mailing list. Users or ecosystem list? Simon On Thu, Apr 25, 2013 at 6:23 AM, Ruben S. Montero rsmont...@opennebula.orgwrote: Hi Simon The criteria is that every thing to be consumed by OpenNebula should be in the Template, so the user can not modify it. Otherwise it may lead to OpenNebula incorrectly manage the object (e.g. remove or modify an attribute from the DISK section) or a security threat (e.g. a user modifying the SOURCE attribute to access someone else's image ) That is the main reason to place the system generated information in the TEMPLATE section, including monitoring info (you may bypass a billing system based on a probe). You are right that ERROR should be moved to USER TEMPLATE. The user may want to delete the error once she is notified... I've opened an issue for this [1] Now the other probes. This is for historical reasons. First versions of OpenNebula 1.0 (4 years ago!) did not have the functionality that we have now, and that lead to some inconsistencies in the data model. Probably CPU, NETRX... and the other probe results should be placed probably under a MONITOR section. During the development of the project we've opted to keep backwards compatibility over a more consistent data model. Probably we are wrong, but trying to keep the ecosystem and other adaption working from one release to other has been a priority for us. You've raised other interesting issue. First, we are sorry if we failed to engage in any discussion about the implementation of new issues. This is by no means because of a lack of interest but for the trillions of things we have to deal with. Your feedback is very valuable for us and always considered internally even if we fail to answer it. I'd say that comments to issues in redmine is a good place to link the discussions to specific features, new things and general aspects should go to the mailing list. However, this is probably not as fluent and agile as it should. We've done in the past IRC meetings that we may restore plan a regular hangout for example. We'll work on this and send a proposal to the mailing list. Thank you very much for feedback! [1] http://dev.opennebula.org/issues/1955 On Wed, Apr 24, 2013 at 4:24 PM, Simon Boulet si...@nostalgeek.comwrote: Hi, Custom monitoring attributes (extra attributes returned by the IM MONITOR or VMM POLL) are currently being added under the TEMPLATE section of the VM definition (from vm/VirtualMachine.cc:3165) Perhaps I'm wrong, but I am seeing the TEMPLATE section a block that containt the static definition of the VM (number of CPU, maximum memory, attached NICs, Disks, etc.). Ex. one could cache the information found in the TEMPLATE section on their frontend for a certain period of time. And it starts to make even more sense now that we have a USER_TEMPLATE section (since OpenNebula 4.0). Also errors are added under the TEMPLATE section. Wouldn't it make more sense if the custom monitoring attributes (and errors) were being reported directly under the VM section (just like the other monitoring attributes NETRX, NETTX, etc. are being reported). PS. Not sure if the ecosystem list is the right place for this. In the past I used the users list as well as the bug tracker to submit technical questions and discussions. And I find it difficult to be informed, sharing the vision and debating some implementations of upcoming features in OpenNebula. Simon ___ Ecosystem mailing list ecosys...@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/ecosystem-opennebula.org -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - The Open Source
[one-users] CentOS 6.4 - 3.9.90-2 rpm installation problem with opennebula-server-3.9.90-2.x86_64.rpm
Hi,
when installing the new CentOS 6.4 rpm packages for OpenNebula 4 RC there's
a permission problem with opennebula-server-3.9.90-2.x86-64.rpm. It
complains about not being able to create the .ssh directory and the
public/private keys: Could not create directory '/var/lib/one/.ssh
I think line 307 in centos6.4.spec should be changed from:
/bin/chown -R oneadmin:oneadmin %{oneadmin_home}/.one
to
/bin/chown -R oneadmin:oneadmin %{oneadmin_home}
I've rebuild the rpm package and the permission problem is solved with this
mod.
Hope it helps!
Regards,
Miguel
--
*Miguel Ángel Álvarez Cabrerizo*
MACTO apps · cloud · security*
**Blog http://n40lab.wordpress.com
Skype n40lab
Email / Google Talk mcabrerizo at macto.es*
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] VNC problem: Failed to connect to server (code: 1006)
People, I up a VM, but when try conection whit VNC, I present the problem: Failed to connect to server (code: 1006) ?Any Ideas? 48 Aniversario de la Cujae, Una obra de la Revolucion Cubana | 2 de diciembre de 1964 | http://cujae.edu.cu Consulte la enciclopedia colaborativa cubana. http://www.ecured.cu ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] VNC problem: Failed to connect to server (code: 1006)
Hi, if you're using OpenNebula 3.8.3 1) Check that you've installed novnc (if not go to /usr/share/one and run ./install_novnc.sh) 2) If novnc is installed check if you have set 0.0.0.0 address in the Graphics section of your VM (you should insert a port also e.g 5901). 3) If you are running iptables try to stop the firewall maybe you need a rule to allow traffic. Regards, Miguel -- *Miguel Ángel Álvarez Cabrerizo* MACTO apps · cloud · security* **Blog http://n40lab.wordpress.com Skype n40lab Email mcabrerizo at macto.es* ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] [one-ecosystem] Custom monitoring attributes in VM TEMPLATE
Hi USER_TEMPLATE = updated on vm.update or when a VM action fails (and the ERROR attribute is updated) TEMPLATE = updated on vm.resize, attach, detach, etc. operation MONITOR = updated on each poll (typically LASTPOLL + MONITORING_INTERVAL in oned.conf.. perhaps add a NEXTPOLL attribute to make caching lifetime easier) HISTORY_RECORDS = updated on VM state changes (one.vm.action) etc. Exactly that would be perfect! Then perhaps vm.vmpool could return only the base VM attributes (nothing below the USER_TEMPLATE, TEMPLATE, MONITOR) and one would have to call one.vm.info to retrieve the full VM XML. As the DB is structured in XML blobs it is in fact faster for the oned daemon to deliver the whole thing and let the clients parse the XML. I understand that would break backward compatibility. But I think it would be a huge improvement to ease caching of the OpenNebula information. This has been a long debate within the team. If we go for this: 1.- This can not happen in the 4.0 timeframe as we are just fixing the last bugs and this would require touching to many parts now. 4.0 would be the perfect release as we are changing major... 2.- I think we can fix something in the onedb upgrade process to restructure the xml's 3.- This would only impact on custom applications on top of OpenNebula 4.- As we are sending the whole XML, probably we would not help on the caching... 5.- We need to address similar situations in other objects e.g.. MONITOR in hosts... Let's go like this: 1.- I've created an issue http://dev.opennebula.org/issues/1967 2.- We'll add a proposal there with the changes 3.- Then we can discuss if we want this change or not... if it'll break to many things... I'd say that comments to issues in redmine is a good place to link the discussions to specific features, new things and general aspects should go to the mailing list. Users or ecosystem list? Users Ruben Simon On Thu, Apr 25, 2013 at 6:23 AM, Ruben S. Montero rsmont...@opennebula.org wrote: Hi Simon The criteria is that every thing to be consumed by OpenNebula should be in the Template, so the user can not modify it. Otherwise it may lead to OpenNebula incorrectly manage the object (e.g. remove or modify an attribute from the DISK section) or a security threat (e.g. a user modifying the SOURCE attribute to access someone else's image ) That is the main reason to place the system generated information in the TEMPLATE section, including monitoring info (you may bypass a billing system based on a probe). You are right that ERROR should be moved to USER TEMPLATE. The user may want to delete the error once she is notified... I've opened an issue for this [1] Now the other probes. This is for historical reasons. First versions of OpenNebula 1.0 (4 years ago!) did not have the functionality that we have now, and that lead to some inconsistencies in the data model. Probably CPU, NETRX... and the other probe results should be placed probably under a MONITOR section. During the development of the project we've opted to keep backwards compatibility over a more consistent data model. Probably we are wrong, but trying to keep the ecosystem and other adaption working from one release to other has been a priority for us. You've raised other interesting issue. First, we are sorry if we failed to engage in any discussion about the implementation of new issues. This is by no means because of a lack of interest but for the trillions of things we have to deal with. Your feedback is very valuable for us and always considered internally even if we fail to answer it. I'd say that comments to issues in redmine is a good place to link the discussions to specific features, new things and general aspects should go to the mailing list. However, this is probably not as fluent and agile as it should. We've done in the past IRC meetings that we may restore plan a regular hangout for example. We'll work on this and send a proposal to the mailing list. Thank you very much for feedback! [1] http://dev.opennebula.org/issues/1955 On Wed, Apr 24, 2013 at 4:24 PM, Simon Boulet si...@nostalgeek.comwrote: Hi, Custom monitoring attributes (extra attributes returned by the IM MONITOR or VMM POLL) are currently being added under the TEMPLATE section of the VM definition (from vm/VirtualMachine.cc:3165) Perhaps I'm wrong, but I am seeing the TEMPLATE section a block that containt the static definition of the VM (number of CPU, maximum memory, attached NICs, Disks, etc.). Ex. one could cache the information found in the TEMPLATE section on their frontend for a certain period of time. And it starts to make even more sense now that we have a USER_TEMPLATE section (since OpenNebula 4.0). Also errors are added under the TEMPLATE section. Wouldn't it make more sense if the custom monitoring attributes (and errors) were being reported directly under the VM section (just like
