mirror of
https://github.com/GNS3/gns3-server.git
synced 2024-11-16 16:54:51 +02:00
d926a713b9
Some cloud providers (example, AWS EC2 for non-metal instances) do not support nested virtualization, as well as some hypervisors (example, VirtualBox prior to 6.x, Hyper-V on AMD). Option `--without-kvm` can be used to disable hardware acceleration in these scenarios. Otherwise, user will receive error when trying to start Qemu-based devices. Commit also: replace `enable_kvm` and `require_kvm` with newer config options (`enable_hardware_acceleration` and `require_hardware_acceleration`); and do some code refactors. One can argue that, instead of prividing option `--without-kvm`, we should check if system supports KVM and enable/disable hardware acceleration accordingly. However, there is the case when the hypervisor supports nested virtualization, but feature is just disabled. The chosen approach for this case is to keep KVM enabled and let user known (user will eventually receive an error) so user can fix it. Otherwise, user might never know and suffer from performance degradation. |
||
|---|---|---|
| .. | ||
| docker_dev_server.sh | ||
| documentation.sh | ||
| random_query.py | ||
| remote-install.sh | ||
| run_on_gns3vm.sh | ||
| sync_appliances.sh | ||
| update-bundled-web-ui.sh | ||