Hi.
The shutdown make a copy of a Running machine (after make a shutdown)
is... like a ordered shutdown
onevm delete, just destroy a VM (not make a copy, therefore is necesary
make de scp manual to keep the lasted VM)
For example.
imagine that:
you, in 2011, make a image and upload to openebula repository
(oneimage create ...). That image is a empty OS
after, you instanciate that image, and install some app (like tomcat,
for example)
your machine is running during 2011, and in 2012 (365 days later) you do
the following command:
onevm delete VM-ID
Now, you LOST your work during 365 days. Because OpenNebula assumes,
that not need make a copy
If, instead delete, you use "onevm shutdown VM-ID". OpenNebula update
your repository image. Now you have at local repository an image updated
365 days.
Hope that help :)
El 05/06/12 13:51, Mohsen Amini escribió:
Thank you for the comprehensive response.
May I ask what is the difference of
onevm shutdown
and
onevm delete
?
Thanks
--------
Mohsen Amini Salehi
PhD Student
CLOUDS Lab,
Room 5.30A, ICT building,
Department of Computing and Information Systems,
Melbourne University,
http://www.csse.unimelb.edu.au/~mohsena
<http://www.csse.unimelb.edu.au/%7Emohsena>
On Tue, Jun 5, 2012 at 8:05 PM, Alejandro Feijoo Fraga
<[email protected] <mailto:[email protected]>> wrote:
The problem is at kvm dom0 (not opennebula) i have a similar
problem some times... but i dont know how solve...
in my case. when that happend i just return manually the image to
the repository.
for example, if the image disk is 111, the VM is 4444 and the dom0
is 99.99.99.99 i do the following
as oneadmin
oneimage show 111 | grep SOURCE
that return the path, similar like that:
/srv/cloud/one/var/images/5963e9e0f2ed9524e90c3b4c1d8b01ab
then make a backup (backup are your friend)
cp /srv/cloud/one/var/images/5963e9e0f2ed9524e90c3b4c1d8b01ab
/srv/cloud/one/var/images/5963e9e0f2ed9524e90c3b4c1d8b01ab.bk
now, i can shutdown the VM
ssh VM && shutdown -h now
check if at dom0 the VM is running (KVM)
virsh list | grep one-4444
(if no output, jump to scp command)
else do: virsh destroy one-4444 (or destroy VMID)
and after retreive the image:
scp 99.99.99.99:/path/to/image/4444/images/disk.0
/srv/cloud/one/var/images/5963e9e0f2ed9524e90c3b4c1d8b01ab
usually disk.0 is the image correct to backup, but see
deployment.0 file to see if you need backup other disk
(deployment.0 file is at disk.0 directory)
at the last, delete VM under OpenNebula (onevm delete 4444)
Sure you yet know the steps, sorry 4 the possible spam :)
keep in touch to see if anybody can resolve the problem to stop an
unstoppable VM.
El 05/06/12 10:42, Mohsen Amini escribió:
Hello everybody,
I came to know that onevm shutdown <vmid> does not work.
In fact, in the begining the VM goes to the "shutdown" state but
after some time it again changes to "runn".
Can someone help me on this issue?
Regards,
--------
Mohsen Amini Salehi
PhD Student
CLOUDS Lab,
Room 5.30A, ICT building,
Department of Computing and Information Systems,
Melbourne University,
http://www.csse.unimelb.edu.au/~mohsena
<http://www.csse.unimelb.edu.au/%7Emohsena>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
