- Users - oVirt List Archives

Can't remove snapshot due to low disk space on storage domain?
by Rik Theys 11 Feb '15

11 Feb '15

Hi, I'm running the ovirt engine 3.4 series. I've created a snapshot of a VM with an OS and data disk before upgrading the machine. The upgrade went fine and I now want to remove the snapshot. Unfortunately this fails with the error: "Cannot remove Snapshot. Low disk space on target Storage Domain stadius-virt2_PERC." So I can't free disk space by removing the snapshot because I don't have enough space? When I look at the VM the disks are shown as preallocated (which is what I selected during installation). When I look at the storage tab and list the disks in my storage domain, the disks are now shown as thin provisioned with the actual size > virtual size. How can I remove this snapshot? I don't have enough free disk space in my storage domain to duplicate the data disk of my VM. Regards, Rik -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee +32(0)16/32.11.07 ---------------------------------------------------------------- <<Any errors in spelling, tact or fact are transmission errors>>

3 9

importing iscsi storage domain
by Steven M. Bellistri 11 Feb '15

11 Feb '15

--_000_9EB77BD1668726458ACABD8FBB68AF6ADD2A5980STLMS1LDIPBMINT_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am trying to test failing over to a DR site using the storage domain = import. The DR site shows that it imported the iscsi storage domain, and = activates it in the datacenter, but none of the vm's or anything shows up. = What am I missing. thanks Steven Bellistri This email and its attachments may contain privileged and confidential = information and/or protected health information (PHI) intended solely for = the use of LDI Integrated Pharmacy Services and the recipient(s) named = above. If you are not the recipient, or the employee or agent responsible = for delivering this message to the intended recipient, you are hereby = notified that any review, dissemination, distribution, printing or copying = of this email message and/or any attachments is strictly prohibited. If = you have received this transmission in error, please notify the sender = immediately at 1-866-516-3121 and permanently delete this email and any = attachments.= --_000_9EB77BD1668726458ACABD8FBB68AF6ADD2A5980STLMS1LDIPBMINT_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D=22urn:schemas-microsoft-com:vml=22 = xmlns:o=3D=22urn:schemas-microsoft-com:office:office=22 = xmlns:w=3D=22urn:schemas-microsoft-com:office:word=22 = xmlns:m=3D=22http://schemas.microsoft.com/office/2004/12/omml=22 = xmlns=3D=22http://www.w3.org/TR/REC-html40=22> <head> <meta http-equiv=3D=22Content-Type=22 content=3D=22text/html; = charset=3Dus-ascii=22> <meta name=3D=22Generator=22 content=3D=22Microsoft Word 15 (filtered = medium)=22> <style><=21-- /* Font Definitions */ =40font-face =09=7Bfont-family:=22Cambria Math=22; =09panose-1:2 4 5 3 5 4 6 3 2 4;=7D =40font-face =09=7Bfont-family:Calibri; =09panose-1:2 15 5 2 2 2 4 3 2 4;=7D /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal =09=7Bmargin:0in; =09margin-bottom:.0001pt; =09font-size:11.0pt; =09font-family:=22Calibri=22,sans-serif;=7D a:link, span.MsoHyperlink =09=7Bmso-style-priority:99; =09color:=230563C1; =09text-decoration:underline;=7D a:visited, span.MsoHyperlinkFollowed =09=7Bmso-style-priority:99; =09color:=23954F72; =09text-decoration:underline;=7D span.EmailStyle17 =09=7Bmso-style-type:personal-compose; =09font-family:=22Calibri=22,sans-serif; =09color:windowtext;=7D =2EMsoChpDefault =09=7Bmso-style-type:export-only; =09font-family:=22Calibri=22,sans-serif;=7D =40page WordSection1 =09=7Bsize:8.5in 11.0in; =09margin:1.0in 1.0in 1.0in 1.0in;=7D div.WordSection1 =09=7Bpage:WordSection1;=7D --></style><=21--=5Bif gte mso 9=5D><xml> <o:shapedefaults v:ext=3D=22edit=22 spidmax=3D=221026=22 /> </xml><=21=5Bendif=5D--><=21--=5Bif gte mso 9=5D><xml> <o:shapelayout v:ext=3D=22edit=22> <o:idmap v:ext=3D=22edit=22 data=3D=221=22 /> </o:shapelayout></xml><=21=5Bendif=5D--> </head> <body lang=3D=22EN-US=22 link=3D=22=230563C1=22 vlink=3D=22=23954F72=22> <div class=3D=22WordSection1=22> <p class=3D=22MsoNormal=22>I am trying to test failing over to a DR site = using the storage domain import.  The DR site shows that it imported = the iscsi storage domain, and activates it in the datacenter, but none of = the vm&=238217;s or anything shows up.  What am I = missing.<o:p></o:p></p> <p class=3D=22MsoNormal=22><o:p> </o:p></p> <p class=3D=22MsoNormal=22>thanks<o:p></o:p></p> <p class=3D=22MsoNormal=22><o:p> </o:p></p> <p class=3D=22MsoNormal=22>Steven Bellistri<o:p></o:p></p> </div> </body> </html> <BR> This email and its attachments may contain privileged and confidential = information and/or protected health information (PHI) intended solely for = the use of LDI Integrated Pharmacy Services and the recipient(s) named = above. If you are not the recipient, or the employee or agent responsible = for delivering this message to the intended recipient, you are hereby = notified that any review, dissemination, distribution, printing or copying = of this email message and/or any attachments is strictly prohibited. If = you have received this transmission in error, please notify the sender = immediately at 1-866-516-3121 and permanently delete this email and any = attachments. --_000_9EB77BD1668726458ACABD8FBB68AF6ADD2A5980STLMS1LDIPBMINT_--

