[ovirt-users] Re: upgrading to 4.4.6 with Rocky Linux 8

[Hayden Young via Users]

On Tue, 2021-07-13 at 21:01 +0300, Nir Soffer wrote:
> On Tue, Jul 13, 2021 at 2:57 PM Branimir Pejakovic <
> branim...@gmail.com> wrote:
> ...
> > > On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic
> > >  > > 
> > > Unfortunately vdsm (the core package for ovirt host) does not
> > > have ovirt-prefix. Which version do you have?
> > > ...
> > 
> > Just in case:
> > 
> > # rpm -qa | grep vdsm
> > vdsm-jsonrpc-4.40.60.7-1.el8.noarch
> > vdsm-yajsonrpc-4.40.60.7-1.el8.noarch
> > vdsm-common-4.40.60.7-1.el8.noarch
> > vdsm-client-4.40.60.7-1.el8.noarch
> > vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
> > vdsm-api-4.40.60.7-1.el8.noarch
> > vdsm-python-4.40.60.7-1.el8.noarch
> > vdsm-network-4.40.60.7-1.el8.x86_64
> > vdsm-http-4.40.60.7-1.el8.noarch
> > vdsm-4.40.60.7-1.el8.x86_64
> > 
> > > This package requires qemu-img >= 5.2.0
> > > Maybe the requirement is broken (missing epoch).
> > > 
> > > What does "qemu-img --version" tell?
> > 
> > # qemu-img --version
> > qemu-img version 4.2.0 (qemu-kvm-4.2.0-
> > 48.module+el8.4.0+534+4680a14e)
> > Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project
> > developers
> > 
> > During the installation itself, there were no errors/surprises.
> > Everything went smoothly.
> 
> So vdsm spec is broken on Rocky, letting you install vdsm when the
> required
> qemu-kvm version is not available.
> 
> Can you file an ovirt/vdsm bug for this?
> https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm
> 
> I tried to add a Rocky host to my setup and I can confirm that it
> works.
> 
> I create a new vm from:
> https://download.rockylinux.org/pub/rocky/8/isos/x86_64/Rocky-8.4-x86_64-dvd1.iso
> 
> Install ovirt-release44.rpm from:
> https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
> 
> And added the host to my engine (4.4.8 master). The host was
> installed
> and activated, and can runs.
> 
> I found that migrating vms from other hosts (qemu-6.0, libvirt 7.4)
> does not work. I think this issue was already reported here and fix
> is
> expected from libvirt soon.
> 
> However I do get the the *right* version of qemu-kvm, provided by:
> 
> [root@rocky1 ~]# dnf info qemu-kvm
> Last metadata expiration check: 18:02:00 ago on Tue 13 Jul 2021
> 02:37:31 AM IDT.
> Installed Packages
> Name : qemu-kvm
> Epoch: 15
> Version  : 5.2.0
> Release  : 16.el8
> Architecture : x86_64
> Size : 0.0
> Source   : qemu-kvm-5.2.0-16.el8.src.rpm
> Repository   : @System
> From repo: ovirt-4.4-advanced-virtualization
> 
> [root@rocky1 ~]# grep -A2 ovirt-4.4-advanced-virtualization
> /etc/yum.repos.d/ovirt-4.4-dependencies.repo
> [ovirt-4.4-advanced-virtualization]
> name=Advanced Virtualization packages for $basearch
> mirrorlist=
> http://mirrorlist.centos.org/?arch=$basearch=8=virt-advanced-virtualization
> 
> So oVirt is ready to rock on Rocky with little help from Centos :-)
> 
> I'm not sure about the future of the ovirt-4.4-advanced-
> virtualization
> repository after Centos 8 will be discontinued, so this does not look
> like production ready yet.
> 
> The advanced virtualization packages are likely needed by other
> virtualization
> systems (openstack, proxmox, ...) or anyone that wants to consume the
> latest
> features from libvirt and qemu, so packing it in oVirt is not the
> right solution.
> 
> Nir
> 

So some good news on the adv. virt front -- My colleague Louis has
informed me that the module is actually already staged for build &
import in Distrobuild with some passing builds in Koji & MBS.

https://distrobuildstg.rockylinux.org/packages/3424

I have no ETA on when those will be available in repos, and is 110%
being put back until we have Secure Boot completed, but it's a start!
You can see the MBS link in the Builds column for logs & info from our
MBS instance, and r8-stream-rhel is a link to the RPM sources in our
Gitlab.

Good progress!

If someone would go ahead and verify that the package versions in here
match what oVirt needs, that'd give us some sense of assurance that
we're poking the right bear, so to speak haha

-- 
- Hayden, Rocky Team Lead


signature.asc
Description: This is a digitally signed message part
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/TCCRNMXG2RIZVNRAHJDSXNEHDTVOC5A3/

[ovirt-users] Re: How to remove "VM is being cloned" flag in a failed clone VM operation

[Richard Chan]

That worked! Thank you very much.

