- Users - oVirt List Archives

Minor issue upgrading to 4.2
by Chris Adams 26 Dec '17

26 Dec '17

I upgraded a CentOS 7 oVirt 4.1.7 (initially installed as 3.5 if it matters) test oVirt cluster to 4.2.0, and ran into one minor issue. The update installed firewalld on the host, which was set to start on boot. This replaced the iptables rules with a blank firewalld setup that only allowed SSH, which kept the host from working. Stopping and disabling firewalld, then reloading iptables, got the host back working. In a quick search, I didn't see anything noting that firewalld was now required, and it didn't seem to be configured correctly if oVirt was trying to use it. -- Chris Adams <cma(a)cmadams.net>

3 5

Issue starting VM using run-once
by Alex Bartonek 25 Dec '17

25 Dec '17

This is a multi-part message in MIME format. --b1_9b226ccada30e17dcd549d070ae4b383 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 TWVycnkgQ2hyaXN0bWFzIHRvIHlvdSBhbGwuLgoKTmV3IGluc3RhbGwgb2Ygb1ZpcnQgNC4yIG9u IGEgQ2VudE9TIDcgc3lzdGVtLiAgV2F0Y2hlZCBhIHZpZCBhbmQgcmVhZCBzb21lIHN0dWZmIG9u IHRoZSBzaXRlIHJlZ2FyZGluZyBpbnN0YWxsYXRpb24vY29uZmlnLiAgSSBoYXZlIGl0IGluc3Rh bGxlZCB1c2luZyB0aGlzIHZpZDoKaHR0cHM6Ly93d3cueW91dHViZS5jb20vd2F0Y2g/dj1QYXN6 LWx2M2dUWQoKU2luZ2xlIHNlcnZlciBob3N0LgoKV2hlbiBJIGdvIHRvIHJ1biBteSBXaW5kb3dz IDcgNjRiaXQgVk0gYW5kIHNldCBpdCB0byBhdHRhY2ggYSBjZCBJU08gaW1hZ2UsIGFzIHNvb24g YXMgSSBkbyBhIHJ1bi1vbmNlIGEgZmV3IHNlY29uZHMgbGF0ZXIgSSBzZWUgdGhpcyBlcnJvcjoK IkZhaWxlZCB0byBydW4gVk0gV2luZG93c183IGluIHJ1bi1vbmNlIG1vZGUiLgoKZG1lc2cgZG9l c250IHNob3cgYW55dGhpbmcuLndoZXJlIGVsc2UgY2FuIEkgY2hlY2sgPwoKU2VudCB3aXRoIFtQ cm90b25NYWlsXShodHRwczovL3Byb3Rvbm1haWwuY29tKSBTZWN1cmUgRW1haWwu --b1_9b226ccada30e17dcd549d070ae4b383 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: base64 PGRpdj5NZXJyeSBDaHJpc3RtYXMgdG8geW91IGFsbC4uPGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2 PjxkaXY+TmV3IGluc3RhbGwgb2Ygb1ZpcnQgNC4yIG9uIGEgQ2VudE9TIDcgc3lzdGVtLiZuYnNw OyBXYXRjaGVkIGEgdmlkIGFuZCByZWFkIHNvbWUgc3R1ZmYgb24gdGhlIHNpdGUgcmVnYXJkaW5n IGluc3RhbGxhdGlvbi9jb25maWcuJm5ic3A7IEkgaGF2ZSBpdCBpbnN0YWxsZWQgdXNpbmcgdGhp cyB2aWQ6PGJyPjwvZGl2PjxkaXY+PGEgaHJlZj0iaHR0cHM6Ly93d3cueW91dHViZS5jb20vd2F0 Y2g/dj1QYXN6LWx2M2dUWSI+aHR0cHM6Ly93d3cueW91dHViZS5jb20vd2F0Y2g/dj1QYXN6LWx2 M2dUWTwvYT48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5TaW5nbGUgc2VydmVyIGhvc3Qu PGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+V2hlbiBJIGdvIHRvIHJ1biBteSBXaW5kb3dz IDcgNjRiaXQgVk0gYW5kIHNldCBpdCB0byBhdHRhY2ggYSBjZCBJU08gaW1hZ2UsIGFzIHNvb24g YXMgSSBkbyBhIHJ1bi1vbmNlIGEgZmV3IHNlY29uZHMgbGF0ZXIgSSBzZWUgdGhpcyBlcnJvcjo8 YnI+PC9kaXY+PGRpdj4iPHNwYW4gY2xhc3M9ImRyYXdlci1wZi1ub3RpZmljYXRpb24tbWVzc2Fn ZSI+RmFpbGVkIHRvIHJ1biBWTSBXaW5kb3dzXzcgaW4gcnVuLW9uY2UgbW9kZSIuPC9zcGFuPjxi cj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PjxzcGFuIGNsYXNzPSJkcmF3ZXItcGYtbm90aWZp Y2F0aW9uLW1lc3NhZ2UiPmRtZXNnIGRvZXNudCBzaG93IGFueXRoaW5nLi53aGVyZSBlbHNlIGNh biBJIGNoZWNrID88L3NwYW4+PGJyPjwvZGl2PjxkaXY+PHNwYW4gY2xhc3M9ImRyYXdlci1wZi1u b3RpZmljYXRpb24tbWVzc2FnZSI+PC9zcGFuPjxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2 IGNsYXNzPSJwcm90b25tYWlsX3NpZ25hdHVyZV9ibG9jayI+PGRpdiBjbGFzcz0icHJvdG9ubWFp bF9zaWduYXR1cmVfYmxvY2stdXNlciBwcm90b25tYWlsX3NpZ25hdHVyZV9ibG9jay1lbXB0eSI+ PGJyPjwvZGl2PjxkaXYgY2xhc3M9InByb3Rvbm1haWxfc2lnbmF0dXJlX2Jsb2NrLXByb3RvbiI+ U2VudCB3aXRoIDxhIGhyZWY9Imh0dHBzOi8vcHJvdG9ubWFpbC5jb20iPlByb3Rvbk1haWw8L2E+ IFNlY3VyZSBFbWFpbC48YnI+PC9kaXY+PC9kaXY+PGRpdj48YnI+PC9kaXY+ --b1_9b226ccada30e17dcd549d070ae4b383--

