| Summary: | autostart behavior after migration unclearly defined | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | dann frazier <dannf> | ||||||
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | ||||||
| Status: | CLOSED DEFERRED | QA Contact: | |||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | unspecified | CC: | crobinso, eblake, xen-maint | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-03-23 13:59:42 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 526097 [details]
Document current behavior, as determined through experimentation w/ kvm
Oops - hadn't saved my latest changes yet in the first patch.
Would you mind posting this patch on libvir-list? Also, I think that what we should really be doing is enhancing the v3 migration protocol to send autostart as part of the cookie, so that it properly migrates from source to destination, rather than locking the poor behavior in stone by documenting that autostart doesn't migrate. Dan indicated here at one point that maybe we shouldn't mirror autostart: https://www.redhat.com/archives/libvir-list/2010-August/msg00346.html The proposed API docs addition though may not be entirely accurate, I believe for xend autostart is strictly a domain config setting. |
Created attachment 526093 [details] Document current behavior Description of problem: The documentation doesn't clearly define what affect migration has on the autostart setting. Version-Release number of selected component (if applicable): 0.8.8 How reproducible: N/A Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: