Bug 537270

Summary: RFE: Automatically shutdown guests on host shutdown
Product: [Fedora] Fedora Reporter: Henrik Nordström <henrik>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: berrange, clalance, crobinso, dcantrell, itamar, jforbes, markmc, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-19 14:08:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Henrik Nordström 2009-11-13 00:49:55 UTC
Description of problem:

Currently libvirt only autostarts guests, it does not autostop guests on shutdown, causing guest corruption on host reboots.

Version-Release number of selected component (if applicable):

libvirt-0.8.1-16.fc12

How reproducible:

always

Steps to Reproduce:
1. Start a guest
2. Reboot the host
3. Start the guest again
  
Actual results:

Guest complains about unclean shutdown, checks filessytems etc. In worst case guest may even be corrupted.

Expected results:

Cleanly shut down guests before host is shutdown / rebooted.

Additional info:

A suggested init script doing this was posted on the list in July

https://www.redhat.com/archives/libvir-list/2009-July/msg00467.html

the script works for me with just a minor patch

export LC_ALL=C
instead of
LC_ALL=C


Additionally providing the option of saving & restoring the vm state instead of shutting down would be very nice, but making sure running guests are shut down is a good start.

Comment 1 Mark McLoughlin 2009-11-19 14:08:36 UTC
Thanks for the report, this has been discussed several times upstream and we have a bz tracking it

*** This bug has been marked as a duplicate of bug 444273 ***