John Garbutt
bfdae32efb
We can hit issues with corrupted VHDs if we copy a VHD while XenServer is performing other operations. This happens because there are times when we copy the VHD chains while XenServer is still performing a coalesce of the VHD chain. In most cases, vhd-util should be able to safely repair any metadata corruption. It can copy the copy of the VHD footer at the front of the VHD file and add it at the bottom on the VHD file. There is no VM data loss, due to the way the coalesce happens, but the chain will be bigger than it would be both before and after the coalesce. This does not, however, ensure that snapshots are valid before uploading them to glance. But should you launch a corrupted snapshot, this change would fix up the snapshot, and allow it to boot correctly. Closes-Bug: #1362595 Change-Id: I88b737d7e97964a9db5ccf2c39dea7fd0701ead4
OpenStack Nova README ===================== OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs. OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file. Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities. To keep updated with new developments in the OpenStack project follow `@openstack <http://twitter.com/openstack>`_ on Twitter. To learn how to deploy OpenStack Nova, consult the documentation available online at: http://docs.openstack.org For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki: https://wiki.openstack.org/wiki/HypervisorSupportMatrix In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at: http://bugs.launchpad.net/nova Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at: https://git.openstack.org/cgit/openstack/nova Developers should also join the discussion on the mailing list, at: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests. Further developer focused documentation is available at: http://docs.openstack.org/developer/nova/ For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file. -- End of broadcast