Differences

This shows you the differences between two versions of the page.

--- omv6:omv6_plugins:kvm [2023/05/27 13:21] – [Remote connection with virt-manager to KVM] chente
+++ omv6:omv6_plugins:kvm [2024/04/22 04:02] (current) – crashtest
@@ Line 1: / Line 1: @@
-{{indexmenu_n>5}}
+{{indexmenu_n>7}}
 \\
 <html><center><b>KVM Plugin For OMV6</b></center></html>
@@ Line 54: / Line 54: @@
   * The virtualization feature must be enabled in the server BIOS -> Consult your server's motherboard manual.
   * Consider the RAM needs for the guest VMs on your system.
+  * A couple of cool beers on hand will be welcome.
 ----
@@ Line 61: / Line 62: @@
 In OMV6's GUI:\\
 Under **System** > **Plugins**, find and highlight **openmediavault-kvm 6.X**, and click the **install** button.
+<html><body><table width="100%" border="0"><tr><td colspan="2" style="background-color:#69A5FF;height:30px;"><strong><span style="color:#FFFFFF;font-size:110%;">&#160; Note
+</span></strong></td></tr><tr><td style="background-color:#E6FEFF;height:25px;width:380px;">
+Depending on the development state of Debian at any given time, you may need to activate backports for the installation of this plugin.<br>
+To do this go to the omv-extras tab in the OMV GUI and click the <b>Activate Backports</b> button. Once the installation is done you can disable backports again if you want.
+</tr></table></body></html>
 ----
@@ Line 168: / Line 176: @@
 </tr></table></body></html>
         * ...
-      * 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**
       * Now the pool is created, it only remains to activate it so that KVM can use it. To do it:
@@ Line 253: / 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 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.
+    * 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.
 <html><body><table width="100%" border="0"><tr><td colspan="2" style="background-color:#69A5FF;height:30px;"><strong><span style="color:#FFFFFF;font-size:110%;">&#160;
@@ Line 450: / Line 460: @@
     * Click on **Connect**.
     * Your VMs should now appear on the dashboard.
+  * You can also use virt-manager through a docker container. In the [[omv6:omv6_plugins:docker_compose|openmediavault-compose]] plugin there is an example for using virt-manager via a docker container.
 <html><body><table width="100%" border="0"><tr><td colspan="2" style="background-color:#FFB663;height:30px;"><strong><span style="color:#FFFFFF;font-size:110%;">&#160;