<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<small>Here, this is slightly less ugly and still works:<br>
<br>
deploy_name=$(virsh --connect $LIBVIRT_URI --readonly dominfo
$deploy_id \<br>
| grep "Name:" | nawk '{print $2}')<br>
<br>
count=0<br>
while [ "$(virsh --connect $LIBVIRT_URI --readonly domstate
$deploy_name)" != "shut off" ]<br>
do <br>
sleep $POLL_INTERVAL<br>
if [ "$count" -gt "$TIMEOUT" ]<br>
then<br>
error_message "Timeout reached and VM $deploy_id is still
alive"<br>
echo "Timeout reached" >&2<br>
exit 1<br>
fi<br>
let count=count+$POLL_INTERVAL<br>
done<br>
</small><br>
<br>
On 05/18/2012 04:56 AM, Jaime Melis wrote:
<blockquote
cite="mid:CA+HrgRqZ8zNbHGAAS1BdxqOye4QtKZKG1+opVoxH=3zNo6oooQ@mail.gmail.com"
type="cite">
<pre wrap="">Hello Sean,
The shutdown script includes a timeout, when it's reached it assumes the VM is
still running. However it looks like the VM is indeed shutting down after that
timeout. I think that's why your vm is in such an ugly state.
Possible fixes:
* Disable the acpi popup in your VM [1][2]
* Install the *server* distribution, not the desktop.
* Try with the appliance we created [3]
* Increase the timeout in the shutdown script [4] (not recommended!!)
[1]
<a class="moz-txt-link-freetext" href="http://askubuntu.com/questions/66723/how-do-i-modify-the-power-options-in-ubuntu-11-10">http://askubuntu.com/questions/66723/how-do-i-modify-the-power-options-in-ubuntu-11-10</a>
[2]
<a class="moz-txt-link-freetext" href="http://www.liberiangeek.net/2012/04/disable-shutdown-restart-logout-prompts-in-ubuntu-12-04-precise-pangolin/">http://www.liberiangeek.net/2012/04/disable-shutdown-restart-logout-prompts-in-ubuntu-12-04-precise-pangolin/</a>
[3] <a class="moz-txt-link-freetext" href="http://appliances.c12g.com/Ubuntu-Server-12.04/">http://appliances.c12g.com/Ubuntu-Server-12.04/</a>
[4]
<a class="moz-txt-link-freetext" href="https://github.com/OpenNebula/one/blob/one-3.4/src/vmm_mad/remotes/kvm/shutdown#L27">https://github.com/OpenNebula/one/blob/one-3.4/src/vmm_mad/remotes/kvm/shutdown#L27</a>
<a class="moz-txt-link-rfc2396E" href="https://github.com/OpenNebula/one/blob/one-3.4/src/vmm_mad/remotes/kvm/shutdown"><https://github.com/OpenNebula/one/blob/one-3.4/src/vmm_mad/remotes/kvm/shutdown></a>
Regards,
Jaime
On Thu, May 17, 2012 at 6:43 PM, Sean Abbott <<a class="moz-txt-link-abbreviated" href="mailto:seabbott@akamai.com">seabbott@akamai.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:seabbott@akamai.com"><mailto:seabbott@akamai.com></a>> wrote:
So, I'm attempting to create a master linux client image from which I
can deploy new clients easily. I know that I'll eventually need to get
master contextualization. However, before I get there, I'm having problems.
I created a template that used a raw hard disk and an ubuntu boot cd to
create a working ubuntu 12.04 VM. Done, worked.
I used onevm saveas <vm-name> <disk-id> "ubuntu-base-image" to set up a
save.
I used onevm shutdown <vm-id> to shut it down.
At first, it appeared to work. I was watching the vm from VNC and it
popped up a window asking if I wanted to shut it down (I need to
research how to make that window not happen in ubuntu).
However. The VM transitioned to "unknown" state about 5 minutes later
(initially it was "shutdown"), and the log says that it didn't properly
finish shutdown:
Thu May 17 16:19:33 2012 [LCM][I]: New VM state is SHUTDOWN
Thu May 17 16:24:38 2012 [VMM][I]: Command execution fail:
/var/tmp/one/vmm/kvm/shutdown one-7 172.26.210.149 7 172.26.210.149
Thu May 17 16:24:38 2012 [VMM][E]: Timeout reached and VM one-7 is still alive
Thu May 17 16:24:38 2012 [VMM][I]: Timeout reached
Thu May 17 16:24:38 2012 [VMM][I]: ExitCode: 1
Thu May 17 16:24:38 2012 [VMM][I]: Failed to execute virtualization driver
operation: shutdown.
Thu May 17 16:24:38 2012 [VMM][E]: Error shuting down VM: Timeout reached
and VM one-7 is still alive
Thu May 17 16:24:38 2012 [LCM][I]: Fail to shutdown VM. Assuming that the VM
is still RUNNING (will poll VM).
Thu May 17 16:24:38 2012 [VMM][I]: ExitCode: 0
Thu May 17 16:24:38 2012 [VMM][I]: VM not found, setting to UNKNOWN
And, presumably because of this, my image status "locked" and there is
no data that has made it into the image.
Is the answer that I need to figure out how to make ubuntu do a
clean/fast ACPI shutdown before I can make this work, or is something
else afoot. Corollary question: has anyone managed to make ubuntu do a
clean ACPI shutdown with no intervention?
Thanks!
sean
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:Users@lists.opennebula.org"><mailto:Users@lists.opennebula.org></a>
<a class="moz-txt-link-freetext" href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a>
--
Jaime Melis
Project Engineer
OpenNebula - The Open Source Toolkit for Cloud Computing
<a class="moz-txt-link-abbreviated" href="http://www.OpenNebula.org">www.OpenNebula.org</a> <a class="moz-txt-link-rfc2396E" href="http://www.OpenNebula.org"><http://www.OpenNebula.org></a> | <a class="moz-txt-link-abbreviated" href="mailto:jmelis@opennebula.org">jmelis@opennebula.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:jmelis@opennebula.org"><mailto:jmelis@opennebula.org></a>
</pre>
</blockquote>
</body>
</html>