- Users - oVirt List Archives

High level network advice request
by Richard Nilsson 31 Jan '20

31 Jan '20

High level network advice request :) I have a self-hosted engine deployed on a node, Ovirt v. 4.3. I am testing, but I don't understand the big idea of how to set-up Ovirt networking for hosted / engine-managed virtual servers. I would like to host a few virtual servers for things like Next/OwnCloud, SuiteCRM, NethServer or others. For example, I know exactly how set-up a virtual machine with a centos / lamp stack on a fedora host, I can make a network bridge for the vm with fedora cli, then use haproxy (or squid) as a reverse-redirect server to allow WAN access to the vm server using FQDNs. What is a good strategy for Ovirt hosting a webserver? To use the default ovirt management network for the virtual server machines doesn't seem like a best practice? Should I make a new logical network for the virtual servers? Do I need to configure bridges for the machines? It looks like bridges and virtual NICs are automatically configured when I make the network and virtual machines, is that right? Is it the usual or typical practice that one ovirt logical network uses only one network bridge to a one physical NIC? Would all of the kVMs on the logical network share the same / single bridge of the particular network? I'm not sure what the big idea should be, what is a best practice? I wonder, should I bond several physical NICs, then point the bridge, for a new / dedicated logical network for webservers, to the the bonded NICs? There is more than a little new vocabulary for me to onboard for Ovirt / virtual / logical networks...I will greatly appreciate, and I thank you in advance for any top level / best practice advice!

3 4

Remembering Lars Kurth at FOSDEM
by Tal Nisan 31 Jan '20

31 Jan '20

The Virtualization community that is gathering at FOSDEM would like to share its plans to remember the life and accomplishments of our valued friend and colleague, Lars Kurth, who has recently passed away. The remembrance will be at 09:45 Sunday Feb. 2 in the Virtualization Devroom (H.1309). We invite all to attend who would like to share in their memories of Lars and celebrate his life.

1 0

Assign permissions from within the VM portal?
by nicolas＠devels.es 31 Jan '20

31 Jan '20

Hi, We're testing version 4.3.8, we're planning to upgrade to this version in production as currently we're still using 4.1.9. In 4.1.9, users could grant permissions on their created VMs to other users from within the VM portal, however I can't find this option on version 4.3.8. Permissions granted to users so they can create and handle their VMs are VmCreator and DiskProfileUser on the DataCenter. Is there a way to allow users grant permissions on their VMs to other users in the VM portal? Thanks

1 0

FOSDEM 2020 - AMENDMENT In Memory of our Friend, Lars Kurth
by Doron Fediuck 31 Jan '20

31 Jan '20

Hi all, For those of you who are unaware of this, Lars Kurth from the Xen project has passed away [1]. Lars was one of the people who truly practiced open source and worked with the oVirt project on running FOSDEM's Virtualization and IaaS room in the past years. In Lars' memory there will be a special session [2] on Sunday morning, which will be broadcasted live. You're all welcomed to join physically or via the live stream. Thanks, Doron [1] https://lists.xenproject.org/archives/html/xen-announce/2020-01/msg00004.ht… [2] https://fosdem.org/2020/schedule/event/vai_memory_of_lars_kurth/

1 0

problem with qemu / dynamic_ownership
by Christoph Köhler 31 Jan '20

31 Jan '20

Hey, is the problem back with qemu/dynamic_ownership? We have one DC with two clusters: one: vdsm-4.30.38 / libvirt-4.5.0-23, two: vdsm-4.30.40 / libvirt-4.5.0-23, LibgfApi enabled, Gluster-Server 6.5.1, Gluster-Client 6.7, opVersion 60000 It went well for a log time but now, with getting vdsm like above, we are getting old problems: °setting disk files to root:root when VM went down °cannot create snapshot etc. Do we have to set dynamic_ownership=0 in qemu.conf? We were testing anything but nothing other worked. Is there any idea? Christoph

1 0

