- Users - oVirt List Archives

[Users] Searching for VMs with snapshots
by noc 17 Jan '14

17 Jan '14

Hi All, I would like to see, in the webui, all VMs that have snapshots attached to them but I'm not able to construct a search that will work. For one thing there is no 'Snapshot' category so I think that it will be impossible. The use case is that I would like to have a way to see, in the webui, which VMs are running stateless, accidents happen :-( . Joop

2 1

[Users] [QE] oVirt 3.4.0 alpha / beta status
by Sandro Bonazzola 17 Jan '14

17 Jan '14

Hi, oVirt 3.4.0 alpha has been released and is actually on QA. An issue has been found in VDSM so we have updated the packages in alpha repositories for Fedora. We had an issue with nightly build for EL6 packages yesterday so EL6 repository is not yet updated. We'll try to sync it today, I'm sorry for the inconvenient. We'll start composing oVirt 3.4.0 beta on 2014-01-20 14:00 UTC from 3.4 branches. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Summary gluster 1038988 Gluster brick sync does not work when host has multiple interfaces integration 1054080 gracefully warn about unsupported upgrade from legacy releases network 1054195 [NetworkLabels] Attaching two labeled networks to a cluster result in failure of the latter There are still 280 bugs [2] targeted to 3.4.0. Excluding node and documentation bugs we still have 237 bugs [3] targeted to 3.4.0. Please review them as soon as possible. Maintainers: - Please remember to rebuild your packages before 2014-01-21 12:00 UTC if you want them to be included in 3.4.0 beta. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on blockers bugs - Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-01-23 For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug. Please also be prepared for upcoming oVirt 3.4.0 Test Day on 2014-01-23! Thanks to all people already testing 3.4.0 alpha! [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://red.ht/1auBU3r [4] http://www.ovirt.org/OVirt_3.4.0_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

[Users] Issues installing hosted-engine with 3.4.0 alpha
by Andrew Lau 17 Jan '14

17 Jan '14

Hi, I'm giving the new hosted-engine feature a try with the new 3.4.0 alpha build on centos 6.5 hosted-engine --deply seems to fail at the 'Environment setup" [ ERROR ] Failed to execute stage 'Environment setup': Command '/sbin/service' failed to execute Within the logs I believe it seems to be related to vdsm. Logs show "VDS daemon is not running" service vdsm start gives the following error: initctl: Job is already running: libvirtd vdsm: Running mkdirs vdsm: Running configure_coredump vdsm: Running run_init_hooks vdsm: Running gencerts vdsm: Running check_is_configured libvirt is already configured for vdsm sanlock service is already configured vdsm: Running validate_configuration SUCCESS: ssl configured to true. No conflicts vdsm: Running prepare_transient_repository vdsm: Running syslog_available vdsm: Running nwfilter vdsm: Running dummybr vdsm: Running load_needed_modules vdsm: Running tune_system vdsm: Running test_space vdsm: Running test_lo vdsm: Running restore_nets vdsm: Running unified_network_persistence_upgrade Usage: /usr/bin/vdsm-tool [options] <action> [arguments] Valid options: -h, --help Commands in module configurator: configure Configure external services for vdsm is-configured Determine if module is configured validate-config Determine if configuration is valid Commands in module dummybr: dummybr Defines dummy bridge on libvirt network. Commands in module load_needed_modules: load-needed-modules Load needed modules Commands in module nwfilter: nwfilter Defines network filters on libvirt Commands in module passwd: set-saslpasswd Set vdsm password for libvirt connection Commands in module restore_nets: restore-nets Restores the networks to what was previously persisted via vdsm. Commands in module seboolsetup: sebool-config Enable the required selinux booleans sebool-unconfig Disable the required selinux booleans Commands in module service: service-disable Disable a system service service-is-managed Check the existence of a service service-reload Notify a system service to reload configurations service-restart Restart a system service service-start Start a system service service-status Get status of a system service service-stop Stop a system service Commands in module transient: cleanup-transient-repository Cleanup the unused transient disks present in the repository. (NOTE: it is recommended to NOT execute this command when the vdsm daemon is running) setup-transient-repository Prepare the transient disks repository Commands in module unified_persistence: upgrade-unified-persistence Upgrade host networking persistence from ifcfg to unified if the persistence model is set as unified in /usr/lib64/python2.X/site-packages/ vdsm/config.py Commands in module upgrade: Commands in module upgrade_300_networks: upgrade-3.0.0-networks Since ovirt-3.0, Vdsm uses libvirt networks (with names vdsm-*) to store its own networks. Older Vdsms did not have those defined, and used only linux bridges. This command is kept as an upgrade tool for the (very few) people who still have such old setups running. Commands in module validate_ovirt_certs: validate-ovirt-certs Validate vdsmcert.pem against cacert.pem. If current cacert.pem is invalidate, it will find a validate certificate file and replace the old cacert.pem with it. And then persist it. Commands in module vdsm-id: vdsm-id Printing host uuid vdsm: failed to execute unified_network_persistence_upgrade, error code 1 vdsm start [FAILED] Any suggestions? Thanks, Andrew

