cannot install kvm-plugin

henfri · 4. Januar 2023

Hello,

I fail installing the KVM Plugin (I think this is the recommended way for virtualization in OMV6, right?).

On the webinterface, the Error-Message disappears to quickly.

On the commandline, I get:

Code

apt-get install openmediavault-kvm
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libnss-systemd : Depends: systemd (= 247.3-7+deb11u1) but 251.3-1~bpo11+1 is to be installed
 policykit-1 : Depends: default-logind or
                        logind
E: Unable to correct problems, you have held broken packages.

Alles anzeigen

What am I doing wrong?

I did an apt-get dist-upbrade before, which worked.

Best regards,

HEndrik

BernH · 4. Januar 2023

install omv-extras first, then you will find it in the additional plugins that it makes available.

start [omv-extras.org]

henfri · 5. Januar 2023

Ah, sorry. That ist Not the Problem.

I find it in the Webinterface.

But when installing, an Error appears and disappears immediately.

Thus I do it via Shell. This gives me above Error.

BernH · 5. Januar 2023

Well this may be a topic better answered by ryecoaaron since he is the one that makes and maintains the omv-extras, but the end of your output says there are unmet dependencies.

Your systemd seems to be wanting to install a newer version from backports than libnss-systemd wants. Do you have backports enabled?

I know Aaron has been doing a fair bit of work on the kvm plugin recently and I think backports is required for it, so he is the one to ask really.

ryecoaaron · 5. Januar 2023

This problem has happened before but no one sticks around long enough to figure out the exact fix. It is a dependency problem and order of install issue. Sadly, I could fix this in a matter of minutes if I was logged in but it will take a bunch of back and forth to fix it.

To start, what is the output of:

sudo apt-get install policykit-1=0.105-31+deb11u1

dpkg -l | grep qemu

KM0201 · 5. Januar 2023

Zitat von ryecoaaron

This problem has happened before but no one sticks around long enough to figure out the exact fix. It is a dependency problem and order of install issue. Sadly, I could fix this in a matter of minutes if I was logged in but it will take a bunch of back and forth to fix it.

To start, what is the output of:

sudo apt-get install policykit-1=0.105-31+deb11u1
dpkg -l | grep qemu

Alles anzeigen

Not sure I'm having the same problem as everyone else... but I'm your Huckleberry.. :). This is an up to date 6.1.4-1 OMV install, with really nothing on it. Backports is not enabled.

Code

root@omv6-test:~# apt install openmediavault-k
openmediavault-kernel   openmediavault-keyring  openmediavault-kvm
root@omv6-test:~# apt install openmediavault-kvm 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 openmediavault-kvm : Depends: qemu-system-arm but it is not going to be installed
                      Depends: qemu-system-data but it is not going to be installed
                      Depends: qemu-system-mips but it is not going to be installed
                      Depends: qemu-system-ppc but it is not going to be installed
                      Depends: qemu-system-x86 but it is not going to be installed
                      Depends: swtpm but it is not installable
                      Depends: swtpm-tools but it is not installable
E: Unable to correct problems, you have held broken packages.
root@omv6-test:~# sudo apt-get install policykit-1=0.105-31+deb11u1

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-image-5.10.0-19-amd64
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  libpolkit-agent-1-0 libpolkit-gobject-1-0
The following NEW packages will be installed:
  libpolkit-agent-1-0 libpolkit-gobject-1-0 policykit-1
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 173 kB of archives.
After this operation, 572 kB of additional disk space will be used.
Do you want to continue? [Y/n]

Alles anzeigen

No output on the dpkg command... before or after installing the libpolkit package

After installing libpolkit, I get the same error, which seems to suggest the swmtp-tools package is the issue... So I enabled backports and installed that package...

Code

root@omv6-test:~# apt install swtpm-tools 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-image-5.10.0-19-amd64
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  gnutls-bin libgnutls-dane0 libjson-glib-1.0-0 libjson-glib-1.0-common libopts25 libtpms0 libunbound8 swtpm swtpm-libs
Suggested packages:
  dns-root-data trousers
The following NEW packages will be installed:
  gnutls-bin libgnutls-dane0 libjson-glib-1.0-0 libjson-glib-1.0-common libopts25 libtpms0 libunbound8 swtpm swtpm-libs swtpm-tools
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
Need to get 2232 kB of archives.
After this operation, 5755 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://deb.debian.org/debian bullseye/main amd64 libunbound8 amd64 1.13.1-1 [504 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 libgnutls-dane0 amd64 3.7.1-5+deb11u2 [395 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 libopts25 amd64 1:5.18.16-4 [69.2 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 gnutls-bin amd64 3.7.1-5+deb11u2 [647 kB]
Get:5 http://httpredir.debian.org/debian bullseye-backports/main amd64 libtpms0 amd64 0.9.2-3~bpo11+1 [324 kB]
Get:6 http://deb.debian.org/debian bullseye/main amd64 libjson-glib-1.0-common all 1.6.2-1 [56.9 kB]
Get:7 http://deb.debian.org/debian bullseye/main amd64 libjson-glib-1.0-0 amd64 1.6.2-1 [65.4 kB]
Get:8 http://httpredir.debian.org/debian bullseye-backports/main amd64 swtpm-libs amd64 0.7.1-1~bpo11+1 [40.9 kB]
Get:9 http://httpredir.debian.org/debian bullseye-backports/main amd64 swtpm amd64 0.7.1-1~bpo11+1 [25.2 kB]
Get:10 http://httpredir.debian.org/debian bullseye-backports/main amd64 swtpm-tools amd64 0.7.1-1~bpo11+1 [105 kB]
Fetched 2232 kB in 1s (1722 kB/s) 
Selecting previously unselected package libunbound8:amd64.
(Reading database ... 49847 files and directories currently installed.)
Preparing to unpack .../0-libunbound8_1.13.1-1_amd64.deb ...
Unpacking libunbound8:amd64 (1.13.1-1) ...
Selecting previously unselected package libgnutls-dane0:amd64.
Preparing to unpack .../1-libgnutls-dane0_3.7.1-5+deb11u2_amd64.deb ...
Unpacking libgnutls-dane0:amd64 (3.7.1-5+deb11u2) ...
Selecting previously unselected package libopts25:amd64.
Preparing to unpack .../2-libopts25_1%3a5.18.16-4_amd64.deb ...
Unpacking libopts25:amd64 (1:5.18.16-4) ...
Selecting previously unselected package gnutls-bin.
Preparing to unpack .../3-gnutls-bin_3.7.1-5+deb11u2_amd64.deb ...
Unpacking gnutls-bin (3.7.1-5+deb11u2) ...
Selecting previously unselected package libjson-glib-1.0-common.
Preparing to unpack .../4-libjson-glib-1.0-common_1.6.2-1_all.deb ...
Unpacking libjson-glib-1.0-common (1.6.2-1) ...
Selecting previously unselected package libjson-glib-1.0-0:amd64.
Preparing to unpack .../5-libjson-glib-1.0-0_1.6.2-1_amd64.deb ...
Unpacking libjson-glib-1.0-0:amd64 (1.6.2-1) ...
Selecting previously unselected package libtpms0:amd64.
Preparing to unpack .../6-libtpms0_0.9.2-3~bpo11+1_amd64.deb ...
Unpacking libtpms0:amd64 (0.9.2-3~bpo11+1) ...
Selecting previously unselected package swtpm-libs:amd64.
Preparing to unpack .../7-swtpm-libs_0.7.1-1~bpo11+1_amd64.deb ...
Unpacking swtpm-libs:amd64 (0.7.1-1~bpo11+1) ...
Selecting previously unselected package swtpm.
Preparing to unpack .../8-swtpm_0.7.1-1~bpo11+1_amd64.deb ...
Unpacking swtpm (0.7.1-1~bpo11+1) ...
Selecting previously unselected package swtpm-tools.
Preparing to unpack .../9-swtpm-tools_0.7.1-1~bpo11+1_amd64.deb ...
Unpacking swtpm-tools (0.7.1-1~bpo11+1) ...
Setting up libopts25:amd64 (1:5.18.16-4) ...
Setting up libunbound8:amd64 (1.13.1-1) ...
Setting up libjson-glib-1.0-common (1.6.2-1) ...
Setting up libtpms0:amd64 (0.9.2-3~bpo11+1) ...
Setting up libgnutls-dane0:amd64 (3.7.1-5+deb11u2) ...
Setting up swtpm-libs:amd64 (0.7.1-1~bpo11+1) ...
Setting up libjson-glib-1.0-0:amd64 (1.6.2-1) ...
Setting up swtpm (0.7.1-1~bpo11+1) ...
Setting up gnutls-bin (3.7.1-5+deb11u2) ...
Setting up swtpm-tools (0.7.1-1~bpo11+1) ...
Adding group `tss' (GID 120) ...
Done.
Warning: The home dir /var/lib/tpm you specified can't be accessed: No such file or directory
Adding system user `tss' (UID 114) ...
Adding new user `tss' (UID 114) with group `tss' ...
Not creating home directory `/var/lib/tpm'.
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u5) ...
root@omv6-test:~#

Alles anzeigen

After that, I installed openmediavault-kvm and it seems to be working.

dpkg now shows an output for qemu of course...

Code

root@omv6-test:~# dpkg -l | grep qemu
ii  ipxe-qemu                            1.0.0+git-20190125.36a4c85-5.1 all          PXE boot firmware - ROM images for qemu
ii  libvirt-daemon-driver-qemu           8.0.0-1~bpo11+1                amd64        Virtualization daemon QEMU connection driver
ii  qemu-efi                             2020.11-2+deb11u1              all          transitional dummy package
ii  qemu-efi-aarch64                     2020.11-2+deb11u1              all          UEFI firmware for 64-bit ARM virtual machines
ii  qemu-efi-arm                         2020.11-2+deb11u1              all          UEFI firmware for 32-bit ARM virtual machines
ii  qemu-system-arm                      1:7.1+dfsg-2~bpo11+3           amd64        QEMU full system emulation binaries (arm)
ii  qemu-system-common                   1:7.1+dfsg-2~bpo11+3           amd64        QEMU full system emulation binaries (common files)
ii  qemu-system-data                     1:7.1+dfsg-2                   all          QEMU full system emulation (data files)
ii  qemu-system-mips                     1:7.1+dfsg-2~bpo11+3           amd64        QEMU full system emulation binaries (mips)
ii  qemu-system-ppc                      1:7.1+dfsg-2~bpo11+3           amd64        QEMU full system emulation binaries (ppc)
ii  qemu-system-x86                      1:7.1+dfsg-2~bpo11+3           amd64        QEMU full system emulation binaries (x86)
ii  qemu-utils                           1:7.1+dfsg-2~bpo11+3           amd64        QEMU utilities
root@omv6-test:~#

Alles anzeigen

If you need more help with it/more info, let me know. I can even nuke the virtual machine and do it again if you need me to.

henfri · 5. Januar 2023

Zitat von ryecoaaron

This problem has happened before but no one sticks around long enough to figure out the exact fix. It is a dependency problem and order of install issue. Sadly, I could fix this in a matter of minutes if I was logged in but it will take a bunch of back and forth to fix it.

To start, what is the output of:

sudo apt-get install policykit-1=0.105-31+deb11u1
dpkg -l | grep qemu

Alles anzeigen

I will stick around to figure out the exact fix

Here we go:

Code

sudo apt-get install policykit-1=0.105-31+deb11u1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 policykit-1 : Depends: default-logind or
                        logind
E: Unable to correct problems, you have held broken packages.
root@homeserver:~# dpkg -l | grep qemu
root@homeserver:~#

Alles anzeigen

Best regards,

Hendrik

KM0201 · 5. Januar 2023

Zitat von henfri

I will stick around to figure out the exact fix

Here we go:

Code

sudo apt-get install policykit-1=0.105-31+deb11u1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 policykit-1 : Depends: default-logind or
                        logind
E: Unable to correct problems, you have held broken packages.
root@homeserver:~# dpkg -l | grep qemu
root@homeserver:~#

Alles anzeigen

Best regards,

Hendrik

Alles anzeigen

That's weird.. are you on OMV 6? That package installed for me no problem before I enabled backports

henfri · 5. Januar 2023

Yes, OMV6.

I May have installed some more recent systems once to fix a Bug though.

ryecoaaron · 5. Januar 2023

apt-cache policy policykit-1

henfri · 5. Januar 2023

Hello,

Code

policykit-1:
  Installiert:           (keine)
  Installationskandidat: 0.105-31+deb11u1
  Versionstabelle:
     0.105-31+deb11u1 500
        500 http://ftp.halifax.rwth-aachen.de/debian bullseye/main amd64 Packages
        500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
        100 /var/lib/dpkg/status

Best regards,

Hendrik

ryecoaaron · 5. Januar 2023

That is correct. You must have something going on with systemd:

dpkg -l | grep -E "dbus|systemd"

henfri · 5. Januar 2023

Code

ii  dbus                                  1.12.24-0+deb11u1              amd64        simple interprocess messaging system (daemon and utilities)
ii  dbus-x11                              1.12.24-0+deb11u1              amd64        simple interprocess messaging system (X11 deps)
ii  libdbus-1-3:amd64                     1.12.24-0+deb11u1              amd64        simple interprocess messaging system (library)
ii  libdbus-glib-1-2:amd64                0.110-6                        amd64        deprecated library for D-Bus IPC
ii  libqt5dbus5:amd64                     5.15.2+dfsg-9                  amd64        Qt 5 D-Bus module
ii  libsystemd-shared:amd64               251.3-1~bpo11+1                amd64        systemd shared private library
ii  libsystemd0:amd64                     251.3-1~bpo11+1                amd64        systemd utility library
ii  python3-dbus                          1.2.16-5                       amd64        simple interprocess messaging system (Python 3 interface)
ii  python3-systemd                       234-3+b4                       amd64        Python 3 bindings for systemd
ii  systemd                               251.3-1~bpo11+1                amd64        system and service manager
ii  systemd-sysv                          247.3-7+deb11u1                amd64        system and service manager - SysV links

Alles anzeigen

ryecoaaron · 5. Januar 2023

There is the problem. You have systemd installed from backports. I can't tell you why especially since only a few packages are pinned from backports even when it is enabled. You can try to downgrade but I won't promise it will go well. I don't have a system to test it on but I would imagine something like this would do it:

Code

sudo apt-get install libnss-systemd=247.3-7+deb11u1 libpam-systemd=247.3-7+deb11u1 \
  libsystemd0=247.3-7+deb11u1 systemd=247.3-7+deb11u1 systemd-container=247.3-7+deb11u1 \
  systemd-sysv=247.3-7+deb11u1

henfri · 5. Januar 2023

Thanks a lot, that worked.

I am now installing the kvm-plugin (install is running, i.e. no version conflicts)

ryecoaaron · 5. Januar 2023

Good to hear.

pjnollae · 23. August 2023

I have just setup OMV on an Intel NUC, and I cant install the KVM plugin

Code

root@xnas:~# apt install openmediavault-kvm
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:


The following packages have unmet dependencies:
libdw1 : Depends: libelf1 (= 0.183-1) but 0.187-1~bpo11+1 is to be installed
policykit-1 : Depends: default-logind or
logind
python3-setuptools : Depends: python3-pkg-resources (= 52.0.0-4) but 66.1.1-1~bpo11+1 is to be installed
E: Unable to correct problems, you have held broken packages.

Alles anzeigen

I have tried the commans above, but it wont help me ?

ryecoaaron · 23. August 2023

Zitat von pjnollae

I have just setup OMV on an Intel NUC, and I cant install the KVM plugin

Did you use the OMV iso to install?

pjnollae · 23. August 2023

yes, I used the ISO and then I have updated the system (and rebooted) and enabled omv-extras :-|

ryecoaaron · 23. August 2023

Do you get the same issue installing from the web interface? I guess I need to setup a fresh system to see if something in Debian backports changed.

Jetzt mitmachen!