Re: [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing
by Strahil 31 Jan '20

31 Jan '20

I got upgraded to RC3 and now cannot power any VM . Constantly getting I/O error, but checking at gluster level - I can dd from each disk or even create a new one. Removing the HighAvailability doesn't help. I guess I should restore the engine from the gluster snapshot and rollback via 'yum history undo last'. Does anyone else have my issues ? Best Regards, Strahil NikolovOn Nov 13, 2019 15:31, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > > Il giorno mer 13 nov 2019 alle ore 14:25 Sandro Bonazzola <sbonazzo(a)redhat.com> ha scritto: >> >> >> >> Il giorno mer 13 nov 2019 alle ore 13:56 Florian Schmid <fschmid(a)ubimet.com> ha scritto: >>> >>> Hello, >>> >>> I have a question about bugs, which are flagged as [downstream clone - 4.3.7], but are not yet released. >>> >>> I'm talking about this bug: >>> https://bugzilla.redhat.com/show_bug.cgi?id=1749202 >>> >>> I can't see it in 4.3.7 release notes. Will it be included in a further release candidate? This fix is very important I think and I can't upgrade yet because of this bug. >> >> >> >> Looking at the bug, the fix was done with $ git tag --contains 12bd5cb1fe7c95e29b4065fca968913722fe9eaa >> ovirt-engine-4.3.6.6 >> ovirt-engine-4.3.6.7 >> ovirt-engine-4.3.7.0 >> ovirt-engine-4.3.7.1 >> >> So the fix is already included in release oVirt 4.3.6. > > > Sent a fix to 4.3.6 release notes: https://github.com/oVirt/ovirt-site/pull/2143. @Ryan Barry can you please review? > > >> >> >> >> >> >> >>> >>> >>> BR Florian Schmid >>> >>> ________________________________ >>> Von: "Sandro Bonazzola" <sbonazzo(a)redhat.com> >>> An: "users" <users(a)ovirt.org> >>> Gesendet: Mittwoch, 13. November 2019 13:34:59 >>> Betreff: [ovirt-users] [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing >>> >>> The oVirt Project is pleased to announce the availability of the oVirt 4.3.7 Third Release Candidate for testing, as of November 13th, 2019. >>> >>> This update is a release candidate of the seventh in a series of stabilization updates to the 4.3 series. >>> This is pre-release software. This pre-release should not to be used in production. >>> >>> This release is available now on x86_64 architecture for: >>> * Red Hat Enterprise Linux 7.7 or later (but <8) >>> * CentOS Linux (or similar) 7.7 or later (but <8) >>> >>> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: >>> * Red Hat Enterprise Linux 7.7 or later (but <8) >>> * CentOS Linux (or similar) 7.7 or later (but <8) >>> * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release >>> >>> See the release notes [1] for known issues, new features and bugs fixed. >>> >>> While testing this release candidate please note that oVirt node now includes: >>> - ansible 2.9.0 >>> - GlusterFS 6.6 >>> >>> Notes: >>> - oVirt Appliance is already available >>> - oVirt Node is already available >>> >>> Additional Resources: >>> * Read more about the oVirt 4.3.7 release highlights: http://www.ovirt.org/release/4.3.7/ >>> * 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.3.7/ >>> [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ >>> >>> -- >>> >>> Sandro Bonazzola >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA >>> >>> sbonazzo(a)redhat.com >>> >>> Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. >>> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/24QUREJPZHTSM… >> >> >> >> -- >> >> Sandro Bonazzola >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA >> >> sbonazzo(a)redhat.com >> >> Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. > > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA > > sbonazzo(a)redhat.com > > Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

7 20

Re: Problems in new oVirt install
by Steve Watkins 30 Jan '20

30 Jan '20

> Yes that's what usually happens the VM will be paused when the backing storage starts > running out of space, try deleting the ISO from where you uploaded it to. > > Regards, > > Paul S. > > ________________________________ > From: Steve Watkins <watkinssr(a)gmail.com> > Sent: 29 January 2020 00:13 > To: users(a)ovirt.org <users(a)ovirt.org> > Subject: [ovirt-users] Problems in new oVirt install > > Caution External Mail: Do not click any links or open any attachments unless you trust the > sender and know that the content is safe. > > Got everything installed and was uploding an ISO when the system just stopped responding. > Went to the host and saw the hostedengine was paused. Looked online and found the > following instructions for unpausing it > > virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf > resume HostedEngine > > And get the following error > Failed to acquire lock: No space left on device > > any ideas? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... > oVirt Code of Conduct: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... > List Archives: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o... > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ Since the hostedengine won't start, I don't see any way to delete it.

2 2

[ANN] oVirt 4.3.8 is now generally available
by Sandro Bonazzola 30 Jan '20

30 Jan '20

The oVirt Project is pleased to announce the general availability of oVirt 4.3.8 as of January 27th, 2020. This update is the eighth in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) * oVirt Node 4.3 (available for x86_64 only) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] oVirt Node and Appliance have been updated including: - oVirt 4.3.8: http://www.ovirt.org/release/4.3.8/ - Including fixes for CVE-2019-19336 oVirt Engine Cross Site Scripting Vulnerability <https://www.symantec.com/security-center/vulnerabilities/writeup/111466> - Latest CentOS 7.7 updates including: - CEBA-2019:3970 CentOS 7 ca-certificates BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035571.html> - CEBA-2019:3971 CentOS 7 curl BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035558.html> - CEBA-2019:3985 CentOS 7 iproute BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035568.html> - CESA-2019:3979 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035574.html> - CEBA-2019:4106 CentOS 7 kernel BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035575.html> - CEBA-2019:3983 CentOS 7 util-linux BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035567.html> - CEBA-2019:3972 CentOS 7 sssd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035565.html> - CEBA-2019:3969 CentOS 7 samba BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035561.html> - CEBA-2019:3975 CentOS 7 libvirt BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035562.html> - CEEA-2019:4161 CentOS 7 microcode_ctl Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035586.html> - CESA-2019:4190 Important CentOS 7 nss Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035590.html> - CESA-2019:4190 Important CentOS 7 nss-softokn Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035589.html> - CESA-2019:4190 Important CentOS 7 nss-util Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035587.html> - CEBA-2019:3977 CentOS 7 numactl BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035573.html> - CEBA-2019:3982 CentOS 7 selinux-policy BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035559.html> - CEBA-2019:3973 CentOS 7 sos BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035572.html> - CESA-2019:3976 Low CentOS 7 tcpdump Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035570.html> - latest CentOS Virt and Storage SIG updates: - Ansible 2.9.4: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 6.7: https://docs.gluster.org/en/latest/release-notes/6.7/ Given the amount of security fixes provided by this release, upgrade is recommended as soon as practical. Additional Resources: * Read more about the oVirt 4.3.8 release highlights: http://www.ovirt.org/release/4.3.8/ * 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.3.8/ [2] http://resources.ovirt.org/pub/ovirt-4.3/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/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

