Re: [Users] Trouble upgrading
Hi, well we in Europe tend to sleep :) beside that: we don't run RHEL, but CentOS, and we didn't try upgrading our compute nodes until know. Am 22.11.2013 01:33, schrieb Bob Doolittle: Not sure why I'm the only person reporting this (am I the only person who runs RH 6 on their KVM hosts who has tried upgrading??), but the problem has not resolved. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.3.1 rlease
I'd just like to say that I just upgraded from 3.3.0.1 to 3.3.1 without problems. It was a smooth experience, for both Engine and VDSM. Cheers, Martijn. Kiril Nesenko schreef op 21-11-2013 16:43: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 01:00 PM, Itamar Heim wrote: On 11/22/2013 06:08 AM, Vijay Bellur wrote: On 11/22/2013 06:25 AM, Bob Doolittle wrote: On 11/21/2013 07:53 PM, Itamar Heim wrote: On 11/22/2013 02:52 AM, Bob Doolittle wrote: On 11/21/2013 07:48 PM, Itamar Heim wrote: On 11/22/2013 02:33 AM, Bob Doolittle wrote: On 11/21/2013 12:57 PM, Itamar Heim wrote: On 11/21/2013 07:38 PM, Bob Doolittle wrote: On 11/21/2013 12:00 PM, Itamar Heim wrote: On 11/21/2013 06:32 PM, Bob Doolittle wrote: Yay! Congratulations to all of the oVirt team. I am having trouble locating upgrade instructions, however. There's nothing in the release notes. I discovered through trial-and-error that running engine-setup again handles upgrade of the Engine. But I don't know how to upgrade my RH 6.4 KVM host. When I try to run yum update it fails due to dependency errors notably in: glusterfs qemu vdsm can you please include the yum output log? Sorry yes. Attached are three outputs. First my repolist. Then yum update with no options, and yum update with --skip-broken (so you can see the lurking issues masked by the first failure). It appears that the glusterfs issue is due to a newer version offered by rhel-x86_64-server-6: glusterfs-3.4.0.36rhs-1.el6.x86_64. This has dependencies which conflict with the version provided by ovirt-stable (and glusterfs-epel). It looks like there was a large update to the Red Hat repo last night that has caused conflicts with ovirt-stable. Note I can get it to the point where it's willing to install packages if I specify --skip-broken and also --exclude vdsm-python-4.12.1, but that's a bit too scary for me without checking first. oh, you may caught rhel repo in middle of a refresh - try again in a few hours first, but could be the refresh may cause an issue we'd need to resolve. Not sure why I'm the only person reporting this (am I the only person who runs RH 6 on their KVM hosts who has tried upgrading??), but the problem has not resolved. What's the next step? Does it need a bug opened? Let me know if I can provide any more information. have you tried refreshing your repo / clear yum cache? (since glusterfs-3.4.0.36rhs-1.el6 should be in the repo) I just did yum clean all; yum update. Same result. do you have glusterfs-3.4.0.36rhs-1.el6 in the repo? Apparently: Error: Package: glusterfs-cli-3.4.0-8.el6.x86_64 (@glusterfs-epel) Requires: glusterfs-libs = 3.4.0-8.el6 Removing: glusterfs-3.4.0-8.el6.x86_64 (@glusterfs-epel) glusterfs-libs = 3.4.0-8.el6 Updated By: glusterfs-3.4.0.36rhs-1.el6.x86_64 (rhel-x86_64-server-6) Not found Removing: glusterfs-libs-3.4.0-8.el6.x86_64 (@glusterfs-epel) glusterfs-libs = 3.4.0-8.el6 Updated By: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 (rhel-x86_64-server-6) glusterfs-libs = 3.4.0.36rhs-1.el6 Available: glusterfs-3.2.7-1.el6.i686 (epel) glusterfs-libs = 3.2.7-1.el6 If you are using EPEL packages to create/run gluster volumes on RHEL (essentially the server side functionality of gluster), it would be better to move to GlusterFS 3.4.1 and then try the upgrade. If you are not making use of gluster's server side packages, you can remove glusterfs-cli and related dependencies. If an upgrade is initiated after that, it should go through. Regards, Vijay doesn't vdsm require vdsm-gluster which requires them? vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence if gluster server side functionality is being exercised, we would need to use EPEL packages. For a virt only cluster, only the client side packages are needed and RHEL 6.5 has these packages. Thanks, Vijay ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Migration problem - non-English characters
Hi! One of our VMs had the letter č in its Name field. When we set the note to maintenance mode, the VM refused to migrate to another node. It had to be manually shut down and then restarted. Here are the events when we reproduced this with test VM. 2013-Nov-22, 10:29 Migration completed (VM: letter_c_test, Source: onode1.example.com, Destination: onode2.example.com, Duration: 9 sec). 2013-Nov-22, 10:29 Migration started (VM: letter_c_test, Source: onode1.example.com, Destination: onode2.example.com, User: admin@internal). 2013-Nov-22, 10:20 Migration completed (VM: letter_c_test, Source: onode3.example.com, Destination: onode1.example.com, Duration: 12 sec). 2013-Nov-22, 10:19 Migration started (VM: letter_c_test, Source: onode3.example.com, Destination: onode1.example.com, User: admin@internal). 2013-Nov-22, 10:19 VM letter_c_test started on Host onode3.example.com 2013-Nov-22, 10:19 VM letter_c_test was started by admin@internal (Host: onode3.example.com). 2013-Nov-22, 10:19 VM letter_c_test is down. Exit message: User shut down 2013-Nov-22, 10:18 VM shutdown initiated by admin@internal on VM letter_c_test (Host: onode1.example.com). 2013-Nov-22, 10:17 Migration failed due to Error: Unexpected exception (VM: letter_c_test, Source: onode1.example.com, Destination: onode3.example.com). 2013-Nov-22, 10:17 Migration started (VM: letter_c_test, Source: onode1.example.com, Destination: onode3.example.com, User: admin@internal). 2013-Nov-22, 10:17 Interface nic1 (VirtIO) was updated for VM letter_c_test. (User: admin@internal) 2013-Nov-22, 10:17 VM letter_č_test configuration was updated by admin@internal. 2013-Nov-22, 10:17 VM letter_č_test was renamed from letter_č_test to letter_c_test. 2013-Nov-22, 10:16 Migration failed due to Error: Unexpected exception (VM: letter_č_test, Source: onode1.example.com, Destination: onode3.example.com). 2013-Nov-22, 10:16 Migration started (VM: letter_č_test, Source: onode1.example.com, Destination: onode3.example.com, User: admin@internal). 2013-Nov-22, 10:15 VM letter_č_test started on Host onode1.example.com 2013-Nov-22, 10:15 VM letter_č_test was started by USERNAME (Host: onode1.example.com). 2013-Nov-22, 10:14 VM letter_č_test creation has been completed. 2013-Nov-22, 10:13 VM letter_č_test creation was initiated by USERNAME. After the VM was renamed (č was replaced with c), stopped and then started it migrated normally. Regards, Mitja -- -- Mitja Mihelič ARNES, Tehnološki park 18, p.p. 7, SI-1001 Ljubljana, Slovenia tel: +386 1 479 8877, fax: +386 1 479 88 78 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Guest Agent
On Nov 22, 2013, at 10:03 , Martijn Grendelman martijn.grendel...@isaac.nl wrote: And is there any news on a packaged guest agent for Windows? It would be great if someone can help with that. It should not be at all difficult to actually build it in Visual Studio. Vinzenz should be able to provide guidance. Same applies to el5, there should be very few changes needed, Vinzenz has it in todo list but this is the first time someone is actually asking:) Thanks, michal Cheers, Martijn. Thomas Suckow schreef op 22-11-2013 2:04: Ok, so what about an el5 guest agent? The github repo https://github.com/oVirt/ovirt-guest-agent hints at there being support for el5, but it is incompatible with the automake version in el5. Is there a prebuilt rpm somewhere that I am missing? -- Thomas ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Guest Agent
On Fri, Nov 22, 2013 at 8:08 AM, Gianluca Cecchi wrote: On Fri, Nov 22, 2013 at 2:18 AM, Itamar Heim wrote: i guess no one asked for one till now so its not built. I knew I was the last one on earth supporting RHEL5. rhev does have a rhev-guest-agent for .el5, supported and all. i just don't remember we heard anyone asking for this in the ovirt community. Not tried yet myself, but I think you can download related source rpm here and try to rebuld: http://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/RHEV/SRPMS/ HIH, Gianluca Just rebuilt rhev-agent-2.3.16-3.el5.src.rpm on a CentOS 5.10 x86_64 VM on oVirt 3.3.1-2.fc19 and the agent seems to work. In the sense that: - I get VM ip in web gui - I get list of applications in web gui: Installed Applications kernel-2.6.18-371.1.2.el5 kernel-2.6.18-371.el5 rhev-agent-2.3.16-3 xorg-x11-drv-qxl-0.0.12-2.el5 - when there is activity, I see memory,cpu and network usage rows with consistent values Other things to verify? Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 11:21 AM, Vijay Bellur wrote: On 11/22/2013 01:00 PM, Itamar Heim wrote: On 11/22/2013 06:08 AM, Vijay Bellur wrote: On 11/22/2013 06:25 AM, Bob Doolittle wrote: On 11/21/2013 07:53 PM, Itamar Heim wrote: On 11/22/2013 02:52 AM, Bob Doolittle wrote: On 11/21/2013 07:48 PM, Itamar Heim wrote: On 11/22/2013 02:33 AM, Bob Doolittle wrote: On 11/21/2013 12:57 PM, Itamar Heim wrote: On 11/21/2013 07:38 PM, Bob Doolittle wrote: On 11/21/2013 12:00 PM, Itamar Heim wrote: On 11/21/2013 06:32 PM, Bob Doolittle wrote: Yay! Congratulations to all of the oVirt team. I am having trouble locating upgrade instructions, however. There's nothing in the release notes. I discovered through trial-and-error that running engine-setup again handles upgrade of the Engine. But I don't know how to upgrade my RH 6.4 KVM host. When I try to run yum update it fails due to dependency errors notably in: glusterfs qemu vdsm can you please include the yum output log? Sorry yes. Attached are three outputs. First my repolist. Then yum update with no options, and yum update with --skip-broken (so you can see the lurking issues masked by the first failure). It appears that the glusterfs issue is due to a newer version offered by rhel-x86_64-server-6: glusterfs-3.4.0.36rhs-1.el6.x86_64. This has dependencies which conflict with the version provided by ovirt-stable (and glusterfs-epel). It looks like there was a large update to the Red Hat repo last night that has caused conflicts with ovirt-stable. Note I can get it to the point where it's willing to install packages if I specify --skip-broken and also --exclude vdsm-python-4.12.1, but that's a bit too scary for me without checking first. oh, you may caught rhel repo in middle of a refresh - try again in a few hours first, but could be the refresh may cause an issue we'd need to resolve. Not sure why I'm the only person reporting this (am I the only person who runs RH 6 on their KVM hosts who has tried upgrading??), but the problem has not resolved. What's the next step? Does it need a bug opened? Let me know if I can provide any more information. have you tried refreshing your repo / clear yum cache? (since glusterfs-3.4.0.36rhs-1.el6 should be in the repo) I just did yum clean all; yum update. Same result. do you have glusterfs-3.4.0.36rhs-1.el6 in the repo? Apparently: Error: Package: glusterfs-cli-3.4.0-8.el6.x86_64 (@glusterfs-epel) Requires: glusterfs-libs = 3.4.0-8.el6 Removing: glusterfs-3.4.0-8.el6.x86_64 (@glusterfs-epel) glusterfs-libs = 3.4.0-8.el6 Updated By: glusterfs-3.4.0.36rhs-1.el6.x86_64 (rhel-x86_64-server-6) Not found Removing: glusterfs-libs-3.4.0-8.el6.x86_64 (@glusterfs-epel) glusterfs-libs = 3.4.0-8.el6 Updated By: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 (rhel-x86_64-server-6) glusterfs-libs = 3.4.0.36rhs-1.el6 Available: glusterfs-3.2.7-1.el6.i686 (epel) glusterfs-libs = 3.2.7-1.el6 If you are using EPEL packages to create/run gluster volumes on RHEL (essentially the server side functionality of gluster), it would be better to move to GlusterFS 3.4.1 and then try the upgrade. If you are not making use of gluster's server side packages, you can remove glusterfs-cli and related dependencies. If an upgrade is initiated after that, it should go through. Regards, Vijay doesn't vdsm require vdsm-gluster which requires them? vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence if gluster server side functionality is being exercised, we would need to use EPEL packages. For a virt only cluster, only the client side packages are needed and RHEL 6.5 has these packages. vijay - didn't we add gluster-cli for libgfapi support in core vdsm? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] info on virtio-scsi
Hello, I had a CentOS 6.4 VM created in oVirt 3.3.0 Then I updated to 3.3.1 I created a CentOS 5.10 VM In CentOS 5.10 I built rhev-agent-2.3.16-3.el5.src.rpm In CentOS 6.4 I have ovirt-guest-agent-1.0.8-1.el6.noarch Both are configured with one virtio disk. In CentOS 5 I can add a disk and select virtio-scsi... but I can't use it because of no support in 5.x kernels. In CentOS 6.4 I'm not presented with the option virtio-scsi. What can I do to get it? Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] [OT] Spanish translation
Hi, Sorry if it's the wrong place, but don't know where to place the request (besides bugzilla). I won't speak for the hole Spanish community, but in the webadmin, in the VMs tab says Crear una toma de pantalla referring to create a snapshot but that is an incorrect translation in my opinion as it's not related to the screen in first place, and though there's no literal translation for the technical term, it should be more like Crear una instantánea or what should be better, Crear un snapshot and it would be correct as when you say whisky instead of licor de cebada of football instead of balón pie ... :-) Regards, ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On Fri, Nov 22, 2013 at 05:51:48PM +0200, Itamar Heim wrote: doesn't vdsm require vdsm-gluster which requires them? vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence if gluster server side functionality is being exercised, we would need to use EPEL packages. For a virt only cluster, only the client side packages are needed and RHEL 6.5 has these packages. vijay - didn't we add gluster-cli for libgfapi support in core vdsm? glusterVolume uses the cli to only to tell if it's using tcp or rdma. This vdsm dependency is currently a soft one (not declared in the spec), and would only affect users which attempt to user true glusterfs storage domains without installing gluster-cli. Luckily we do not have this problem since we can only use gluster-fuse.. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [OT] Spanish translation
Thanks - can you please open a BZ on this issue [1]? Regards, Einav [1] https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt - Original Message - From: Juan Pablo Lorier jplor...@gmail.com To: users@ovirt.org Sent: Friday, November 22, 2013 11:29:06 AM Subject: [Users] [OT] Spanish translation Hi, Sorry if it's the wrong place, but don't know where to place the request (besides bugzilla). I won't speak for the hole Spanish community, but in the webadmin, in the VMs tab says Crear una toma de pantalla referring to create a snapshot but that is an incorrect translation in my opinion as it's not related to the screen in first place, and though there's no literal translation for the technical term, it should be more like Crear una instantánea or what should be better, Crear un snapshot and it would be correct as when you say whisky instead of licor de cebada of football instead of balón pie ... :-) Regards, ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle bob@... writes: On 11/21/2013 12:57 PM, Itamar Heim wrote: On 11/21/2013 07:38 PM, Bob Doolittle wrote: On 11/21/2013 12:00 PM, Itamar Heim wrote: On 11/21/2013 06:32 PM, Bob Doolittle wrote: Yay! Congratulations to all of the oVirt team. I am having trouble locating upgrade instructions, however. There's nothing in the release notes. I discovered through trial-and-error that running engine-setup again handles upgrade of the Engine. But I don't know how to upgrade my RH 6.4 KVM host. When I try to run yum update it fails due to dependency errors notably in: glusterfs qemu vdsm can you please include the yum output log? Sorry yes. Attached are three outputs. First my repolist. Then yum update with no options, and yum update with --skip-broken (so you can see the lurking issues masked by the first failure). It appears that the glusterfs issue is due to a newer version offered by rhel-x86_64-server-6: glusterfs-3.4.0.36rhs-1.el6.x86_64. This has dependencies which conflict with the version provided by ovirt-stable (and glusterfs-epel). It looks like there was a large update to the Red Hat repo last night that has caused conflicts with ovirt-stable. Note I can get it to the point where it's willing to install packages if I specify --skip-broken and also --exclude vdsm-python-4.12.1, but that's a bit too scary for me without checking first. oh, you may caught rhel repo in middle of a refresh - try again in a few hours first, but could be the refresh may cause an issue we'd need to resolve. Not sure why I'm the only person reporting this (am I the only person who runs RH 6 on their KVM hosts who has tried upgrading??), but the problem has not resolved. What's the next step? Does it need a bug opened? Let me know if I can provide any more information. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay I'm wondering if the qemu issue I was when I tried --skip-broken is just an artifact of this, or some other issue entirely. We won't know until this glusterfs-cli issue is resolved. -Bob ___ Users mailing list Users@ovirt.org
Re: [Users] Trouble upgrading
On 11/22/2013 11:45 AM, Dan Kenigsberg wrote: On Fri, Nov 22, 2013 at 05:51:48PM +0200, Itamar Heim wrote: doesn't vdsm require vdsm-gluster which requires them? vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence if gluster server side functionality is being exercised, we would need to use EPEL packages. For a virt only cluster, only the client side packages are needed and RHEL 6.5 has these packages. vijay - didn't we add gluster-cli for libgfapi support in core vdsm? glusterVolume uses the cli to only to tell if it's using tcp or rdma. This vdsm dependency is currently a soft one (not declared in the spec), and would only affect users which attempt to user true glusterfs storage domains without installing gluster-cli. This is not what I see. I see that vdsm.x86_64 has a dependency on glusterfs-cli: # rpm -qa --whatrequires glusterfs-cli vdsm-4.12.1-4.el6.x86_64 Hence the problem, since the new version of glusterfs does not deliver this package. -Bob Luckily we do not have this problem since we can only use gluster-fuse.. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 12:21 PM, Vijay Bellur wrote: On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle bob@... writes: On 11/21/2013 12:57 PM, Itamar Heim wrote: On 11/21/2013 07:38 PM, Bob Doolittle wrote: On 11/21/2013 12:00 PM, Itamar Heim wrote: On 11/21/2013 06:32 PM, Bob Doolittle wrote: Yay! Congratulations to all of the oVirt team. I am having trouble locating upgrade instructions, however. There's nothing in the release notes. I discovered through trial-and-error that running engine-setup again handles upgrade of the Engine. But I don't know how to upgrade my RH 6.4 KVM host. When I try to run yum update it fails due to dependency errors notably in: glusterfs qemu vdsm can you please include the yum output log? Sorry yes. Attached are three outputs. First my repolist. Then yum update with no options, and yum update with --skip-broken (so you can see the lurking issues masked by the first failure). It appears that the glusterfs issue is due to a newer version offered by rhel-x86_64-server-6: glusterfs-3.4.0.36rhs-1.el6.x86_64. This has dependencies which conflict with the version provided by ovirt-stable (and glusterfs-epel). It looks like there was a large update to the Red Hat repo last night that has caused conflicts with ovirt-stable. Note I can get it to the point where it's willing to install packages if I specify --skip-broken and also --exclude vdsm-python-4.12.1, but that's a bit too scary for me without checking first. oh, you may caught rhel repo in middle of a refresh - try again in a few hours first, but could be the refresh may cause an issue we'd need to resolve. Not sure why I'm the only person reporting this (am I the only person who runs RH 6 on their KVM hosts who has tried upgrading??), but the problem has not resolved. What's the next step? Does it need a bug opened? Let me know if I can provide any more information. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay Yes. If I update the glusterfs-epel.repo file to use 3.4.1 instead of 3.4.0, yum is happy to do the update. Hopefully there are no incompatibilities in the interfaces consumed by vdsm. So the question is how to
Re: [Users] Trouble upgrading
On 11/22/2013 12:21 PM, Vijay Bellur wrote: On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle bob@... writes: On 11/21/2013 12:57 PM, Itamar Heim wrote: On 11/21/2013 07:38 PM, Bob Doolittle wrote: On 11/21/2013 12:00 PM, Itamar Heim wrote: On 11/21/2013 06:32 PM, Bob Doolittle wrote: Yay! Congratulations to all of the oVirt team. I am having trouble locating upgrade instructions, however. There's nothing in the release notes. I discovered through trial-and-error that running engine-setup again handles upgrade of the Engine. But I don't know how to upgrade my RH 6.4 KVM host. When I try to run yum update it fails due to dependency errors notably in: glusterfs qemu vdsm can you please include the yum output log? Sorry yes. Attached are three outputs. First my repolist. Then yum update with no options, and yum update with --skip-broken (so you can see the lurking issues masked by the first failure). It appears that the glusterfs issue is due to a newer version offered by rhel-x86_64-server-6: glusterfs-3.4.0.36rhs-1.el6.x86_64. This has dependencies which conflict with the version provided by ovirt-stable (and glusterfs-epel). It looks like there was a large update to the Red Hat repo last night that has caused conflicts with ovirt-stable. Note I can get it to the point where it's willing to install packages if I specify --skip-broken and also --exclude vdsm-python-4.12.1, but that's a bit too scary for me without checking first. oh, you may caught rhel repo in middle of a refresh - try again in a few hours first, but could be the refresh may cause an issue we'd need to resolve. Not sure why I'm the only person reporting this (am I the only person who runs RH 6 on their KVM hosts who has tried upgrading??), but the problem has not resolved. What's the next step? Does it need a bug opened? Let me know if I can provide any more information. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay Vijay, Do you know why the glusterfs folks felt compelled to do a minor update of 3.4.0 to 3.4.1 utilizing an entirely new repository, instead of reusing the old repository with new versioning? That would have
Re: [Users] Trouble upgrading
On 11/22/2013 11:18 PM, Bob Doolittle wrote: On 11/22/2013 12:21 PM, Vijay Bellur wrote: On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle bob@... writes: On 11/21/2013 12:57 PM, Itamar Heim wrote: On 11/21/2013 07:38 PM, Bob Doolittle wrote: On 11/21/2013 12:00 PM, Itamar Heim wrote: On 11/21/2013 06:32 PM, Bob Doolittle wrote: Yay! Congratulations to all of the oVirt team. I am having trouble locating upgrade instructions, however. There's nothing in the release notes. I discovered through trial-and-error that running engine-setup again handles upgrade of the Engine. But I don't know how to upgrade my RH 6.4 KVM host. When I try to run yum update it fails due to dependency errors notably in: glusterfs qemu vdsm can you please include the yum output log? Sorry yes. Attached are three outputs. First my repolist. Then yum update with no options, and yum update with --skip-broken (so you can see the lurking issues masked by the first failure). It appears that the glusterfs issue is due to a newer version offered by rhel-x86_64-server-6: glusterfs-3.4.0.36rhs-1.el6.x86_64. This has dependencies which conflict with the version provided by ovirt-stable (and glusterfs-epel). It looks like there was a large update to the Red Hat repo last night that has caused conflicts with ovirt-stable. Note I can get it to the point where it's willing to install packages if I specify --skip-broken and also --exclude vdsm-python-4.12.1, but that's a bit too scary for me without checking first. oh, you may caught rhel repo in middle of a refresh - try again in a few hours first, but could be the refresh may cause an issue we'd need to resolve. Not sure why I'm the only person reporting this (am I the only person who runs RH 6 on their KVM hosts who has tried upgrading??), but the problem has not resolved. What's the next step? Does it need a bug opened? Let me know if I can provide any more information. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay Vijay, Do you know why the glusterfs folks felt compelled to do a minor update of 3.4.0 to 3.4.1 utilizing an entirely new repository, instead of reusing the old repository with new
Re: [Users] [OT] Spanish translation
ok On 22/11/13 15:18, Einav Cohen wrote: Thanks - can you please open a BZ on this issue [1]? Regards, Einav [1] https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt - Original Message - From: Juan Pablo Lorier jplor...@gmail.com To: users@ovirt.org Sent: Friday, November 22, 2013 11:29:06 AM Subject: [Users] [OT] Spanish translation Hi, Sorry if it's the wrong place, but don't know where to place the request (besides bugzilla). I won't speak for the hole Spanish community, but in the webadmin, in the VMs tab says Crear una toma de pantalla referring to create a snapshot but that is an incorrect translation in my opinion as it's not related to the screen in first place, and though there's no literal translation for the technical term, it should be more like Crear una instantánea or what should be better, Crear un snapshot and it would be correct as when you say whisky instead of licor de cebada of football instead of balón pie ... :-) Regards, ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 12:52 PM, Vijay Bellur wrote: On 11/22/2013 11:18 PM, Bob Doolittle wrote: On 11/22/2013 12:21 PM, Vijay Bellur wrote: On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle bob@... writes: On 11/21/2013 12:57 PM, Itamar Heim wrote: On 11/21/2013 07:38 PM, Bob Doolittle wrote: On 11/21/2013 12:00 PM, Itamar Heim wrote: On 11/21/2013 06:32 PM, Bob Doolittle wrote: Yay! Congratulations to all of the oVirt team. I am having trouble locating upgrade instructions, however. There's nothing in the release notes. I discovered through trial-and-error that running engine-setup again handles upgrade of the Engine. But I don't know how to upgrade my RH 6.4 KVM host. When I try to run yum update it fails due to dependency errors notably in: glusterfs qemu vdsm can you please include the yum output log? Sorry yes. Attached are three outputs. First my repolist. Then yum update with no options, and yum update with --skip-broken (so you can see the lurking issues masked by the first failure). It appears that the glusterfs issue is due to a newer version offered by rhel-x86_64-server-6: glusterfs-3.4.0.36rhs-1.el6.x86_64. This has dependencies which conflict with the version provided by ovirt-stable (and glusterfs-epel). It looks like there was a large update to the Red Hat repo last night that has caused conflicts with ovirt-stable. Note I can get it to the point where it's willing to install packages if I specify --skip-broken and also --exclude vdsm-python-4.12.1, but that's a bit too scary for me without checking first. oh, you may caught rhel repo in middle of a refresh - try again in a few hours first, but could be the refresh may cause an issue we'd need to resolve. Not sure why I'm the only person reporting this (am I the only person who runs RH 6 on their KVM hosts who has tried upgrading??), but the problem has not resolved. What's the next step? Does it need a bug opened? Let me know if I can provide any more information. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay Vijay, Do you know why the glusterfs folks felt compelled to do a minor update of 3.4.0 to 3.4.1 utilizing an entirely new
Re: [Users] Guest Agent
On 11/22/2013 05:18 PM, Gianluca Cecchi wrote: On Fri, Nov 22, 2013 at 8:08 AM, Gianluca Cecchi wrote: On Fri, Nov 22, 2013 at 2:18 AM, Itamar Heim wrote: i guess no one asked for one till now so its not built. I knew I was the last one on earth supporting RHEL5. rhev does have a rhev-guest-agent for .el5, supported and all. i just don't remember we heard anyone asking for this in the ovirt community. Not tried yet myself, but I think you can download related source rpm here and try to rebuld: http://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/RHEV/SRPMS/ HIH, Gianluca Just rebuilt rhev-agent-2.3.16-3.el5.src.rpm on a CentOS 5.10 x86_64 VM on oVirt 3.3.1-2.fc19 and the agent seems to work. In the sense that: - I get VM ip in web gui - I get list of applications in web gui: Installed Applications kernel-2.6.18-371.1.2.el5 kernel-2.6.18-371.el5 rhev-agent-2.3.16-3 xorg-x11-drv-qxl-0.0.12-2.el5 - when there is activity, I see memory,cpu and network usage rows with consistent values Other things to verify? I don't think the .el5 one has any SSO in it, so i think this covers it. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Guest Agent
On 11/22/2013 10:53 AM, Itamar Heim wrote:
On 11/22/2013 05:18 PM, Gianluca Cecchi wrote:
On Fri, Nov 22, 2013 at 8:08 AM, Gianluca Cecchi wrote:
On Fri, Nov 22, 2013 at 2:18 AM, Itamar Heim wrote:
i guess no one asked for one till now so its not built.
I knew I was the last one on earth supporting RHEL5.
rhev does have a rhev-guest-agent for .el5, supported and all.
i just don't remember we heard anyone asking for this in the ovirt
community.
Not tried yet myself, but I think you can download related source rpm
here and try to rebuld:
http://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/RHEV/SRPMS/
HIH,
Gianluca
Just rebuilt rhev-agent-2.3.16-3.el5.src.rpm on a CentOS 5.10 x86_64
VM on oVirt 3.3.1-2.fc19 and the agent seems to work.
In the sense that:
- I get VM ip in web gui
- I get list of applications in web gui:
Installed Applications
kernel-2.6.18-371.1.2.el5
kernel-2.6.18-371.el5
rhev-agent-2.3.16-3
xorg-x11-drv-qxl-0.0.12-2.el5
- when there is activity, I see memory,cpu and network usage rows with
consistent values
Other things to verify?
I don't think the .el5 one has any SSO in it, so i think this covers it.
Alright so far so good. I setup a jenkins job to build this for me. So
far working like a dream.
wget
http://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/RHEV/SRPMS/rhev-agent-2.3.16-3.el5.src.rpm
mkdir -p build/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
rpmbuild --define _topdir $WORKSPACE/build --rebuild
rhev-agent-2.3.16-3.el5.src.rpm
Any chance of an 'official' build ending up in the EPEL for anyone else
who may desire this?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble Upgrading (Fedora)
On 11/22/2013 06:55 PM, Nicholas Kesick wrote: I am having trouble upgrading on Fedora 19 to 3.3.1. Two observations: 1) I can't find ovirt-engine-3.3.1, even after a yum clear all; yum update. run engine-setup - it will unlock ovirt-engine and will handle backup/upgrade/etc. danken/yaniv/douglas? 2) There is a dependency update circle involving python-cpopen-1.2.3-4.fc19.x86_64 and vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 Searching for ovirt-engine (after yum clear all) yum list ovirt-engine Loaded plugins: langpacks, refresh-packagekit, versionlock Installed Packages ovirt-engine.noarch 3.3.0-4.fc19 @ovirt-stable Next a the yum update sudo yum history info 8 Loaded plugins: langpacks, refresh-packagekit, versionlock Transaction ID : 8 Begin time : Thu Nov 21 18:28:24 2013 Begin rpmdb: 1184:c12933940909ba00699a2269f2a08082654d7bdc End time :18:30:41 2013 (137 seconds) End rpmdb : 1186:39b969c3d77367584456e993c37378e6e578a638 User : root root Return-Code: Success Command Line : update Transaction performed with: Installed rpm-4.11.1-3.fc19.x86_64 @updates Installed yum-3.4.3-111.fc19.noarch@updates Installed yum-plugin-versionlock-1.1.31-18.fc19.noarch @updates Packages Altered: Updatedacl-2.2.51-9.fc19.x86_64 @fedora Update 2.2.51-10.fc19.x86_64 @updates Updateddbus-1:1.6.12-1.fc19.x86_64 @updates Update 1:1.6.12-2.fc19.x86_64 @updates Updateddbus-libs-1:1.6.12-1.fc19.x86_64 @updates Update 1:1.6.12-2.fc19.x86_64 @updates Updatedgnutls-3.1.15-1.fc19.x86_64 @updates Update3.1.16-1.fc19.x86_64 @updates Updatedgnutls-dane-3.1.15-1.fc19.x86_64 @updates Update 3.1.16-1.fc19.x86_64 @updates Updatedgnutls-utils-3.1.15-1.fc19.x86_64 @updates Update 3.1.16-1.fc19.x86_64 @updates Updatedgtk2-2.24.22-1.fc19.x86_64 @updates Update 2.24.22-2.fc19.x86_64 @updates Updatediw-3.8-2.fc19.x86_64 @fedora Update3.11-1.fc19.x86_64 @updates Installkernel-3.11.8-200.fc19.x86_64 @updates Installkernel-modules-extra-3.11.8-200.fc19.x86_64 @updates Updatedlibacl-2.2.51-9.fc19.x86_64 @fedora Update2.2.51-10.fc19.x86_64 @updates Updatedlibvirt-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-client-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-config-network-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-config-nwfilter-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-interface-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-libxl-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-lxc-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-network-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-nodedev-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-nwfilter-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-qemu-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-secret-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-storage-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-uml-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-xen-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-kvm-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-qemu-1.0.5.6-3.fc19.x86_64 @updates Update
Re: [Users] Migration problem - non-English characters
On 11/22/2013 03:04 PM, Mitja Mihelič wrote: Hi! One of our VMs had the letter č in its Name field. When we set the note to maintenance mode, the VM refused to migrate to another node. It had to be manually shut down and then restarted. Here are the events when we reproduced this with test VM. 2013-Nov-22, 10:29 Migration completed (VM: letter_c_test, Source: onode1.example.com, Destination: onode2.example.com, Duration: 9 sec). 2013-Nov-22, 10:29 Migration started (VM: letter_c_test, Source: onode1.example.com, Destination: onode2.example.com, User: admin@internal). 2013-Nov-22, 10:20 Migration completed (VM: letter_c_test, Source: onode3.example.com, Destination: onode1.example.com, Duration: 12 sec). 2013-Nov-22, 10:19 Migration started (VM: letter_c_test, Source: onode3.example.com, Destination: onode1.example.com, User: admin@internal). 2013-Nov-22, 10:19 VM letter_c_test started on Host onode3.example.com 2013-Nov-22, 10:19 VM letter_c_test was started by admin@internal (Host: onode3.example.com). 2013-Nov-22, 10:19 VM letter_c_test is down. Exit message: User shut down 2013-Nov-22, 10:18 VM shutdown initiated by admin@internal on VM letter_c_test (Host: onode1.example.com). 2013-Nov-22, 10:17 Migration failed due to Error: Unexpected exception (VM: letter_c_test, Source: onode1.example.com, Destination: onode3.example.com). 2013-Nov-22, 10:17 Migration started (VM: letter_c_test, Source: onode1.example.com, Destination: onode3.example.com, User: admin@internal). 2013-Nov-22, 10:17 Interface nic1 (VirtIO) was updated for VM letter_c_test. (User: admin@internal) 2013-Nov-22, 10:17 VM letter_č_test configuration was updated by admin@internal. 2013-Nov-22, 10:17 VM letter_č_test was renamed from letter_č_test to letter_c_test. 2013-Nov-22, 10:16 Migration failed due to Error: Unexpected exception (VM: letter_č_test, Source: onode1.example.com, Destination: onode3.example.com). 2013-Nov-22, 10:16 Migration started (VM: letter_č_test, Source: onode1.example.com, Destination: onode3.example.com, User: admin@internal). 2013-Nov-22, 10:15 VM letter_č_test started on Host onode1.example.com 2013-Nov-22, 10:15 VM letter_č_test was started by USERNAME (Host: onode1.example.com). 2013-Nov-22, 10:14 VM letter_č_test creation has been completed. 2013-Nov-22, 10:13 VM letter_č_test creation was initiated by USERNAME. After the VM was renamed (č was replaced with c), stopped and then started it migrated normally. Regards, Mitja sounds like this http://gerrit.ovirt.org/#/c/21521/ in queue, hopefylly will make 3.3.2 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Guest Agent
I think I may have stumbled on a bug. On a RHEL6 guest I got MainThread::ERROR::2013-11-21 17:18:17,290::ovirt-guest-agent::117::root::Unhandled exception in oVirt guest agent! Traceback (most recent call last): File /usr/share/ovirt-guest-agent/ovirt-guest-agent.py, line 111, in module agent.run(daemon, pidfile) File /usr/share/ovirt-guest-agent/ovirt-guest-agent.py, line 42, in run self.agent = LinuxVdsAgent(config) File /usr/share/ovirt-guest-agent/GuestAgentLinux2.py, line 324, in __init__ AgentLogicBase.__init__(self, config) File /usr/share/ovirt-guest-agent/OVirtAgentLogic.py, line 90, in __init__ self.vio = VirtIoChannel(config.get(virtio, device)) File /usr/share/ovirt-guest-agent/VirtIoChannel.py, line 125, in __init__ self._vport = os.open(vport_name, os.O_RDWR) OSError: [Errno 2] No such file or directory: '/dev/virtio-ports/com.redhat.rhevm.vdsm' Sure enough, there is only org.qemu.guest_agent.0 in there. Halted the VM and started it again and then it was all shiny with com.redhat.rhevm.vdsm com.redhat.spice.0 org.qemu.guest_agent.0 Not the end of the world, but though I should mention it. - Thomas ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] info on virtio-scsi
On 11/22/2013 05:54 PM, Gianluca Cecchi wrote: Hello, I had a CentOS 6.4 VM created in oVirt 3.3.0 Then I updated to 3.3.1 I created a CentOS 5.10 VM In CentOS 5.10 I built rhev-agent-2.3.16-3.el5.src.rpm In CentOS 6.4 I have ovirt-guest-agent-1.0.8-1.el6.noarch Both are configured with one virtio disk. In CentOS 5 I can add a disk and select virtio-scsi... but I can't use it because of no support in 5.x kernels. In CentOS 6.4 I'm not presented with the option virtio-scsi. What can I do to get it? did you do a clean install of the guest OS to a virtio-scsi disk? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] info on virtio-scsi
Il 22/nov/2013 21:00 Itamar ha scritto Both are configured with one virtio disk. In CentOS 5 I can add a disk and select virtio-scsi... but I can't use it because of no support in 5.x kernels. In CentOS 6.4 I'm not presented with the option virtio-scsi. What can I do to get it? did you do a clean install of the guest OS to a virtio-scsi disk? As I wrote above, both installed with only one disk as virtio. C5 right after update to 3.3.1 C6 before. Both powered on. In c5 I have chance to add virtio-scsi in drop down menu (even if then I cannot use it due to missing driver it seems); in c6 I only have ide and virtio... ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] info on virtio-scsi
On 11/22/2013 10:14 PM, Gianluca Cecchi wrote: Il 22/nov/2013 21:00 Itamar ha scritto Both are configured with one virtio disk. In CentOS 5 I can add a disk and select virtio-scsi... but I can't use it because of no support in 5.x kernels. In CentOS 6.4 I'm not presented with the option virtio-scsi. What can I do to get it? did you do a clean install of the guest OS to a virtio-scsi disk? As I wrote above, both installed with only one disk as virtio. C5 right after update to 3.3.1 C6 before. Both powered on. In c5 I have chance to add virtio-scsi in drop down menu (even if then I cannot use it due to missing driver it seems); in c6 I only have ide and virtio... oh, that's strange. derez/roy - no virtio-iscsi definition for .el6 VM? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Migration problem - non-English characters
On 22 Nov 2013, at 20:59, Itamar Heim ih...@redhat.com wrote: On 11/22/2013 03:04 PM, Mitja Mihelič wrote: Hi! One of our VMs had the letter č in its Name field. When we set the note to maintenance mode, the VM refused to migrate to another node. It had to be manually shut down and then restarted. Here are the events when we reproduced this with test VM. 2013-Nov-22, 10:29 Migration completed (VM: letter_c_test, Source: onode1.example.com, Destination: onode2.example.com, Duration: 9 sec). 2013-Nov-22, 10:29 Migration started (VM: letter_c_test, Source: onode1.example.com, Destination: onode2.example.com, User: admin@internal). 2013-Nov-22, 10:20 Migration completed (VM: letter_c_test, Source: onode3.example.com, Destination: onode1.example.com, Duration: 12 sec). 2013-Nov-22, 10:19 Migration started (VM: letter_c_test, Source: onode3.example.com, Destination: onode1.example.com, User: admin@internal). 2013-Nov-22, 10:19 VM letter_c_test started on Host onode3.example.com 2013-Nov-22, 10:19 VM letter_c_test was started by admin@internal (Host: onode3.example.com). 2013-Nov-22, 10:19 VM letter_c_test is down. Exit message: User shut down 2013-Nov-22, 10:18 VM shutdown initiated by admin@internal on VM letter_c_test (Host: onode1.example.com). 2013-Nov-22, 10:17 Migration failed due to Error: Unexpected exception (VM: letter_c_test, Source: onode1.example.com, Destination: onode3.example.com). 2013-Nov-22, 10:17 Migration started (VM: letter_c_test, Source: onode1.example.com, Destination: onode3.example.com, User: admin@internal). 2013-Nov-22, 10:17 Interface nic1 (VirtIO) was updated for VM letter_c_test. (User: admin@internal) 2013-Nov-22, 10:17 VM letter_č_test configuration was updated by admin@internal. 2013-Nov-22, 10:17 VM letter_č_test was renamed from letter_č_test to letter_c_test. 2013-Nov-22, 10:16 Migration failed due to Error: Unexpected exception (VM: letter_č_test, Source: onode1.example.com, Destination: onode3.example.com). 2013-Nov-22, 10:16 Migration started (VM: letter_č_test, Source: onode1.example.com, Destination: onode3.example.com, User: admin@internal). 2013-Nov-22, 10:15 VM letter_č_test started on Host onode1.example.com 2013-Nov-22, 10:15 VM letter_č_test was started by USERNAME (Host: onode1.example.com). 2013-Nov-22, 10:14 VM letter_č_test creation has been completed. 2013-Nov-22, 10:13 VM letter_č_test creation was initiated by USERNAME. After the VM was renamed (č was replaced with c), stopped and then started it migrated normally. Regards, Mitja sounds like this http://gerrit.ovirt.org/#/c/21521/ in queue, hopefylly will make 3.3.2 Indeed. Patch was accepted today to master, backport to 3.3.2 posted, should get in really soon Thanks, michal ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On Fri, Nov 22, 2013 at 12:36:41PM -0500, Bob Doolittle wrote: On 11/22/2013 11:45 AM, Dan Kenigsberg wrote: On Fri, Nov 22, 2013 at 05:51:48PM +0200, Itamar Heim wrote: doesn't vdsm require vdsm-gluster which requires them? vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence if gluster server side functionality is being exercised, we would need to use EPEL packages. For a virt only cluster, only the client side packages are needed and RHEL 6.5 has these packages. vijay - didn't we add gluster-cli for libgfapi support in core vdsm? glusterVolume uses the cli to only to tell if it's using tcp or rdma. This vdsm dependency is currently a soft one (not declared in the spec), and would only affect users which attempt to user true glusterfs storage domains without installing gluster-cli. This is not what I see. I see that vdsm.x86_64 has a dependency on glusterfs-cli: # rpm -qa --whatrequires glusterfs-cli vdsm-4.12.1-4.el6.x86_64 You are correct. My statement about vdsm's dependency is valid only for the not-yet-released rhev-3.3.0 (and thus, is not really apropriate for this venue). Hence the problem, since the new version of glusterfs does not deliver this package. I still think that your problem stems from mixing and matching epel-gluster repositories with rhs ones. It would be easier to deploy oVirt+epel-gluster and rhev+rhs. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] info on virtio-scsi
On Fri, Nov 22, 2013 at 10:49 PM, Itamar Heim wrote: oh, that's strange. derez/roy - no virtio-iscsi definition for .el6 VM? Actually I don't think so. I have tried creating a new rh el 6.x x86_64 vm and at disk creation I do see virtio-scsi as an option. But for this preexisting VM I don't see it when I try to add. Tried both in powered on state and in powered off. See here difference between c6 and c5 dynamic xml in /var/run/libvirt/qemu https://drive.google.com/file/d/0BwoPbcrMv8mvemtSalRkTTZlV1k/edit?usp=sharing And here for qemu command line generated: https://drive.google.com/file/d/0BwoPbcrMv8mvOHZrTHduN1ZCUFU/edit?usp=sharing Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] info on virtio-scsi
On Fri, Nov 22, 2013 at 11:51 PM, Gianluca Cecchi wrote: On Fri, Nov 22, 2013 at 10:49 PM, Itamar Heim wrote: oh, that's strange. derez/roy - no virtio-iscsi definition for .el6 VM? Actually I don't think so. I have tried creating a new rh el 6.x x86_64 vm and at disk creation I do see virtio-scsi as an option. But for this preexisting VM I don't see it when I try to add. Tried both in powered on state and in powered off. See here difference between c6 and c5 dynamic xml in /var/run/libvirt/qemu https://drive.google.com/file/d/0BwoPbcrMv8mvemtSalRkTTZlV1k/edit?usp=sharing And here for qemu command line generated: https://drive.google.com/file/d/0BwoPbcrMv8mvOHZrTHduN1ZCUFU/edit?usp=sharing Gianluca I found it! By default now when I create a VM, I can see that in advanced parameters -- Resource Allocation I have virtio-scsi enabled. Instead for pre-existing VM it wasn't. I tested editing the VM while powered on and then I was able to add and activate a virtio-scsi disk. In guests's messages: Nov 22 22:15:51 c6s kernel: pci :00:07.0: BAR 2: assigned [mem 0x8000-0x80001fff] Nov 22 22:15:51 c6s kernel: pci :00:07.0: BAR 2: set to [mem 0x8000-0x80001fff] (PCI address [0x8000-0x80001fff] Nov 22 22:15:51 c6s kernel: pci :00:07.0: BAR 1: assigned [mem 0x80002000-0x800023ff] Nov 22 22:15:51 c6s kernel: pci :00:07.0: BAR 1: set to [mem 0x80002000-0x800023ff] (PCI address [0x80002000-0x800023ff] Nov 22 22:15:51 c6s kernel: pci :00:07.0: BAR 0: assigned [io 0x1000-0x10ff] Nov 22 22:15:51 c6s kernel: pci :00:07.0: BAR 0: set to [io 0x1000-0x10ff] (PCI address [0x1000-0x10ff] Nov 22 22:15:51 c6s kernel: pci :00:00.0: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: pci :00:00.0: using default PCI settings Nov 22 22:15:51 c6s kernel: pci :00:01.0: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: pci :00:01.0: using default PCI settings Nov 22 22:15:51 c6s kernel: ata_piix :00:01.1: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: ata_piix :00:01.1: using default PCI settings Nov 22 22:15:51 c6s kernel: uhci_hcd :00:01.2: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: uhci_hcd :00:01.2: using default PCI settings Nov 22 22:15:51 c6s kernel: piix4_smbus :00:01.3: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: piix4_smbus :00:01.3: using default PCI settings Nov 22 22:15:51 c6s kernel: pci :00:02.0: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: pci :00:02.0: using default PCI settings Nov 22 22:15:51 c6s kernel: virtio-pci :00:03.0: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: virtio-pci :00:03.0: using default PCI settings Nov 22 22:15:51 c6s kernel: virtio-pci :00:04.0: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: virtio-pci :00:04.0: using default PCI settings Nov 22 22:15:51 c6s kernel: virtio-pci :00:05.0: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: virtio-pci :00:05.0: using default PCI settings Nov 22 22:15:51 c6s kernel: virtio-pci :00:06.0: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: virtio-pci :00:06.0: using default PCI settings Nov 22 22:15:51 c6s kernel: pci :00:07.0: no hotplug settings from platform Nov 22 22:15:51 c6s kernel: pci :00:07.0: using default PCI settings Nov 22 22:15:51 c6s kernel: sym53c8xx :00:07.0: enabling device ( - 0003) Nov 22 22:15:51 c6s kernel: sym53c8xx :00:07.0: PCI INT A - Link[LNKC] - GSI 10 (level, high) - IRQ 10 Nov 22 22:15:51 c6s kernel: sym0: 895a rev 0x0 at pci :00:07.0 irq 10 Nov 22 22:15:51 c6s kernel: sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking Nov 22 22:15:51 c6s kernel: sym0: SCSI BUS has been reset. Nov 22 22:15:51 c6s kernel: scsi2 : sym-2.2.3 Nov 22 22:15:54 c6s kernel: sym0: unknown interrupt(s) ignored, ISTAT=0x5 DSTAT=0x80 SIST=0x0 Nov 22 22:15:54 c6s kernel: scsi 2:0:0:0: Direct-Access QEMU QEMU HARDDISK1.0 PQ: 0 ANSI: 5 Nov 22 22:15:54 c6s kernel: scsi target2:0:0: tagged command queuing enabled, command queue depth 16. Nov 22 22:15:54 c6s kernel: scsi target2:0:0: Beginning Domain Validation Nov 22 22:15:54 c6s kernel: scsi target2:0:0: Domain Validation skipping write tests Nov 22 22:15:54 c6s kernel: scsi target2:0:0: Ending Domain Validation Nov 22 22:15:54 c6s kernel: scsi 2:0:0:0: Attached scsi generic sg1 type 0 Nov 22 22:15:54 c6s kernel: sd 2:0:0:0: [sda] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB) Nov 22 22:15:54 c6s kernel: sd 2:0:0:0: [sda] Write Protect is off Nov 22 22:15:54 c6s kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 22 22:15:54 c6s kernel: sda: unknown partition table Nov 22 22:15:54 c6s kernel: sd 2:0:0:0: [sda] Attached SCSI disk I was also able to extend online the disk, and if I create a PV on the whole disk I'm also able to online resize PV, LV
Re: [Users] info on virtio-scsi
For pre-existing VMs you have to enable it in the VM-Edit dialog first. Edit VM - Show Adv. Options - Resource Alloc. - Virtio-SCSI Enabled After that step you can change your disk from IDE/Virtio to Virtio-SCSI -Original message- From:Gianluca Cecchi gianluca.cec...@gmail.com Sent: Friday 22nd November 2013 23:55 To: Itamar Heim ih...@redhat.com Cc: users users@ovirt.org Subject: Re: [Users] info on virtio-scsi On Fri, Nov 22, 2013 at 10:49 PM, Itamar Heim wrote: oh, that's strange. derez/roy - no virtio-iscsi definition for .el6 VM? Actually I don't think so. I have tried creating a new rh el 6.x x86_64 vm and at disk creation I do see virtio-scsi as an option. But for this preexisting VM I don't see it when I try to add. Tried both in powered on state and in powered off. See here difference between c6 and c5 dynamic xml in /var/run/libvirt/qemu https://drive.google.com/file/d/0BwoPbcrMv8mvemtSalRkTTZlV1k/edit?usp=sharing And here for qemu command line generated: https://drive.google.com/file/d/0BwoPbcrMv8mvOHZrTHduN1ZCUFU/edit?usp=sharing Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] hacking at the ovirt db howto?
- Original Message - From: Jason Brooks jbro...@redhat.com To: users@ovirt.org Sent: Wednesday, October 16, 2013 9:02:35 PM Subject: hacking at the ovirt db howto? Hi All -- I'm finding myself sometimes in need of hacking at the oVirt DB -- has anyone written a wiki page or something about this? For posterity, what I was missing was: su - postgres psql engine And then hack away. I've had to do a bunch of manual unlocking to allow me to remove VMs following failed snapshot operations. Thanks, Jason --- Jason Brooks Red Hat Open Source and Standards @jasonbrooks | @redhatopen http://community.redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] unsupported configuration: spice secure channels set in XML configuration, but TLS port is not provided.
On Nov 18, 2013, at 2:05 AM, Omer Frenkel ofren...@redhat.com wrote: you set non-secure configuration on vdsm side, you need to set the secure spice configuration to false in the engine as well, you can do this with engine-config: engine-config -s SSLEnabled=false and restart the engine. This resolved my problem…Thank you! ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
