- Users - oVirt List Archives

Re: Mount ISO to VM
by Shani Leviim 07 Apr '20

07 Apr '20

Hi Anton, You can upload an ISO file as a disk using the UI: Storage -> Disks -> upload. Further information can be found here under the "Uploading a Disk Image to a Storage Domain" section: https://www.ovirt.org/documentation/admin-guide/chap-Virtual_Machine_Disks.… Or use the following script using SDK: https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_d… *Regards,* *Shani Leviim* On Tue, Apr 7, 2020 at 11:45 AM Anton Louw <Anton.Louw(a)voxtelecom.co.za> wrote: > > > Hi Everybody, > > > > Is there a way to mount an ISO to one of my VMs if I do not have an ISO > domain, but the ISO file is on a Data domain? > > > > 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> > > [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/D7ONE6IJN6RK2… >

2 1

ISO and Export domains deprecated
by Colin Coe 07 Apr '20

07 Apr '20

Hi all I'm trying to understand how ISO and Export domains going away is going to affect us. We have four RHV instances: - Prod DC1 (RHV4.1) - Prod DC2 (RHV4.1) - DEV (RHV4.3) - TEST (RHV4.3) Prod DC1, DEV and TEST all share export and ISO domains. Prod DC2 is remote and currently has its own ISO and Export domains. When ISO and Export domains go away, can I still share ISO domains between the RHV instances? Thanks

5 9

Mount ISO to VM
by Anton Louw 07 Apr '20

07 Apr '20

Hi Everybody, Is there a way to mount an ISO to one of my VMs if I do not have an ISO domain, but the ISO file is on a Data domain? Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za

1 0

oVirt 4.4.0 Beta release refresh is now available for testing
by Sandro Bonazzola 07 Apr '20

07 Apr '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 for testing, as of April 3rd, 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 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 tools, 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 389-ds - 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.*

3 5

Add gluster storage domain incomplete documentation
by Gianluca Cecchi 07 Apr '20

07 Apr '20

Hello, I think both at oVirt and Red Hat official docs the steps regarding adding a new Gluster storage domain on an existing installation is quite confusing and misaligned. Below I explain my reasons for both. In the mean time, suppose I have a single host HCI with self hosted engine (but it could be useful to have hints for multi-hosts too) and the 3 storage domains configured during install (engine and data on a disk and vmstore on another disk). The system initially had 3 disks, the first used for the ovirt-node-ng system, the second for engine and data, the third for vmstore initial gluster storage domains Now I go and add a fourth disk, say 4Tb in size. I would like to create a new Gluster storage domain on it What are the suggested steps? BTW: after booting, the new disk has been automatically included in multipath eui.01000000010000005cd2e4b5e7db4d51 dm-6 NVME,INTEL SSDPEDKX040T7 size=3.6T features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 1:0:1:0 nvme1n1 259:1 active undef running Coming back to the docs - oVirt documentation I base my considerations on page https://www.ovirt.org/documentation/admin-guide/chap-Working_with_Gluster_S… 1) the picture in that page is still based on 3.6 GUI, so the initial approach tends to make me feel the page could be not up to date 2) I would put the section "Creating a Storage Volume" before "Attaching a Gluster Storage Volume as a Storage Domain" and not the opposite as it is now 3) In "Creating a Storage Volume" there is the note that " You must create brick directories or mountpoints before you can add them to volumes. " This sentence in my opinion is not so clear (see also details at the end)... what is a user expected to have done on hypervisors? Creation of directories or file systems (and what type: prefered xfs or ext4?). Perhaps an example of commands would be useful. 4) in the workflow of creating volume, item 7: Click the Add Bricks button to select bricks to add to the volume. Bricks must be created externally on the Gluster Storage nodes. I would expect an indication of commands to be run instead... This implies knowledge of Gluster that the GUI functionality is aimed to hide... but so, not completely... I can see in my existing bricks, going to their advanced details: " xfs rw,seclabel,noatime,nodiratime,attr2,inode64,logbsize=128k,sunit=256,swidth=512,noquota " There is also the fstab portion of creating bricks... 5) In the workflow of creating volume, item 9: It is not clear the default "*" value for access if is the recommended one or not. I presume not - RHV documentation https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… 4.3 Administrator Guide downloaded today Chapter 8, section 8.6 PREPARING AND ADDING RED HAT GLUSTER STORAGE There is reference to Red Hat Gluster Storage, version 3.4. I think it should be 3.5 instead? Because at the same time in 3.4 there is reference to RHV 4.1, not 4.3. While in "Configuring Red Hat Virtualization with Red Hat Gluster Storage" version 3.5 there is correct reference to RHV 4.3 Anyway this mix of product documentation is not optimal in my opinion. I would directly include inside RHV docs the Gluster part related to it, without jumping between the two comlete, with the risk of misalignment in time. Also, in Gluster Storage guide referred, there is the part related to volumes but not to bricks.... Possibly the correct reference for the brick part, that is the one missing in webadmin GUI, could be this: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5/h… and/or this https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5/h… ? Thanks for reading and hoping to get commands' workflow to configure this new disk for a new gluster storage domain. It seems inside the guides is oversimplified the process of creating bricks, that in the documentation seem actually to be xfs filesystems mounted over thin pool based logical volumes residing on top of volume groups with particular alignment settings specified during their creation.... Gianluca

2 3

Engine/host communication maybe broken
by Sven Achtelik 06 Apr '20

06 Apr '20

