Re: [Users] Fedora 20 support, Was: oVirt Weekly Meeting Minutes -- 2013-11-27
I updated the environment to support f20, including new slave and nighlites. i will send a separate email on it soon to infra/users/devel. Eyal. - Original Message - From: Doron Fediuck dfedi...@redhat.com To: Dan Kenigsberg dan...@redhat.com, David Caro Estevez dcaro...@redhat.com Cc: bo...@ovirt.org, users users@ovirt.org, ee...@redhat.com, Sandro Bonazzola sbona...@redhat.com Sent: Thursday, November 28, 2013 1:55:13 PM Subject: Re: Fedora 20 support, Was: [Users] oVirt Weekly Meeting Minutes -- 2013-11-27 - Original Message - From: Dan Kenigsberg dan...@redhat.com To: bo...@ovirt.org, users users@ovirt.org Cc: Doron Fediuck dfedi...@redhat.com, ee...@redhat.com Sent: Thursday, November 28, 2013 12:19:05 PM Subject: Fedora 20 support, Was: [Users] oVirt Weekly Meeting Minutes -- 2013-11-27 We've forgotten to discuss an important issue: Fedora 20, which is expected to be out in two weeks: http://fedoraproject.org/wiki/Releases/20/Schedule. I believe that ovirt-3.4 must support it, and that ovirt-3.3.2 would better do so. Toni has fixed two issues regarding Vdsm-networking, and they are going into ovirt-3.3.2 beta. However, we must perform much more comprehensive testing. We'd need to have f20 Jenkins slave(s), and someone in each team responsible to testing functionality. Who can cover for storage, virt, infra and integration? Dan. Indeed so, thanks Dan. David, is this something we have resources for? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] [ANN] new fedora20 nightlies rpms for oVirt are available for download
fyi, oVirt infra has added support for nighlies rpms for various oVirt projects for fedora 20. the following has be done: - All ovirt projects were added f20 nightlies on jenkins.ovirt.org. (replaced f18, which is NOT built nightly anymore). - One jenkins f19 slave (vm02) was upgraded to f20, and we also have a bare metal host running f20 as well. - Nightlies rpms can be downloaded on the repos [1] - Nightlies publish cleanup scripts were updated on the resources.ovirt.org to support f20. I didn't update any ovirt-node* job, since i'm not familiar with them. if you would like to build f20 builds, just add the 'fedora20' label to the relevant jobs. Eyal. [1] http://resources.ovirt.org/releases/nightly/rpm/Fedora/20/ ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] VM Migration
I installed ovirt on a machine that was already hosting KVM virtual machines. I am now trying to migrate those VMs over to RHEV format, but I am receiving SASL authentication errors using virt-v2v. I am not being prompted for credentials upon running the command: virt-v2v Windows7.xml -o rhev -os host.domain.net:/home/images --network ovirtmgmt Windows7 The error is: virt-v2v: Failed to connect to qemu:///system: libvirt error code: 45, message: authentication failed: Failed to step SASL negotiation: -7 (SASL(-7): invalid parameter supplied: Unexpectedly missing a prompt result) This has been driving me crazy all night. Does anyone know anything about this? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] backups
On 11/27/2013 10:52 AM, Sander Grendelman wrote: The main problem in oVirt with this strategy would be the lack of live snapshot deletion. Having to shut down the VM to delete/merge a snapshot is not nice :( Ouch?! Is there an ETA as to when you'll be able to delete a live snapshot ? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] backups
On 11/27/2013 11:27 AM, Juan Pablo Lorier wrote: Hi, Just curious, is it really the porpoise of the snapshot to backup both the vm and the application data? I think snapshot is appropriate to backup the vm and the you should have your regular backup for the app, as a database backup that can be done online. In this scenario you take a backup of the vm when something changes (updates, new software, configs, etc) and not all the time and do regular backups of the db as it's the information that changes all the time. I said this because I'm curious about the benefits of doing backups the way it's been posted. Regards, Contrary to my other post, which was more educational than practical, yes, you generally would not back up app data via a hypervisor snapshot. Generally you would only backup the OS disk and perhaps the application binaries. This would be for quick restore of the OS and app, so you don't have to spend hours reconfiguring your OS. (especially Windows based OSes) I also do an IN OS backup as well, for individual file restores in the instances you accidentally destroy something in /etc for example. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] What agents are needed?
There doesn't seem to be a single tools or agent install like there is under ESXi, that's required to be installed under ovirt, instead I've seen references to 1) virtio drivers 2) Spice drivers 3) qemu agent What's really needed under both Windows and Linux to get guests working properly? Are all these agents included in Fedora? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] VM Migration
On Sat, Nov 30, 2013 at 7:08 PM, Maurice James wrote: I installed ovirt on a machine that was already hosting KVM virtual machines. I am now trying to migrate those VMs over to RHEV format, but I am receiving SASL authentication errors using virt-v2v. I am not being prompted for credentials upon running the command: virt-v2v Windows7.xml -o rhev -os host.domain.net:/home/images --network ovirtmgmt Windows7 The error is: virt-v2v: Failed to connect to qemu:///system: libvirt error code: 45, message: authentication failed: Failed to step SASL negotiation: -7 (SASL(-7): invalid parameter supplied: Unexpectedly missing a prompt result) This has been driving me crazy all night. Does anyone know anything about this? Hi, I made some tests as I could need something similar in the near future... This is what I found from my tests You need authentication for libvirt after oVirt configuration took place on your server. So you can create a user for libvirt and try then the commands with that user credentials. It worked for me in the past to try to start a VM directly from libvirt on an all-in-one system to debug problems. So: # saslpasswd2 -a libvirt virshuser Password: define a password probably the disks of your pre-existing vm should be put with these permissions chown vdsm.kvm /var/lib/libvirt/images/testvm.img chmod 0660 /var/lib/libvirt/images/testvm.img try to see eventually if you can start your vm now: # virsh start testvm I have an AIO install with fedora 19 and oVirt 3.3.1 stable Actually I have not a kvm infra but I created one fake in the sense that I created a storage pool and a disk inside it [root@tekkaman ~]# cat pool.xml pool type=dir namevirtimages/name target path/var/lib/libvirt/images/path /target /pool virsh pool-create pool.xml I copied an image (fedora19) inside it and refreshed the pool virsh pool-refresh virtimages virsh vol-list --pool virtimages [root@tekkaman ~]# virsh vol-list --pool virtimages Please enter your authentication name: virshuser Please enter your password: Name Path - testvm.img /var/lib/libvirt/images/testvm.img I define a basic VM with test.img as a disk virsh define test.xml [root@tekkaman ~]# virsh list --all Please enter your authentication name: virshuser Please enter your password: IdName State 2 f19running - test shut off NOTE: the f19 above is a fedora 19 vm running inside oVirt itself, while test is the VM just created with virsh commands Now, even if I don't now if it is still required in f19 export LIBGUESTFS_ATTACH_METHOD=appliance and also if you want to debug virt-v2v (used to debug, see below my workaround due to a permission error otherwise...) export LIBGUESTFS_DEBUG=1 Now you can run virt-v2v -ic qemu://virshuser@tekkaman.localdomain.local/system -o rhev -os tekkaman.localdomain.local:/data/export_domain --network ovirtmgmt test tekkaman.localdomain.local is my server from which I run the comamnds that is both oVirt AIO (so engine+hypervisor) and now is also source for the KVM vm I want to put into oVirt export domain NOTE: the command will not ask a password.. donna if it is a bug or not... During virt-v2v, the export domain is mounted locally under /tmp/random_path (eg. /tmp/f6X_Ea809r/) For some reason the permissions are not ok for virt-v2v and give an error of permission denied attempting to open the disk. You cannot directly change the permissions under /tmp, you have to do on the local path of the export domain. In my case it is on the very same server under /data/export_domain path SO I did these tricks below to the temporarily created dir to have virt-v2v able to complete. And now I see the imported VM under export domain 'VM import sub-tab in webadmin page [root@tekkaman ~]# ll /data/export_domain/44327985-44c5-4e17-9396-1469b191fafc/ total 32 drwxr-xr-x. 2 vdsm kvm 4096 May 1 2013 dom_md drwxr-xr-x. 4 vdsm kvm 4096 May 1 2013 images drwxr-xr-x. 4 vdsm kvm 4096 May 1 2013 master drwx--. 3 vdsm kvm 4096 Dec 1 00:33 v2v.ISfFuM4P root@tekkaman ~]# chmod 770 /data/export_domain/44327985-44c5-4e17-9396-1469b191fafc/v2v.ISfFuM4P/ [root@tekkaman ~]# ll /data/export_domain/44327985-44c5-4e17-9396-1469b191fafc/v2v.ISfFuM4P/ total 8 drwxr-xr-x. 2 vdsm kvm 4096 Dec 1 00:33 a7a38c80-2862-46a3-833a-93394d916c5d [root@tekkaman ~]# chmod 775 /data/export_domain/44327985-44c5-4e17-9396-1469b191fafc/v2v.ISfFuM4P/a7a38c80-2862-46a3-833a-93394d916c5d/ [root@tekkaman ~]# ll /data/export_domain/44327985-44c5-4e17-9396-1469b191fafc/v2v.ISfFuM4P/a7a38c80-2862-46a3-833a-93394d916c5d/ total 1912208 -rw-r--r--. 1 vdsm kvm 8589934592 Dec 1 00:33 2ada28ad-e98c-4ff8-afb2-280dcb72c1c4 [root@tekkaman ~]# chmod 664
[Users] Keepalived on oVirt Hosts has engine networking issues
Hi, I have the scenario where I have gluster and ovirt hosts on the same box, to keep the gluster volumes highly available incase a box drops I'm using keepalived across the boxes and using that IP as the means for the storage domain. I documented my setup here in case anyone needs a little more info http://www.andrewklau.com/returning-to-glusterized-ovirt-3-3/ However, the engine seems to be picking up the floating IP assigned to keepalived as the interface and messing with the ovirtmgmt migration network, so migrations are failing as my floating IP gets assigned to the ovirtmgmt bridge in the engine however it's not actually there on most hosts (except one) so vdsm seems to report destination same as source. I've since created a new vlan interface just for storage to avoid the ovirtmgmt conflict, but the engine will still pick up the wrong IP on the storage vlan because of keepalived. This means I can't use the save network feature within the engine as it'll save the floating ip rather than the one already there. Is this a bug or just the way it's designed. eth0.2 - ovirtmgmt (172.16.0.11) - management and migration network - engine sees, sets and saves 172.16.0.11 eth0.3 - storagenetwork (172.16.1.11) - gluster network - engine sees, sets and saves 172.16.1.5 (my floating IP) I hope this makes sense. p.s. can anyone also confirm, does gluster support multi pathing by default? If I'm using this keepalived method, am I bottle necking myself to one host? Thanks, Andrew ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-setup error
Finally got the downgrades cleaned up and see this in the error log for engine-upgrade: YumBaseError: [u'otopi-java-1.1.0-0.0.master.el6.noarch requires otopi = 1.1.0-0.0.master.el6’] Thoughts? Already have this installed: Package matching otopi-1.1.0-0.0.master.el6.noarch already installed. Checking for update. On 11/26/13, 2:33 AM, Sandro Bonazzola sbona...@redhat.com wrote: Il 25/11/2013 16:53, Karl Mozurkewich ha scritto: I¹m on Cent 6.4 and used the AIO rpm install. How do I upgrade to 3.2 then to 3.3? (engine-udgrade? Etc.) For upgrading to 3.2 you'll need 3.2 stable repository. So, first step is disable 3.3 / stable repository and enable 3.2: [ovirt-32] name=Stable builds of the oVirt 3.2 project baseurl=http://ovirt.org/releases/3.2/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 Then yum update ovirt-engine-setup it should install ovirt-engine-setup-3.2.3-1.el6.noarch.rpm if you have already updated to 3.3.x please use distro-sync or downgrade instead of update. Then run engine-upgrade. This will upgrade your system to latest 3.2. Once you've all working on 3.2, enable 3.3/stable repository, then just yum update ovirt-engine-setup followed by engine-setup will upgrade to latest 3.3. Thanks. On 11/25/13, 4:25 AM, Sandro Bonazzola sbona...@redhat.com wrote: Il 25/11/2013 03:30, Karl Mozurkewich ha scritto: Hi, Trying to upgrade from 3.1 to 3.3 and am running engine-setup, but it¹s bombing at the following: Hi, just to be sure, are you on Fedora and just running yum upgrade from the 3.1 version provided by Fedora? Because if you're not just updating rpms, the direct upgrade process from 3.1 to 3.3 through engine-setup is not supported. In this case you should upgrade to 3.2 before upgrading to 3.3. [ INFO ] Stage: Setup validation During execution engine service will be stopped (OK, Cancel) [OK]: [ ERROR ] Failed to execute stage 'Setup validation': Cannot get JAVA_HOME ([]) [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20131124212809.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of upgrade failed Should be a simple fix, but where does it get JAVA_HOME from? Setting it in the running shell doesn¹t work. (export JAVA_HOME, etc.) Also wondering why it can¹t find it if the engine is currently workingŠ Thanks. -K ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-setup error
Got the octopi error fixed by downgrading until I found a version that the 3.2 yum pkgs played nice with. Trying to get past a new problem with the version of jboss: **Error: Upgrade failed, rolling back** **Reason: Test Transaction Errors: file /usr/share/jboss-as-7.1.1.Final/bin/init.d/jboss-as.conf from install of jboss-as-7.1.1-11.el6.x86_64 conflicts with file from package ovirt-engine-jbossas711-1-3.el6.alt.x86_64 ** Will work on the conflict but any help is appreciated. On 11/30/13, 11:17 PM, Karl Mozurkewich k...@utropicmedia.com wrote: Finally got the downgrades cleaned up and see this in the error log for engine-upgrade: YumBaseError: [u'otopi-java-1.1.0-0.0.master.el6.noarch requires otopi = 1.1.0-0.0.master.el6’] Thoughts? Already have this installed: Package matching otopi-1.1.0-0.0.master.el6.noarch already installed. Checking for update. On 11/26/13, 2:33 AM, Sandro Bonazzola sbona...@redhat.com wrote: Il 25/11/2013 16:53, Karl Mozurkewich ha scritto: I¹m on Cent 6.4 and used the AIO rpm install. How do I upgrade to 3.2 then to 3.3? (engine-udgrade? Etc.) For upgrading to 3.2 you'll need 3.2 stable repository. So, first step is disable 3.3 / stable repository and enable 3.2: [ovirt-32] name=Stable builds of the oVirt 3.2 project baseurl=http://ovirt.org/releases/3.2/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 Then yum update ovirt-engine-setup it should install ovirt-engine-setup-3.2.3-1.el6.noarch.rpm if you have already updated to 3.3.x please use distro-sync or downgrade instead of update. Then run engine-upgrade. This will upgrade your system to latest 3.2. Once you've all working on 3.2, enable 3.3/stable repository, then just yum update ovirt-engine-setup followed by engine-setup will upgrade to latest 3.3. Thanks. On 11/25/13, 4:25 AM, Sandro Bonazzola sbona...@redhat.com wrote: Il 25/11/2013 03:30, Karl Mozurkewich ha scritto: Hi, Trying to upgrade from 3.1 to 3.3 and am running engine-setup, but it¹s bombing at the following: Hi, just to be sure, are you on Fedora and just running yum upgrade from the 3.1 version provided by Fedora? Because if you're not just updating rpms, the direct upgrade process from 3.1 to 3.3 through engine-setup is not supported. In this case you should upgrade to 3.2 before upgrading to 3.3. [ INFO ] Stage: Setup validation During execution engine service will be stopped (OK, Cancel) [OK]: [ ERROR ] Failed to execute stage 'Setup validation': Cannot get JAVA_HOME ([]) [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20131124212809.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of upgrade failed Should be a simple fix, but where does it get JAVA_HOME from? Setting it in the running shell doesn¹t work. (export JAVA_HOME, etc.) Also wondering why it can¹t find it if the engine is currently workingŠ Thanks. -K ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ 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] ovirtmgmt not installed
- Original Message - Hi there Hi Pascal, I installed a console on F19, then a F19 host (time 11:09 today). Everything works fine, apart from the installation of the mgmt network at the end. Can someone tell me what's going wrong ? Can you please send the output of vdsCaps from the host (vdsClient -s 0 getVdsCaps)? Thxs in advance Pascal ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-setup error
- Original Message - From: Karl Mozurkewich k...@utropicmedia.com To: users@ovirt.org Sent: Sunday, December 1, 2013 6:42:09 AM Subject: Re: [Users] engine-setup error Got the octopi error fixed by downgrading until I found a version that the 3.2 yum pkgs played nice with. Trying to get past a new problem with the version of jboss: You can use the otopi from 3.3 as it is backward compatible, not sure what actually been done, but not that important. **Error: Upgrade failed, rolling back** **Reason: Test Transaction Errors: file /usr/share/jboss-as-7.1.1.Final/bin/init.d/jboss-as.conf from install of jboss-as-7.1.1-11.el6.x86_64 conflicts with file from package ovirt-engine-jbossas711-1-3.el6.alt.x86_64 ** I think that just removing ovirt-engine-jbossas711 before upgrade will enable installation of the official jboss during upgrade. Will work on the conflict but any help is appreciated. On 11/30/13, 11:17 PM, Karl Mozurkewich k...@utropicmedia.com wrote: Finally got the downgrades cleaned up and see this in the error log for engine-upgrade: YumBaseError: [u'otopi-java-1.1.0-0.0.master.el6.noarch requires otopi = 1.1.0-0.0.master.el6’] Thoughts? Already have this installed: Package matching otopi-1.1.0-0.0.master.el6.noarch already installed. Checking for update. On 11/26/13, 2:33 AM, Sandro Bonazzola sbona...@redhat.com wrote: Il 25/11/2013 16:53, Karl Mozurkewich ha scritto: I¹m on Cent 6.4 and used the AIO rpm install. How do I upgrade to 3.2 then to 3.3? (engine-udgrade? Etc.) For upgrading to 3.2 you'll need 3.2 stable repository. So, first step is disable 3.3 / stable repository and enable 3.2: [ovirt-32] name=Stable builds of the oVirt 3.2 project baseurl=http://ovirt.org/releases/3.2/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 Then yum update ovirt-engine-setup it should install ovirt-engine-setup-3.2.3-1.el6.noarch.rpm if you have already updated to 3.3.x please use distro-sync or downgrade instead of update. Then run engine-upgrade. This will upgrade your system to latest 3.2. Once you've all working on 3.2, enable 3.3/stable repository, then just yum update ovirt-engine-setup followed by engine-setup will upgrade to latest 3.3. Thanks. On 11/25/13, 4:25 AM, Sandro Bonazzola sbona...@redhat.com wrote: Il 25/11/2013 03:30, Karl Mozurkewich ha scritto: Hi, Trying to upgrade from 3.1 to 3.3 and am running engine-setup, but it¹s bombing at the following: Hi, just to be sure, are you on Fedora and just running yum upgrade from the 3.1 version provided by Fedora? Because if you're not just updating rpms, the direct upgrade process from 3.1 to 3.3 through engine-setup is not supported. In this case you should upgrade to 3.2 before upgrading to 3.3. [ INFO ] Stage: Setup validation During execution engine service will be stopped (OK, Cancel) [OK]: [ ERROR ] Failed to execute stage 'Setup validation': Cannot get JAVA_HOME ([]) [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20131124212809.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of upgrade failed Should be a simple fix, but where does it get JAVA_HOME from? Setting it in the running shell doesn¹t work. (export JAVA_HOME, etc.) Also wondering why it can¹t find it if the engine is currently workingŠ Thanks. -K ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
