New openmediavault-kvm plugin

ryecoaaron · Nov 10th 2022

Quote from dildano

are you running xrdp on VMs using KVM?

Yep. I have an Ubuntu 22.04 VM that I use xrdp on every day. I also have a Windows 10 Pro VM that I use every once in a while. I'm using a bridge on them but pretty sure I used to use NAT and was able to connect from a machine other than the host.

dildano · Nov 10th 2022

Quote from ryecoaaron

Yep. I have an Ubuntu 22.04 VM that I use xrdp on every day. I also have a Windows 10 Pro VM that I use every once in a while. I'm using a bridge on them but pretty sure I used to use NAT and was able to connect from a machine other than the host.

Did you have to do anything special on the host or in the KVM setup for the VM? This is driving me crazy.

ryecoaaron · Nov 10th 2022

Nope. Can you telnet from another machine to port 3389? Here is the VM xml:

Code

<domain type="kvm">
  <name>xubuntu</name>
  <uuid>1c23df69-bfcf-4c12-ac71-9f901fbe5b6d</uuid>
  <memory unit="KiB">8388608</memory>
  <currentMemory unit="KiB">8388608</currentMemory>
  <vcpu placement="static">4</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch="x86_64" machine="pc-q35-5.2">hvm</type>
    <boot dev="hd"/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode="custom" match="exact" check="none">
    <model fallback="forbid">qemu64</model>
  </cpu>
  <clock offset="localtime"/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2"/>
      <source file="/srv/nvme/images/xubuntu_boot.qcow2"/>
      <target dev="vda" bus="virtio"/>
      <address type="pci" domain="0x0000" bus="0x05" slot="0x00" function="0x0"/>
    </disk>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2"/>
      <source file="/srv/nvme/images/xubuntu.qcow2"/>
      <target dev="vdb" bus="virtio"/>
      <address type="pci" domain="0x0000" bus="0x07" slot="0x00" function="0x0"/>
    </disk>
    <controller type="usb" index="0" model="qemu-xhci">
      <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
    </controller>
    <controller type="sata" index="0">
      <address type="pci" domain="0x0000" bus="0x00" slot="0x1f" function="0x2"/>
    </controller>
    <controller type="pci" index="0" model="pcie-root"/>
    <controller type="pci" index="1" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="1" port="0x10"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x0" multifunction="on"/>
    </controller>
    <controller type="pci" index="2" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="2" port="0x11"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x1"/>
    </controller>
    <controller type="pci" index="3" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="3" port="0x12"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x2"/>
    </controller>
    <controller type="pci" index="4" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="4" port="0x13"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x3"/>
    </controller>
    <controller type="pci" index="5" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="5" port="0x14"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x4"/>
    </controller>
    <controller type="pci" index="6" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="6" port="0x15"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x5"/>
    </controller>
    <controller type="pci" index="7" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="7" port="0x16"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x6"/>
    </controller>
    <controller type="virtio-serial" index="0">
      <address type="pci" domain="0x0000" bus="0x02" slot="0x00" function="0x0"/>
    </controller>
    <interface type="bridge">
      <mac address="52:54:00:1e:e8:bb"/>
      <source bridge="br0"/>
      <model type="virtio"/>
      <address type="pci" domain="0x0000" bus="0x06" slot="0x00" function="0x0"/>
    </interface>
    <channel type="spicevmc">
      <target type="virtio"/>
      <address type="virtio-serial" controller="0" bus="0" port="1"/>
    </channel>
    <input type="tablet" bus="virtio">
      <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/>
    </input>
    <input type="mouse" bus="ps2"/>
    <input type="keyboard" bus="ps2"/>
    <graphics type="vnc" port="-1" autoport="yes" listen="0.0.0.0">
      <listen type="address" address="0.0.0.0"/>
    </graphics>
    <graphics type="spice" autoport="yes" listen="0.0.0.0">
      <listen type="address" address="0.0.0.0"/>
      <gl enable="no"/>
    </graphics>
    <audio id="1" type="spice"/>
    <video>
      <model type="qxl" ram="65536" vram="65536" vgamem="16384" heads="1" primary="yes"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/>
    </video>
    <memballoon model="virtio">
      <stats period="10"/>
      <address type="pci" domain="0x0000" bus="0x03" slot="0x00" function="0x0"/>
    </memballoon>
  </devices>
  <seclabel type="dynamic" model="dac" relabel="yes"/>
</domain>

Display More

dildano · Nov 10th 2022

Quote from ryecoaaron

Can you telnet from another machine to port 3389?

No, I get "connect failed" when I try to telnet to 3389 on my host. And other than your bridge interface, I don't see any significant differences in our configs. I don't have any firewall rules on my host, so I don't know what would be blocking 3389.

Edit: Definitely something weird going on. I can't ping my Windows PC from the Debian VM either. It's like NAT isn't working at all.

ryecoaaron · Nov 10th 2022

Quote from dildano

No, I get "connect failed" when I try to telnet to 3389 on my host.

Don't use your host. use another system.

Quote from dildano

I can't ping my Windows PC from the Debian VM either. It's like NAT isn't working at all.

