Hi,
I am experiencing a strange behaviour, VMs regularly goes into POWEROFF state automatically and then I have to manually Resume them all the time.
Any reason why this is happening?
Regards,
Arshad
Hi,
I think you should post VM’s log for investigate easier.
Regards,
Thanks for replying vynt.
below is the log:
Tue Jul 26 15:57:57 2016 [Z0][LCM][I]: New VM state is RUNNING
Tue Jul 26 16:03:07 2016 [Z0][DiM][I]: New VM state is POWEROFF
Tue Jul 26 16:17:24 2016 [Z0][DiM][I]: New VM state is ACTIVE.
Tue Jul 26 16:17:26 2016 [Z0][LCM][I]: New VM state is BOOT_POWEROFF
Tue Jul 26 16:17:26 2016 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/29/deployment.16
Tue Jul 26 16:17:27 2016 [Z0][VMM][I]: ExitCode: 0
Tue Jul 26 16:17:27 2016 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Tue Jul 26 16:17:32 2016 [Z0][VMM][D]: deploy: Credits set to 256
Tue Jul 26 16:17:32 2016 [Z0][VMM][I]: ExitCode: 0
Tue Jul 26 16:17:32 2016 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Tue Jul 26 16:17:32 2016 [Z0][VMM][I]: ExitCode: 0
Tue Jul 26 16:17:32 2016 [Z0][VMM][I]: Successfully execute network driver operation: post.
Tue Jul 26 16:17:32 2016 [Z0][LCM][I]: New VM state is RUNNING
Tue Jul 26 16:22:42 2016 [Z0][DiM][I]: New VM state is POWEROFF
Regards,
Arshad
Is there any hint can be seen via VNC console connected to such VM?
I am not using any VNC console.
Regards,
Arshad Shaikh
What OS are you trying to run inside VM and what amount of resources were assigned to that VM? I would assume that VM goes into poweroff state because of luck of resources for running that OS and/or software inside VM.
I am running Ubuntu inside the VMs and the capacity of the VMs is 1GB. Please let me know if you need any other information. Actually I am very new to open-nebula so facing issues with smallest of things.
Regards,
Arshad
1 GB of what? Disk space or RAM? Could you try to create VM with 1 core, 2 GB of RAM and 10 GB of disk space to see if VM will run in such configuration?