Hi All, I'm currently facing a situation which I don't know how to resolve and I don't know how that happened. The hosted engine HA part is working fine and the vm starts. It's accessible via the gui and that's it. It's showing some hosts online and some offline. It looks like it's not communication with the nodes anymore to get the latest status or to start task. Is there a cache or something that can be cleared on the engine vm to force a connection the the nodes ? Or is there a way to analyze if communication is really broken ? Any ideas how to start from here ? Thank you, Sven

3 3

"Actual timezone differs [...]" after using the new virtio-win guest tools
by Tobias Scheinert 06 Apr '20

06 Apr '20

Hi, we are currently preparing our Windows software packages for update oVirt from version 4.3 to version 4.4. One of the novelties[1] of version 4.4 is the change from the ovirt-guest-tools to the virtio-win guest tools. We are currently running version 4.3.9.4-1.el7 in our oVirt cluster. When we are installing the new virtio-win guest tools we get the tooltip message: "Actual timezone in the guest differs from the configuration". The guest agents of the two guest tools are completely different, the ovirt-guest-agent is written in Python, the qemu-guest-agent is written in C. So my guess was, that there would different result send to the ovirt-engine. As I looked into the sources of ovirt-engine, especially into the timezone Java stuff, I did not found any changes in the last few months. So is this bug fixed, with the new ovirt version 4.4, or is this aspect new? P.S. The os in the vm was Windows 10 version 1909 [1] <https://ovirt.org/release/4.4.0/> Best Regards Tobias Scheinert

2 3

Windows Guest Agent Issues Since 4.3
by Alex McWhirter 06 Apr '20

06 Apr '20

Upgraded a installation to 4.3, and update the guest agent on all VM's, now all of my Windows VM's have a exclamation point telling me to install the latest guest agent. Some parts of the guest agent still seem to work, the IP addresses are still showing in the portal, but not FQDN and for some machine the shutdown button no longer functions correctly. I also tried to a fresh 4.3 install on a test cluster, and at first it worked great. But after a few days all of the windows vm's on that setup are showing the same behavior. Linux guests are fine on both systems. Not really sure where to start looking.

1 0

oVirt 4.4.0 Beta release is now available for testing
by Sandro Bonazzola 06 Apr '20

06 Apr '20

oVirt 4.4.0 Beta release is now available for testing The oVirt Project is excited to announce the availability of the beta release of oVirt 4.4.0 for testing, as of March 27th, 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 which are currently included in Red Hat Enterprise Linux 8.2 beta. If you want to have a better experience you can test oVirt 4.4.0 Beta on Red Hat Enterprise Linux 8.2 beta. Known Issues - ovirt-imageio development is still in progress. In this beta you can’t upload images to data domains. You can still copy iso images into the deprecated ISO domain for installing VMs. 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 389-ds - 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 - 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 or newer * CentOS Linux (or similar) 8.1 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 or newer * CentOS Linux (or similar) 8.1 or newer * 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.*

4 5

Re: Multiple NICs on hosted engine, oVirt 4.3
by Jiří Sléžka 06 Apr '20

06 Apr '20

Hello Paul, thanks for reply and for pointing me to RHV documentation. Shame on me, I forogot it exists and is well maintained and super relevant for oVirt. But in this case I am a bit lost. I can't find something relevant to my effort to modify HE vm's config to add the second NIC to it. Or do you mean I should change the location of vm.conf from /var/run location to something persistent and then modify this vm.conf as mentioned in that old post? For example, now I got this output for conf key [root@ovirt-hci01 ~]# hosted-engine --get-shared-config conf --type=he_shared conf : /var/run/ovirt-hosted-engine-ha/vm.conf, type : he_shared [root@ovirt-hci01 ~]# hosted-engine --get-shared-config conf --type=he_local conf : /var/run/ovirt-hosted-engine-ha/vm.conf, type : he_local Is it valid to change it to (for example) /etc/ovirt-hosted-engine/vm.conf and modify that file there? Is it safe for further updates, maintenance, etc.? Maybe the second question - which process creates vm.conf in /var/run path? Cheers, Jiri On 4/5/20 8:35 AM, Staniforth, Paul wrote: > Hello Jri, > The configurations local and shared are managed by > hosted-engine command. > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… > <https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht…> > > Chapter 12. Administering the Self-Hosted Engine Red Hat Virtualization > 4.3 | Red Hat Customer Portal > <https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht…> > The Red Hat Customer Portal delivers the knowledge, expertise, and > guidance available through your Red Hat subscription. > access.redhat.com > > see > "hosted-engine --help" > "man hosted-engine" > > Regards, > Paul S. > ------------------------------------------------------------------------ > *From:* Jiří Sléžka <jiri.slezka(a)slu.cz> > *Sent:* 04 April 2020 21:02 > *To:* users(a)ovirt.org <users(a)ovirt.org> > *Subject:* [ovirt-users] Multiple NICs on hosted engine, oVirt 4.3 > > Caution External Mail: Do not click any links or open any attachments > unless you trust the sender and know that the content is safe. > > Hello, > > I would like to add second NIC to hosted engine vm (I need access to > isolated network with host's power management). I found this solution... > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > > ...which seems to work in oVirt 3.5 but in oVirt 4.3 there is no file > like /etc/ovirt-hosted-engine/vm.conf anymore. > > In the file /etc/ovirt-hosted-engine/hosted-engine.conf is a line > > ... > conf=/var/run/ovirt-hosted-engine-ha/vm.conf > ... > > which points to this config but this is a running config... > > Is there a way to add a second NIC to hosted engin vm? > > Cheers, > > Jiri > > > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ >

2 1