4 5

Async release for ovirt-engine-metrics is now available for oVirt 4.3.8
by Sandro Bonazzola 30 Jan '20

30 Jan '20

The oVirt Team has just released a new version of ovirt-engine-metrics package that fixes the deployment of the metrics solution when using foreman/satellite. The deployment was previously failing on missing rhsub_orgid in vars.yaml.template. We recommend to update ovirt-engine-metrics if you're planning to use it with foreman/satellite. Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Virtual disk attached to VM showing in the Webui but not identified by the system
by Eugène Ngontang 30 Jan '20

30 Jan '20

Hi, I'm facing a virtual disk behavior I don't understand. Currently my VMs are spun up with a Boot disk of 25GB and an additional disk of 215/45/65 GB depending. When logged to the webui I see the two disks, but when I ssh to VM we only see the primary boot disk, the other one can't get a *UUID* and then cannot and is not mounted I also noticed in the webui the second disk doesn't have a logical name as you can see in the screenshot. Pleas can someone explain this behavior please? Here is my disk management commands outputs [root@fp-gpu-node3 centos]# fdisk -l > > > Disque /dev/vda : 26.8 Go, 26843545600 octets, 52428800 secteurs > > Unités = secteur de 1 × 512 = 512 octets > > Taille de secteur (logique / physique) : 512 octets / 512 octets > > taille d'E/S (minimale / optimale) : 512 octets / 512 octets > > Type d'étiquette de disque : dos > > Identifiant de disque : 0x000b6061 > > > Périphérique Amorçage Début Fin Blocs Id. Système > > /dev/vda1 * 2048 52428766 26213359+ 83 Linux > > > Disque /dev/vdb : 48.3 Go, 48318382080 octets, 94371840 secteurs > > Unités = secteur de 1 × 512 = 512 octets > > Taille de secteur (logique / physique) : 512 octets / 512 octets > > taille d'E/S (minimale / optimale) : 512 octets / 512 octets > > > [root@fp-gpu-node3 centos]# blkid > > /dev/vda1: UUID="3ef2b806-efd7-4eef-aaa2-2584909365ff" TYPE="xfs" > > [root@fp-gpu-node3 centos]# lsblk -f > > NAME FSTYPE LABEL UUID MOUNTPOINT > > sr0 > > vda > > └─vda1 xfs 3ef2b806-efd7-4eef-aaa2-2584909365ff / > > vdb > Thanks for your help. -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

2 4