Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
omv6:omv6_plugins:kvm [2023/07/04 15:38] – [Installation] chente | omv6:omv6_plugins:kvm [2024/04/22 04:02] (current) – crashtest | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{indexmenu_n> | + | {{indexmenu_n> |
\\ | \\ | ||
< | < | ||
Line 54: | Line 54: | ||
* The virtualization feature must be enabled in the server BIOS -> Consult your server' | * The virtualization feature must be enabled in the server BIOS -> Consult your server' | ||
* Consider the RAM needs for the guest VMs on your system. | * Consider the RAM needs for the guest VMs on your system. | ||
+ | * A couple of cool beers on hand will be welcome. | ||
---- | ---- | ||
Line 65: | Line 66: | ||
</ | </ | ||
Depending on the development state of Debian at any given time, you may need to activate backports for the installation of this plugin.< | Depending on the development state of Debian at any given time, you may need to activate backports for the installation of this plugin.< | ||
- | To do this go to the omv-extras tab in the OMV GUI and click the Activate Backports button. | + | To do this go to the omv-extras tab in the OMV GUI and click the <b>Activate Backports</ |
</ | </ | ||
Line 175: | Line 176: | ||
</ | </ | ||
* ... | * ... | ||
- | * In the **Path** field, search for the folder in the tree (button on the right) and select it. | + | * In the **Path** field, search for the folder in the tree (button on the right) and select it. Disk mount folders are usually in the /srv folder. |
* Press **Add** | * Press **Add** | ||
* Now the pool is created, it only remains to activate it so that KVM can use it. To do it: | * Now the pool is created, it only remains to activate it so that KVM can use it. To do it: | ||
Line 260: | Line 261: | ||
* Now the new bridge network interface is configured, when you click on **Accept the changes** in the upper yellow bar, the previous interface will be deleted and the bridge will be created simultaneously. **Accept the changes** in the top yellow bar. | * Now the new bridge network interface is configured, when you click on **Accept the changes** in the upper yellow bar, the previous interface will be deleted and the bridge will be created simultaneously. **Accept the changes** in the top yellow bar. | ||
* Now the original interface is removed and the new bridge type interface is created and working. The name of the original interface no longer appears in the Device field, now the name of the interface is //br0//. | * Now the original interface is removed and the new bridge type interface is created and working. The name of the original interface no longer appears in the Device field, now the name of the interface is //br0//. | ||
+ | * At this point netplan must make several changes to the network configuration. In some cases this procedure may require a server reboot for the configuration to stabilize. | ||
* This is the network interface that we will select in the plugin if we want a VM to use the //br0// bridge. We don't need to configure anything in the Network section of the plugin. | * This is the network interface that we will select in the plugin if we want a VM to use the //br0// bridge. We don't need to configure anything in the Network section of the plugin. | ||
+ | * To select this network in a new vm, in the vm creation interface go to the Network Section and change the value of the Model field to Bridge, then change the value of the Bridge field to br0. | ||
< | < | ||
Line 457: | Line 460: | ||
* Click on **Connect**. | * Click on **Connect**. | ||
* Your VMs should now appear on the dashboard. | * Your VMs should now appear on the dashboard. | ||
+ | * You can also use virt-manager through a docker container. In the [[omv6: | ||
< | < |