I would expect that since your Debian VM is on the wrong side of the NAT to see your Windows PC. You really should convert to a bridge. There are instructions on how to do that in the kvm guide.

dildano · Nov 10th 2022

Quote from ryecoaaron

You really should convert to a bridge. There are instructions on how to do that in the kvm guide.

Thanks. I'll try this. I don't think the KVM guide existed when I set all this up initially. Took me forever to figure it out. Spice works fine, but I just can't get xrdp working.

ryecoaaron · Nov 10th 2022

Quote from dildano

Spice works fine

When you use spice, you only need to connect to the host. The spice service is connecting directly to the spice component of the VM without involving networking.

dildano · Nov 10th 2022

Quote from ryecoaaron

When you use spice, you only need to connect to the host. The spice service is connecting directly to the spice component of the VM without involving networking.

Just to be clear, for xrdp, I should be connecting to the IP of the host, correct? So let's say the host is 192.168.1.10 and the VM is 192.168.122.100. I'm connecting to 192.168.1.10:3389, right? Neither one works for me. Obviously, the host is accessible on my LAN because it's my NAS, and my Windows PC is on the same subnet (192.168.1.9). I feel like I'm just missing something really obvious.

ryecoaaron · Nov 10th 2022

Quote from dildano

Just to be clear, for xrdp, I should be connecting to the IP of the host, correct? So let's say the host is 192.168.1.10 and the VM is 192.168.122.100. I'm connecting to 192.168.1.10:3389, right? Neither one works for me. Obviously, the host is accessible on my LAN because it's my NAS, and my Windows PC is on the same subnet (192.168.1.9). I feel like I'm just missing something really obvious.

if xrdp is running on the guest, you should be connecting to the guest's IP address UNLESS you are using NAT. You should only use the host's ip when connecting to spice or vnc adapters for the VM or if you have some kind of port forwarding enabled to allow the outside world to talk to the VM inside the NAT. You really should switch to a bridge. Then the guest would be on the same network as all of your other machines.

dildano · Nov 10th 2022

Quote from ryecoaaron

if xrdp is running on the guest, you should be connecting to the guest's IP address UNLESS you are using NAT.

OK, I understood it correctly, and there's just something on my LAN preventing access. I'm clearly not a networking expert. Time to try out a bridge. Thanks for the help.

gedarius · Nov 12th 2022

Hello,

I have a mini PC that is running proxmox, inside the proxmox i have a VM running OMV with KVM plugin, i followed this instructions and every thing seens fine, but when i tryed to start my VM (Home Assistant qcow2 image) the VM don't start and the follow error appear:

Anyone can help? i don't found solutions on internet =/

Krisbee · Nov 13th 2022

gedarius You need to configure you proxmox host to support nested virtualisation.

donh · Nov 13th 2022

Or why not just run it on proxmox?

RaHe67 · Dec 9th 2022

Hi, just trying to build up a new OMV6 NAS with KVM and I am struggling already around about 2 days to build up a KVM VM with bridged network.
Sorry if the same issue pops up here many times before, but I didn't got the clue here to fix my problem here (as a not so experienced Linux User). I tried different variants already.

I configured my system as described here:

[How-To] Use the Openmediavault-KVM plugin - Guides - openmediavault

The situation is that I can access the Host via br0, but the guest OS only sees its own loopback Adapter - therefore it cannot get its ip via DHCP and I cannot access it via network.

Network Settings:

Network Bound to KVM:

Docker is disabled

Version
6.1.1-1 (Shaitan)

Processor
Intel(R) Xeon(R) CPU E31260L @ 2.40GHz

Kernel
Linux 5.16.0-0.bpo.4-amd64

HW: HP Microserver Gen8

Code

================================================================================
= Network interfaces
================================================================================
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP group default qlen 1000
link/ether d0:bf:9c:46:9b:94 brd ff:ff:ff:ff:ff:ff
altname enp3s0f0
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d0:bf:9c:46:9b:95 brd ff:ff:ff:ff:ff:ff
altname enp3s0f1
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 0e:fd:2a:70:25:1a brd ff:ff:ff:ff:ff:ff
inet 192.168.2.3/24 brd 192.168.2.255 scope global dynamic br0
valid_lft 816002sec preferred_lft 816002sec
6: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0
valid_lft forever preferred_lft forever
7: vethdc9e2ad9@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether be:8e:ee:53:8b:4c brd ff:ff:ff:ff:ff:ff link-netns cni-c9cfa94a-f721-b323-d4eb-11fb40030ea8
inet 172.16.16.1/32 scope global vethdc9e2ad9
valid_lft forever preferred_lft forever
inet6 fe80::74f5:e7ff:fe1e:800a/64 scope link
valid_lft forever preferred_lft forever
10: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:e5:77:97 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fee5:7797/64 scope link
valid_lft forever preferred_lft forever

Display More

Has anyone an idea how to proceed or what to check further?

ryecoaaron · Dec 9th 2022

Your OMV config looks fine. What OS is the guest?

You really should update your system. The 5.16 backports kernel is very old.

RaHe67 · Dec 9th 2022