3 11

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

11 Feb '15

Hi, here's an update on 3.6 status on integration / rel-eng side ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 22: 2015-05-19 Fedora 20 End Of Life:2015-06-19 (1 month after Fedora 22 release) Foreman 1.8.0: 2015-04-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 545 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 503 bugs [4] targeted to 3.6.0. NEW ASSIGNED POST Total 1 0 0 1 docs 11 0 0 11 gluster 25 2 1 28 i18n 2 0 0 2 infra 80 10 3 93 integration 59 4 2 65 network 29 2 8 39 node 26 2 3 31 ppc 0 0 1 1 sla 56 3 1 60 spice 1 0 0 1 storage 76 4 5 85 ux 35 1 3 39 virt 74 6 9 89 Total 475 34 36 545 oVirt Live for 3.6 has been rebased on EL7. Nightly builds are available here: http://jenkins.ovirt.org/job/ovirt_live_create_iso/ [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%… [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

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

11 Feb '15

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

1 0

virtual disk terminology in oVirt/RHEV improvements needed?
by Gianluca Cecchi 10 Feb '15

10 Feb '15

Hello, in my opinion the terms raw, qcow2, thin provisioned, sparse, preallocated are used in sub optimal way in oVirt and RHEV documentation and create confusion for the new incoming user (but not only to him/her) My referrals for them are: oVirt Admin Guide at: http://www.ovirt.org/OVirt_Administration_Guide and the draft RHEV 3.5: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualiza… Sometimes I have to come back to docs to clear my doubts and I'm never fully satisfied. I report below only some excerpts to explain my findings oVirt 1) Virtual disks can have one of two formats, either Qcow2 or RAW. The type of storage can be either Sparse or Preallocated. Snapshots are always sparse but can be taken for disks created either as RAW or sparse. --> From above one concludes that "format" is one thing and "type" is another thing and that all the mix format/type are in general possible (depending on storage layout... see below): Qcow2/Sparse, RAW/Prellocated, Qcow2/Preallocated, RAW/Sparse But then, both in Ovirt and RHEV page 2) A virtual disk with a preallocated (RAW) format has significantly faster write speeds than a virtual disk with a thin provisioning (Qcow2) format. Thin provisioning takes significantly less time to create a virtual disk. The thin provision format is suitable for non-IO intensive virtual machines. --> now one concludes instead that format==type and that so preallocated==RAW thin provisioning==Qcow2 and also indirectly that thin provisioning == sparse because in point 1) the term sparse was the one used.. Indeed later, in section 12.2 of RHEV and in section "Understanding Virtual Disks" of oVirt guide there is the classification of the 2 "types" again, Preallocated and Thin Provisioned and the latter contains: "For sparse virtual disks backing storage is not reserved and is allocated as needed during runtime. This allows for storage overcommitment ..." And this confirms that sparse==thin provisioned In the same part for both docs 3) Table 11.1. Permitted Storage Combinations for oVirt and Table 12.1. Permitted Storage Combinations for RHEV Again there are almost-all the combinations described: For file based storage (NFS) only Qcow2/Preallocated is not contemplated For iSCSI/SAN only RAW/Sparse is not contemplated 4) Gluster last but not least, It is not clear in my opinion where should be put Gluster (file based or SAN based)... I think that depending on POSIXFS_DOMAIN (pre 3.5, correct?) or GLUSTERFS_DOMAIN usage it could match both of them.... As far as format, it seems both qcow2 and raw are possible This message is just to share my uncertainty when I have to deal with disks in oVirt and explain/compare with VMware, to make it possible to simplify life to new users. Coming from VMware world they know about: - thin provision - thick provision (lazy zeroed) - thick provision (eager zeroed) see also: https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.st… In my opinion it could be useful to have a preface with a short description of all the terminology that will be used HIH improving docs, Gianluca

3 2

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

10 Feb '15

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

4 5

Dockerized ovirt-optimizer
by Roy Golan 10 Feb '15

10 Feb '15

This is a multi-part message in MIME format. --------------070802040709010306050907 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Dockerized ovirt-optimizer is here! check out the Dockerfile[1], build and run with an engine running on your host. zero work (almost :)) you will need the ovirt-optimizer-ui-plugin installed on engine - get it from within the docker instance at: /home/ovirt/ovirt-optimizer/dist/ovirt-optimizer-uiplugin To any of you not familiar with the work of Martin on ovirt-optimizer[2] over OptaPlanner[3] have a pick at the links. [1] https://github.com/rgolangh/Fedora-Dockerfiles/tree/ovirt-optimizer/ovirt-o… [1] http://www.ovirt.org/Features/Optaplanner [2] http://www.optaplanner.org/ Thanks, Roy --------------070802040709010306050907 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-text-flowed" style="font-family: -moz-fixed; font-size: 12px;" lang="x-unicode">Dockerized ovirt-optimizer is here! <br> <br> check out the Dockerfile[1], build and run with an engine running on your host. zero work (almost :)) <br> <br> you will need the ovirt-optimizer-ui-plugin installed on engine - get it from within the docker instance at: <br> /home/ovirt/ovirt-optimizer/dist/ovirt-optimizer-uiplugin <br> <br> To any of you not familiar with the work of Martin on ovirt-optimizer[2] over OptaPlanner[3] have a pick at the links. <br> <br> [1] <a class="moz-txt-link-freetext" href="https://github.com/rgolangh/Fedora-Dockerfiles/tree/ovirt-optimizer/ovirt-o…">https://github.com/rgolangh/Fedora-Dockerfiles/tree/ovirt-optimizer/ovirt-o…</a> <br> [1] <a class="moz-txt-link-freetext" href="http://www.ovirt.org/Features/Optaplanner">http://www.ovirt.org/Features/Optaplanner</a> <br> [2] <a class="moz-txt-link-freetext" href="http://www.optaplanner.org/">http://www.optaplanner.org/</a> <br> <br> Thanks, <br> Roy <br> <br> </div> </body> </html> --------------070802040709010306050907--

1 0

Re: [ovirt-users] restore state is very long after suspending
by Oved Ourfali 10 Feb '15

10 Feb '15

Can you please provide the engine and vdsm logs? It might shed some light on why it took so long. On Jan 30, 2015 12:43 PM, Nathanaël Blanchet <blanchet(a)abes.fr> wrote: > > Hello, > > Suspending one vm (2 GB RAM) is quite short (about 1 minute) while > restoring it is over 20 minutes... This make the suspend feature unusable. > Is it a regular work? > > ovirt 3.5, el6 vdsm 4.16. > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users

3 2

Howto restart VMs on the Unknown state?
by Николаев Алексей 10 Feb '15

10 Feb '15

2 1

[GSoC] Announcing the 2015 Google Summer of Code!
by Brian Proffitt 09 Feb '15

09 Feb '15

Hey, oVirt Community! Though there was some question regarding oVirt's eligibility in the 2015 Google Summer of Code, it turns out that we *are* eligible to apply for the program again. Applications for potential mentoring organizations are now open and are due at 1100 PST (1900 UTC) on Feb. 20, 2015. http://www.google-melange.com/gsoc/homepage/google/gsoc2015 As with last year, we would need to come up with projects for students to work on. The projects can be different skill levels, and they can be modular. They should also be doable within eight weeks in a summer with mentor help. If you are interested in mentoring such a project, visit http://google-opensource.blogspot.com/2015/02/mentoring-organization-applic… for more information, then come to http://www.ovirt.org/Summer_of_Code so we can coordinate ideas prior to submitting to Google. Given the issues from last summer, it is very important that all mentors be very familiar with project deadlines. If you have any questions, please contact me as soon as possible Peace, Brian -- Brian Proffitt Community Liaison oVirt Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

1 0