Re: [Users] How to make host ovirt on hetzner server
Hello did you sort this out ? I am planning to run a 2 node HA cluster and I am afraid I will have issues with networking ! Regards Dimitrios ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Unable to install oVirt Node 3.0.1: Exception: RunTimeError('Failed to partition/format')
Am Dienstag, den 22.10.2013, 00:00 +0200 schrieb Edgars M.:
Hi, thanks for your replies..
As suggested by Gabi C, I destroyed RAID on my RAID controller,
re-created it and after that it worked.
Hey Edgars and Gabi,
nice that both of you could solve this problem.
Could you tell what kind of raid it was? Was it a fake raid or a real
raid controller, and how did the raid setup look when it failed and how
did it look afterwards?
I'd like to capture these informations to nail down this problem a bit
more.
Thanks
fabian
Thanks again.
On Mon, Oct 21, 2013 at 10:45 PM, Joey Boggs jbo...@redhat.com
wrote:
On 10/21/2013 08:59 AM, Gabi C wrote:
Hello!
Had same problem on IBM xSeries 3650. Aparently was an RAID
problem (Serve RID in my case). I had to wipe the disk,
recreate the array an wait until it was OK and only after
that I manage to install.
On Mon, Oct 21, 2013 at 3:45 PM, Edgars M.
edgars.maz...@gmail.com wrote:
Hi
I am trying to install oVirt Node
(ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso) on DELL
R805 server, but every time install fails
with Exception: RunTimeError('Failed to
partition/format'). I also
tried ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso
version and the same error occures. I tried
different partition sizes and I always make sure
that partitions dont exceed the total disk space. I
browsed log fails and could not find anything
relevant. I am really out of ideas...
Any advise?
Thanks
Edgars
___
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
Once it fails, press F2 to drop to
shell. /tmp/ovirt.log /var/log/ovirt.log
and /var/log/ovirt-node.log will have the debug messages in
it. Paste those in here if you can.
___
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] Unable to install oVirt Node 3.0.1: Exception: RunTimeError('Failed to partition/format')
Hello!
It is a real RAID controller ServeRAID 8k that comes with IBM xSeries 3650.
First I hit this problem, tryin' to upgrade from 3.2 - i.e
ovirt-node-iso-2.6.1-20120228.fc18.isohttp://resources.ovirt.org/releases/3.2/iso/ovirt-node-iso-2.6.1-20120228.fc18.iso-
to 3.3 - ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso.
http://resources.ovirt.org/releases/3.3/iso/ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso...in
fact the message was Error 'Failed to set install bootloader' - see
http://lists.ovirt.org/pipermail/users/2013-September/016434.html --,
message which appear in the last styage of upgrade ( 5 out of 5).
Then I rebooted, enter the RAID setup, erase the array, reinitiliaze the
disks, recrete the array with option full - this take some time to complete
but when ready the array was available. I also tried to create the array
with Quick option - this option immediately create the array and made it
available to the OS but in the background RAID controller was still
creating the array i.e. some disk operations and got same error.
http://resources.ovirt.org/releases/3.3/iso/ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso
On Tue, Oct 22, 2013 at 11:15 AM, Fabian Deutsch fabi...@redhat.com wrote:
Am Dienstag, den 22.10.2013, 00:00 +0200 schrieb Edgars M.:
Hi, thanks for your replies..
As suggested by Gabi C, I destroyed RAID on my RAID controller,
re-created it and after that it worked.
Hey Edgars and Gabi,
nice that both of you could solve this problem.
Could you tell what kind of raid it was? Was it a fake raid or a real
raid controller, and how did the raid setup look when it failed and how
did it look afterwards?
I'd like to capture these informations to nail down this problem a bit
more.
Thanks
fabian
Thanks again.
On Mon, Oct 21, 2013 at 10:45 PM, Joey Boggs jbo...@redhat.com
wrote:
On 10/21/2013 08:59 AM, Gabi C wrote:
Hello!
Had same problem on IBM xSeries 3650. Aparently was an RAID
problem (Serve RID in my case). I had to wipe the disk,
recreate the array an wait until it was OK and only after
that I manage to install.
On Mon, Oct 21, 2013 at 3:45 PM, Edgars M.
edgars.maz...@gmail.com wrote:
Hi
I am trying to install oVirt Node
(ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso) on DELL
R805 server, but every time install fails
with Exception: RunTimeError('Failed to
partition/format'). I also
tried ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso
version and the same error occures. I tried
different partition sizes and I always make sure
that partitions dont exceed the total disk space. I
browsed log fails and could not find anything
relevant. I am really out of ideas...
Any advise?
Thanks
Edgars
___
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
Once it fails, press F2 to drop to
shell. /tmp/ovirt.log /var/log/ovirt.log
and /var/log/ovirt-node.log will have the debug messages in
it. Paste those in here if you can.
___
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] Unable to install oVirt Node 3.0.1: Exception: RunTimeError('Failed to partition/format')
Hi Fabian
I am using DELL R805 server with PERC 6/i RAID controller and two SAS
disks. PERC 6/i is real hardware RAID controller (although cheap one).
First I created RAID1 and did fast initialisation. (PERC RAID controllers
has this stupid requirement that you need to initialise RAID before you can
use it). After this oVirt Node installation failed every time with Failed
to partition/format.
Then I destroyed RAID1 and created it again, but this time I did full RAID
initialisation (instead of fast). After that oVirt Node installation went
smooth.
The thing is that I never do full initialisation when I install any OS,
because it is very slow process and can take hours and I never had any
problems with fast initialisation before. But apparently there is some
trick with oVirt Node.
From documentation:
Fast initialization writes zeroes to the first 8 MB and to the last 8 MB
of the virtual disk so that initialization occurs in 2–3 seconds. A
progress bar displays next to the selected virtual disk as it initializes.
Whereas:
A regular (meaning full) initialization permanently destroys any data that
already exists.
Hope that helps.
Edgars
On Tue, Oct 22, 2013 at 10:15 AM, Fabian Deutsch fabi...@redhat.com wrote:
Am Dienstag, den 22.10.2013, 00:00 +0200 schrieb Edgars M.:
Hi, thanks for your replies..
As suggested by Gabi C, I destroyed RAID on my RAID controller,
re-created it and after that it worked.
Hey Edgars and Gabi,
nice that both of you could solve this problem.
Could you tell what kind of raid it was? Was it a fake raid or a real
raid controller, and how did the raid setup look when it failed and how
did it look afterwards?
I'd like to capture these informations to nail down this problem a bit
more.
Thanks
fabian
Thanks again.
On Mon, Oct 21, 2013 at 10:45 PM, Joey Boggs jbo...@redhat.com
wrote:
On 10/21/2013 08:59 AM, Gabi C wrote:
Hello!
Had same problem on IBM xSeries 3650. Aparently was an RAID
problem (Serve RID in my case). I had to wipe the disk,
recreate the array an wait until it was OK and only after
that I manage to install.
On Mon, Oct 21, 2013 at 3:45 PM, Edgars M.
edgars.maz...@gmail.com wrote:
Hi
I am trying to install oVirt Node
(ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso) on DELL
R805 server, but every time install fails
with Exception: RunTimeError('Failed to
partition/format'). I also
tried ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso
version and the same error occures. I tried
different partition sizes and I always make sure
that partitions dont exceed the total disk space. I
browsed log fails and could not find anything
relevant. I am really out of ideas...
Any advise?
Thanks
Edgars
___
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
Once it fails, press F2 to drop to
shell. /tmp/ovirt.log /var/log/ovirt.log
and /var/log/ovirt-node.log will have the debug messages in
it. Paste those in here if you can.
___
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] oVirt October Updates
On Mon, Oct 21, 2013 at 11:33 AM, Vijay Bellur wrote: The following commands might help: Thanks for your commands. In the mean time I noticed that as I changed gluster sources to allow live migration, offsetting the port to 50152+ as in http://review.gluster.org/#/c/6075/ referred in https://bugzilla.redhat.com/show_bug.cgi?id=1018178 I missed the iptables rules that contained: # Ports for gluster volume bricks (default 100 ports) -A INPUT -p tcp -m tcp --dport 24009:24108 -j ACCEPT -A INPUT -p tcp -m tcp --dport 49152:49251 -j ACCEPT So I had some gluster communication problems too. I updated it at the moment to # Ports for gluster volume bricks (default 100 ports) -A INPUT -p tcp -m tcp --dport 24009:24108 -j ACCEPT -A INPUT -p tcp -m tcp --dport 49152:49251 -j ACCEPT -A INPUT -p tcp -m tcp --dport 50152:50251 -j ACCEPT until libvirt for fedora19 get patched as upstream (a quick test on rebuilding libvirt-1.0.5.6-3.fc19.src.rpm with the patches proposed gave many failure and in the mean time I saw that also some other parts are to be patched...) I put in iptables these lines # Ports for gluster volume bricks (default 100 ports) -A INPUT -p tcp -m tcp --dport 24009:24108 -j ACCEPT -A INPUT -p tcp -m tcp --dport 49152:49251 -j ACCEPT -A INPUT -p tcp -m tcp --dport 50152:50251 -j ACCEPT I'm going to retest completely and see how it behaves. See here for my test case and begin of problem simulation: http://lists.ovirt.org/pipermail/users/2013-October/017228.html It represents a realistic maintenance scenario that forced a manual alignment on gluster that is in my opinin not feasible Eventually I'm going to put into a bugzilla if new test with correct iptables ports gives problems I would like to have oVirt more conscious about it and have sort of capability to solve itself the misalignments generated on gluster backend during mainteneance of a node. At the moment it seems to me it only shows volumes are ok in the sense of started, but they could be very different... For example another tab with details about heal info; something like the output of the command gluster volume heal $VOLUME info and/or gluster volume heal $VOLUME info split-brain Yes, we are looking to build this for monitoring replicated gluster volumes. Good! Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Gluster not aligned with double maintenance... problem
On Thu, Oct 17, 2013 at 5:45 PM, Gianluca Cecchi wrote: Hello, One engine and two hosts all with updated f19 (despite on their names) and ovirt updates-testing repo enabled. So I have 3.3.0.1-1 and vdsm-4.12.1-4 kernel is 3.11.2-201.fc19.x86_64 (problems booting with latest 3.11.4-201.fc19.x86_64) Storage domain configured with gluster as in f19 (3.4.1-1.fc19.x86_64 recompiled binding to port 50152+) and distributed replicated bricks I do this kind of operations: - power off all VMs (to start clean) - put both hosts in maintenance - shutdown both hosts - startup one host - activate one host in webadmin gui after about 2-3 minutes delay it comes up and so it has its own gluster copy active - power on VM and write 3Gb on it [snip] - power on second host I missed the iptables rules that contained: # Ports for gluster volume bricks (default 100 ports) -A INPUT -p tcp -m tcp --dport 24009:24108 -j ACCEPT -A INPUT -p tcp -m tcp --dport 49152:49251 -j ACCEPT So I had some gluster communication problems too. I updated it at the moment to # Ports for gluster volume bricks (default 100 ports) -A INPUT -p tcp -m tcp --dport 24009:24108 -j ACCEPT -A INPUT -p tcp -m tcp --dport 49152:49251 -j ACCEPT -A INPUT -p tcp -m tcp --dport 50152:50251 -j ACCEPT until libvirt for fedora19 get patched as upstream I put in iptables these lines # Ports for gluster volume bricks (default 100 ports) -A INPUT -p tcp -m tcp --dport 24009:24108 -j ACCEPT -A INPUT -p tcp -m tcp --dport 49152:49251 -j ACCEPT -A INPUT -p tcp -m tcp --dport 50152:50251 -j ACCEPT So that I can test both gluster and live migration. I'm going to retest completely and see how it behaves. Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt October Updates
On Tue, Oct 22, 2013 at 12:14 PM, Gianluca Cecchi wrote: On Mon, Oct 21, 2013 at 11:33 AM, Vijay Bellur wrote: The following commands might help: Thanks for your commands. In the mean time I noticed that as I changed gluster sources to allow live migration, offsetting the port to 50152+ as in http://review.gluster.org/#/c/6075/ referred in https://bugzilla.redhat.com/show_bug.cgi?id=1018178 I missed the iptables rules that contained: # Ports for gluster volume bricks (default 100 ports) -A INPUT -p tcp -m tcp --dport 24009:24108 -j ACCEPT -A INPUT -p tcp -m tcp --dport 49152:49251 -j ACCEPT So I had some gluster communication problems too. I updated it at the moment to # Ports for gluster volume bricks (default 100 ports) -A INPUT -p tcp -m tcp --dport 24009:24108 -j ACCEPT -A INPUT -p tcp -m tcp --dport 49152:49251 -j ACCEPT -A INPUT -p tcp -m tcp --dport 50152:50251 -j ACCEPT until libvirt for fedora19 get patched as upstream (a quick test on rebuilding libvirt-1.0.5.6-3.fc19.src.rpm with the patches proposed gave many failure and in the mean time I saw that also some other parts are to be patched...) I put in iptables these lines # Ports for gluster volume bricks (default 100 ports) -A INPUT -p tcp -m tcp --dport 24009:24108 -j ACCEPT -A INPUT -p tcp -m tcp --dport 49152:49251 -j ACCEPT -A INPUT -p tcp -m tcp --dport 50152:50251 -j ACCEPT Strangely, after fixing iptables rules, still te second node has problems with the VM iage file where I ran the command [g.cecchi at c6s ~]$ sudo time dd if=/dev/zero bs=1024k count=3096 of=/testfile 3096+0 records in 3096+0 records out 3246391296 bytes (3.2 GB) copied, 42.3414 s, 76.7 MB/s 0.01user 7.99system 0:42.34elapsed 18%CPU (0avgtext+0avgdata 7360maxresident)k 0inputs+6352984outputs (0major+493minor)pagefaults 0swaps If I delete the img file that has the delta: [root@f18ovn03 /]# find /gluster/DATA_GLUSTER/brick1/ -samefile /gluster/DATA_GLUSTER/brick1/d0b96d4a-62aa-4e9f-b50e-f7a0cb5be291/images/15f9ca1c-c435-4892-9eb7-0c84583b2a7d/a123801a-0a4d-4a47-a426-99d8480d2e49 -print -delete /gluster/DATA_GLUSTER/brick1/d0b96d4a-62aa-4e9f-b50e-f7a0cb5be291/images/15f9ca1c-c435-4892-9eb7-0c84583b2a7d/a123801a-0a4d-4a47-a426-99d8480d2e49 /gluster/DATA_GLUSTER/brick1/.glusterfs/f4/c1/f4c1b1a4-7328-4d6d-8be8-6b7ff8271d51 then auto heal happens: [root@f18ovn03 15f9ca1c-c435-4892-9eb7-0c84583b2a7d]# gluster volume heal gvdata info Gathering Heal info on volume gvdata has been successful Brick f18ovn01.mydomain:/gluster/DATA_GLUSTER/brick1 Number of entries: 2 /d0b96d4a-62aa-4e9f-b50e-f7a0cb5be291/images/15f9ca1c-c435-4892-9eb7-0c84583b2a7d/a123801a-0a4d-4a47-a426-99d8480d2e49 /d0b96d4a-62aa-4e9f-b50e-f7a0cb5be291/dom_md/ids Brick f18ovn03.mydomain:/gluster/DATA_GLUSTER/brick1 Number of entries: 1 /d0b96d4a-62aa-4e9f-b50e-f7a0cb5be291/dom_md/ids [root@f18ovn03 15f9ca1c-c435-4892-9eb7-0c84583b2a7d]# gluster volume heal gvdata info Gathering Heal info on volume gvdata has been successful Brick f18ovn01.mydomain:/gluster/DATA_GLUSTER/brick1 Number of entries: 1 /d0b96d4a-62aa-4e9f-b50e-f7a0cb5be291/images/15f9ca1c-c435-4892-9eb7-0c84583b2a7d/a123801a-0a4d-4a47-a426-99d8480d2e49 Brick f18ovn03.mydomain:/gluster/DATA_GLUSTER/brick1 Number of entries: 0 at the end: [root@f18ovn03 15f9ca1c-c435-4892-9eb7-0c84583b2a7d]# gluster volume heal gvdata info Gathering Heal info on volume gvdata has been successful Brick f18ovn01.mydomain:/gluster/DATA_GLUSTER/brick1 Number of entries: 0 Brick f18ovn03.mydomain:/gluster/DATA_GLUSTER/brick1 Number of entries: 0 But [root@f18ovn03 15f9ca1c-c435-4892-9eb7-0c84583b2a7d]# qemu-img info a123801a-0a4d-4a47-a426-99d8480d2e49 image: a123801a-0a4d-4a47-a426-99d8480d2e49 file format: raw virtual size: 10G (10737418240 bytes) disk size: 1.4G [root@f18ovn01 15f9ca1c-c435-4892-9eb7-0c84583b2a7d]# qemu-img info a123801a-0a4d-4a47-a426-99d8480d2e49 image: a123801a-0a4d-4a47-a426-99d8480d2e49 file format: raw virtual size: 10G (10737418240 bytes) disk size: 4.2G any problem here? Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host Error
On 22.10.2013 10:57, Dan Kenigsberg wrote: On Tue, Oct 22, 2013 at 06:56:09AM +0100, Itamar Heim wrote: On 10/21/2013 03:39 PM, Neil wrote: Thanks guys, Your questions lead me to the fact that another technician had installed vdsm-hook-nestedvt to try and get nested virtualization on a VM working a while back. I have removed the hook and restarted and this resolved the issue. Thanks once again, much appreciated. danken - shouldn't the hook (if in rpm form) require a kernel which actually supports nested, to not be installed on .el6, etc.? I do not think we should have such a static requirement. The hook was ment to be used by people on EL6 who love re-compiling the kernel. Hi, but it would be cool if this would be documented, not just on the mailing list? For the people who don't love re-compiling? :-) ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host Error
Hi guys, Sorry not sure if you need any comments from me, but just in case, our kernel is stock standard. Linux ovirt02.blabla.co.za 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Regards. Neil Wilson. On Tue, Oct 22, 2013 at 1:56 PM, Sven Kieske s.kie...@mittwald.de wrote: On 22.10.2013 10:57, Dan Kenigsberg wrote: On Tue, Oct 22, 2013 at 06:56:09AM +0100, Itamar Heim wrote: On 10/21/2013 03:39 PM, Neil wrote: Thanks guys, Your questions lead me to the fact that another technician had installed vdsm-hook-nestedvt to try and get nested virtualization on a VM working a while back. I have removed the hook and restarted and this resolved the issue. Thanks once again, much appreciated. danken - shouldn't the hook (if in rpm form) require a kernel which actually supports nested, to not be installed on .el6, etc.? I do not think we should have such a static requirement. The hook was ment to be used by people on EL6 who love re-compiling the kernel. Hi, but it would be cool if this would be documented, not just on the mailing list? For the people who don't love re-compiling? :-) ___ 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] Host Error
On 10/22/2013 01:16 PM, Neil wrote: Hi guys, Sorry not sure if you need any comments from me, but just in case, our kernel is stock standard. Linux ovirt02.blabla.co.za 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux yes. this kernel doesn't support nested virt, hence the hook is not relevant for it (and is causing problems) Regards. Neil Wilson. On Tue, Oct 22, 2013 at 1:56 PM, Sven Kieske s.kie...@mittwald.de wrote: On 22.10.2013 10:57, Dan Kenigsberg wrote: On Tue, Oct 22, 2013 at 06:56:09AM +0100, Itamar Heim wrote: On 10/21/2013 03:39 PM, Neil wrote: Thanks guys, Your questions lead me to the fact that another technician had installed vdsm-hook-nestedvt to try and get nested virtualization on a VM working a while back. I have removed the hook and restarted and this resolved the issue. Thanks once again, much appreciated. danken - shouldn't the hook (if in rpm form) require a kernel which actually supports nested, to not be installed on .el6, etc.? I do not think we should have such a static requirement. The hook was ment to be used by people on EL6 who love re-compiling the kernel. Hi, but it would be cool if this would be documented, not just on the mailing list? For the people who don't love re-compiling? :-) ___ 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
Re: [Users] Host Error
On Tue, Oct 22, 2013 at 11:56:48AM +, Sven Kieske wrote: On 22.10.2013 10:57, Dan Kenigsberg wrote: On Tue, Oct 22, 2013 at 06:56:09AM +0100, Itamar Heim wrote: On 10/21/2013 03:39 PM, Neil wrote: Thanks guys, Your questions lead me to the fact that another technician had installed vdsm-hook-nestedvt to try and get nested virtualization on a VM working a while back. I have removed the hook and restarted and this resolved the issue. Thanks once again, much appreciated. danken - shouldn't the hook (if in rpm form) require a kernel which actually supports nested, to not be installed on .el6, etc.? I do not think we should have such a static requirement. The hook was ment to be used by people on EL6 who love re-compiling the kernel. Hi, but it would be cool if this would be documented, not just on the mailing list? For the people who don't love re-compiling? :-) Makes sense. http://gerrit.ovirt.org/20399 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] [Bug] 3.2 repo rpm
Hi, the rpm for the 3.2 repo doesn't point to the 3.2 branch, instead it points to stable (3.3): http://resources.ovirt.org/releases/3.2/rpm/EL/6/noarch/ovirt-release-el6-7-1.noarch.rpm It would be kind if this could be fixed. Thanks Sven ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Bug] 3.2 repo rpm
On 10/22/2013 02:39 PM, Sven Kieske wrote: Hi, the rpm for the 3.2 repo doesn't point to the 3.2 branch, instead it points to stable (3.3): http://resources.ovirt.org/releases/3.2/rpm/EL/6/noarch/ovirt-release-el6-7-1.noarch.rpm It would be kind if this could be fixed. In general, oVirt strongly recommends that you install the latest version. We don't provide any fixes/help on the previous versions. The ovirt-release rpm provides repo definitions for the stable beta nightly and alpha repos, and not for individual versions. Editing the ovirt-stable entry on your host to point to /releases/3.2 instead of releases/stable would solve your problem, but I would strongly prefer *not* changing the entries in the rpm. Mike Thanks Sven ___ 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] Reclaim deleted blocks from thin provisioned vdisk
Hi fellow Ovirt users, I have a situation where I need to clone a database VM several times. I have a 200GB thin allocated vdisk associated with it which had a large database on it. I have since truncated several tables, removed bin logs etc. and reduced the disk usage to about 26GB. But the Ovirt UI still shows actual size at 185GB. Screen Shots [cid:image001.png@01CECF3F.8F96B130] [cid:image002.png@01CECF3F.8F96B130] How would I go about reclaiming deleted blocks? This would speed up the cloning process and obviously use a lot less space. I goggled but did not find much on the topic except for a similar article for VMware http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=2014849 Thank you for your time! Usman inline: image001.pnginline: image002.png___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.3.1 Beta now available
Am Freitag, den 18.10.2013, 07:03 -0400 schrieb Mike Burns: The oVirt team is pleased to announce that the 3.3.1 Release is now available in beta. Release notes for this update are still being worked on, but information on the changes can be found on the wiki[1]. A new oVirt Node build will be available soon as well. Hey, the patches for the oVirt Node image are ready. We are currently waiting for the selinux-policy-targeted = 3.7.19-213 on EL6 to land. We will give this a couple of days. Greetings fabian ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] CfP: Virtualisation and IaaS DevRoom at FOSDEM'14
https://groups.google.com/forum/#!forum/fosdem14-virt-and-iaas-devroom Call for Participation The scope for this devroom is open source, openly-developed projects in the areas of virtualisation and IaaS type clouds, ranging from low level to data center, up to cloud management platforms and cloud resource orchestration. Sessions should always target a developer audience. Bonus points for collaborative sessions that would be appealing to developers from multiple projects. We are particularly interested in the following themes: - low level virtualisation aspects - new features in classic and container-based virtualisation technologies - new use cases for virtualisation, such as virtualisation in mobile, automotive and embedded in general - other resource virtualisation technologies: networking, storage, … - deep technical dives into specific IaaS or virtualisation management projects features - relationship between IaaS projects and specific dependencies (not just virtualisation) - integration and development leveraging solutions from multiple projects Important dates Submission deadline: Sunday, December 1st, 2013 Acceptance notifications: Sunday, December 15th, 2013 Final schedule announcement: Friday January 10th, 2014 Devroom @ FOSDEM'14: February 1st 2nd, 2014 Practical Submissions should be 40 minutes, and consist of a 30 minute presentation with 10 minutes of QA or 40 minutes of discussions (e.g., requests for feedback, open discussions, etc.). Interactivity is encouraged, but optional. Talks are in English only. We do not provide travel assistance or reimbursement of travel expenses for accepted speakers. Submissions should be made via the FOSDEM submission page at https://penta.fosdem.org/submission/FOSDEM14 : - If necessary, create a Pentabarf account and activate it - In the “Person” section, provide First name, Last name (in the “General” tab), Email (in the “Contact” tab) and Bio (“Abstract” field in the “Description” tab) - Submit a proposal by clicking on “Create event - Important! Select the Virtualisation and IaaS track (on the “General” tab) - Provide the title of your talk (“Event title” in the “General” tab) - Provide a 250-word description of the subject of the talk and the intended audience (in the “Abstract” field of the “Description” tab) - Provide a rough outline of the talk or goals of the session (a short list of bullet points covering topics that will be discussed) in the “Full description” field in the “Description” tab Contact For questions w.r.t. the Virtualisation and IaaS DevRoom at FOSDEM'14, please contact the organizers via fosdem14-virt-and-iaas-devr...@googlegroups.com (or via https://groups.google.com/forum/#!forum/fosdem14-virt-and-iaas-devroom). ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] vdsmd seg fault
So, just an update... I upgraded to Ovirt 3.3.0.1 today and I have the latest libvirt. I *THINK* the issue may be gone, but I will have to do a little more testing. Dan On 10/18/2013 11:15 AM, Dan Ferris wrote: That did work. vdsmd decided it would start again. Dan On 10/17/2013 3:15 PM, Jason Brooks wrote: - Original Message - From: Dan Ferris dfer...@prometheusresearch.com To: users@ovirt.org users@ovirt.org Sent: Tuesday, October 15, 2013 9:24:44 AM Subject: [Users] vdsmd seg fault I updated to the latest Fedora 19 on two test servers, and now vdsmd will not start. Systedctl says this: dsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) Active: failed (Result: exit-code) since Mon 2013-10-14 12:31:30 EDT; 23h ago Process: 1788 ExecStart=/lib/systemd/systemd-vdsmd start (code=exited, status=139) Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 ask_user_info() Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 client step 2 Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 ask_user_info() Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 make_client_response() Oct 14 12:31:30 rs0-ovirt0.rexdb.us python[1862]: DIGEST-MD5 client step 3 Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd-vdsmd[1788]: /lib/systemd/systemd-vdsmd: line 185: 1862 Segmentation fault $VDSM_TOOL nwfilter Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd-vdsmd[1788]: vdsm: Failed to define network filters on libvirt[FAILED] Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd[1]: vdsmd.service: control process exited, code=exited status=139 Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd[1]: Failed to start Virtual Desktop Server Manager. Oct 14 12:31:30 rs0-ovirt0.rexdb.us systemd[1]: Unit vdsmd.service entered failed state. Has anyone else experienced this? I just hit this on one of my test installs. I did yum downgrade libvirt* and then vdsmd would start Jason Dan ___ 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
