- Devel - oVirt List Archives

Engine's jvm stats via jmx and metrics
by Piotr Kliczewski 09 Feb '15

09 Feb '15

Hi, During my work I found myself in situation when I realized that I have no clue what engine or engine's jvm is doing. I wanted to use visualvm [1] to monitor engine's jvm. There are two ways to monitor jvm. One of them is by using jstatd which is limited and the second one is jmx. I found a blog [2] which helped me to understand how to connect to the engine. In order to connect you need to run visualvm using attached script. Please modify JBOSS_HOME. Once visualvm is up and running you can click "Add jmx connection...". In connection text box please enter (assuming that your iptables allows 8706): service:jmx:remoting-jmx://<engine_ip>:8706 and click OK. Now you can understand what is going on with engine's jvm. I am able see jvm level information but I still have no clue how well high level engine commands are running. I have been looking for a while how to integrate Metrics [3] with the engine to understand how engine behaves over time. I wonder if there is anyone except me interested in understanding how well engine is running. Thanks, Piotr [1] http://visualvm.java.net/ [2] http://blog.akquinet.de/2012/11/01/connecting-visualvm-with-a-remote-jboss-… [3] https://github.com/dropwizard/metrics

2 2

Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to Cluster 3.6
by Sandro Bonazzola 09 Feb '15

09 Feb '15

Il 08/02/2015 16:15, Michael Burman ha scritto: > Hi everyone! > > Is any one knows when it will be possible to join vdsm-4.17.0 to 3.6 Cluster?? > I know that the libvirt version is not supported, but isn't should be? even if it's rhel7..? > > I changed the /usr/share/vdsm/dsaversion.py file to: > 'supportedENGINEs': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5', '3.6'], > 'supportedProtocols': ['2.2', '2.3'], > 'clusterLevels': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5', '3.6'], > > But caps.py is still: > if not hasattr(libvirt, 'VIR_MIGRATE_AUTO_CONVERGE'): > return _dropVersion('3.6', > 'VIR_MIGRATE_AUTO_CONVERGE not found in libvirt,' > ' support for clusterLevel >= 3.6 is disabled.' > ' For Fedora 20 users, please consider upgrading' > ' libvirt from the virt-preview repository') > > if not hasattr(libvirt, 'VIR_MIGRATE_COMPRESSED'): > return _dropVersion('3.6', > 'VIR_MIGRATE_COMPRESSED not found in libvirt,' > ' support for clusterLevel >= 3.6 is disabled.' > ' For Fedora 20 users, please consider upgrading' > ' libvirt from the virt-preview repository') > > libvirt is still disabled for 3.6 clusters... > > > I already tried to rebuild from fedora(with Sandro appreciated help), but had a lot of issues dependencies. > > I'm running on- > ovirt-engine-3.6.0-0.0.master.20150206122208.gitd429375.el6.noarch > vdsm-4.17.0-390.gita3163f3.el7.x86_64 > libvirt-1.1.1-29.el7_0.7.x86_64 > > I would like to know if and when it will be possible to join rhel7 host(vdsm-4.17.0) to Cluster 3.6? Moving to devel list, not really an infra issue. > > Best regards, > > Michael B > > > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[QE] oVirt Live re-based on EL7 for oVirt 3.6
by Sandro Bonazzola 06 Feb '15

06 Feb '15

Hi, oVirt Live has been rebased on EL7 for oVirt 3.6. An initial ISO is available here: http://resources.ovirt.org/pub/ovirt-master-snapshot-static/iso/ovirt-live-… Nightly build will be always available here: http://jenkins.ovirt.org/job/ovirt_live_create_iso/ Help with testing and bugfix is welcome! -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Help with issues with migration
by David Caro 04 Feb '15

04 Feb '15