On Wed, Jul 14, 2021 at 12:11 AM Arik Hadas  wrote:

>
>
> On Tue, Jul 13, 2021 at 3:56 PM Richard Chan 
> wrote:
>
>> Hello list,
>>
>> I had an unsuccessful zombie clone VM task  -
>> 1. Target: was able to unlock the disks and delete the target VM
>> 2. Source: able to unlock the disks.
>>
>> Now I cannot do anything with the source as it is flagged as "VM is being
>> clone".
>>
>> Is there a way to remove this flag manually?
>>
>
>> vdms-client Host -> this does not show any tasks outstanding.
>>
>
> That's an in-memory lock - if the tasks were removed also on the engine
> side, just restart ovirt-engine and the vm would be unlocked
>
>
>>
>> Thank you.
>>
>> Richard Chan
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/PJZMIIGTEKDM2EPKMQTXU7AEDWAUFFT2/
>>
>

-- 
Richard Chan
Chief Architect

TreeBox Solutions Pte Ltd
1 Commonwealth Lane #03-01
Singapore 149544
Tel: 6570 3725
http://www.treeboxsolutions.com

Co.Reg.No. 201100585R
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/TU7M7BFCGYNE64ZQ3N65HKAS53CTTJJ2/

[ovirt-users] Re: 4.4.7 gluster quorum problem

[Strahil Nikolov via Users]

After rebootof node1 -> bricks must always come up. Most probably VDO had to 
recover for a longer period blocking the bricks coming up on time.Investigate 
this issue before rebooting another host.
Best Regards,Strahil Nikolov
 
 
Hi guys,
one strange thing happens, cannot understand it.
Today i installed last version 4.4.7 on centos stream, replica 3, via cockpit, 
internal lan for sync. Seems all ok, if reboot 3 nodes together aslo ok. But if 
i reboot 1 node ( and declare node rebooted through web ui) the bricks (engine 
and data) remain down on that node. All is clear on logs without explicit 
indication of the situation except "Server quorum regained for volume data. 
Starting local bricks" on glusterd.log. After "systemctl restart glusterd" 
bricks gone down on another node. After  "systemctl restart glusterd" on that 
node all is ok.
Where should i look?

some errors of log that i found:

- bdocker.log:
statusStorageThread::ERROR::2021-07-12 
22:17:02,899::storage_broker::223::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(put_stats)
 Failed to write metadata for ho$
Traceback (most recent call last):
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
 line 215, in put_stats
    f = os.open(path, direct_flag | os.O_WRONLY | os.O_SYNC)
FileNotFoundError: [Errno 2] No such file or directory: 
'/run/vdsm/storage/53b068c1-beb8-4048-a766-3a4e71ded624/d3df7eb6-d453-439a-8436-d3694d4b5179/de18b2cc-a4e1-4afc-9b5a-6063$
StatusStorageThread::ERROR::2021-07-12 
22:17:02,899::status_broker::90::ovirt_hosted_engine_ha.broker.status_broker.StatusBroker.Update::(run)
 Failed to update state.
Traceback (most recent call last):
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
 line 215, in put_stats
    f = os.open(path, direct_flag | os.O_WRONLY | os.O_SYNC)
FileNotFoundError: [Errno 2] No such file or directory: 
'/run/vdsm/storage/53b068c1-beb8-4048-a766-3a4e71ded624/d3df7eb6-d453-439a-8436-d3694d4b5179/de18b2cc-a4e1-4afc-9b5a-6063$

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/status_broker.py",
 line 86, in run
    entry.data
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
 line 225, in put_stats
    .format(str(e)))
ovirt_hosted_engine_ha.lib.exceptions.RequestError: failed to write metadata: 
[Errno 2] No such file or directory: 
'/run/vdsm/storage/53b068c1-beb8-4048-a766-3a4e71ded624/d3df7e$
StatusStorageThread::ERROR::2021-07-12 
22:17:02,899::storage_broker::223::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(put_stats)
 Failed to write metadata for ho$
Traceback (most recent call last):
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
 line 215, in put_stats
    f = os.open(path, direct_flag | os.O_WRONLY | os.O_SYNC)
FileNotFoundError: [Errno 2] No such file or directory: 
'/run/vdsm/storage/53b068c1-beb8-4048-a766-3a4e71ded624/d3df7eb6-d453-439a-8436-d3694d4b5179/de18b2cc-a4e1-4afc-9b5a-6063$
StatusStorageThread::ERROR::2021-07-12 
22:17:02,899::status_broker::90::ovirt_hosted_engine_ha.broker.status_broker.StatusBroker.Update::(run)
 Failed to update state.
Traceback (most recent call last):
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
 line 215, in put_stats
    f = os.open(path, direct_flag | os.O_WRONLY | os.O_SYNC)
FileNotFoundError: [Errno 2] No such file or directory: 
'/run/vdsm/storage/53b068c1-beb8-4048-a766-3a4e71ded624/d3df7eb6-d453-439a-8436-d3694d4b5179/de18b2cc-a4e1-4afc-9b5a-6063$

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/status_broker.py",
 line 86, in run
    entry.data
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
 line 225, in put_stats
    .format(str(e)))