1 1

ovirt disk extend
by Rajat Patel 24 Dec '17

24 Dec '17

We are using Ovirt4.1 we are facing an issues in regards to one of vm disk. While creating vm we have add 120GB of disk as Thin Provision after like few week we want to have more disk using extend size by GB we add 160GB it is showing at ovirt console right size 280GB. But if we login to vm it show origanl size of the disk which creating what we have commited.( https://access.redhat.com/solutions/697303) df -HTP Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/rhel-root xfs 120G 119G 923M 100% / devtmpfs devtmpfs 8.4G 0 8.4G 0% /dev tmpfs tmpfs 8.4G 13k 8.4G 1% /dev/shm tmpfs tmpfs 8.4G 8.9M 8.4G 1% /run tmpfs tmpfs 8.4G 0 8.4G 0% /sys/fs/cgroup /dev/sda1 xfs 1.1G 200M 865M 19% /boot tmpfs tmpfs 1.7G 0 1.7G 0% /run/user/0 Any advise on this issues. --

2 1

oVirt 4.2.0 is now generally available
by Sandro Bonazzola 24 Dec '17

24 Dec '17

The oVirt project is excited to announce the general availability of oVirt 4.2.0, as of December 20, 2017. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses over 1000 individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics. Key features include: - A redesigned Administration Portal, with an improved user-interface - A new VM portal for non-admin users, for a more streamlined experience - High Performance virtual machine type, for easy optimization of high performance workloads. - oVirt metrics store, a new monitoring solution providing complete infrastructure visibility - Support for virtual machine connectivity via software-defined networks - oVirt now supports Nvidia vGPU - The ovirt-ansible-roles set of packages helps users with common administration tasks - Virt-v2v now supports Debian/Ubuntu and EL and Windows-based virtual machines For more information about these and other features, check out the oVirt 4.2.0 blog post <https://ovirt.org/blog/2017/12/ovirt-4.2.0-now-ga/>. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts on x86_64 and ppc64le (with 4.1 cluster compatibility only) architectures for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.2 (available for x86_64 only) See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. If you’re managing more than one oVirt instance, OpenShift Origin or RDO we also recommend to try ManageIQ <http://manageiq.org/>. Notes: - oVirt Appliance is already available. - oVirt Node is already available [4] - oVirt Windows Guest Tools iso is already available [4] Additional Resources: * Read more about the oVirt 4.2.0 release highlights: http://www.ovirt.org/release/4.2.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] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.2.0/ [4] http://resources.ovirt.org/pub/ovirt-4.2/iso/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

7 7

How do I connect to my VM from another PC?
by José Manuel Noguerol 24 Dec '17

24 Dec '17

Hi all. After a month, I have installed my first VM. And it works almost perfect… I added a vnic but there is no ethernet interface in the VM… I got one more question… Supposing that my VM is completely installed… How do I access to it from a different PC. I mean, a PC apart from the one which has the ovirt engine. I got another host in the hosts list but I can’t access to the portal. Thanks for your time! Regards.

2 2

None
by Jason Keltz 24 Dec '17

24 Dec '17

Content analysis details: (-1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SHORTCIRCUIT Not all rules were run, due to a shortcircuited rule -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP Subject: [ovirt-users] took the plunge to 4.2 but not so sure it was a good idea X-BeenThere: users(a)ovirt.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Main users mailing list for oVirt <users.ovirt.org> List-Unsubscribe: <http://lists.ovirt.org/mailman/options/users>, <mailto:users-request@ovirt.org?subject=unsubscribe> List-Archive: <http://lists.ovirt.org/pipermail/users/> List-Post: <mailto:users@ovirt.org> List-Help: <mailto:users-request@ovirt.org?subject=help> List-Subscribe: <http://lists.ovirt.org/mailman/listinfo/users>, <mailto:users-request@ovirt.org?subject=subscribe> X-List-Received-Date: Sat, 23 Dec 2017 23:04:35 -0000 Hi.. I took the plunge to 4.2, but I think maybe I should have waited a bit... Initially, after upgrade to 4.2, the status of many of my hosts changed from "server" to "desktop". That's okay - I can change them back. My first VM, "archive", I had the ability to access console after the upgrade. I rebooted archive, and I lost the ability (option is grayed out). The VM boots, but I need access to the console. My second VM is called "dist". That one, ovirt says is running, but I can't access it, can't ping it, and there's no console either, so I literally can't get to it. I can reboot it, and shut it down, but it would be helpful to be able to access it. What to do? I've very afraid to reboot my engine because it seems like when I reboot hosts, I lose access to console. In addition, when I try to check for "host updates", I get an error that it can't check for host updates. I ran a yum update on the hosts (after upgrading repo to 4.2 and doing a yum update) and all I'm looking for it to do is clear status, but it doesn't seem to work. Let me know the exact log files to provide, and I will provide details. Thanks! Jason.

2 4

Re: [ovirt-users] ovirt 4.2 host not compatible
by Paul Dyer 24 Dec '17

24 Dec '17

It seems that I am using net_persistence = ifcfg, and that I have lost the definitions for the logical networks. I have recovered these, and was able to do setup logical networks. It is all working now. Paul On Fri, Dec 22, 2017 at 1:46 PM, Paul Dyer <pmdyermms(a)gmail.com> wrote: > My setup is RHEL 7.4, with the host separate from the engine. > > The ovirt-release42 rpm was added to the engine host, but not to the > virtualization host. The vhost was still running v4.1 rpms. I installed > ovirt-release42 on the vhost, then updated the rest of the rpms with "yum > update". I am still getting an error on activation of the vhost... > > Host parasol does not comply with the cluster Intel networks, the > following networks are missing on host: 'data30,data40,ovirtmgmt' > > It seems like the networks bridges are not there anymore?? > > Paul > > > > On Fri, Dec 22, 2017 at 12:46 PM, Paul Dyer <pmdyermms(a)gmail.com> wrote: > >> Hi, >> >> I have upgraded to ovirt 4.2 without issue. But I cannot find a way to >> upgrade the host compatibility in the new OVirt Manager. >> >> I get this error when activiating the host... >> >> host parasol is compatible with versions (3.6,4.0,4.1) and cannot join >> Cluster Intel which is set to version 4.2. >> >> Thanks, >> Paul >> >> >> -- >> Paul Dyer, >> Mercury Consulting Group, RHCE >> 504-302-8750 <(504)%20302-8750> >> > > > > -- > Paul Dyer, > Mercury Consulting Group, RHCE > 504-302-8750 <(504)%20302-8750> > -- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750

2 1

Re: [ovirt-users] oVirt 4.2.0 is now generally available
by Gary Pedretty 23 Dec '17

23 Dec '17

Unable to upgrade a self-hosted engine installation to 4.2.0 due to the following error ovirt-engine-setup-plugin-ovirt-engine conflicts with ovirt-engine-4.0.6.3-1.el7.centos.noarch When trying to do the first step of updating the hosted engine vm Gary ------------------------------------------------------------------------ Gary Pedretty gary(a)ravnalaska.net Systems Manager www.flyravn.com Ravn Alaska /\ W 907-450-7251 5245 Airport Industrial Road / \/\ C 907-388-2247 Fairbanks, Alaska 99709 /\ / \ \ Second greatest commandment Serving All of Alaska / \/ /\ \ \/\ “Love your neighbor as White as far as the eye can see. Must be winter yourself” Matt 22:39 ------------------------------------------------------------------------

2 1

Info from 4.2 beta2 to 4.2
by Gianluca Cecchi 23 Dec '17

23 Dec '17

Hello, I have an host where I only installed ovirt-node-ng from iso of 4.2 beta2 and then I didn't run any deploy of hosted engine yet. If I want to start doing it but with the final 4.2 what is the correct step to do (other than starting from scratch with final 4.2 iso)? yum update (after installing 4.2 repo file) gives me what below and not a full image layer, is it correct? Thanks, Gianluca # yum update ... Dependencies Resolved ============================================================================================================================================================================================================================== Package Arch Version Repository Size ============================================================================================================================================================================================================================== Updating: ansible noarch 2.4.2.0-0.el7 ovirt-4.2-centos-ovirt42 7.6 M collectd x86_64 5.8.0-2.el7 ovirt-4.2-centos-opstools 624 k collectd-disk x86_64 5.8.0-2.el7 ovirt-4.2-centos-opstools 26 k collectd-netlink x86_64 5.8.0-2.el7 ovirt-4.2-centos-opstools 27 k collectd-write_http x86_64 5.8.0-2.el7 ovirt-4.2-centos-opstools 33 k gdeploy noarch 2.0.6-1.el7 ovirt-4.2-centos-gluster312 203 k glusterfs x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 558 k glusterfs-api x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 97 k glusterfs-cli x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 197 k glusterfs-client-xlators x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 854 k glusterfs-events x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 62 k glusterfs-fuse x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 141 k glusterfs-geo-replication x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 230 k glusterfs-libs x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 399 k glusterfs-rdma x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 64 k glusterfs-server x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 1.2 M openvswitch x86_64 1:2.7.3-1.1fc27.el7 ovirt-4.2-centos-ovirt42 4.6 M openvswitch-ovn-common x86_64 1:2.7.3-1.1fc27.el7 ovirt-4.2-centos-ovirt42 1.4 M openvswitch-ovn-host x86_64 1:2.7.3-1.1fc27.el7 ovirt-4.2-centos-ovirt42 802 k python2-gluster x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 39 k python2-openvswitch noarch 1:2.7.3-1.1fc27.el7 ovirt-4.2-centos-ovirt42 167 k qemu-img-ev x86_64 10:2.9.0-16.el7_4.11.1 ovirt-4.2-centos-qemu-ev 2.2 M qemu-kvm-common-ev x86_64 10:2.9.0-16.el7_4.11.1 ovirt-4.2-centos-qemu-ev 914 k qemu-kvm-ev x86_64 10:2.9.0-16.el7_4.11.1 ovirt-4.2-centos-qemu-ev 2.8 M Transaction Summary ============================================================================================================================================================================================================================== Upgrade 24 Packages Total download size: 25 M Is this ok [y/d/N]:

2 1

non-operational host issues following 4.2 upgrade
by Jason Brooks 22 Dec '17

22 Dec '17

Hi all, I upgraded my 4 host converged gluster/ovirt lab setup to 4.2 yesterday, and now 3 of my hosts won't connect to my main data domain, so they're non-operational when I try to activate them. Here's what seems like a relevant passage of vdsm.log: https://paste.fedoraproject.org/paste/JZuxul6-HZjjl8uHzgqL-w The hosts can mount the gluster storage just fine, I can mount to a test location on the hosts, and I can see that the hosts are mounting the storage in the usual place when they attempt to activate. Permissions look normal, too. I undeployed the hosted engine from the three problem machines, in case that was causing an issue. The hosts are running centos 7. Does any of this ring a bell for anyone? Thanks, Jason

2 3