New openmediavault-kvm plugin

ANDROD2468 · 18. März 2023

Zitat von ryecoaaron

cut & paste is so much easier. I don't see anything wrong there.

What is the output of:
grep -v '#' /etc/default/libvirtd
sudo /usr/sbin/libvirtd

sorry it was over the word limit...

Code

root@nick-nas:~# grep -v '#' /etc/default/libvirtd


LIBVIRTD_ARGS=""




root@nick-nas:~# sudo /usr/sbin/libvirtd

2023-03-19 17:32:48.121+0000: 409163: info : libvirt version: 8.0.0, package: 1~bpo11+1 (Michael Tokarev <mjt@tls.msk.ru> Thu, 27 Jan 2022 10:36:33 +0300)
2023-03-19 17:32:48.121+0000: 409163: info : hostname: nick-nas
2023-03-19 17:32:48.121+0000: 409163: error : virAuditOpen:56 : Unable to initialize audit layer: Permission denied
2023-03-19 17:32:48.122+0000: 409163: error : virNetSocketNewListenUNIX:492 : Failed to create socket: Permission denied
root@nick-nas:~#

Alles anzeigen

ryecoaaron · 18. März 2023

If the cut&paste is too big, you can put it in a file and attach it. Just hard to see screenshots sometimes.

lsmod | grep kvm

dpkg -l | grep apparmor

ANDROD2468 · 18. März 2023

Zitat von ryecoaaron

If the cut&paste is too big, you can put it in a file and attach it. Just hard to see screenshots sometimes.

lsmod | grep kvm
dpkg -l | grep apparmor

root@nick-nas:~# lsmod | grep kvm

kvm_amd 167936 0

kvm 1110016 1 kvm_amd

irqbypass 16384 1 kvm

ccp 106496 1 kvm_amd

root@nick-nas:~# dpkg -l | grep apparmor

ii apparmor 2.13.6-10 amd64 user-space parser utility for AppArmor

ii libapparmor1:amd64 2.13.6-10 amd64 changehat AppArmor library

root@nick-nas:~#

ryecoaaron · 18. März 2023

I think apparmor is causing this. I would try to disable it.

sudo systemctl stop apparmor

sudo systemctl start libvirtd

ANDROD2468 · 18. März 2023

Zitat von ryecoaaron

I think apparmor is causing this. I would try to disable it.

sudo systemctl stop apparmor
sudo systemctl start libvirtd

stoping it didnt't do it bit i did a "apt purge apparmor" and reboot and libvirtd starts!

I added the pool whith no errors

crashtest · 18. März 2023

Zitat von chente

Even if you change the properties of a pool, the existing files are not changed.

ANDROD2468 chente's right. Existing file properties are not changed. Only new files will get the new properties. It's best to run that command list, against the pool, before data is added to the pool.

Zitat von chente

To get out of this problem I guess you could move the files to another storage and copy them back.

When I first ran into this issue, that's how I handled it. (At that time, I couldn't find a reference for changing file properties at the file system level.)

ANDROD2468 · 18. März 2023

Zitat von crashtest

ANDROD2468 chente's right. Existing file properties are not changed. Only new files will get the new properties. It's best to run that command list, against the pool, before data is added to the pool.

When I first ran into this issue, that's how I handled it. (At that time, I couldn't find a reference for changing file properties at the file system level.)

I got 2.65 TB of data in my pool of ssds so I kind of don't want to do that.... (I used ssd because the server is in my room.)

I deleted the vm folder and created a new one.

\

BernH · 20. März 2023

Zitat von ryecoaaron

The plugin is all libvirt including lxc. The lxc-* tools will not work with or detect libvirt lxc (as you have found) just like regular kvm tools won't work with libvirt kvm VMs. I did look at the regular lxc-* stuff but it was MUCH more work to get the plugin to work with them and I don't think they worked any better. Other than having less characters in the command, I didn't find them simpler.

Further to my exploration of the lxc plugin, I just encountered a little hiccup I though I should mention.

When using a VM, I have been using virt-manager to thake the virtual nic and attach it via a direct macvtap connection to a physical nic that I have connected to my LAN but not configured so that the nic acts like a switch and my VM's get a LAN IP.

LXC's don't offer this option, so I created a macvtap tetwork in the KVM plugin and attached the virtual NIC's to that. Different method to get the same LAN IP result. However, when I rebooted the system the macvtap network did not auto-start, so the lxc failed to start. I easily fixed this with virt-manager, as the network connections page has the auto start option to enable that seems to be missing from the kvm plugin network page.

This system was installed from the OMV ISO, but another system I recently installed using the debian net install and OMV script did not suffer from the same issue of the macvtap not starting.

ryecoaaron · 20. März 2023

Zitat von BernH

as the network connections page has the auto start option to enable that seems to be missing from the kvm plugin network page.

The plugin sets the auto-start bit when you click the start network menu option - https://github.com/OpenMediaVa…/engined/rpc/kvm.inc#L346

If you created a network from the plugin and started the network with something else, the autostart bit would never get set.

BernH · 20. März 2023

Zitat von ryecoaaron

