I know what you are trying to do. you need to enable backports. There is a button to do in omv-extras.
Thanks you a lot sir, I installed the backport and after that KVM installed without any problems. Openmediavault is the best NAS software!
Beiträge von romanad
-
-
No, just clean install + configuring network interface + adding repositories + updates. + omv-extras+ zfs plugin and now I'm trying to install KVM plugin.
I'm trying to figure out how to install openmediavault that works stable and with main functions (zfs, kvm, docker).
-
I don't even need to look at the output. When you install without networking, you will not have the primary debian repos. You will need to change /etc/apt/sources.list to look like this:
deb http://deb.debian.org/debian/ bookworm main non-free non-free-firmware
deb http://deb.debian.org/debian/ bookworm-updates main non-free-firmware
Thank you very much.
I still use stable version, so I changed to:
deb http://deb.debian.org/debian/ bullseye main non-free non-free-firmware
deb http://deb.debian.org/debian/ bullseye-updates main non-free-firmware
ZFS is working, but KVM still has an error.
-
Did you installed docker from CLI or from OMV?
What is the output of
omv-aptclean repos
cat /etc/apt/sources.list.d/omvdocker.list
Thank you very much, looks like it helped.
-
When updating, an error appears:
"GPG Error: https://download.docker.com/linux/debian bullseye InRelease: The following signatures cannot be verified because the public key is not available: NO_PUBKEY 7EA0A9C3F273FCD8
E: The repository 'https://download.docker.com/linux/debian bullseye InRelease' is not signed.
N: Updating from such a repository cannot be done safely, so it is disabled by default.
N: See the apt-secure(8) manual page for details on repository creation and user configuration."
The command "gpg --debug-level guru --keyserver hkps://keyserver.ubuntu.com --recv-keys 7EA0A9C3F273FCD8" gives the error: " ERR 219 Server indicated failure <Unspecified source>".
Linux version: Debian 6.1.55-1~bpo11+1 (2023-10-08) x86_64 GNU/Linux.
-
I would guess your Debian repos are not correct. Did you install Debian without network? What is the output: sudo omv-aptclean (please cut&paste instead of screenshot).
Yes, I installed without network because with networking enabled omv hangs during installation for some reason.
I've attached the file with output.
-
Your first two images are dependency issues with other packages not the kvm plugin.
In addition to chente's output, also post:
dpkg -l | grep -E "kvm|libvirt|qemu"
I just install the clean stable version, do everything standard, update only via web-interface, then run omv-upgrade. Than I install extras ( from this link https://github.com/OpenMediaVa…Script/raw/master/install ) and immediately get problems with dependencies.
-
What is the output of
dpkg -l | grep openmediavault
Do you have backports activated?
-
I have recently encountered problems with OMV stability in terms of KVM and ZFS. Now after installing the current distribution I have problems with KVM and ZFS, the custom proxmox kernel solves the problem with ZFS, which is very happy, but the KVM web interface plugin doesn't work anywhere else, neither in 6 nor 7 versions if freshly instal it now, there are problems with dependencies.
Maybe I just don't understand something and everything is not so sad?
Please explain the situation.
-
I'm able to use virt-manager with WSL (Windows Subsystem for Linux). But the question is not about virt-manager.
QEMU can have additional functionality by enabling modules while building - for example - VirGL .
It can't be enabled with virt-manager.
I just want to add them.
-
Dear friends,
I would like to enable additional modules like Pulse audio and VirGL (a virtual 3D GPU for use inside QEMU virtual machines, that allows the guest operating system to use the capabilities of the host GPU to accelerate 3D rendering).
Usually modules can be enabled with building command like: "./configure --enable-sdl --with-sdlabi=2.0 --enable-opengl --enable-virglrenderer --enable-system --enable-modules --audio-drv-list=pa --target-list=x86_64-softmmu --enable-kvm".
How to properly add additional modules to KVM plugin or any other workaround?
-
I'm using Intel Core i5-10400. Full specs are in attachment.
Wetty works if I install it separately with docker container, but it's not very handy due to inability to run it from openmediavault web-interface.
-
Dear friends,
I'm not able to make WeTTY work.
I'm using 6.9.0-1 (Shaitan)
I have this error:
"Trying to pull docker.io/wettyoss/wetty:latest...
unexpected end of JSON input
Error: Error initializing source docker://wettyoss/wetty:latest: error getting username and password: error reading JSON file "/root/.docker/config.json": error unmarshaling JSON at "/root/.docker/config.json": unexpected end of JSON input"
Screenshot and full log are in attachments.
-
sorry not related to your original question, but i have interest to know how you implement a RAIDZ self-encrypred ZFS volume and how do you un-encrypt it for use on OMV.
I'm interested if you do it from shell and problems that you see actually for use on OMV.
1) how you implement a RAIDZ self-encrypted ZFS volume:
Install Omv Extras and ZFS plugins
2) how do you un-encrypt it for use on OMV:
OMV fully support Open ZFS with plugin so every operation on ZFS (encrypt/decrypt) you can do on OMV
-
Dear friends,
I have some Issues with ssh, X11 forwarding and gedit.
When I'm running OMV6 on VMware Workstation gedit and X11 forwarding work fine.
But when I running OMV6 on ASRock H570M-ITXac motherboard I'm keep getting this error when trying to launch gedit - "(gedit:36935): Gtk-WARNING **: 23:12:38.291: cannot open display:"
When I'm running "xhost +" I'm getting this error - " xhost: unable to open display "" "
Could you please help me to troubleshoot.
-
I know I also can use VNC with specific motherboards for example Intel AMT feature but they are too big for home NAS builds : )
-
Can't you just do snapshots?
Or make a backup of the virtual disk if that is not possible? In that case I would switch to KVM
Thank you very much, that's a viable workaround
