Bug 487557 - libvirtd forgets about migrated guests when it is restarted
Summary: libvirtd forgets about migrated guests when it is restarted
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-26 17:52 UTC by Chris Lalancette
Modified: 2010-03-16 17:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-30 11:40:15 UTC
Embargoed:


Attachments (Terms of Use)

Description Chris Lalancette 2009-02-26 17:52:11 UTC
Description of problem:

There's a corner case with the new libvirtd feature to "remember" guests when it is restarted.  Take the following example:

1.  virDomainDefineXML on src
2.  virDomainStart on src
3.  virDomainMigrate on src -> migrates guest to dest
4.  Shut-down libvirtd on dest
5.  Restart libvirtd on dest

After step 5, you would expect libvirtd to "remember" the migrated guest, but at present, it does not.  DanB says this is because it is a "transient" guest, so doesn't have an /etc/libvirt/qemu config file.  It does, however, have a /var/run/libvirt/qemu state and pid file, so we could scan the entire directory looking for transient guests as well.

Comment 1 Daniel Berrangé 2009-05-27 16:00:47 UTC
Prototype fix posted

http://www.redhat.com/archives/libvir-list/2009-May/msg00573.html

Comment 2 Gerrit Slomma 2009-07-29 21:01:01 UTC
This problem still exists in libvirt-0.6.3-11.el5.x86_64.rpm from rhel5.4 beta.
Is there a plan to integrate the fix into the release?

Comment 3 Daniel Berrangé 2009-07-30 11:40:15 UTC
The redetection of transient VMs is now fixed in libvirt repos. The fix will be included in the forthcoming 0.7.0 release

http://libvirt.org/git/?p=libvirt.git;a=commit;h=56a46886ad4335b81daac32c86c77ccbcefa3e23


Note You need to log in before you can comment on or make changes to this bug.