** Description changed: + This feature will cause an ACPI event to be sent to the system while + shutting down, and the acpid running inside the system can catch the + event, thus giving the system a chance to shutdown cleanly. + [Impact] - * VMs being shutdown with any signal/notification from the The + * VMs being shutdown with any signal/notification from the The hypervisor level, services running inside VMs have no chance to perform a clean shutoff [Test Case] - * 1. stop a VM - 2. the VM is shutdown without any notification + * 1. stop a VM + 2. the VM is shutdown without any notification + + The can be easily seen by ssh into the system before shutting down. With + the patch in place, the ssh session will be close during shutdown, + because the sshd has the chance to close the connection before being + brought down. Without the patch, the ssh session will just hang there + for a while until timeout, because the connection is not promptly + closed. + + + To leverage the clean shutdown feature, one can create a file named /etc/acpi/events/power that contains the following: + + event=button/power + action=/etc/acpi/power.sh "%e" + + Then create a file named /etc/acpi/power.sh that contains whatever required to gracefully shutdown a particular server (VM). + With the apicd running, shutdown of the VM will cause the rule in /etc/acpi/events/power to trigger the script in /etc/acpi/power.sh, thus cleanly shutdown the system. + [Regression Potential] - * none + * none - Currently in libvirt stop and delete operations simply destroy the - underlying VM. Some GuestOS's do not react well to this type of - power failure, and it would be better if these operations followed the - same approach a a soft_reboot and give the guest a chance to shutdown - gracefully. Even where VM is being deleted, it may be booted from a - volume which will be reused on another server. + Currently in libvirt stop and delete operations simply destroy the underlying VM. Some GuestOS's do not react well to this type of power failure, and it would be better if these operations followed the same approach a a soft_reboot and give the guest a chance to shutdown gracefully. Even where VM is being deleted, it may be booted from a volume which will be reused on another server.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1196924 Title: Stop and Delete operations should give the Guest a chance to shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1196924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