The plugin sets the auto-start bit when you click the start network menu option - https://github.com/OpenMediaVa…/engined/rpc/kvm.inc#L346

If you created a network from the plugin and started the network with something else, the autostart bit would never get set.

I created the network with the plugin and started it there too. I only looked at it in virt-manager after it didn't start on a reboot. I have no idea why it happened on one system and not the other but it might be worth while putting an auto-start button in the network page too, just like it is in the VM page, so that this can be manually controlled.

ryecoaaron · 20. März 2023

Zitat von BernH

I created the network with the plugin and started it there too. I only looked at it in virt-manager after it didn't start on a reboot. I have no idea why it happened on one system and not the other but it might be worth while putting an auto-start button in the network page too, just like it is in the VM page, so that this can be manually controlled.

I didn't add a separate auto-start option to pools or networks because it doesn't make sense to me to create a network or pool and not have it auto-start. VMs are completely different. I don't think all VMs should auto-start.

I will try to improve the code to notify the user if the autostart is failed to be set. Adding a button because it failed once in your case is not the right path in my opinion. You can always stop the network and start it again if you don't think the auto-start is set. But if the start code is improved, that shouldn't be an issue.

BernH · 20. März 2023

Zitat von ryecoaaron

I didn't add a separate auto-start option to pools or networks because it doesn't make sense to me to create a network or pool and not have it auto-start. VMs are completely different. I don't think all VMs should auto-start.

I will try to improve the code to notify the user if the autostart is failed to be set. Adding a button because it failed once in your case is not the right path in my opinion. You can always stop the network and start it again if you don't think the auto-start is set. But if the start code is improved, that shouldn't be an issue.

Fair enough, tackle it how you want, I just though enabling manual control might be the easiest "fix" for oddities like this.

ryecoaaron · 20. März 2023

Zitat von BernH

Fair enough, tackle it how you want, I just though enabling manual control might be the easiest "fix" for oddities like this.

I will add it then.

henfri · 20. März 2023

Zitat von ryecoaaron

This has been covered before. The plugin doesn't run dnsmasq or even install the full dnsmasq package (just dnsmasq-base). It will spin up a dnsmasq instance that listens only on the virtual network. It is used to assign IPs to NAT VMs. This should only be a problem if you are telling pihole to listen on every network. There are plenty of ways to avoid that.

Thanks for your reply - and sorry for the delay in mine.

I do not tell pihole to listen on every interface. In fact, I try to run it in a docker container.

I have no Idea what else could start dnsmasq.

Zitat

root@homeserver:/etc# docker start 7dce988c209d

Error response from daemon: driver failed programming external connectivity on endpoint pihole (4b7a93429cb7fb4817d18a6917fe892ccf8a592df8188f5cd03d07ddc2aa8081): Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use

Error: failed to start containers: 7dce988c209d

root@homeserver:/etc# netstat -tulpn |grep ":53 "

tcp 0 0 10.0.3.1:53 0.0.0.0:* LISTEN 2246/dnsmasq

udp 0 0 10.0.3.1:53 0.0.0.0:* 2246/dnsmasq

Alles anzeigen

10.0.3.1 is not the IP of my host though....

Let me know, if I should start a new thread on this. I tried to purge dnsmasq, but that would have purged omv-kvm as well.

On a different matter:

I am using a bridge network. For some reason, I can access from the host (or other machines) to the VM, but I cannot access from the VM to the host (not even a ping to the host IP gets a response).

What could be the reason?

Best regards,

Hendrik

ryecoaaron · 20. März 2023

Zitat von henfri

I do not tell pihole to listen on every interface. In fact, I try to run it in a docker container.
I have no Idea what else could start dnsmasq.

I have almost no info. How are you starting the container? docker-compose? If you aren't binding the container to a network or ip address, you are binding it to 0.0.0.0 which is all network interfaces. I don't have enough info to know what 10.0.3.1 is but the output of ip a would help.

Zitat von henfri

I tried to purge dnsmasq, but that would have purged omv-kvm as well.

Why would you purge it after I told you it wasn't causing the problem? You could try disabling all NAT networks in the kvm plugin. It shouldn't start a dnsmasq listener on that network then.

Zitat von henfri

I am using a bridge network. For some reason, I can access from the host (or other machines) to the VM, but I cannot access from the VM to the host (not even a ping to the host IP gets a response).

A bridge network defined in the plugin or a bridge network interface defined at the OMV network level? The latter should be used and is described thoroughly in the kvm guide.

rudder · 23. März 2023

Hello everyone!

I am using OMV6 with the KVM plugin and recently ran into an issue.

I have two Windows 10 guest virtual machines and I also have two USB keys connected to the OMV host.

Both of these USB keys (AVEST AvPass) have the same PID.

Code

root@server:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 0451:16a8 Texas Instruments, Inc. CC2531 ZigBee
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID c1a5:0502 AVEST AvPass
Bus 001 Device 012: ID 03f0:5d17 HP, Inc HP LaserJet P2035
Bus 001 Device 003: ID 0001:0000 Fry's Electronics MEC0003
Bus 001 Device 013: ID c1a5:0502 AVEST AvPass
Bus 001 Device 007: ID 048d:5702 Integrated Technology Express, Inc. ITE Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I need to permanently redirect each of the USB keys to the guest OS.

