New openmediavault-kvm plugin

    • Offizieller Beitrag

    An other solution would be a access option to some logging files, so i can calculate the whole timing

    All backups log to /var/log/omv-backup-vm.log. There should be a starting and ending event for each one.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    This log is viewable from the web interface under kvm backups too.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    You could also just make a script that runs under scheduled tasks that looks like:


    #!/bin/bash

    omv-backup-vm -v omv5dev -d /srv/backup/vm/ -k 2 >/dev/null 2>&1

    omv-backup-vm -v omv6dev -d /srv/backup/vm/ -k 3 >/dev/null 2>&1

    omv-backup-vm -v vm1 -d /srv/backup/vm/ -k 1 >/dev/null 2>&1

    omv-backup-vm -v vm2 -d /srv/backup/vm/ -k 1 >/dev/null 2>&1

    omv-backup-vm -v vm3 -d /srv/backup/vm/ -k 1 >/dev/null 2>&1


    -v is the VM

    -d is the backup directory

    -k is the number of backups to keep

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Hi Guys! after installing virt-manager, when i want to create a vm throught web cnsole i see this warning, and cant chose virtual disk to connect to the VM.
    Warning:

    500 - Internal Server Error Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; virsh vol-list VM's --details | sed 1,2d | awk NF | awk -F '[[:space:]][[:space:]]+' '{ print $1","$2","$4 }'' with exit code '2':

    OMV 6.
    Motherboard: Intel DP55WG
    CPU: Intel Xeon X3470
    12GB DDR3 RAM
    WD Black WD5000LPSX - system
    WD Blue 4GB x4 - RAID 10
    500GB SSD x2 - RAID 1 for VM's and Docker containers

  • You could also just make a script that runs under scheduled tasks that looks like:


    -v is the VM

    -d is the backup directory

    -k is the number of backups to keep

    I've come up with the following script. It's more dynamic and backs up every existing vm. Don't roast me too much, i'm not a dev.


    • Offizieller Beitrag

    I've come up with the following script. It's more dynamic and backs up every existing vm. Don't roast me too much, i'm not a dev.

    Looks ok to me. This was the one I wrote that I was going to post:


    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Hi Guys! after installing virt-manager, when i want to create a vm throught web cnsole i see this warning, and cant chose virtual disk to connect to the VM.
    Warning:

    500 - Internal Server Error Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; virsh vol-list VM's --details | sed 1,2d | awk NF | awk -F '[[:space:]][[:space:]]+' '{ print $1","$2","$4 }'' with exit code '2':

    Can anyone help?

    OMV 6.
    Motherboard: Intel DP55WG
    CPU: Intel Xeon X3470
    12GB DDR3 RAM
    WD Black WD5000LPSX - system
    WD Blue 4GB x4 - RAID 10
    500GB SSD x2 - RAID 1 for VM's and Docker containers

    • Offizieller Beitrag

    i have one VM which is running fine, but backup isn't working with the plugin. The error isn't reaching the log, it's only viewable via omv GUI.

    Because of that, i've added a screenshot

    It is failing to snapshot the VM (no guest tools installed?). Try taking a snapshot with virsh to get a better error message.

    an other, for me new error is, that if the VNC passwords in the VM configs are longer than 8 characters, the plugin has problems (start vm etc.). This was not the case with OMV5 kvm plugin

    I didn't think a password longer than 8 characters was a valid password for vnc? But anyway, I'm not sure why it isn't start since both versions started the VM exactly the same way with libvirt-php - 6.x and 5.x

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Can anyone help?

    You have an illegal pool name - VM's. Not sure how you created it but you shouldn't have spaces or punctuation in VM, network, or pool names.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • You have an illegal pool name - VM's. Not sure how you created it but you shouldn't have spaces or punctuation in VM, network, or pool names.

    Thanks! Ive created that pool before i upgrade to omv6. In omv5 all work great!
    But i cant rename pool. Is it only might be deleted and recreat? or i can rename pool?

    OMV 6.
    Motherboard: Intel DP55WG
    CPU: Intel Xeon X3470
    12GB DDR3 RAM
    WD Black WD5000LPSX - system
    WD Blue 4GB x4 - RAID 10
    500GB SSD x2 - RAID 1 for VM's and Docker containers

    • Offizieller Beitrag

    Is it only might be deleted and recreat?

    I guess I will have to escape the pool name since the plugin allows some punctuation. yuck.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • It is failing to snapshot the VM (no guest tools installed?). Try taking a snapshot with virsh to get a better error message.

    I didn't think a password longer than 8 characters was a valid password for vnc? But anyway, I'm not sure why it isn't start since both versions started the VM exactly the same way with libvirt-php - 6.x and 5.x

    was working in OMV5, (VNC password), nothing changed with the VMS...well....

    regarding the failed backup, it fails even with not running VM, so only copying the file should take place. I cannot install guest tools as there are none for this OS.

    Can you provide a virsh command to test the backup? i only found whole scripts while googling....

    • Offizieller Beitrag

    was working in OMV5, (VNC password), nothing changed with the VMS...well....

    I don't maintain libvirt-php. So, if something changes, I can't control that. Does virsh start VMNAME work?

    regarding the failed backup, it fails even with not running VM, so only copying the file should take place. I cannot install guest tools as there are none for this OS.

    Can you provide a virsh command to test the backup? i only found whole scripts while googling....

    What OS is it?


    virsh isn't backing things up. The script I wrote is. And if the VM is powered off, it doesn't take a snapshot. The script enumerates the disks on the VM and backs them up using qemu-img. What do you get if you run the omv-backup-vm script against that machine?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I don't maintain libvirt-php. So, if something changes, I can't control that. Does virsh start VMNAME work?

    What OS is it?


    virsh isn't backing things up. The script I wrote is. And if the VM is powered off, it doesn't take a snapshot. The script enumerates the disks on the VM and backs them up using qemu-img. What do you get if you run the omv-backup-vm script against that machine?

    OS is XPEnology, the "x-86" mod of a Synology Device


    the backup script shows:


    [2022-06-04 18:53:49+0200] [backup] Copy disks to backup directory...

    [2022-06-04 18:53:49+0200] [backup] Copying disk :: syno-ds918-qcow2.img

    qemu-img: Could not open 'syno-ds918-qcow2.img': Could not open 'syno-ds918-qcow2.img': No such file or directory


    which is the only script output of a working VM with only shows the file instead the whole path /srv/dev- ...you name it/ i don't know why the backup of THIS VM doesn't find the path


    ...and regarding the VNC password... i had passwords <8 chars, but cannot enter them into virt manager anymore. So huh.... consider it solved. Something changed on an other end.....

    • Offizieller Beitrag

    qemu-img: Could not open 'syno-ds918-qcow2.img': Could not open 'syno-ds918-qcow2.img': No such file or directory


    which is the only script output of a working VM with only shows the file instead the whole path /srv/dev- ...you name it/ i don't know why the backup of THIS VM doesn't find the path

    Can you post (or PM me) the xml for this VM?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I guess I will have to escape the pool name since the plugin allows some punctuation. yuck.

    When i'm trying to stop VM's pool (i create anoter pool with same path) i see an error( screns from syslog and the error)

    All machines wich uses pool is stopped

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!