On Mon, Jun 15, 2020 at 5:58 PM Marco Fais <evilmf@gmail.com> wrote:
Hi Nir,
I have raised the same issue here: https://bugzilla.redhat.com/show_bug.cgi?id=1840414
It is indeed working with the libvirt and qemu versions you mention below, however in order to use them I had to add the testing repository for AV which could bring other issues... Also ovirt-node-4.4.0 ships with libvirt 5.6/qemu 4.1 -- if the recommended versions are the more recent ones, should they not be included in ovirt-node-4.4.x as well?
At this point, yes, you should use the testing repos, since libivrt and qemu are too old in CentOS 8.1. Once CentOS 8.2 is released, we should be good with the official packages.
Thanks, Marco
On Mon, 15 Jun 2020 at 13:00, Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Jun 15, 2020 at 2:38 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Mon, Jun 15, 2020 at 2:13 PM minnie.du@vinchin.com <minnie.du@vinchin.com> wrote:
Hi,
I tried to send the log to you by email, but it fails. So I have sent them to Google Drive. Please go to the link below to get them:
https://drive.google.com/file/d/1c9dqkv7qyvH6sS9VcecJawQIg91-1HLR/view?usp=s... https://drive.google.com/file/d/1zYfr_6SLFZj_IpM2KQCf-hJv2ZR0zi1c/view?usp=s...
I did get them, but not engine logs. Can you please attach them as well? Thanks.
vdsm.log.61 has:
2020-05-26 14:36:49,668+0000 ERROR (jsonrpc/6) [virt.vm] (vmId='e78ce69c-94f3-416b-a4ed-257161bde4d4') Live merge failed (job: 1c308aa8-a829-4563-9c01-326199c3d28b) (vm:5381) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5379, in merge bandwidth, flags) File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f ret = attr(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python3.6/site-packages/libvirt.py", line 728, in blockCommit if ret == -1: raise libvirtError ('virDomainBlockCommit() failed', dom=self) libvirt.libvirtError: internal error: qemu block name 'json:{"backing": {"driver": "qcow2", "file": {"driver": "file", "filename": "/rhev/data-center/mnt/192.168.67.8:_root_nfs_ovirt44__vm/01477dfd-1f4c-43d4-b000-603c6ed839b6/images/6140b67d-9895-4ee6-90a9-5410de8b5a01/08f91e3f-f37b-4434-a183-56478b732c1b"}}, "driver": "qcow2", "file": {"driver": "file", "filename": "/rhev/data-center/mnt/192.168.67.8:_root_nfs_ovirt44__vm/01477dfd-1f4c-43d4-b000-603c6ed839b6/images/6140b67d-9895-4ee6-90a9-5410de8b5a01/5ba0d7e5-afa8-4d75-bc5a-1b077955a990"}}' doesn't match expected '/rhev/data-center/mnt/192.168.67.8:_root_nfs_ovirt44__vm/01477dfd-1f4c-43d4-b000-603c6ed839b6/images/6140b67d-9895-4ee6-90a9-5410de8b5a01/5ba0d7e5-afa8-4d75-bc5a-1b077955a990'
This is a known issue in libvirt 5.6/qemu 4.1.
It works in libivrt >= 6.0 and qemu >= 4.2, which are the versions needed for 4.4.
Adding Eyal. Eyal, can you please have a look? Thanks.
Best regards,
Minnie Du--Presales & Business Development
Mob : +86-15244932162 Tel : +86-28-85530156 Skype :minnie.du@vinchin.com Email: minnie.du@vinchin.com Website: www.vinchin.com
F5, Building 8, National Information Security Industry Park, No.333 YunHua Road, Hi-Tech Zone, Chengdu, China
From: Yedidyah Bar David Date: 2020-06-15 15:42 To: minnie.du CC: users Subject: Re: [ovirt-users] Problem with oVirt 4.4 On Mon, Jun 15, 2020 at 10:39 AM <minnie.du@vinchin.com> wrote:
We have met a problem when testing oVirt 4.4.
Our VM is on NFS storage. When testing the snapshot function of oVirt 4.4, we created snapshot 1 and then snapshot 2, but after clicking the delete button of snapshot 1, snapshot 1 failed to be deleted and the state of corresponding disk became illegal. Removing the snapshot in this state requires a lot of risky work in the background, leading to the inability to free up snapshot space. Long-term backups will cause the target VM to create a large number of unrecoverable snapshots, thus taking up a large amount of production storage. So we need your help.
Can you please share relevant parts of engine and vdsm logs? Perhaps open a bug and attach all of them, just in case.
Thanks! -- Didi
-- Didi _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/U4SBKJTS4OSWVZ...
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VJ7T5B3URAV3QV...