ovirt_hosted_engine_ha.lib.exceptions.RequestError: failed to write metadata: 
[Errno 2] No such file or directory: 
'/run/vdsm/storage/53b068c1-beb8-4048-a766-3a4e71ded624/d3df7e$
StatusStorageThread::ERROR::2021-07-12 
22:17:02,902::status_broker::70::ovirt_hosted_engine_ha.broker.status_broker.StatusBroker.Update::(trigger_restart)
 Trying to restart the $
StatusStorageThread::ERROR::2021-07-12 
22:17:02,902::storage_broker::173::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(get_raw_stats)
 Failed to read metadata fro$
Traceback (most recent call last):
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
 line 155, in get_raw_stats
    f = os.open(path, direct_flag | os.O_RDONLY | os.O_SYNC)
FileNotFoundError: [Errno 2] No such file or directory: 

[ovirt-users] Re: [4.4.7] The latest guest agent needs to be installed and running on the guest

[Gervais de Montbrun]

Thanks folks.

Submitted:
https://bugzilla.redhat.com/show_bug.cgi?id=1981946

Hope sufficient info is included.

Cheers,
Gervais



> On Jul 13, 2021, at 4:35 AM, Tomáš Golembiovský  wrote:
> 
> Hi, sorry for late reply. To understand this we will have to see the
> logs. Please open a bug on vdsm with description of the problem and log
> attached.
> 
> Use the following procedure:
> - stop the VM on problematic host
> - enable debug logs for vds logger, you can do that either in
>  /etc/vdsm/logger.conf (requires vdsmd restart) or temporarily from
>  command line with:
> 
>vdsm-client Host setLogLevel level=DEBUG name=vds
> 
> - start the VM
> - let it run for several minutes
> - attach vdsm.log, engine.log and output of:
> 
>vdsm-client VM getStats vmID=
> 
> Thanks,
> 
>Tomas
> 
> On Sun, Jul 11, 2021 at 09:15:35PM -0300, Gervais de Montbrun wrote:
>> This problem continues and I am expecting issues tomorrow morning when my 
>> developers return to the office... ☹️
>> 
>> I did notice that my ovirt-engine is still running CentOS Linux and not 
>> CentOS Stream. The release notes say that the oVirt nodes and the engine 
>> would be running CentOS Stream after updating. The nodes are all on CentOS 
>> stream and I had to do the necessary steps to get selinux to allow 
>> migrations and fixed up the extra yum repos.
>> 
>> Does something need to be done regarding the ovirt-engine. I'm not seeing 
>> anything in the release notes or in general documentation regarding 
>> upgrades. Could the issues I am having be related to still being on CentOS 
>> Linux?
>> 
>> Cheers,
>> Gervais
>> 
>> 
>> 
>>> On Jul 9, 2021, at 4:18 PM, Gervais de Montbrun  
>>> wrote:
>>> 
>>> Hi Folks,
>>> 
>>> I upgraded my cluster yesterday and am having the same issue described 
>>> here.  Boxes are booting up, but their IP addresses are never being updated 
>>> in the oVirt admin console.
>>> 
>>> Restarting the hosts seemed to temporarily solve the issue, but it quickly 
>>> returns. This is a huge issue for us as we need the ovirt engine to have 
>>> the correct IP address of vm's in it as the vagrant plugin we use queries 
>>> the ovirt api and uses this IP to communicate with vm's.
>>> 
>>> This is stopping our development team from being able to create new vm's. 
>>> It will become a massive issue for me very quickly.
>>> 
>>> My installed versoion:
>>> libvirt-7.4.0-1.el8s.x86_64
>>> vdsm-common-4.40.70.6-1.el8.noarch
>>> qemu-kvm-6.0.0-19.el8s.x86_64
>>> 
>>> Any help would be greatly appreciated.
>>> 
>>> Cheers,
>>> Gervais
>>> 
>>> 
>>> 
 On Jul 9, 2021, at 6:51 AM, Christoph Timm >>> > wrote:
 
 Hi Tomáš,
 
 I put the host in maintenance today and give it another reboot.
 After that the information are available for the VMs running on that host.
 Also the exclamation mark is gone.
 
 So I guess something did not come up correctly during the restart of the 
 host.
 
 Best regards
 Christoph
 
 Am 08.07.21 um 20:36 schrieb Christoph Timm:
> Hi Tomáš,
> 
> sorry for the late reply and for my the missing information.
> 
> Am 08.07.21 um 16:50 schrieb Tomáš Golembiovský:
>> On Thu, Jul 08, 2021 at 02:02:14PM +0200, Christoph Timm wrote:
>>> Hi list,
>>> 
>>> I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs 
>>> have
>>> issues to report the performance information via the guest agent.
>> The performance info is provided by libvirt and not by guest agent.
>> Could you be more specific about which information is missing?
> Sorry I did not mean the performance information like Memory, CPU and 
> Network. These are available. The missing information are IP Addresses 
> and FQDN. 
>> What is the version of vdsm and libvirt on the host?
> All hosts are running: libvirt-7.0.0-14.1.el8
>> 
>>> I see the following message on the VMs: The latest guest agent needs to 
>>> be
>>> installed and running on the guest
>>> 
>> This is probably unrelated to the above. But still, what is the exact
>> version of the guest agent?
> I have tried already different versions.
> For example: 
> qemu-guest-agent.x86_64
> 15:4.2.0-48.module_el8.4.0+783+f8734d30 @@commandline
> qemu-guest-agent.x86_64
> 15:2.12.0-88.module_el8.1.0+248+298dec18 @AppStream
> 
>>> The qemu-guest agent is installed on VMs (the VM OS is CentOS 8).
>>> 
>>> Any advice how to troubleshoot this?
>>> 
>>> I can see the stats will be presented in the GUI, if I migrate the VM 
>>> to a
>>> different host.
>> Same here, could you provide version of vdsm and libvirt on the host
>> where your VM is working fine?
> KVM Version: 5.2.0 - 16.el8
> LIBVIRT Version: libvirt-7.0.0-14.1.el8
> VDSM Version: 

[ovirt-users] Re: oVirt and ARM

[Marko Vrgotic]

Dear Arik and Milan,

In the meantime, I was asked to check if in current 4.4 version or coming 4.5, 
are/will there any capabilities or options of emulating aarch64 on x86_64 
platform and if so, what would be the steps to test/enable it.

Can you provide some information?

-
kind regards/met vriendelijke groeten

Marko Vrgotic
Sr. System Engineer @ System Administration

ActiveVideo
o: +31 (35) 6774131
m: +31 (65) 5734174
e: m.vrgo...@activevideo.com
w: www.activevideo.com

ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ 
Hilversum, The Netherlands. The information contained in this message may be 
legally privileged and confidential. It is intended to be read only by the 
individual or entity to whom it is addressed or by their designee. If the 
reader of this message is not the intended recipient, you are on notice that 
any distribution of this message, in any form, is strictly prohibited.  If you 
have received this message in error, please immediately notify the sender 
and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or 
destroy any copy of this message.



From: Sandro Bonazzola 
Date: Friday, 9 July 2021 at 15:37
To: Marko Vrgotic , Arik Hadas , 
Milan Zamazal 
Cc: Evgheni Dereveanchin , Zhenyu Zheng 
, Joey Ma , users@ovirt.org 

Subject: Re: [ovirt-users] oVirt and ARM

***CAUTION: This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender!!!***


Il giorno ven 9 lug 2021 alle ore 11:00 Marko Vrgotic 
mailto:m.vrgo...@activevideo.com>> ha scritto:
Hi Sandro and the rest of oVirt gurus,

My managers are positive regarding helping provide some ARM hardware, but it 
would not happened earlier than three months from now, as we are in process of 
establishing certain relationship with ARM HW vendor.

T news!


In the meantime, I was asked to check if in current 4.4 version or coming 4.5, 
are/will there any capabilities or options of emulating aarch64 on x86_64 
platform and if so, what would be the steps to test/enable it.

+Arik Hadas , +Milan 
Zamazal ?


Kindly awaiting your reply.

Marko Vrgotic

From: Marko Vrgotic 
mailto:m.vrgo...@activevideo.com>>
Date: Monday, 28 June 2021 at 15:38
To: Sandro Bonazzola mailto:sbona...@redhat.com>>, Evgheni 
Dereveanchin mailto:edere...@redhat.com>>
Cc: Zhenyu Zheng mailto:zhengzhenyul...@gmail.com>>, 
Joey Ma mailto:majunj...@gmail.com>>, 
users@ovirt.org 
mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] oVirt and ARM
Hi Sandro,

I will check with my managers if we have and could spare some hardware to 
contribute developing for oVirt.


-
kind regards/met vriendelijke groeten

Marko Vrgotic
Sr. System Engineer @ System Administration

ActiveVideo
o: +31 (35) 6774131
m: +31 (65) 5734174
e: m.vrgo...@activevideo.com
w: www.activevideo.com

ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ 
Hilversum, The Netherlands. The information contained in this message may be 
legally privileged and confidential. It is intended to be read only by the 
individual or entity to whom it is addressed or by their designee. If the 
reader of this message is not the intended recipient, you are on notice that 
any distribution of this message, in any form, is strictly prohibited.  If you 
have received this message in error, please immediately notify the sender 
and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or 
destroy any copy of this message.



From: Sandro Bonazzola mailto:sbona...@redhat.com>>
Date: Friday, 25 June 2021 at 15:26
To: Marko Vrgotic 
mailto:m.vrgo...@activevideo.com>>, Evgheni 
Dereveanchin mailto:edere...@redhat.com>>
Cc: Zhenyu Zheng mailto:zhengzhenyul...@gmail.com>>, 
Joey Ma mailto:majunj...@gmail.com>>, 
users@ovirt.org 
mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] oVirt and ARM

***CAUTION: This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender!!!***


Il giorno ven 25 giu 2021 alle ore 14:20 Marko Vrgotic 
mailto:m.vrgo...@activevideo.com>> ha scritto:
Hi Sandro,

Thank you for the update. I am not equipped to help on development side, but I 
can most certainly do test deployments, once there is something available.

We are big oVirt shop and moving to ARM64 with new product, it would be great 
if oVirt would start supporting it.

If we are able to help somehow, let me know.

I guess a start could be adding some arm64 machine to oVirt infrastructure so 
developers can build for it.
You can have a look at 

[ovirt-users] Re: upgrading to 4.4.6 with Rocky Linux 8

[Nir Soffer]

On Tue, Jul 13, 2021 at 4:19 PM Marcin Sobczyk  wrote:
>
>
>
> On 7/12/21 2:11 AM, Nir Soffer wrote:
> > On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic  
> > wrote:
> >> It was a fresh install of 2 VMs on top of VirtualBox with Rocky fully 
> >> updated on both prior to oVirt installation. I installed it yesterday and 
> >> followed the usual way of installing it: 
> >> https://www.ovirt.org/download/alternate_downloads.html.
> >>
> >> Here are the oVirt packages that are installed on the hypervisor:
> > Unfortunately vdsm (the core package for ovirt host) does not
> > have ovirt-prefix. Which version do you have?
> > ...
> >> ovirt-imageio-client-2.2.0-1.el8.x86_64
> > This package requires qemu-img >= 5.2.0
> > Maybe the requirement is broken (missing epoch).
> As you quoted, the requirement states:
>
> %if 0%{?rhel} >= 8
> %if 0%{?centos}
> Rocky linux probably doesn't have these macros.
> OTOH 'ovirt-host' package requires plain 'libvirt',
> no version limitations, and that probably sucks in "any 'qemu-kvm'
> possible".

I expect "rhel" to be available on every rhel-like distro but centos is
most likely not available.

So we expect to use the rhel branch:

# 4.4, AV 8.4 - https://bugzilla.redhat.com/1948532
Requires: qemu-kvm >= 15:5.2.0-15.module+el8.4.0+10650+50781ca0

And this should fail if only qemu-kvm 4.2.0 is available.

I could reproduce this strange behavior, even when qemu 5.2.0
is available:

1. Remove host from engine
2. dnf remove vdsm-\* qemu-\* libvirt-\*
3. dnf install qemu-img-4.2.0
   (I needed this for testing imageio patch)
4. dnf install vdsm vdsm-client

And I ended with qemu-kvm 4.2.0 instead of 5.2.0.

5. dnf update

qemu-kvm was updated to 5.2.0.

I hope that someone community can help to resolve this issue.

vdsm patches can be sent using gerrit, please see:
https://github.com/oVirt/vdsm/blob/master/README.md#submitting-patches

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/P7SB4OR2DAO7BXNLWSD63PBPCKGUXYW4/

[ovirt-users] Re: upgrading to 4.4.6 with Rocky Linux 8

[Nir Soffer]

On Tue, Jul 13, 2021 at 2:57 PM Branimir Pejakovic  wrote:
...
> > On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic 
> >  >
> > Unfortunately vdsm (the core package for ovirt host) does not
> > have ovirt-prefix. Which version do you have?
> > ...
>
> Just in case:
>
> # rpm -qa | grep vdsm
> vdsm-jsonrpc-4.40.60.7-1.el8.noarch
> vdsm-yajsonrpc-4.40.60.7-1.el8.noarch
> vdsm-common-4.40.60.7-1.el8.noarch
> vdsm-client-4.40.60.7-1.el8.noarch
> vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
> vdsm-api-4.40.60.7-1.el8.noarch
> vdsm-python-4.40.60.7-1.el8.noarch
> vdsm-network-4.40.60.7-1.el8.x86_64
> vdsm-http-4.40.60.7-1.el8.noarch
> vdsm-4.40.60.7-1.el8.x86_64
>
> > This package requires qemu-img >= 5.2.0
> > Maybe the requirement is broken (missing epoch).
> >
> > What does "qemu-img --version" tell?
>
> # qemu-img --version
> qemu-img version 4.2.0 (qemu-kvm-4.2.0-48.module+el8.4.0+534+4680a14e)
> Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
>
> During the installation itself, there were no errors/surprises. Everything 
> went smoothly.

So vdsm spec is broken on Rocky, letting you install vdsm when the required
qemu-kvm version is not available.

Can you file an ovirt/vdsm bug for this?
https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm

I tried to add a Rocky host to my setup and I can confirm that it works.

I create a new vm from:
https://download.rockylinux.org/pub/rocky/8/isos/x86_64/Rocky-8.4-x86_64-dvd1.iso

Install ovirt-release44.rpm from:
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm

And added the host to my engine (4.4.8 master). The host was installed
and activated, and can runs.

I found that migrating vms from other hosts (qemu-6.0, libvirt 7.4)
does not work. I think this issue was already reported here and fix is
expected from libvirt soon.

However I do get the the *right* version of qemu-kvm, provided by:

[root@rocky1 ~]# dnf info qemu-kvm
Last metadata expiration check: 18:02:00 ago on Tue 13 Jul 2021 02:37:31 AM IDT.
Installed Packages
Name : qemu-kvm
Epoch: 15
Version  : 5.2.0
Release  : 16.el8
Architecture : x86_64
Size : 0.0
Source   : qemu-kvm-5.2.0-16.el8.src.rpm
Repository   : @System
From repo: ovirt-4.4-advanced-virtualization

[root@rocky1 ~]# grep -A2 ovirt-4.4-advanced-virtualization
/etc/yum.repos.d/ovirt-4.4-dependencies.repo
[ovirt-4.4-advanced-virtualization]
name=Advanced Virtualization packages for $basearch
mirrorlist=http://mirrorlist.centos.org/?arch=$basearch=8=virt-advanced-virtualization

So oVirt is ready to rock on Rocky with little help from Centos :-)

I'm not sure about the future of the ovirt-4.4-advanced-virtualization
repository after Centos 8 will be discontinued, so this does not look
like production ready yet.

The advanced virtualization packages are likely needed by other virtualization
systems (openstack, proxmox, ...) or anyone that wants to consume the latest
features from libvirt and qemu, so packing it in oVirt is not the
right solution.

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/XFAMHNHU47OCXP3T7UBRKGZEAGA7BYS5/

[ovirt-users] Re: How to remove "VM is being cloned" flag in a failed clone VM operation

[Arik Hadas]

On Tue, Jul 13, 2021 at 3:56 PM Richard Chan 
wrote:

> Hello list,
>
> I had an unsuccessful zombie clone VM task  -
> 1. Target: was able to unlock the disks and delete the target VM
> 2. Source: able to unlock the disks.
>
> Now I cannot do anything with the source as it is flagged as "VM is being
> clone".
>
> Is there a way to remove this flag manually?
>

> vdms-client Host -> this does not show any tasks outstanding.
>

That's an in-memory lock - if the tasks were removed also on the engine
side, just restart ovirt-engine and the vm would be unlocked


>
> Thank you.
>
> Richard Chan
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/PJZMIIGTEKDM2EPKMQTXU7AEDWAUFFT2/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DVHFOZ5IDHMLF7SWMQRIVJHWOAKQ5VTZ/

[ovirt-users] Re: upgrading to 4.4.6 with Rocky Linux 8

[Marcin Sobczyk]

On 7/12/21 2:11 AM, Nir Soffer wrote:

On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic  wrote:

It was a fresh install of 2 VMs on top of VirtualBox with Rocky fully updated 
on both prior to oVirt installation. I installed it yesterday and followed the 
usual way of installing it: 
https://www.ovirt.org/download/alternate_downloads.html.

Here are the oVirt packages that are installed on the hypervisor:

Unfortunately vdsm (the core package for ovirt host) does not
have ovirt-prefix. Which version do you have?
...

ovirt-imageio-client-2.2.0-1.el8.x86_64

This package requires qemu-img >= 5.2.0
Maybe the requirement is broken (missing epoch).

As you quoted, the requirement states:

%if 0%{?rhel} >= 8
%if 0%{?centos}


Rocky linux probably doesn't have these macros.
OTOH 'ovirt-host' package requires plain 'libvirt',
no version limitations, and that probably sucks in "any 'qemu-kvm' 
possible".


Regards, Marcin



What does "qemu-img --version" tell?

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/FGKGSVRMFVED3HK4KGFL6JZRV574YMKW/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/LDCXTAYEKN3L7LXYKYAP2BYQ3QITJ6PA/

[ovirt-users] Re: upgrading to 4.4.6 with Rocky Linux 8

[Jason Keltz]

On 7/13/2021 8:11 AM, Branimir Pejakovic wrote:

I've been giving this a look and it seems that we aren't building the
advanced virt modules because CentOS builds them from upstream?

I've found no mention of them in their Pagure, and they're built on
their Community Build System via a SIG, with the metadata set on them
as `Extra: {'source': {'original_url': 'libvirt-7.0.0-
14.1.el8.src.rpm'}}`.

My colleague Neil looked into it, and concluded it seems to be a CLI
build being manually run(?).

We could investigate building that, but I'm not sure how good we'd be
to do so as it would likely involve repackaging straight from RHEL
sources via a RHEL machine.

Anyway, happy to help in any way I can on this, I'm in our
SIG/Virtualization channel on Mattermost if anyone wants to get to me
easily.

Hi Hayden

If you can do this - the word awesome would be an understatement ;-)

I have been using oVirt for 7 years now and it is a fantastic product (I 
started using it when it was 3.1 or 3.4). I am in a similar position as Jason 
who started this thread. The main goal of my experiment described above is to 
see if I can deploy it on bare metal nodes with Rocky as a hypervisor 
replacement for CentOS. I actually wanted to convert to Proxmox but wanted to 
give oVirt one more chance :)

Thank you.

Kind regards,
Branimir


Thanks, Branimir.

I am really hoping that Sandro and the rest of the oVirt team can help 
make this possible for Rocky Linux.  It seems like it won't be too 
tricky.  I've heard offline from a lot of people who would be very 
interested in using Rocky Linux for this very purpose, so there's a lot 
of interest out there.  It would be a huge win for oVirt.


Jason.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/OJ2M6FFSU6WDAYDITRTZIYNYDYSRJYIC/

[ovirt-users] How to remove "VM is being cloned" flag in a failed clone VM operation

[Richard Chan]

Hello list,

I had an unsuccessful zombie clone VM task  -
1. Target: was able to unlock the disks and delete the target VM
2. Source: able to unlock the disks.

Now I cannot do anything with the source as it is flagged as "VM is being
clone".

Is there a way to remove this flag manually?

vdms-client Host -> this does not show any tasks outstanding.

Thank you.

Richard Chan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/PJZMIIGTEKDM2EPKMQTXU7AEDWAUFFT2/

[ovirt-users] Re: upgrading to 4.4.6 with Rocky Linux 8

[Branimir Pejakovic]

> I've been giving this a look and it seems that we aren't building the
> advanced virt modules because CentOS builds them from upstream?
> 
> I've found no mention of them in their Pagure, and they're built on
> their Community Build System via a SIG, with the metadata set on them
> as `Extra: {'source': {'original_url': 'libvirt-7.0.0-
> 14.1.el8.src.rpm'}}`.
> 
> My colleague Neil looked into it, and concluded it seems to be a CLI
> build being manually run(?).
> 
> We could investigate building that, but I'm not sure how good we'd be
> to do so as it would likely involve repackaging straight from RHEL
> sources via a RHEL machine.
> 
> Anyway, happy to help in any way I can on this, I'm in our
> SIG/Virtualization channel on Mattermost if anyone wants to get to me
> easily.

Hi Hayden

If you can do this - the word awesome would be an understatement ;-)

I have been using oVirt for 7 years now and it is a fantastic product (I 
started using it when it was 3.1 or 3.4). I am in a similar position as Jason 
who started this thread. The main goal of my experiment described above is to 
see if I can deploy it on bare metal nodes with Rocky as a hypervisor 
replacement for CentOS. I actually wanted to convert to Proxmox but wanted to 
give oVirt one more chance :)

Thank you.

Kind regards,
Branimir

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7VRZVVOR76LUUOHRNUKM25U7N2NI7TEH/

[ovirt-users] Re: upgrading to 4.4.6 with Rocky Linux 8

[Branimir Pejakovic]

Hi Nir

> On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic  wrote:
> 
> Unfortunately vdsm (the core package for ovirt host) does not
> have ovirt-prefix. Which version do you have?
> ...

Just in case:

# rpm -qa | grep vdsm
vdsm-jsonrpc-4.40.60.7-1.el8.noarch
vdsm-yajsonrpc-4.40.60.7-1.el8.noarch
vdsm-common-4.40.60.7-1.el8.noarch
vdsm-client-4.40.60.7-1.el8.noarch
vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
vdsm-api-4.40.60.7-1.el8.noarch
vdsm-python-4.40.60.7-1.el8.noarch
vdsm-network-4.40.60.7-1.el8.x86_64
vdsm-http-4.40.60.7-1.el8.noarch
vdsm-4.40.60.7-1.el8.x86_64
 
> This package requires qemu-img >= 5.2.0
> Maybe the requirement is broken (missing epoch).
> 
> What does "qemu-img --version" tell?

# qemu-img --version
qemu-img version 4.2.0 (qemu-kvm-4.2.0-48.module+el8.4.0+534+4680a14e)
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers

During the installation itself, there were no errors/surprises. Everything went 
smoothly.

Thank you.

Kind regards,
Branimir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/F7BITB6DSR7GIHOF3YRC5DUGENZWYX43/

[ovirt-users] Re: Create new disk failure

[Vojtech Juranek]

On Monday, 12 July 2021 16:59:40 CEST Gangi Reddy wrote:
> Thank you. 
> 
> Kindly share the Ovirt Node and VM max limits please. In terms  of
> CPU/Memory/Storage.
 
> How many storage disks we can provision through one storage domain?

see e.g.
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/R3BF7D6ZNVVI4ASJ44MYXEPGR3C4QBKS/


> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/EJVYPGMT2MJGD
> LER4OL672LEWMJRUSCW/



signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IUMVPPGQZEWB7TTPU5YKQXC26LULUFSC/

[ovirt-users] Re: [4.4.7] The latest guest agent needs to be installed and running on the guest

[Tomáš Golembiovský]

Hi, sorry for late reply. To understand this we will have to see the
logs. Please open a bug on vdsm with description of the problem and log
attached.