--KscVNZbUup0vZz0f Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! Upstream phoenix lab has stabilized, but after the outages we are finding s= ome issues probably caused by it. One of them is that th vm migration is not working, ew have two hosts srv05= and srv06, and we want to migrate vms from 06 to 05 but we find those errors on vdsm on 05: Feb 04 02:56:50 ovirt-srv05 vdsm[5170]: vdsm vm.Vm WARNING vmId=3D`434152= 76-a7bf-4c86-b0e9-70a5f6d39a40`::Unknown type found, device: '{'device': 'u= nix', 'alias': 'channel0', 'type': 'channel', 'address': {'bus': '0', 'cont= roller': '0', 'type': 'virtio-serial', 'port': '1'}}' found Feb 04 02:56:50 ovirt-srv05 vdsm[5170]: vdsm vm.Vm WARNING vmId=3D`434152= 76-a7bf-4c86-b0e9-70a5f6d39a40`::Unknown type found, device: '{'device': 'u= nix', 'alias': 'channel1', 'type': 'channel', 'address': {'bus': '0', 'cont= roller': '0', 'type': 'virtio-serial', 'port': '2'}}' found Feb 04 02:56:50 ovirt-srv05 vdsm[5170]: vdsm vm.Vm WARNING vmId=3D`434152= 76-a7bf-4c86-b0e9-70a5f6d39a40`::Unknown type found, device: '{'device': 's= picevmc', 'alias': 'channel2', 'type': 'channel', 'address': {'bus': '0', '= controller': '0', 'type': 'virtio-serial', 'port': '3'}}' found Feb 04 02:56:50 ovirt-srv05 vdsm[5170]: vdsm vm.Vm ERROR vmId=3D`43415276= -a7bf-4c86-b0e9-70a5f6d39a40`::Alias not found for device type graphics dur= ing migration at destination host After that sanlock complains: Feb 04 02:56:50 ovirt-srv05 sanlock[1055]: 2015-02-04 02:56:50-0700 1453 = [1055]: cmd 9 target pid 6479 not found but it seems that the vm is starting up: Feb 04 02:56:50 ovirt-srv05 systemd[1]: Starting Virtual Machine qemu-el6= -vm03-phx-ovirt-org. -- Subject: Unit machine-qemu\x2del6\x2dvm03\x2dphx\x2dovirt\x2dorg.scope= has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel --=20 -- Unit machine-qemu\x2del6\x2dvm03\x2dphx\x2dovirt\x2dorg.scope has begu= n starting up. Feb 04 02:56:50 ovirt-srv05 systemd-machined[5642]: New machine qemu-el6-= vm03-phx-ovirt-org. -- Subject: A virtual machine or container has been started -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel --=20 -- The virtual machine qemu-el6-vm03-phx-ovirt-org with its leader PID 64= 79 has been -- started is now ready to use. Feb 04 02:56:50 ovirt-srv05 systemd[1]: Started Virtual Machine qemu-el6-= vm03-phx-ovirt-org. -- Subject: Unit machine-qemu\x2del6\x2dvm03\x2dphx\x2dovirt\x2dorg.scope= has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel --=20 -- Unit machine-qemu\x2del6\x2dvm03\x2dphx\x2dovirt\x2dorg.scope has fini= shed starting up. --=20 -- The start-up result is done. But it shuts down: Feb 04 02:56:51 ovirt-srv05 systemd-machined[5642]: Machine qemu-el6-vm03-p= hx-ovirt-org terminated. -- Subject: A virtual machine or container has been terminated -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel --=20 -- The virtual machine qemu-el6-vm03-phx-ovirt-org with its leader PID 64= 79 has been -- shut down. Feb 04 02:56:51 ovirt-srv05 vdsm[5170]: vdsm vm.Vm ERROR vmId=3D`43415276= -a7bf-4c86-b0e9-70a5f6d39a40`::Failed to start a migration destination vm Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py"= , line 2298, in _startUnderlyingVm self._completeIncomingMigration= () File "/usr/share/vdsm/virt/vm.py"= , line 4107, in _completeIncomingMigration self._incomingMigrationFinished= =2EisSet(), usedTimeout) File "/usr/share/vdsm/virt/vm.py"= , line 4160, in _attachLibvirtDomainAfterMigration raise MigrationError(e.get_erro= r_message()) MigrationError: Domain not found: n= o domain with matching uuid '43415276-a7bf-4c86-b0e9-70a5f6d39a40' Feb 04 02:56:51 ovirt-srv05 vdsm[5170]: vdsm root WARNING File: /var/lib/= libvirt/qemu/channels/43415276-a7bf-4c86-b0e9-70a5f6d39a40.com.redhat.rhevm= =2Evdsm already removed Feb 04 02:56:51 ovirt-srv05 vdsm[5170]: vdsm root WARNING File: /var/lib/= libvirt/qemu/channels/43415276-a7bf-4c86-b0e9-70a5f6d39a40.org.qemu.guest_a= gent.0 already removed Feb 04 02:56:51 ovirt-srv05 vdsm[5170]: vdsm vm.Vm WARNING vmId=3D`434152= 76-a7bf-4c86-b0e9-70a5f6d39a40`::trying to set state to Down when already D= own Any ideas? Thanks! Though --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com Web: www.redhat.com RHT Global #: 82-62605 --KscVNZbUup0vZz0f Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU0fKyAAoJEEBxx+HSYmnD2ncH/1mKX22wzX5xmd6k2F/dVlWg ZY7NrN5YEFjkjLpECkTnD+1/HzoAy72PXvitsnwiEn1vQFp87g6QJQFz4dgFyoXt S/fRFtAERisaMvVUWk1H78HnMSsW9KwNFrYq4StAO87ctp55Jjm62hEPp5ysoCFY qb570Bt6fB+XoLQENvvxtxIc3OoeBS0MCjhoW6QeHmhbC7yV3LdyBt6A95NFgE8x CaBNIyErNwgtTvT+wdgE8XhRSU2eHrdYSGK0sq7c8AVWGi4qa+oZ6PYGnkulazUi jDVF8zVGYjQ22sWgsMTOybhRL0AW90PRx3TnnwvmJ3VWSyko35091YFOA7ISOVo= =ZerK -----END PGP SIGNATURE----- --KscVNZbUup0vZz0f--

2 2

[Event] 2015 oVirt Asia Workshop
by Brian Proffitt 04 Feb '15

04 Feb '15

As oVirt strives to become the best open source and comprehensive data center virtualization management suite, and its community rapidly evolves and grows, one of the ways its vibrant community connects is through our Global Workshops. The events are conducted solely to introduce new users and veteran oVirt admins to new features and new techniques found in oVirt, as well as provide a forum for our users to connect directly with the development team behind oVirt. With that in mind, we are pleased to announce that registration is now open for the 2014 oVirt Workshop! The next 2015 oVirt workshop will be co-located with the FOSSAsia in Singapore on March 14, 2015. This workshop is designed to encourage collaboration in our community, lay the foundation for best practices in oVirt use, convey end-user stories, and help answer questions about the project from both a developer and user's perspective. For more information, and to register for the event, visit the Workshop page[1] today! [1] http://www.ovirt.org/Asia_Workshop_Mar_2015 -- Brian Proffitt Community Liaison oVirt Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

1 0

[QE] oVirt 3.6.0 nightly build testing
by Sandro Bonazzola 04 Feb '15

04 Feb '15

Hi, I've been asked to start the discussion about testing 3.6.0 nightly builds. Once http://gerrit.ovirt.org/37384 will be merged or manually applied on the testing host, 3.6 cluster compatibility will be enabled on the following distributions: Fedora 21: no special instructions for this distribution, should work out of the box. Fedora 20: requires virt-preview repository. you can find the .repo file[1] in the virt-preview home[2]. AN update to ovirt-release-master rpm will enable the repository by default, it will be available probably tomorrow. RHEL / CentOS 7.1: not yet released, but once they'll be out they'll support 3.6 cluster compatibility RHEL / CentOS <= 7.0 won't have 3.6 cluster compatibility. [1] https://fedorapeople.org/groups/virt/virt-preview/fedora-virt-preview.repo [2] https://fedorapeople.org/groups/virt/virt-preview/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 3

[QE][ACTION REQUIRED] oVirt 3.6.0 status
by Sandro Bonazzola 04 Feb '15

04 Feb '15

Hi, here's an update on 3.6 status on integration / rel-eng side ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 22: 2015-05-19 Fedora 20 End Of Life: 2015-06-19 (1 month after Fedora 22 release) Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 548 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 506 bugs [4] targeted to 3.6.0. oVirt 3.6 cluster compatibility status in nightly builds: VDSM patch introducing 3.6 compatibility[5] has not been merged yet, waiting for CentOS and RHEL 7.1 to be released for getting libvirt support. CentOS and RHEL 6.z won't have 3.6 compatibility by design [6]. Fedora 20 won't have 3.6 compatibility level since virt maintainers are going to maintain latest libvirt rpms only in latest stable Fedora release (currently Fedora 21). There's no point in providing Fedora 20 packages on oVirt side since Fedora 20 will go EOL before oVirt 3.6.0 GA. Fedora 21 will be able to support 3.6 compatibility once VDSM patch[5] will be merged. Fedora 22 may not be able to support VDSM at all since it will run Python 3 instead of Python 2 as default python interpreter[7], so more work will be needed there. [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%… [4] http://goo.gl/ZbUiMc [5] http://gerrit.ovirt.org/37384 [6] http://lists.ovirt.org/pipermail/users/2014-September/027421.html [7] https://fedoraproject.org/wiki/Releases/22/ChangeSet -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[QE][ACTION REQUIRED] oVirt 3.5.2 RC status
by Sandro Bonazzola 04 Feb '15

04 Feb '15

Hi, We're going to start composing oVirt 3.5.2 RC on *2015-02-25 08:00 UTC* from 3.5 branch. Maintainers: - Please be sure that 3.5 snapshot allow to create VMs before *2015-02-24 15:00 UTC* - Please be sure that no pending patches are going to block the release before *2015-02-24 15:00 UTC* - If any patch must block the RC release please raise the issue as soon as possible. A release management entry has been added for tracking the schedule of 3.5.2 [0] A bug tracker [1] has been created and currently has no open blockers. There are still 43 bugs [2] targeted to 3.5.2. Excluding node and documentation bugs we still have 35 bugs [3] targeted to 3.5.2. Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.5.2 should not be released without them fixed. - Please update the target to 3.5.3 or later for bugs that won't be in 3.5.2: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] Community: - If you're testing oVirt 3.5 nightly snapshot, please add yourself to the test page [5] [0] http://www.ovirt.org/OVirt_3.5.z_Release_Management#oVirt_3.5.2 [1] http://bugzilla.redhat.com/1186161 [2] http://goo.gl/crVJPH [3] http://goo.gl/2qTZZU [4] http://www.ovirt.org/OVirt_3.5.2_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.5.2_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

please test and give karma to novnc on epel6
by Sandro Bonazzola 04 Feb '15

04 Feb '15

Hi, a new package restoring novnc on epel6 has been pushed: https://admin.fedoraproject.org/updates/novnc-0.4-9.el6 Please help testing and giving karma. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 7

otopi missing from f19 master snapshot repo
by Greg Sheremeta 03 Feb '15

03 Feb '15

I noticed that there is no otopi available in http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc19/noarch/ I didn't see it in any of the f19 master repos, actually. I had to install otopi from the fc20 repo. Not sure if this is intentional. Thanks, Greg Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme(a)redhat.com

2 1