The kernel came with a fresh OMV6 installation. Neither the Web-Gui, nor apt-get is offering me something newer ...

Code

uname -srm
Linux 5.16.0-0.bpo.4-amd64 x86_64

> apt-get update
> apt-get dist-upgrade
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

Edit:
> omv-upgrade
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Display More

Sorry, I'm not the linux expert. How could I upgrade the system? Usually I used the GUI with OMV.

The Guest OS is MLD (I think Debian based?) I used already for years under OM4 Virtual Box with a Bridged Network

MiniDVBLinux Distribution

My intention was to Upgrade the old System (OMV4, still running smoothly) with hard disk replacements (the old were running 24h 6 years now) by new ones (old ones available as backup).

So I tried a new clean installation with new disks (building up the same configuration), just using KVM instead of VirtualBox.

ryecoaaron · Dec 9th 2022

Quote from RaHe67

How could I upgrade the system

Sounds like you installed without a internet connection and your repos are incomplete. What is the output of: sudo apt-get update

RaHe67 · Dec 9th 2022

Like I tried to state above, looks ok for me:

Code

root@homenas1:~# sudo apt-get update
Holen:1 file:/var/cache/openmediavault/archives  InRelease
Ign:1 file:/var/cache/openmediavault/archives  InRelease
Holen:2 file:/var/cache/openmediavault/archives  Release
Ign:2 file:/var/cache/openmediavault/archives  Release
Holen:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Holen:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Holen:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Ign:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Holen:6 file:/var/cache/openmediavault/archives  Translation-de
Ign:6 file:/var/cache/openmediavault/archives  Translation-de
Holen:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Holen:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Holen:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Ign:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Holen:6 file:/var/cache/openmediavault/archives  Translation-de
Ign:6 file:/var/cache/openmediavault/archives  Translation-de
Holen:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Holen:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Holen:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Ign:5 file:/var/cache/openmediavault/archives  Translation-de_DE


Holen:6 file:/var/cache/openmediavault/archives  Translation-de
Ign:6 file:/var/cache/openmediavault/archives  Translation-de
Holen:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Holen:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Holen:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Ign:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Holen:6 file:/var/cache/openmediavault/archives  Translation-de
Ign:6 file:/var/cache/openmediavault/archives  Translation-de
Holen:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Holen:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Holen:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Ign:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Holen:6 file:/var/cache/openmediavault/archives  Translation-de
Ign:6 file:/var/cache/openmediavault/archives  Translation-de
Holen:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Holen:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Holen:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Ign:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Holen:6 file:/var/cache/openmediavault/archives  Translation-de
Ign:6 file:/var/cache/openmediavault/archives  Translation-de
Holen:3 file:/var/cache/openmediavault/archives  Packages
Holen:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Holen:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Ign:5 file:/var/cache/openmediavault/archives  Translation-de_DE
Holen:6 file:/var/cache/openmediavault/archives  Translation-de
Ign:6 file:/var/cache/openmediavault/archives  Translation-de
OK:7 http://packages.openmediavault.org/public shaitan InRelease
OK:8 http://deb.debian.org/debian bullseye InRelease
OK:9 http://security.debian.org/debian-security bullseye-security InRelease
OK:10 http://deb.debian.org/debian bullseye-updates InRelease
OK:11 https://download.docker.com/linux/debian bullseye InRelease
OK:12 https://openmediavault-plugin-developers.github.io/packages/debian shaitan InRelease
OK:13 https://openmediavault.github.io/packages shaitan InRelease
OK:14 http://httpredir.debian.org/debian bullseye-backports InRelease
Paketlisten werden gelesen… Fertig

Display More

Internet connection should be available:

Code

root@homenas1:~# ping google.de
PING google.de (142.250.186.131) 56(84) bytes of data.
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=1 ttl=119 time=11.4 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=2 ttl=119 time=10.1 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=3 ttl=119 time=10.1 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=4 ttl=119 time=10.2 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=5 ttl=119 time=10.3 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=6 ttl=119 time=10.1 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=7 ttl=119 time=10.1 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=8 ttl=119 time=10.1 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=9 ttl=119 time=10.0 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=10 ttl=119 time=10.3 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=11 ttl=119 time=10.4 ms
64 bytes from fra24s07-in-f3.1e100.net (142.250.186.131): icmp_seq=12 ttl=119 time=10.2 ms
^C
--- google.de ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11015ms

Display More

RaHe67 · Dec 9th 2022

Seems that I forgot the reboot after ugrading ....

After reboot I have:

Code

uname -srm
Linux 6.0.0-0.deb11.2-amd64 x86_64

Edit:

Building up a new VM Machine now with the same settings as described above:
Now I cannot start: Error Message:

ryecoaaron · Dec 9th 2022

Quote from RaHe67

Like I tried to state above, looks ok for me:

Sorry, you are incorrect. You did install without an internet connection as I stated above. You only have the security repo because omv adds it. Run this to fix:

echo "deb http://deb.debian.org/debian/ bullseye main contrib non-free" | sudo tee /etc/apt/sources.list

echo "deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free" | sudo tee -a /etc/apt/sources.list

Participate now!