bff45b4d55
Currently users of KVM/QEMU must set libvirt_use_virtio_for_bridges to true to get a virtio based NIC, instead of the awful rtl8139 that QEMU defaults to. Switch libvirt_use_virtio_for_bridges to default to enabled, but ensure it only takes effect if libvirt_type is 'kvm' or 'qemu'. Although it is possible that some guest OS do not support virtio drivers, currently Nova hardcodes use of 'virtio' for disks, so this change doesn't make the current guest OS support situation worse. Obviously in the future, both NIC & disk models will have to be made fully configurable Change-Id: I7c0d306921f554ac2d06b5bdb1f9017ab7f9c643 Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
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 on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
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:
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:
Developers should also join the discussion on the mailing list, at:
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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast