- Users - oVirt List Archives

Sometimes VM fails to power on: device busy in adding vnet port
by Gianluca Cecchi 05 May '20

05 May '20

Hi, my environment info: centos-release.x86_64 7-7.1908.0.el7.centos glusterfs.x86_64 6.8-1.el7 ovirt-engine.noarch 4.3.9.4-1.el7 ovirt-release43.noarch 4.3.9-1.el7 I have an external agent (openstack staging_oviirt) that powers on/off VMs during bulk install. See also here some other details: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/B4CDWTAR7YLRLR… I repeat many times the installation for test purposes and during these phases the application powers on (through ostacpm user) about 8 VMs in the same moment. Sometimes it happens that one or more of them fail to start and in web admin gui I see this kind of sequence of events: VM ostack-ceph2 was started by ostackpm@internal-authz (Host: ovirt.mydomain). User <UNKNOWN> got disconnected from VM ostack-ceph2. VM ostack-ceph2 is down with error. Exit message: Unable to add bridge vlan23 port vnet21: Device or resource busy. Failed to run VM ostack-ceph2 on Host ovirt.mydomain Failed to run VM ostack-ceph2 (User: ostackpm@internal-authz). Soon I press the start button from web admin gui and the VM powers on without problems. I think this kind of problem doesn't depend on the rest api agent. Could it be a sort of bug or concurrency of power on commands? If I grep VM UUID and name of the VM for the one above, I get this in engine.log: https://drive.google.com/file/d/1QsedDqvlbvVPCifDNted4ipSsJ2GeBJV/view?usp=… On ovirt host I see: 2020-05-04 10:16:05,491+0200 ERROR (vm/38f806e7) [virt.vm] (vmId='38f806e7-5c48-4ffe-90e8-671b1a585256') The vm start process failed (vm:934) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 868, in _startUnderlyingVm self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2895, in _run dom.createWithFlags(flags) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1110, in createWithFlags if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) libvirtError: Unable to add bridge vlan23 port vnet21: Device or resource busy 2020-05-04 10:16:05,492+0200 INFO (vm/38f806e7) [virt.vm] (vmId='38f806e7-5c48-4ffe-90e8-671b1a585256') Changed state to Down: Unable to add bridge vlan23 port vnet21: Device or resource busy (code=1) (vm:1702) Let me know if you meed more information Gianluca

1 0

oVirt 4.4.0 Beta release refresh is now available for testing
by Sandro Bonazzola 03 May '20

03 May '20

oVirt 4.4.0 Beta release refresh is now available for testing The oVirt Project is excited to announce the availability of the beta release of oVirt 4.4.0 refresh (beta 4) for testing, as of April 17th, 2020 This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics on top of oVirt 4.3. Important notes before you try it Please note this is a Beta release. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production. In particular, please note that upgrades from 4.3 and future upgrades from this beta to the final 4.4 release from this version are not supported. Some of the features included in oVirt 4.4.0 Beta require content that will be available in CentOS Linux 8.2 but can’t be tested on RHEL 8.2 beta yet due to some incompatibility in openvswitch package shipped in CentOS Virt SIG which requires to rebuild openvswitch on top of CentOS 8.2. Known Issues - ovirt-imageio development is still in progress. In this beta you can’t upload images to data domains using the engine web application. You can still copy iso images into the deprecated ISO domain for installing VMs or upload and download to/from data domains is fully functional via the REST API and SDK. For uploading and downloading via the SDK, please see: - https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_d… - https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/download… Both scripts are standalone command line tool, try --help for more info. Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8 minimal from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to engine and let it be deployed. What’s new in oVirt 4.4.0 Beta? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts - Easier network management and configuration flexibility with NetworkManager - VMs based on a more modern Q35 chipset with legacy seabios and UEFI firmware - Support for direct passthrough of local host disks to VMs - Live migration improvements for High Performance guests. - New Windows Guest tools installer based on WiX framework now moved to VirtioWin project - Dropped support for cluster level prior to 4.2 - Dropped SDK3 support - 4K disks support only for file based storage. iSCSI/FC storage do not support 4k disks yet. - Exporting a VM to a data domain - Editing of floating disks - Integrating ansible-runner into engine, which allows a more detailed monitoring of playbooks executed from engine - Adding/reinstalling hosts are now completely based on Ansible - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 * oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such a case, please be sure to take the qc2 image and not the ova image. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.0 release highlights: http://www.ovirt.org/release/4.4.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.0/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>* <https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>* *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

5 4

Engine UI exception while viewing unattached hosts in Network tab
by Shareef Jalloq 03 May '20

03 May '20

Hi, I'm following the Gluster setup blog post ( https://blogs.ovirt.org/2018/02/up-and-running-with-ovirt-4-2-and-gluster-s…) and am at the 'Storage network' section. I've created a new 'gluster' network, selected the network and navigated to the 'Hosts' tab. The guide tells you to click the 'Unattached' button and then 'Setup Host Networks' for each host. However, clicking the 'Unattached' button fires off a bunch of exceptions rather than displaying my 3 hosts. The message is: "Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read property 'N' of null Please have your administrator check the UI logs" Anyone seen this before? Where is the UI log located? Shareef.

3 3

Unable to remove system roles from Everyone group
by miguel.garcia＠toshibagcs.com 02 May '20

02 May '20

I opened Everyone group and added system role UserRole and realized now that everybody can see all VMS which is not good. I tried to remove the role from the group but got the error "Error while executing action: It's not allowed to remove system permissions assigned to built-in Everyone group" Looking into Ovirt forums I see that this change should be made through the engine database but I was not able to reach that part. Can someone help me out how to remove the system role from Everyone group? or at least reset the group?

2 1

Running Host on sudo user
by carl langlois 30 Apr '20

30 Apr '20

Hi, I was wandering if it is possible to run ovirt node using a sudo user instead of the root user? Let says i want or need to disable root ssh login.. Thanks and regards. Carl

3 3

Can we agree on adding reference to version in help request email?
by Sandro Bonazzola 30 Apr '20

30 Apr '20

Hi, I was looking in the past 2 weeks email landing on this mailing list and a common thing I notice is that it's hard to understand which version of the involved software they're referring too. Can we agree on adding at the top of the message a couple of line like output of yum -q list installed centos-release ovirt-release\* ovirt-engine redhat-release vdsm glusterfs centos-release.x86_64 7-7.1908.0.el7.centos glusterfs.x86_64 6.8-1.el7 ovirt-engine.noarch 4.3.9.4-1.el7 ovirt-release43.noarch 4.3.9-1.el7 It will help understanding if the help request is something that may be already known, a regression, and so on. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>* <https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>* *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

3 2

Add custom Network Filter to oVirt
by Hendrik Peyerl 30 Apr '20

30 Apr '20

Hello all, can anyone give me a hint on where to find documentation on how to add custom created network filters through oVirt? Thanks, Hendrik

3 5

Re: Move Hosted Engine VM to a different storage domain
by Yedidyah Bar David 30 Apr '20

30 Apr '20

On Wed, Apr 29, 2020 at 8:42 AM Anton Louw <Anton.Louw(a)voxtelecom.co.za> wrote: > > > Hi, > > > > Thank you for the reply. I am building another environment today, so I > will run through the backup and restore again. I do recall one issue I had > with the restore was that it gave an error that one of the storage domains > were already in use. This was a new storage domain I added, with no VMs on. > > > > I just want to make sure, I probably cannot deploy the HE on a storage > domain that is in maintenance, correct? I will try and create a new storage > domain again, but remove it from the data center, and perhaps see if the HE > will deploy to it. > hosted-engine deploy does not require an "empty storage domain" (in maintenance or not), but one that "does not exist yet" - meaning, a path to storage that will be used as a storage domain, but in which a storage domain was not created yet. The deploy process itself will create the domain there. I hope this clarifies. > > > The main goal was to have no downtime, but if it is going to be too > complex, I think my next option will be to create a new HE, and attach the > current storage domains. Obviously it is going to take a bit of planning, > as I will need to configure all the networks etc. from scratch again. > Good luck and keep us updated! Best regards, > > > Thanks > > > > *Anton Louw* > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > [image: F] <https://www.facebook.com/voxtelecomZA> > [image: T] <https://www.twitter.com/voxtelecom> > [image: I] <https://www.instagram.com/voxtelecomza/> > [image: L] <https://www.linkedin.com/company/voxtelecom> > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > *From:* Strahil Nikolov <hunter86_bg(a)yahoo.com> > *Sent:* 26 April 2020 08:55 > *To:* Yedidyah Bar David <didi(a)redhat.com>; Anton Louw < > Anton.Louw(a)voxtelecom.co.za> > *Cc:* users(a)ovirt.org > *Subject:* Re: [ovirt-users] Re: Move Hosted Engine VM to a different > storage domain > > > > On April 26, 2020 9:39:07 AM GMT+03:00, Yedidyah Bar David < > didi(a)redhat.com> wrote: > >On Fri, Apr 24, 2020 at 1:04 PM Anton Louw > ><Anton.Louw(a)voxtelecom.co.za> > >wrote: > > > >> > >> > >> Hi All, > >> > >> > >> > >> I know this question has been asked before, by myself included. I was > >> hoping that someone has run through the exercise of moving the hosted > >> engine VM to a different storage domain. I have tried many routes, > >but the > >> backup and restore does not work for me. > >> > > > >The "standard answer" is backup and restore. Why does it not work? > > > > > >> > >> > >> Is there anybody that can perhaps give me some guidelines or a > >process I > >> can follow? > >> > > > >I didn't try that myself. > > > >The best guidelines I can give you are: Try first on at a test system. > >Do > >the backup on the real machine, create some isolated VM (isolated so > >that > >it does not interfere with your hosts/storage) somewhere to be used as > >a > >test host (or a physical machine if you have one), some storage > >somewhere, > >and restore on it. Make it work. Document what you needed to do. Ask > >here > >with specific questions if/when you have them. Then do on the > >production > >setup. > > > >Also clarify your needs. Do you need no-downtime for the VMs? If so, > >that's > >more complex. If you don't, it might be enough/simpler to deploy a new > >setup and just import the existing storage. Do you have HA VMs? etc. > > > > > >> > >> > >> The reason I need to move the HE VM is because we are decommissioning > >the > >> current storage array where the HE VM is located. > >> > > > >Good luck! > > > >Best regards, > > > > > >> > >> > >> Thank you very much > >> > >> *Anton Louw* > >> *Cloud Engineer: Storage and Virtualization* at *Vox* > >> ------------------------------ > >> *T:* 087 805 0000 | *D:* 087 805 1572 > >> *M:* N/A > >> *E:* anton.louw(a)voxtelecom.co.za > >> *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > >> www.vox.co.za > >> > >> [image: F] <https://www.facebook.com/voxtelecomZA> > >> [image: T] <https://www.twitter.com/voxtelecom> > >> [image: I] <https://www.instagram.com/voxtelecomza/> > >> [image: L] <https://www.linkedin.com/company/voxtelecom> > >> [image: Y] <https://www.youtube.com/user/VoxTelecom> > >> > >> [image: #VoxBrand] > >> <https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> > >> *Disclaimer* > >> > >> The contents of this email are confidential to the sender and the > >intended > >> recipient. Unless the contents are clearly and entirely of a personal > >> nature, they are subject to copyright in favour of the holding > >company of > >> the Vox group of companies. Any recipient who receives this email in > >error > >> should immediately report the error to the sender and permanently > >delete > >> this email from all storage devices. > >> > >> This email has been scanned for viruses and malware, and may have > >been > >> automatically archived by *Mimecast Ltd*, an innovator in Software as > >a > >> Service (SaaS) for business. Providing a *safer* and *more useful* > >place > >> for your human generated data. Specializing in; Security, archiving > >and > >> compliance. To find out more Click Here > >> <https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. > >> > >> > >> _______________________________________________ > >> Users mailing list -- users(a)ovirt.org > >> To unsubscribe send an email to users-leave(a)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/V3PRBRZD7SLUQ… > >> > > If youchange the gluster volume you can use the 'hosted-engine' tool + > migration of the data ? > > The example is for Gluster, but also > hosted-engine --set-shared-config storage <server1>:/engine > > hosted-engine --set-shared-config mnt_options > backup-volfile-servers=<server2>:<server3> > > Best Regards, > Strahil Nikolov > > -- Didi

1 0

Failed to complete VM creation,help me!
by liug74＠sina.com 29 Apr '20

29 Apr '20

Storage domain usage is as follows： vgdisplay 3542ca36-747b-407c-aa5e-331510f81fd9 --- Volume group --- VG Name 3542ca36-747b-407c-aa5e-331510f81fd9 System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 15998 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1954 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 113.97 TiB PE Size 128.00 MiB Total PE 933647 Alloc PE / Size 64930 / <7.93 TiB Free PE / Size 868717 / 106.04 TiB VG UUID GiL1LL-ggO5-a6mX-62uc-q597-B3X9-6bzC93 __________________________________________________________ The following error occurred when I created the VM: VDSM H5 command HSMGetAllTasksStatusesVDS failed: Error creating a new volume: (u"Volume creation 62220be2-2781-4771-9373-84af5cc18f01 failed: (28, 'Sanlock resource write failure', 'No space left on device')",) Excuse me, what's the reason, thank you!

3 2

ovrt node ng 4.4 different fs layout and error if changed
by Gianluca Cecchi 29 Apr '20

29 Apr '20

Hello, In CentOS 7 default filesystem in anaconda was xfs, but in ovirt node ng 4.3.9 (based on CentOS 7) the default layout was set to ext4. In CentOS 8 again the default is xfs and I see that ovirt node ng 4.4 beta4 (based on CentOS 8.1) has now xfs for all filesystems, excluded /boot that is set to ext4. In general I have a preference for ext4. I notice that while in 4.3.9 I could somehow customize partition layout, even if not recommended, in 4.4 I always get error if I don't accept automatic partitioning. What I sometimes do: - select disk and custom layout - click done and the storage page appears - I click the button to create automatically and I get the automatic partitioning layout - and here I can change fs type and update settings button and/or change size of some filesystems (eg for /var/log if using Gluster) Even if I only set all filesystems automatically generated by installer to ext4, without changing any size, in the final stage of installation I get this error and installation aborts: " There was an error running the kickstart script at line 5. This is a fatal error and installation will be aborted. The details of this error are: 2020-04-19 10:37:50,451 [INFO] (MainThread) Trying to create a manageable base from '/' 2020-04-19 10:37:50,811 [ERROR] (MainThread) LVM Thin Provisioning partitioning scheme is required. For autoinstall via Kickstart with LVM Thin Provisioning check options: --thinpool and --grow. Please consult documentation for details Traceback (most recent call last): File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib/python3.6/site-packages/imgbased/__main__.py", line 53, in <module> CliApplication() File "/usr/lib/python3.6/site-packages/imgbased/__init__.py", line 82, in CliApplication app.hooks.emit("post-arg-parse", args) File "/usr/lib/python3.6/site-packages/imgbased/hooks.py", line 120, in emit cb(self.context, *args) File "/usr/lib/python3.6/site-packages/imgbased/plugins/core.py", line 171, in post_argparse layout.initialize(args.source, args.init_nvr) File "/usr/lib/python3.6/site-packages/imgbased/plugins/core.py", line 215, in initialize self.app.imgbase.init_layout_from(source, init_nvr) File "/usr/lib/python3.6/site-packages/imgbased/imgbase.py", line 293, in init_layout_from self.init_tags_on(existing_lv) File "/usr/lib/python3.6/site-packages/imgbased/imgbase.py", line 271, in init_tags_on pool = lv.thinpool() File "/usr/lib/python3.6/site-packages/imgbased/lvm.py", line 305, in thinpool raise MissingLvmThinPool() imgbased.lvm.MissingLvmThinPool " If I change nothing and choose automatic partitioning the installation completes. Tried different times with same results. Is it expected? In this case instead of specifying "recommended" it should be written sort of "mandatory"... Gianluca

2 1