The first key works fine, but when I redirect the second key, an error appears.

Code

Failed to add USB device.
error: Failed to attach device from /tmp/virsh_usbwgdQui
error: operation error: Multiple USB devices detected for c1a5:502. Please select one device using <address>
virsh attach-device --domain Buh --file '/tmp/virsh_usbwgdQui' --persistent --config --live

OMV\Exception: Failed to add USB device.
error: Failed to attach device from /tmp/virsh_usbwgdQui
error: operation error: Multiple USB devices detected for c1a5:502. Please select one device using <address>
virsh attach-device --domain Buh --file '/tmp/virsh_usbwgdQui' --persistent --config --live in /usr/share/openmediavault/engined/rpc/kvm.inc:2861
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/kvm.inc(1995): OMVRpcServiceKvm->virshCommand(Array, 'Failed to add U...')
#1 [internal function]: OMVRpcServiceKvm->addUsb(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('addUsb', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Kvm', 'addUsb', Array, Array, 1)
#5 {main}

Alles anzeigen

XML OS1:

Code

<domain type='kvm' id='3'>
  <name>1c</name>
  <uuid>b3a0d7fe-45a8-4b60-bf45-8446558cd63b</uuid>
  <description>Windows Server 2022</description>
  <metadata>
    <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
      <libosinfo:os id="http://microsoft.com/win/2k22"/>
    </libosinfo:libosinfo>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <vcpu placement='static'>2</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-7.2'>hvm</type>
    <boot dev='hd'/>
    <boot dev='cdrom'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv mode='custom'>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
    </hyperv>
    <vmport state='off'/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='2' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
    <timer name='hypervclock' present='yes'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none' io='native'/>
      <source file='/srv/dev-disk-by-uuid-78407b9d-5740-4fe1-9421-7d47233bd0e6/VMs/win_server_2022.qcow2' index='2'/>
      <backingStore/>
      <target dev='sda' bus='sata'/>
      <alias name='sata0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/srv/dev-disk-by-uuid-78407b9d-5740-4fe1-9421-7d47233bd0e6/ISO/ru-ru_windows_server_2022_updated_jan_2023_x64_dvd_e0c68073.iso' index='1'/>
      <backingStore/>
      <target dev='sdb' bus='sata'/>
      <readonly/>
      <alias name='sata0-0-1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <alias name='pci.1'/>
      <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'/>
      <alias name='pci.2'/>
      <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'/>
      <alias name='pci.3'/>
      <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'/>
      <alias name='pci.4'/>
      <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'/>
      <alias name='pci.5'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:ac:b2:03'/>
      <source bridge='br0'/>
      <target dev='vnet2'/>
      <model type='e1000e'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/2'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/2'>
      <source path='/dev/pts/2'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5904' autoport='yes' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <graphics type='spice' port='5905' autoport='yes' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
      <image compression='off'/>
    </graphics>
    <sound model='ich9'>
      <alias name='sound0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
    </sound>
    <audio id='1' type='spice'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0xc1a5'/>
        <product id='0x0502'/>
        <address bus='1' device='5'/>
      </source>
      <alias name='hostdev0'/>
      <address type='usb' bus='0' port='4'/>
    </hostdev>
    <redirdev bus='usb' type='spicevmc'>
      <alias name='redir0'/>
      <address type='usb' bus='0' port='2'/>
    </redirdev>
    <redirdev bus='usb' type='spicevmc'>
      <alias name='redir1'/>
      <address type='usb' bus='0' port='3'/>
    </redirdev>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+64055:+64055</label>
    <imagelabel>+64055:+64055</imagelabel>
  </seclabel>
</domain>

Alles anzeigen

I understand that the error is related to the same PID, but how to resolve this?

Could you explain this to a beginner? Thank you very much!

ryecoaaron · 23. März 2023

Zitat von rudder

but how to resolve this?

I don't have a good way to do it with the plugin. You can edit the xml in the plugin and do something like this - https://forums.unraid.net/topi…h-the-same-vendorproduct/

rudder · 23. März 2023

Zitat von ryecoaaron

I don't have a good way to do it with the plugin. You can edit the xml in the plugin and do something like this - https://forums.unraid.net/topi…h-the-same-vendorproduct/

Its work! Thank you!

npanyo · 26. März 2023

Hi everyone!

Maybe it is a dumb question so sorry in advance!

I would like to know where can I found any logs for the plugin. I am asking because I have Home assistant OS running in it but for some time now it shuts down by itself and yesterday I was not even able to start the VM at all. Now it is running again but I cannot tell for how long. I deleted all addons in Home assistant thinking maybe those caused the problem but that random shutdown remained. I tried to check the logs under the Diagnostic tab in OMV but I could not find anything there. I thought maybe the logs of the plugin might help locate the problem.

Thank you in advance!

macom · 26. März 2023

Have a look at

/var/log/libvirt/qemu

on the host. I don't have the plugin running, but that is where I find logs of the VMs on my Laptop.

Jetzt mitmachen!