2 6

Re: [Users] Gluster storage
by Gianluca Cecchi 17 Jan '14

17 Jan '14

On Fri, Nov 29, 2013 at 11:48 AM, Dan Kenigsberg wrote: > On Fri, Nov 29, 2013 at 04:04:03PM +0530, Vijay Bellur wrote: > >> >> There are two ways in which GlusterFS can be used as a storage domain: >> >> a) Use gluster native/fuse access with POSIXFS >> >> b) Use the gluster native storage domain to bypass fuse (with >> libgfapi). We are currently addressing an issue in libvirt >> (https://bugzilla.redhat.com/show_bug.cgi?id=1017289) to enable >> snapshot support with libgfapi. Once this is addressed, we will have >> libgfapi support in the native storage domain. > > It won't be as immediate, since there's a required fix on Vdsm's side > (Bug 1022961 - Running a VM from a gluster domain uses mount instead of > gluster URI) > >> Till then, fuse would >> be used with native storage domain. You can find more details about >> native storage domain here: >> >> http://www.ovirt.org/Features/GlusterFS_Storage_Domain rg/mailman/listinfo/users Hello, revamping here.... I'm using oVirt 3.3.3 beta1 after upgrade from 3.3.2 on fedora 19 ovirt beta repo It seems bug referred by Vijay (1017289) is still marked as "assigned", but actually it is for rhel 6. Bug referred by Dan (1022961) is marked as "blocked" but I don't see any particular updates since late november. But it is for rhevm, so I think it is for rhel 6... So what is the situation for fedora 19 and oVirt in upcoming 3.3.3? And upcoming fedora 19/20 and 3.4? I ask because I see that in my qemu command line generated by oVirt there is: for virtio (virtio-blk) disk -drive file=/rhev/data-center/mnt/glusterSD/node01.mydomain:gvdata/d0b96d4a-62aa-4e9f-b50e-f7a0cb5be291/images/a5e4f67b-50b5-4740-9990-39deb8812445/53408cb0-bcd4-40de-bc69-89d59b7b5bc2,if=none,id=drive-virtio-disk0,format=raw,serial=a5e4f67b-50b5-4740-9990-39deb8812445,cache=none,werror=stop,rerror=stop,aio=threads for virtio-scsi disk -drive file=/rhev/data-center/mnt/glusterSD/node01.mydomain:gvdata/d0b96d4a-62aa-4e9f-b50e-f7a0cb5be291/images/c1477133-6b06-480d-a233-1dae08daf8b3/c2a82c64-9dee-42bb-acf2-65b8081f2edf,if=none,id=drive-scsi0-0-0-0,format=raw,serial=c1477133-6b06-480d-a233-1dae08daf8b3,cache=none,werror=stop,rerror=stop,aio=threads So it is referred as mount point and not gluster:// way Also, the output of "mount" command on hypervisors shows: node01.mydomain:gvdata on /rhev/data-center/mnt/glusterSD/node01.mydomain:gvdata type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) and it seems indeed fuse mount, so not using libgfapi... output of "lsof -Pp pid" where pid is the qemu process shows libgfapi....: qemu-syst 2057 qemu mem REG 253,0 99440 541417 /usr/lib64/libgfapi.so.0.0.0 (btw: strange version 0.0.0 for a release.. not so reassuring ;-) # ll /usr/lib64/libgfapi.so.0* lrwxrwxrwx. 1 root root 17 Jan 7 12:45 /usr/lib64/libgfapi.so.0 -> libgfapi.so.0.0.0 -rwxr-xr-x. 1 root root 99440 Jan 3 13:35 /usr/lib64/libgfapi.so.0.0.0 ) At page http://www.gluster.org/category/qemu/ there is a schema about mount types and benchmarks 1) FUSE mount 2) GlusterFS block driver in QEMU (FUSE bypass) 3) Base (VM image accessed directly from brick) ( qemu-system-x86_64 –enable-kvm –nographic -smp 4 -m 2048 -drive file=/test/F17,if=virtio,cache=none => /test is brick directory ) I have not understood if we are in Base (best performance) or FUSE (worst performance) thanks in advance for clarifications and possible roadmaps... Gianluca

3 2

[Users] [QE] oVirt 3.3.3 beta / RC status
by Sandro Bonazzola 17 Jan '14

17 Jan '14

Hi, oVirt 3.3.3 beta has been released and is actually on QA. We'll start composing oVirt 3.3.3 RC on 2014-01-21 12:00 UTC. The bug tracker [1] shows no bugs blocking the release The following is a list of the non-blocking bugs still open with target 3.3 - 3.3.3: Whiteboard Bug ID Summary integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 [RFE] oVirt Live - use motd to show the admin password integration 1022440 [RFE] AIO - configure the AIO host to be a gluster cluster/host integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO integration 1050084 Tracker: oVirt 3.3.3 release network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) node 906257 USB Flash Drive install of ovirt-node created via dd fails node 923049 ovirt-node fails to boot from local disk under UEFI mode node 965583 [RFE] add shortcut key on TUI node 976675 [wiki] Update contribution page node 979350 Changes admin password in the first time when log in is failed while finished auto-install node 979390 [RFE] Split defaults.py into smaller pieces node 982232 performance page takes >1sec to load (on first load) node 984441 kdump page crashed before configuring the network after ovirt-node intalled node 986285 UI crashes when no bond name is given node 991267 [RFE] Add TUI information to log file. node 1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on Auto-install node 1018710 [RFE] Enhance API documentation node 1032035 [RFE]re-write auto install function for the cim plugin node 1033286 ovirt-node-plugin-vdsm can not be added to ovirt node el6 base image storage 987917 [oVirt] [glance] API version not specified in provider dialog virt 1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Maintainers: - We'll start composing oVirt 3.3.3 RC on 2014-01-21 12:00 UTC: all non blockers bug still open after the build will be moved to 3.3.4. - Please add the bugs to the tracker if you think that 3.3.3 should not be released without them fixed. - Please provide ETA on bugs you add as blockers - Please re-target all bugs you don't think that should block 3.3.3. - Please fill release notes, the page has been created here [3] - Please remember to rebuild your packages before 2014-01-21 12:00 UTC if you want them to be included in 3.3.3 RC. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. Thanks to Gianluca Cecchi for his testing of oVirt 3.3.3 beta on Gluster storage! [1] http://bugzilla.redhat.com/1050084 [2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing [3] http://www.ovirt.org/OVirt_3.3.3_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] [QE] oVirt bugzilla updates
by Sandro Bonazzola 17 Jan '14

17 Jan '14

Hi oVirt community, for all people interested in joining QE effort, we've created a new user in bugzilla as default QA assignee: bugs(a)ovirt.org. If you want to be updated on QE bugs activity you can just add that user to your bugzilla account watch list: https://bugzilla.redhat.com/userprefs.cgi?tab=email Watch user list -> add "bugs(a)ovirt.org" Any email sent by bugzilla to that user will be also sent to you. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] VM start Options
by Wolfgang Bucher 17 Jan '14

17 Jan '14

This is a multi-part message in MIME format. Your mail reader does not understand MIME message format. --=_B6gRzuLnmV-Qr05NuONpjAYxCVvEbGdhKKZp2OTxeHP+yFqr Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello=0D=0AHow can i change VM start from aio=3Dthread to aio=3Dnative=0D= =0A=0D=0AGreetings=C2=A0=0D=0AWolfgang=0D=0A --=_B6gRzuLnmV-Qr05NuONpjAYxCVvEbGdhKKZp2OTxeHP+yFqr Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://ww= w.w3.org/TR/html4/loose.dtd"><html>=0A<head>=0A <meta name=3D"Generator"= content=3D"Zarafa WebApp v7.1.7-42779">=0A <meta http-equiv=3D"Content-= Type" content=3D"text/html; charset=3Dutf-8">=0A <title>VM start Options= </title>=0A</head>=0A<body>=0A<font face=3D"tahoma" size=3D"2">Hello</fon= t><div><font face=3D"tahoma" size=3D"2">How can i change VM start from ai= o=3Dthread to aio=3Dnative</font></div><div><font face=3D"tahoma" size=3D= "2"><br></font></div><div><font face=3D"tahoma" size=3D"2">Greetings&nbsp= ;</font></div><div><font face=3D"tahoma" size=3D"2">Wolfgang</font></div>= =0A</body>=0A</html> --=_B6gRzuLnmV-Qr05NuONpjAYxCVvEbGdhKKZp2OTxeHP+yFqr--

5 4

[Users] Horrid performance during disk I/O
by Blaster 17 Jan '14

17 Jan '14

This probably more appropriate for the qemu users mailing list, but that list doesn’t get much traffic and most posts go unanswered… As I’ve mentioned in the past, I’m migrating my environment from ESXi to oVirt AIO. Under ESXi I was pretty happy with the disk performance, and noticed very little difference from bare metal to HV. Under oVirt/QEMU/KVM, not so much…. Running hdparm on the disk from the HV and from the guest yields the same number, about 180MB/sec (SATA III disks, 7200RPM). The problem is, during disk activity, and it doesn’t matter if it’s Windows 7 guests or Fedora 20 (both using virtio-scsi) the qemu-system-x86 process starts consuming 100% of the hypervisor CPU. Hypervisor is a Core i7 950 with 24GB of RAM. There’s 2 Fedora 20 guests and 2 Windows 7 guests. Each configured with 4 GB of guaranteed RAM. Load averages can go up over 40 during sustained disk IO. Performance obviously suffers greatly. I have tried all combinations of having the guests on EXT 4, BTRFS and using EXT 4 and BTRFS inside the guests, as well as direct LUN. Doesn’t make any difference. Disk IO sends qemu-system-x86 to high CPU percentages. This can’t be normal, so I’m wondering what I’ve done wrong. Is there some magic setting I’m missing?

6 7

[Users] VirtIO disk latency
by Markus Stockhausen 17 Jan '14

17 Jan '14

This is a multi-part message in MIME format. ------=_NextPartTM-000-e5c11ff1-4bb3-4471-9f08-8adebae2667b Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello,=0A= =0A= coming from the "low cost NFS storage thread" I will open a new one=0A= about a topic that might be interesting for others too.=0A= =0A= We see a quite a heavy latency penalty using KVM VirtIO disks in comparison= =0A= to ESX. Doing one I/O onto disk inside a VM usually adds 370us of overhead = in=0A= the virtualisation layer. This has been tested with VirtIO-SCSI and windows= =0A= guest (2K3). More here (still now answer yet):=0A= =0A= http://lists.nongnu.org/archive/html/qemu-discuss/2013-12/msg00028.html=0A= =0A= A comparison for small sequential 1K I/Os on a NFS datastore in our setup g= ives:=0A= =0A= - access NFS inside the hypervisor - 12.000 I/Os per second - or 83us laten= cy =0A= - access DISK inside ESX VM that resides on NFS - 8000 I/Os per second - or= 125us latency=0A= - access DISK inside OVirt VM that resides on NFS - 2200 I/Os per second - = or 450us latency=0A= =0A= Even the official document at http://www.linux-kvm.org/page/Virtio/Block/La= tency=0A= suggest that the several mechanisms (iothread/vcpu) at least have a overhea= d=0A= of more than 200us=0A= =0A= Has anyone experienced something simlar. If these latency are normal it wou= ld =0A= make no sense to think about SSDs inside a central storage (be it ISCSI or = NFS =0A= or whatever).=0A= =0A= Markus=0A= =0A= ------=_NextPartTM-000-e5c11ff1-4bb3-4471-9f08-8adebae2667b Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-e5c11ff1-4bb3-4471-9f08-8adebae2667b--

3 3

Re: [Users] Attach NFS storage to multiple datacenter
by Amedeo Salvati 16 Jan '14

16 Jan '14

Il 16/01/2014 18:00, users-request(a)ovirt.org ha scritto: > From: "Tobias Fiebig"<mail(a)wybt.net> > To: "Elad Ben Aharon"<ebenahar(a)redhat.com> > Cc:"Users(a)ovirt.org List" <Users(a)ovirt.org> > Sent: Thursday, January 16, 2014 6:37:24 PM > Subject: Re: [Users] Attach NFS storage to multiple datacenter > > Heho, > On Thu, 2014-01-16 at 11:10 -0500, Elad Ben Aharon wrote: >> >You don't have to attach/detach the domain for every VM export. Sorry for not being clear. You can export all your VMs to the export domain at once and then detach the export domain and attach it to the second DC. > May have miscommunicated that... > I can not do this because this kind of means that the vms will be down > during the whole movement process. I'd like to reduce the per-vm > downtime as much as possible. > > With best Regards, > Tobias you can decrease the downtime by: - live snapshot VM1; - clone VM1 from snapshot to VM1-NEW (during this process VM1 is up&running); - export VM1-NEW to export domain (VM1 up&running); - detach export domain from old DC; - attach export domain to new DC; - import VM1-NEW (VM1 still up&running); - start VM1-NEW on single mode and configure; - stop apps from VM1 (downtime); - optionally sync app data from VM1 to VM1-NEW (downtime); - start apps on VM1-NEW (apps up&running on new DC). - stop VM1 on old DC. HTH a -- Amedeo Salvati RHC{DS,E,VA} - LPIC-3 - UCP - NCLA 11 email: amedeo(a)oscert.net email: amedeo(a)linux.com http://plugcomputing.it/redhatcert.php http://plugcomputing.it/lpicert.php

1 0