The libvirt.xml file is written on initial boot of the instance and
may not reflect the current state of the vm if volumes have been
attached. If the libvirt definition of the vm has been lost, it is
safer to regenerate it rather than attempt to load it from the
outdated file. This should properly bring back vms with attached
volumes.
Reviewed: https:/ /review. openstack. org/15153 github. com/openstack/ nova/commit/ b22c3302ccea6b4 b9e685640accbfd bb2856d460
Committed: http://
Submitter: Jenkins
Branch: master
commit b22c3302ccea6b4 b9e685640accbfd bb2856d460
Author: Vishvananda Ishaya <email address hidden>
Date: Wed Oct 31 13:42:12 2012 -0700
libvirt: Regenerates xml instead of using on-disk
The libvirt.xml file is written on initial boot of the instance and
may not reflect the current state of the vm if volumes have been
attached. If the libvirt definition of the vm has been lost, it is
safer to regenerate it rather than attempt to load it from the
outdated file. This should properly bring back vms with attached
volumes.
Fixes bug 1073720
Change-Id: Iaa754700a149f0 9fc0c022fa664c0 6ad17f505f5