Use the following procedure:
- stop the VM on problematic host
- enable debug logs for vds logger, you can do that either in
  /etc/vdsm/logger.conf (requires vdsmd restart) or temporarily from
  command line with:
  
vdsm-client Host setLogLevel level=DEBUG name=vds

- start the VM
- let it run for several minutes
- attach vdsm.log, engine.log and output of:

vdsm-client VM getStats vmID=

Thanks,

Tomas

On Sun, Jul 11, 2021 at 09:15:35PM -0300, Gervais de Montbrun wrote:
> This problem continues and I am expecting issues tomorrow morning when my 
> developers return to the office... ☹️
> 
> I did notice that my ovirt-engine is still running CentOS Linux and not 
> CentOS Stream. The release notes say that the oVirt nodes and the engine 
> would be running CentOS Stream after updating. The nodes are all on CentOS 
> stream and I had to do the necessary steps to get selinux to allow migrations 
> and fixed up the extra yum repos.
> 
> Does something need to be done regarding the ovirt-engine. I'm not seeing 
> anything in the release notes or in general documentation regarding upgrades. 
> Could the issues I am having be related to still being on CentOS Linux?
> 
> Cheers,
> Gervais
> 
> 
> 
> > On Jul 9, 2021, at 4:18 PM, Gervais de Montbrun  
> > wrote:
> > 
> > Hi Folks,
> > 
> > I upgraded my cluster yesterday and am having the same issue described 
> > here.  Boxes are booting up, but their IP addresses are never being updated 
> > in the oVirt admin console.
> > 
> > Restarting the hosts seemed to temporarily solve the issue, but it quickly 
> > returns. This is a huge issue for us as we need the ovirt engine to have 
> > the correct IP address of vm's in it as the vagrant plugin we use queries 
> > the ovirt api and uses this IP to communicate with vm's.
> > 
> > This is stopping our development team from being able to create new vm's. 
> > It will become a massive issue for me very quickly.
> > 
> > My installed versoion:
> > libvirt-7.4.0-1.el8s.x86_64
> > vdsm-common-4.40.70.6-1.el8.noarch
> > qemu-kvm-6.0.0-19.el8s.x86_64
> > 
> > Any help would be greatly appreciated.
> > 
> > Cheers,
> > Gervais
> > 
> > 
> > 
> >> On Jul 9, 2021, at 6:51 AM, Christoph Timm  >> > wrote:
> >> 
> >> Hi Tomáš,
> >> 
> >> I put the host in maintenance today and give it another reboot.
> >> After that the information are available for the VMs running on that host.
> >> Also the exclamation mark is gone.
> >> 
> >> So I guess something did not come up correctly during the restart of the 
> >> host.
> >> 
> >> Best regards
> >> Christoph
> >> 
> >> Am 08.07.21 um 20:36 schrieb Christoph Timm:
> >>> Hi Tomáš,
> >>> 
> >>> sorry for the late reply and for my the missing information.
> >>> 
> >>> Am 08.07.21 um 16:50 schrieb Tomáš Golembiovský:
>  On Thu, Jul 08, 2021 at 02:02:14PM +0200, Christoph Timm wrote:
> > Hi list,
> > 
> > I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs 
> > have
> > issues to report the performance information via the guest agent.
>  The performance info is provided by libvirt and not by guest agent.
>  Could you be more specific about which information is missing?
> >>> Sorry I did not mean the performance information like Memory, CPU and 
> >>> Network. These are available. The missing information are IP Addresses 
> >>> and FQDN. 
>  What is the version of vdsm and libvirt on the host?
> >>> All hosts are running: libvirt-7.0.0-14.1.el8
>  
> > I see the following message on the VMs: The latest guest agent needs to 
> > be
> > installed and running on the guest
> > 
>  This is probably unrelated to the above. But still, what is the exact
>  version of the guest agent?
> >>> I have tried already different versions.
> >>> For example: 
> >>> qemu-guest-agent.x86_64
> >>> 15:4.2.0-48.module_el8.4.0+783+f8734d30 @@commandline
> >>> qemu-guest-agent.x86_64
> >>> 15:2.12.0-88.module_el8.1.0+248+298dec18 @AppStream
> >>> 
> > The qemu-guest agent is installed on VMs (the VM OS is CentOS 8).
> > 
> > Any advice how to troubleshoot this?
> > 
> > I can see the stats will be presented in the GUI, if I migrate the VM 
> > to a
> > different host.
>  Same here, could you provide version of vdsm and libvirt on the host
>  where your VM is working fine?
> >>> KVM Version: 5.2.0 - 16.el8
> >>> LIBVIRT Version: libvirt-7.0.0-14.1.el8
> >>> VDSM Version: vdsm-4.40.70.6-1.el8
> >>> 
> >>> My 4 hosts are running the same versions on CentOS 8.
> >>> As I said I can migrate the VM to another host and the exclamation mark 
> >>> is gone and the information IPs and FQDNs are displayed.
>  Tomas
>  
>