[one-users] error in documentation
http://docs.opennebula.org/4.8/user/references/template.html#features-section In example there is used FEATURE tab, but should be FEATURES. Regards, Rolandas ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] CentOS 7 - KVM - OpenNebula 4.8 from Marketplace doesn't start
Much appreciated! Works now. Only there's a message upon boot: Failed to access perfctr msr (MSR c1 is 0) but I suppose that's a pure OS issue. Other than that, it seems to be all OK. Thanks! On 09/02/2014 02:18 PM, Javier Fontan wrote: Hi, I've just uploaded a new version of the image with the correct format. On Tue, Aug 26, 2014 at 11:52 AM, Pavel Tankov pavel.tan...@strategyobject.com wrote: We are going to convert it to a more compatible version and reupload. Hello, guys. Any progress on that? Thanks. On 08/21/2014 04:23 PM, Javier Fontan wrote: We found a problem with the format of that image. It only works with qemu = 1.10. We are going to convert it to a more compatible version and reupload. In case you have a machine with a newer qemu version you can use this command to convert it: $ qemu-img convert -f qcow2 -O qcow2 -o compat=0.10 orig_image dest_image Sorry for the inconveniences. On Thu, Aug 21, 2014 at 10:16 AM, Pavel Tankov pavel.tan...@strategyobject.com wrote: Hello Users, I have the following setup: Physical host: CentOS 6.5 (64 bit, of course), KVM, all set up following the Quickstart Guide here: http://docs.opennebula.org/4.8/design_and_installation/quick_starts/qs_centos_kvm.html Opennebula 4.8.0 I got from the Marketplace the image named CentOS 7 - KVM - OpenNebula 4.8. Imported it and it and created the template automatically for me. I modified the template to add my ssl public key to be able to login as root, added a network and pretty much that was it. I tried to instantiate the template, but the VM keeps getting into the FAILED status. Do you have any idea why it wouldn't start? Thanks in advance. Here is the VM log: BEGIN LOG Wed Jul 30 18:00:53 2014 [DiM][I]: New VM state is ACTIVE. Wed Jul 30 18:00:53 2014 [LCM][I]: New VM state is PROLOG. Wed Jul 30 18:00:56 2014 [LCM][I]: New VM state is BOOT Wed Jul 30 18:00:56 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Wed Jul 30 18:00:56 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:56 2014 [VMM][I]: Successfully execute network driver operation: pre. Wed Jul 30 18:00:57 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:57 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Wed Jul 30 18:00:57 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:57 2014 [VMM][I]: Successfully execute network driver operation: post. Wed Jul 30 18:00:57 2014 [LCM][I]: New VM state is RUNNING Thu Jul 31 14:03:18 2014 [LCM][I]: New VM state is SHUTDOWN Thu Jul 31 14:03:51 2014 [VMM][I]: ExitCode: 0 Thu Jul 31 14:03:51 2014 [VMM][I]: Successfully execute virtualization driver operation: shutdown. Thu Jul 31 14:03:51 2014 [VMM][I]: ExitCode: 0 Thu Jul 31 14:03:51 2014 [VMM][I]: Successfully execute network driver operation: clean. Thu Jul 31 14:03:51 2014 [LCM][I]: New VM state is EPILOG Thu Jul 31 14:03:51 2014 [DiM][I]: New VM state is DONE Thu Aug 7 12:09:20 2014 [DiM][I]: New VM state is ACTIVE. Thu Aug 7 12:09:20 2014 [LCM][I]: New VM state is PROLOG. Thu Aug 7 12:09:21 2014 [LCM][I]: New VM state is BOOT Thu Aug 7 12:09:21 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Thu Aug 7 12:09:21 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:21 2014 [VMM][I]: Successfully execute network driver operation: pre. Thu Aug 7 12:09:22 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:22 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Thu Aug 7 12:09:22 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:22 2014 [VMM][I]: Successfully execute network driver operation: post. Thu Aug 7 12:09:22 2014 [LCM][I]: New VM state is RUNNING Thu Aug 7 12:24:05 2014 [LCM][I]: New VM state is SHUTDOWN Thu Aug 7 12:24:15 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:24:15 2014 [VMM][I]: Successfully execute virtualization driver operation: shutdown. Thu Aug 7 12:24:15 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:24:15 2014 [VMM][I]: Successfully execute network driver operation: clean. Thu Aug 7 12:24:15 2014 [LCM][I]: New VM state is EPILOG Thu Aug 7 12:24:16 2014 [DiM][I]: New VM state is DONE Tue Aug 19 16:03:52 2014 [DiM][I]: New VM state is ACTIVE. Tue Aug 19 16:03:52 2014 [LCM][I]: New VM state is PROLOG. Tue Aug 19 16:03:53 2014 [LCM][I]: New VM state is BOOT Tue Aug 19 16:03:53 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute network driver operation: pre. Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute network driver operation: post. Tue Aug 19 16:03:53 2014 [LCM][I]: New VM state is RUNNING Tue Aug 19 16:05:37 2014 [LCM][I]: New VM state is CLEANUP. Tue Aug 19 16:05:37 2014 [DiM][I]: New VM state is
Re: [one-users] Fwd: Add New Storage Box
We have not tested that configuration but if you only use persistent images it may work. Make sure you don't try to do cold migrations as the checkpoint is saved to the system datastore and probably will get some time to be synchronized with the new node. On Tue, Aug 26, 2014 at 9:04 AM, Rhesa Mahendra rh...@lintasmediadanawa.com wrote: Datastore 0 and datastore 2 will be synchronized frontend + nodes (we just use persistent image) so i think datastore 0 just synchronized symbolic link. If we have problem maybe existing storage box (datastore 1) broken, all vm used new storage box ( datastore 100) will not impact with datastore 1 because datastore 0 shared and synchronized across frontend +nodes. it possible? Rhesa On 08/26/2014 01:52 PM, Jaime Melis wrote: Rhesa, the problem is datastore 0, it's the system datastore. If you move it to the local nodes, it will not be shared and synchronized across the nodes, therefore you will lose many benefits like live-migration and instant persintant image VM deployment. Why is it that you want to move datastore 0 to the frontend + nodes? On Tue, Aug 26, 2014 at 8:44 AM, Rhesa Mahendra rh...@lintasmediadanawa.com wrote: Jaime, Thanks for your reply, now datastore 0 and datastore 2 are in existing storage box, mounted in frontend + nodes, we want to move datastore 0 and datastore 2 from existing storage box to frontend + nodes, could it be done? So in existing storage box just have datastore 1 and in new storage box just have datastore 100. Rhesa. On 08/26/2014 01:34 PM, Jaime Melis wrote: Hi, I don't entirely understand the difference between both options, could you explain in more detail what you mean by distributing the datastore to all the nodes? Assuming your configuration is as follows: NFS Server exports datastores 0 and 1 - Mounted in Frontend + Nodes I recommend the following option: - Create a new Image datastore (it will have ID = 100, in this example we will assume it has ID: 100) - Create a new exports directive in your new storage box, for example /storage/datastores/100 - Mount that mountpoint in all the nodes including the frontend in the following path: /var/lib/one/datastores/100 Now you can register more images in the new datastore (ID: 100), and since they are all persistent they will not take space in the system datastore (ID: 0) Best regards, Jaime On Tue, Aug 26, 2014 at 6:05 AM, Rhesa Mahendra rh...@lintasmediadanawa.com wrote: Guys, please help. Original Message Subject: Add New Storage Box Date: Mon, 25 Aug 2014 16:21:13 +0700 From: Rhesa Mahendra rh...@lintasmediadanawa.com rh...@lintasmediadanawa.com To: users@lists.opennebula.org users@lists.opennebula.org users@lists.opennebula.org, Javier Fontan jfon...@opennebula.org jfon...@opennebula.org Guys, We have plan to add a new storage box, Our existing storage : /var/lib/one/datastore/0 = system /var/lib/one/datastore/1 = image /var/lib/one/datastore/2 = file All type are from one storage box. We did internal discuss and we get result with two options: 1. We add a new storage box as an image type and define it as /var/lib/one/datastore/3 = image2. Or 2. We will distribute /var/lib/one/datastore/0 = system and /var/lib/one/datastore/2 = file to all nodes (all node are synced), then we add the new storage box as /var/lib/one/datastore/3 = image2 So with this second option, the nodes only mount two path from the storage box (/var/lib/one/datastore/1 = image [from existing storage box] and /var/lib/one/datastore/3 = image2 [from new storage box]). All the images are persistent Please give us some advise with pros and cons within this two options, thanks. Rhesa ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple 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 Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Fwd: Add New Storage Box
thanks for your answer, i will be test and report to you, On 09/03/2014 04:09 PM, Javier Fontan wrote: We have not tested that configuration but if you only use persistent images it may work. Make sure you don't try to do cold migrations as the checkpoint is saved to the system datastore and probably will get some time to be synchronized with the new node. On Tue, Aug 26, 2014 at 9:04 AM, Rhesa Mahendra rh...@lintasmediadanawa.com mailto:rh...@lintasmediadanawa.com wrote: Datastore 0 and datastore 2 will be synchronized frontend + nodes (we just use persistent image) so i think datastore 0 just synchronized symbolic link. If we have problem maybe existing storage box (datastore 1) broken, all vm used new storage box ( datastore 100) will not impact with datastore 1 because datastore 0 shared and synchronized across frontend +nodes. it possible? Rhesa On 08/26/2014 01:52 PM, Jaime Melis wrote: Rhesa, the problem is datastore 0, it's the system datastore. If you move it to the local nodes, it will not be shared and synchronized across the nodes, therefore you will lose many benefits like live-migration and instant persintant image VM deployment. Why is it that you want to move datastore 0 to the frontend + nodes? On Tue, Aug 26, 2014 at 8:44 AM, Rhesa Mahendra rh...@lintasmediadanawa.com mailto:rh...@lintasmediadanawa.com wrote: Jaime, Thanks for your reply, now datastore 0 and datastore 2 are in existing storage box, mounted in frontend + nodes, we want to move datastore 0 and datastore 2 from existing storage box to frontend + nodes, could it be done? So in existing storage box just have datastore 1 and in new storage box just have datastore 100. Rhesa. On 08/26/2014 01:34 PM, Jaime Melis wrote: Hi, I don't entirely understand the difference between both options, could you explain in more detail what you mean by distributing the datastore to all the nodes? Assuming your configuration is as follows: NFS Server exports datastores 0 and 1 - Mounted in Frontend + Nodes I recommend the following option: - Create a new Image datastore (it will have ID = 100, in this example we will assume it has ID: 100) - Create a new exports directive in your new storage box, for example /storage/datastores/100 - Mount that mountpoint in all the nodes including the frontend in the following path: /var/lib/one/datastores/100 Now you can register more images in the new datastore (ID: 100), and since they are all persistent they will not take space in the system datastore (ID: 0) Best regards, Jaime On Tue, Aug 26, 2014 at 6:05 AM, Rhesa Mahendra rh...@lintasmediadanawa.com mailto:rh...@lintasmediadanawa.com wrote: Guys, please help. Original Message Subject:Add New Storage Box Date: Mon, 25 Aug 2014 16:21:13 +0700 From: Rhesa Mahendra rh...@lintasmediadanawa.com mailto:rh...@lintasmediadanawa.com To: users@lists.opennebula.org mailto:users@lists.opennebula.org users@lists.opennebula.org mailto:users@lists.opennebula.org, Javier Fontan jfon...@opennebula.org mailto:jfon...@opennebula.org Guys, We have plan to add a new storage box, Our existing storage : /var/lib/one/datastore/0 = system /var/lib/one/datastore/1 = image /var/lib/one/datastore/2 = file All type are from one storage box. We did internal discuss and we get result with two options: 1. We add a new storage box as an image type and define it as /var/lib/one/datastore/3 = image2. Or 2. We will distribute /var/lib/one/datastore/0 = system and /var/lib/one/datastore/2 = file to all nodes (all node are synced), then we add the new storage box as /var/lib/one/datastore/3 = image2 So with this second option, the nodes only mount two path from the storage box (/var/lib/one/datastore/1 = image [from existing storage box] and /var/lib/one/datastore/3 = image2 [from new storage box]). All the images are persistent Please give us some advise with pros and cons within this two options, thanks. Rhesa ___ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer
Re: [one-users] OpenNebula Puppet resource types available
Thanks Martin! I've added both links to the community wiki: http://community.opennebula.org/start?#system_configuration_management On Fri, Aug 8, 2014 at 9:20 AM, Martin Alfke tux...@gmail.com wrote: Hi, I have created a set of OpenNebula Puppet resource type which allow you to manage your OpenNebula installation using Puppet DSL only. The code can be found on github (https://github.com/epost-dev/opennebula-puppet-module). Example usage is on my blog (http://tuxmea.blogspot.de/2014/08/opennebula-puppet-types-and-providers.html). Please report issues directly at the github project (https://github.com/epost-dev/opennebula-puppet-module/issues). I am still looking for someone who can do a review and code improvements. - Martin ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] 2 problems in VMs
Here is the problem: Wed Aug 20 11:42:39 2014 [ReM][E]: Req:3216 UID:5 TemplateInstantiate result FAILURE [TemplateInstantiate] Error allocating a new virtual machine. DISK 0: User 5 does not own an image with name: CentOS-6.5_x86_64 . Set IMAGE_UNAME or IMAGE_UID of owner in DISK. You need to change IMAGE=.. to IMAGE_UID and the ID number or add IMAGE_UNAME with the owner of that image. On Wed, Aug 20, 2014 at 8:19 AM, Sudeep Narayan Banerjee snbaner...@iitgn.ac.in wrote: Dear Javier, This is the oned.log when user snbanerjee(myself) is trying to instantiate the template CentOS-6.5 from my GUI LDAP account. [oneadmin@front ~]$ tail -f /var/log/one/oned.log Wed Aug 20 11:42:39 2014 [ReM][D]: Req:4288 UID:5 TemplateInfo invoked, 33 Wed Aug 20 11:42:39 2014 [ReM][D]: Req:4288 UID:5 TemplateInfo result SUCCESS, VMTEMPLATEID33/... Wed Aug 20 11:42:39 2014 [ReM][D]: Req:3216 UID:5 TemplateInstantiate invoked, 33, , false, DESCRIPTION=Very sm... Wed Aug 20 11:42:39 2014 [InM][D]: Host nc2 (19) successfully monitored. Wed Aug 20 11:42:39 2014 [ONE][E]: DISK 0: User 5 does not own an image with name: CentOS-6.5_x86_64 . Set IMAGE_UNAME or IMAGE_UID of owner in DISK. Wed Aug 20 11:42:39 2014 [ReM][E]: Req:3216 UID:5 TemplateInstantiate result FAILURE [TemplateInstantiate] Error allocating a new virtual machine. DISK 0: User 5 does not own an image with name: CentOS-6.5_x86_64 . Set IMAGE_UNAME or IMAGE_UID of owner in DISK. Wed Aug 20 11:42:52 2014 [AuM][D]: Message received: AUTHENTICATE SUCCESS 1108 - - [oneadmin@front ~]$ oneimage show 35 IMAGE 35 INFORMATION ID : 35 NAME : CentOS-6.5_x86_64 USER : oneadmin GROUP : oneadmin DATASTORE : default TYPE : OS REGISTER TIME : 08/11 10:32:36 PERSISTENT : No SOURCE : /var/lib/one//datastores/1/89fc59d8a0382ab679df53f3c6c4627c PATH : http://appliances.c12g.com/CentOS-6.5/centos6.5.qcow2.gz SIZE : 267M STATE : rdy RUNNING_VMS: 0 PERMISSIONS OWNER : um- GROUP : um- OTHER : um- IMAGE TEMPLATE DEV_PREFIX=hd DRIVER=qcow2 VIRTUAL MACHINES Regards, Sudeep On Mon, Aug 18, 2014 at 1:47 PM, Javier Fontan jfon...@opennebula.org wrote: Do you get any extra information on oned.log? Maybe the user does not have permission to use a network or the template itself. On Mon, Aug 11, 2014 at 8:20 AM, Sudeep Narayan Banerjee snbaner...@iitgn.ac.in wrote: Dear Valentin, I am using 4.6.2 version. I did from CLI and GUI and checked that is um- for all owner,group,others I also tried by changing the group; chgrp from oneadmin to users but no luck. Users is the group that carries all the LDAP users. The only way it works, if I manually change the ownership of the username. But we have our LDAP users to directly login and use. Is that the only way to manually enter each everyone's ownership!?! Regards, Sudeep On Mon, Aug 11, 2014 at 11:45 AM, Valentin Bud valentin@gmail.com wrote: Hello Sudeep, I don't know what version of OpenNebula are you using. I have tested on my setup, which uses 4.4. The following might not apply in your case. See inline. [oneadmin@front ~]$ oneimage chmod 33 664 [oneadmin@front ~]$ oneimage show 33 IMAGE 33 INFORMATION ID : 33 NAME : win7_sys USER : oneadmin GROUP : oneadmin DATASTORE : default TYPE : OS REGISTER TIME : 07/30 14:49:49 PERSISTENT : No SOURCE : /var/lib/one//datastores/1/0f72c7f0cd7fdc78f53b4fdbd2edb008 PATH : /home/wind.qcow2 SIZE : 9G STATE : rdy RUNNING_VMS: 0 PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- IMAGE TEMPLATE DEV_PREFIX=hd DRIVER=qcow2 According to the above output it seems like oneimage chmod didn't change the permissions. I think they should resemble the following: PERMISSIONS OWNER : um- GROUP : um- OTHER : u-- Can you try chmod-ing again, if it still doesn't work maybe it's a bug. Best, Valentin -- Thanks Regards, Sudeep Narayan Banerjee ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan -- Thanks Regards, Sudeep Narayan Banerjee -- Javier Fontán Muiños Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan
Re: [one-users] Default Attributes
I've just tried the RAW parameter in the driver conf and works OK. Make sure you restart oned as the default values are read by oned and not by the driver itself. Also I had to change the line to this to make it work: RAW = osbootmenu enable='yes'//os On Fri, Aug 29, 2014 at 2:28 PM, Stefan Kooman ste...@bit.nl wrote: Hi, I'm trying to get some Default Attributes for kvm [1], i.e. default bootmenu in vm's: RAW = osbootmenu enable=\'yes\'//os entry in vmm_exec_kvm.conf. I've tried old and new syntax, see [2] but it's not working for newly created vm's. I'm running ONE 4.8. I've synced all the hosts and restarted opennebula (if at all needed). This extra bit of XML is not included in the domain XML's. Any hints? Gr. Stefan [1]: http://docs.opennebula.org/4.8/administration/virtualization/kvmg.html?highlight=kvm#default-attributes [2]: http://dev.opennebula.org/issues/2951 -- | BIT BV http://www.bit.nl/Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Default Attributes
Quoting Javier Fontan (jfon...@opennebula.org): I've just tried the RAW parameter in the driver conf and works OK. Make sure you restart oned as the default values are read by oned and not by the driver itself. Also I had to change the line to this to make it work: RAW = osbootmenu enable='yes'//os Thanks, that did the trick. Obviously I didn't try all combinations ;). Gr. Stefan -- | BIT BV http://www.bit.nl/Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] VMs stuck in pending
Your datastore has this parameter: CLONE_TARGET=SELF That's why it is checking the storage in the images datastore. It thinks the clone is made in the same datastore as the origin image. You have to set it to SYSTEM so it knows you copy the file to the system datastore. On Fri, Aug 22, 2014 at 5:25 PM, Simon Vera-Schockner svera...@akamai.com wrote: Hey all, I've been scratching my head against this one for a while, all my VMs are stuck in a pending mode. I checked sched.log to see why and got this: Fri Aug 22 15:20:47 2014 [VM][D]: Pending/rescheduling VM and capacity requirements: VM CPU Memory System DS Image DS 418 10 1048576 236 DS 100: 20 DS 101: 0 419 10 1048576 236 DS 100: 20 DS 101: 0 Fri Aug 22 15:20:47 2014 [HOST][D]: Discovered Hosts (enabled): 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 246 247 248 249 250 251 252 253 254 255 256 259 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 316 317 318 319 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 Fri Aug 22 15:20:47 2014 [SCHED][I]: VM 418: Image Datastore 100 does not have enough free storage. Fri Aug 22 15:20:47 2014 [SCHED][I]: VM 419: Image Datastore 100 does not have enough free storage. Fri Aug 22 15:20:47 2014 [SCHED][I]: Scheduling Results: This is the datastore in question that it's failing on one-master:~$ onedatastore show 100 DATASTORE 100 INFORMATION ID : 100 NAME : qcow2ssh USER : oneadmin GROUP : oneadmin CLUSTER: - TYPE : IMAGE DS_MAD : fs TM_MAD : qcow2ssh BASE PATH : /var/lib/one//datastores/100 DISK_TYPE : FILE DATASTORE CAPACITY TOTAL: : 233.7G FREE: : 119.6G USED: : 2.4G LIMIT: : - PERMISSIONS OWNER : uma GROUP : u-- OTHER : u-- DATASTORE TEMPLATE CLONE_TARGET=SELF DISK_TYPE=FILE DS_MAD=fs LN_TARGET=NONE TM_MAD=qcow2ssh IMAGES 4 11 13 15 I checked VirtualMachineXML.cc and noticed it looped through all datastores to determine if there was enough capacity. If the virtual machine isn't being deployed to an image datastore, why does it check the capacity, and subsequently cause my vm not to be deployed? Manually deploying using onevm deploy works just fine. Thanks, Simon ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
