Bug 743030 - autostart behavior after migration unclearly defined
Summary: autostart behavior after migration unclearly defined
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-03 16:06 UTC by dann frazier
Modified: 2016-03-23 13:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 13:59:42 UTC

Attachments (Terms of Use)
Document current behavior (699 bytes, patch)
2011-10-03 16:06 UTC, dann frazier 		no flags Details | Diff
Document current behavior, as determined through experimentation w/ kvm (724 bytes, patch)
2011-10-03 16:14 UTC, dann frazier 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Description dann frazier 2011-10-03 16:06:12 UTC 
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:
Comment 1 dann frazier 2011-10-03 16:14:23 UTC 
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.
Comment 2 Eric Blake 2011-10-03 16:18:00 UTC 
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.
Comment 3 Cole Robinson 2016-03-23 13:59:42 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.