- Users - oVirt List Archives

[Users] mark VM to start on boot
by Jim Kinney 20 Jan '13

20 Jan '13

How do I mark a VM to startup if a node fails? 2 hosts in cluster, windows domain controller on one host, backup on second host. Both are marked high priority. "Bad Things" happen and both hosts get rebooted. I want those domain controllers to automatically restart. I'm assuming the failure of the hosts did not knock down the manager. (I have them on separate floors, power, etc). -- -- James P. Kinney III * *Every time you stop a school, you will have to build a jail. What you gain at one end you lose at the other. It's like feeding a dog on his own tail. It won't fatten the dog. - Speech 11/23/1900 Mark Twain * http://electjimkinney.org http://heretothereideas.blogspot.com/ *

2 1

[Users] Move virtual hard disk images between hosts - Howto
by Adrian Gibanel 19 Jan '13

19 Jan '13

------=_Part_211_15072353.1358593952028 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi,=20 I've written a howto on how to move, a better name would be to copy, virtua= l hard disk images between hosts.=20 It has been useful for me in the scenario where I need to move them between= different datacenters. I still don't understand the formal ways you have t= o move hard disks between hosts of the same/different data resource, cluste= r and datacenters so I do it manually.=20 Anyways I wanted you to take a look at it:=20 http://www.ovirt.org/User:Adrian15/Virtual_Machines_Images_Raw_Management= =20 And tell me:=20 * When it would work, when not.=20 * Pieces of advice.=20 * And if I'm missing something like, I don't know, having to edit some valu= es at the database.=20 I think that it will be also useful for some kind of restore on disaster sc= enarios although I'm not sure.=20 I've also used some tricks to deal with sparse files without having to wait= for ages.=20 --=20 Adri=C3=A1n Gibanel=20 I.T. Manager=20 +34 675 683 301=20 www.btactic.com=20 Ens podeu seguir a/Nos podeis seguir en:=20 i=20 Abans d=C2=B4imprimir aquest missatge, pensa en el medi ambient. El medi am= bient =C3=A9s cosa de tothom. / Antes de imprimir el mensaje piensa en el m= edio ambiente. El medio ambiente es cosa de todos.=20 AVIS:=20 El contingut d'aquest missatge i els seus annexos =C3=A9s confidencial. Si = no en sou el destinatari, us fem saber que est=C3=A0 prohibit utilitzar-lo,= divulgar-lo i/o copiar-lo sense tenir l'autoritzaci=C3=B3 corresponent. Si= heu rebut aquest missatge per error, us agrairem que ho feu saber immediat= ament al remitent i que procediu a destruir el missatge .=20 AVISO:=20 El contenido de este mensaje y de sus anexos es confidencial. Si no es el d= estinatario, les hacemos saber que est=C3=A1 prohibido utilizarlo, divulgar= lo y/o copiarlo sin tener la autorizaci=C3=B3n correspondiente. Si han reci= bido este mensaje por error, les agradecer=C3=ADamos que lo hagan saber inm= ediatamente al remitente y que procedan a destruir el mensaje .=20 ------=_Part_211_15072353.1358593952028 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><= div style=3D'font-family: arial,helvetica,sans-serif; font-size: 10pt; colo= r: #000000'>Hi,   I've written a howto on how to move, a better= name would be to copy, virtual hard disk images between hosts. It has b= een useful for me in the scenario where I need to move them between differe= nt datacenters. I still don't understand the formal ways you have to move h= ard disks between hosts of the same/different  data resource, cluster = and datacenters so I do it manually.   Anyways I wanted you to = take a look at it: http://www.ovirt.org/User:Adrian15/Virtual_Machin= es_Images_Raw_Management And tell me: * When it would work, when = not. * Pieces of advice. * And if I'm missing something like, I don't= know, having to edit some values at the database. I think that it w= ill be also useful for some kind of restore on disaster scenarios although = I'm not sure. I've also used some tricks to deal with sparse files w= ithout having to wait for ages. -- <div>= <a style=3D"color: rgb(0, 0, = 0);" href=3D"http://www.btactic.com/"></font= ></a>Adri=C3=A1n Gibanel I= .T. Manager +34 675 683 301 <a href=3D"http://btactic.com/">www.b= tactic.com</a> <img src=3D"http://www.btactic.com/signaturabtacti= cmail/btacticsignature.png" style=3D"border-width: 0px;"> Ens podeu seguir a/Nos podeis seguir en: <a href=3D"http://www.facebook.com/pages/btactic/118651634826= 400?v=3Dapp_9953271133"><img style=3D"border: 0pt none;" src=3D"http://www.= btactic.com/wp-content/themes/btactic/img/facebookfoot.jpg"></a> i <a href= =3D"http://twitter.com/btactic"><img style=3D"border: 0pt none;" src=3D"htt= p://www.btactic.com/wp-content/themes/btactic/img/twitterfoot.jpg"></a></sp= an> </f= ont><div>Abans d=C2=B4imp= rimir aquest missatge, pensa en el medi ambient. El medi ambient =C3=A9s cosa de= =20 tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio=20 ambiente es cosa de todos. = AVIS: El contingut d'aquest missatge i els seus annexos =C3=A9s confidencial. Si = no en sou el destinatari, us fem saber que est=C3=A0 prohibit utilitzar-lo,=20 divulgar-lo i/o copiar-lo sense tenir l'autoritzaci=C3=B3 corresponent. Si heu rebut=20 aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge. AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que est=C3=A1 prohibido utilizarlo,=20 divulgarlo y/o copiarlo sin tener la autorizaci=C3=B3n correspondiente. Si han recibid= o este mensaje por error, les agradecer=C3=ADamos que lo hagan saber=20 inmediatamente al remitente y que procedan= a destruir el mensaje. </div> </div></div></body></html> ------=_Part_211_15072353.1358593952028--

1 0

Re: [Users] Thin provisioning extending while "Make template" still a bug?
by Maor Lipchuk 19 Jan '13

19 Jan '13

Hi Adrian, Sorry for the late respond. Please see inline comments, and feel free if there are any more questions, or other issues which you want us to address to. p.s. Since some of the responds were in different threads, I gathered all of them to this email. > 3) About the attached logs the virtual machine made from template was > finally made at: > 2012/12/22 17:21 > Logs are from 16:17 to 17:21 aproximately and I might reuse them to > ask why it takes so long to make the virtual machine while checking > the storage image at /home/storage (its size) it would seem that the > copy has finished. > I think that the "Make vm from template" task started about 30 > minutes or 40 minutes before it being finished. Well, that's the > average time it takes for me. Since you are creating a server the default behaviour is to clone your disks, which means engine calls copyImage to the SPM. >From what I saw in the logs your template have two disks, which one of them is 1920 GB, this is why it took 30 minutes to copy it. If you want your copy to be faster, you can change the default in the resource allocation tab to use thin instead of clone when you add a new server. although, take in notice that when you will use thin provisioning, the server will be based on the template and you will not be able to remove the template until the VM will be removed. On 12/25/2012 09:34 PM, Adrian Gibanel wrote:> I've described the "Create template from VM" extending bug (the one I > was told in irc) but I've attached the "Create VM from template" logs. > > If there's also a bug about "Create VM from template" being extended > then it's useful. > If it's not I'll try to recreate a "Create template from VM" task and > attach the logs. > > Sorry about the confusion. If you can still reproduce this scenario when you create a template with wrong provisioning, please attach the logs of it. On 12/24/2012 01:51 AM, Adrian Gibanel wrote:> I've just noticed that I made a typo. > This is the right template disk allocation policy table > (The fix is that second hard disk is preallocated instead of being Thin Prov) > > Alias | Virtual Size | Allocation | Target > First | 1920 GB | Thin Prov | local_storage > Seco | 1 GB | Preallocat | local_storage I took a look in your logs, and it seems that when you create a VM from template the passing arguments are preallocated for one image and sparse for the other, so it seems that this is fit with the allocation policy table you sent. > > ----- Mensaje original ----- > >> De: "Adrian Gibanel" <adrian.gibanel(a)btactic.com> >> Para: "users" <users(a)ovirt.org> >> Enviados: Lunes, 24 de Diciembre 2012 0:45:24 >> Asunto: Re: [Users] Thin provisioning extending while "Make template" >> still a bug? > >> 1) So... the mentioned bug does exist or am I just experiencing a >> normal oVirt usage (Making a vm from template with thin provisioning >> works ok without extending)? > >> 2) About template disk allocation policy... > >> When I create a new server based on template and I click on: >> Resource Allocation tab: > >> Template Provisioning: Clone > >> Alias | Virtual Size | Allocation | Target >> First | 1920 GB | Thin Prov | local_storage >> Seco | 1 GB | Thin Prov | local_storage > Regards, Maor

2 1

[Users] hierarchy map of ovirt environment
by Jiri Belka 19 Jan '13

19 Jan '13

Hello, in vSphere you can have 'views' like Storage views, Network views... Example: http://i.techrepublic.com.com/blogs/sept-2010-virtualizationtips-tip4-figc.… This is very useful, typical scenario is when delivery manager asks sysadmins about potential impact on VMs when a scheduled update of a switch/storage box goes wrong. It's easy in vSphere, just check 'views' and you will see it. Something like this possible in oVirt? It would be nice to have it as 'map', also as 'result' of searching, something like... vms: network.name = foo and network.risk = down jbelka

1 0

[Users] Settings lost after node reboot
by Nicolas Ecarnot 18 Jan '13

18 Jan '13

Hi, Migration failed due to a lack of an iptables rules about tls > # libvirt tls > -A INPUT -p tcp --dport 16514 -j ACCEPT I added it in /etc/sysconfig/iptables and migration worked. After a reboot, this rule is lost, as well as some setting I added in /etc. I see the the nodes have very specific mouting strategies, and/or read only architecture. I'm not sure I want to become an expert about why and how it's done, but I'd be glad if someone just tells me where I have to write my settings in order them to resist node reboot? Thank you. -- Nicolas Ecarnot

2 2

Re: [Users] Fwd: API usage - 3.1
by Michael Pasternak 17 Jan '13

17 Jan '13

Hi Tom, > -------- Original Message -------- > Subject: [Users] API usage - 3.1 > Date: Fri, 11 Jan 2013 16:27:03 +0000 > From: Tom Brown <tom(a)ng23.net> > To: users <users(a)ovirt.org> > > Trying to get going adding VM's via the API and so far have managed to get quite far - I am however facing this > > vm_template = """<vm> > <name>%s</name> > <cluster> > <name>Default</name> > </cluster> > <template> > <name>Blank</name> > </template> > <vm_type>server</vm_type> > <memory>536870912</memory> > <os> > <boot dev="hd"/> > </os> > </vm>""" > > The VM is created but the type ends up being a desktop and not a server - > > What did i do wrong? the name of the element is <type> (not <vm_type>). > > thanks > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- Michael Pasternak RedHat, ENG-Virtualization R&D

3 7

[Users] oVirt features survey - please participate!
by Dave Neary 17 Jan '13

17 Jan '13

Hi everyone, After the mammoth thread these past few days on what you would like to see next from oVirt, Itamar and I have put together a list of all of the features you requested and made a survey to help us understand a bit more which features are more important to you, and the way in which you use oVirt. https://www.surveymonkey.com/s/oVirtFeatures It will take you between 1 and 3 minutes to participate in this survey, and help prioritise efforts for the next version or two of oVirt. If you know of people who are oVirt users, but who are not on this mailing list, please feel free to forward this link on to them! Also, let me remind you that you can see first hand what is coming in the upcoming oVirt 3.2 release and talk to the people behind oVirt during the oVirt Workshop in NetApp HQ, Sunnyvale, California next week. Registration is still open for another day or so, and we have about 10 places still available. Sign up now! http://www.ovirt.org/NetApp_Workshop_January_2013 Regards, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13

1 1

[Users] Fail to connect to an iSCSI Eq. LUN
by Nicolas Ecarnot 17 Jan '13

17 Jan '13

Hi, As a beginner, I'm reading again and again, but I'm not sure of the best way to do : Through the oVirt web manager, I'm trying to create an iSCSI storage domain. On my Equalogic SAN, I've created a volume with no restriction access (for the time being). I have two hypervisors on which I'm quite sure my network config is good enough for now (two nics bonded for the management, and 2 nics bonded for the iscsi). Everything is pinging ok. Networking is not an issue. In the ovirt web manager, I try to create the very first storage domain, of iscsi type of course. I choose one of the node, then the iscsi discovery + login is working fine. I can see my Equalogic volume, I'm checking it, and saving with the OK button, and I get the following error : > "Error while executing action New SAN Storage Domain: Physical device > initialization failed. Check that the device is empty. Please remove > all files and partitions from the device." Not very interesting, but the node log file is more instructive : > Thread-2767::INFO::2013-01-16 > 13:35:57,064::logUtils::37::dispatcher::(wrapper) Run and protect: > createVG(vgname='7becc578-a94b-41f4-bbec-8df5fe9f46c0', > devlist=['364ed2ad5297bb022fd0ee5ba36ad91a0'], options=None) > > Thread-2767::DEBUG::2013-01-16 > 13:35:57,066::__init__::1249::Storage.Misc.excCmd::(_log) '/usr/bin/sudo > -n /sbin/lvm pvcreate --config " devices { preferred_names = > [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 > disable_after_error_count=3 filter = [ > \\"a%3600508e000000000ec7b6d8dea602b0e|364ed2ad5297bb022fd0ee5ba36ad91a0%\\", > \\"r%.*%\\" ] } global { locking_type=1 prioritise_write_locks=1 > wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " > --metadatasize 128m --metadatacopies 2 --metadataignore y > /dev/mapper/364ed2ad5297bb022fd0ee5ba36ad91a0' (cwd None) > > Thread-2767::DEBUG::2013-01-16 > 13:35:57,147::__init__::1249::Storage.Misc.excCmd::(_log) FAILED: <err> > = " Can't open /dev/mapper/364ed2ad5297bb022fd0ee5ba36ad91a0 > exclusively. Mounted filesystem?\n"; <rc> = 5 > > Thread-2767::DEBUG::2013-01-16 > 13:35:57,149::__init__::1249::Storage.Misc.excCmd::(_log) '/usr/bin/sudo > -n /sbin/lvm pvs --config " devices { preferred_names = > [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 > disable_after_error_count=3 filter = [ > \\"a%3600508e000000000ec7b6d8dea602b0e|364ed2ad5297bb022fd0ee5ba36ad91a0%\\", > \\"r%.*%\\" ] } global { locking_type=1 prioritise_write_locks=1 > wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " -o > vg_name,pv_name --noheading > /dev/mapper/364ed2ad5297bb022fd0ee5ba36ad91a0' (cwd None) > > Thread-2767::DEBUG::2013-01-16 > 13:35:57,224::__init__::1249::Storage.Misc.excCmd::(_log) FAILED: <err> > = ' No physical volume label read from > /dev/mapper/364ed2ad5297bb022fd0ee5ba36ad91a0\n Failed to read physical > volume "/dev/mapper/364ed2ad5297bb022fd0ee5ba36ad91a0"\n'; <rc> = 5 > > Thread-2767::ERROR::2013-01-16 > 13:35:57,226::task::853::TaskManager.Task::(_setError) > Task=`1c5b8931-0085-489c-8962-ff5cc1323dc7`::Unexpected error > > Traceback (most recent call last): > File "/usr/share/vdsm/storage/task.py", line 861, in _run > File "/usr/share/vdsm/logUtils.py", line 38, in wrapper > File "/usr/share/vdsm/storage/hsm.py", line 1680, in createVG > File "/usr/share/vdsm/storage/lvm.py", line 788, in createVG > File "/usr/share/vdsm/storage/lvm.py", line 631, in _initpvs > PhysDevInitializationError: Failed to initialize physical device: > ("found: {} notFound: ('/dev/mapper/364ed2ad5297bb022fd0ee5ba36ad91a0',)",) I guess the interesting part is : > Can't open /dev/mapper/364ed2ad5297bb022fd0ee5ba36ad91a0 exclusively. Mounted filesystem? On any node, this partition is not mounted. But I have set up the access to this volume as "shared" on the Equalogic SAN, not knowing whether I should do so? I see both nodes connected on the same volume. I tried to remove this permit, but it didn't help. I also found Redhat answering such a question : > There are two ways to clear this error: > > - Remove VG from the Storage LUN using vgremove command. Run this command from one of the hypervisors. > - Clear the first 4K from the disk . Execute the following from one of the hypervisors: > > # dd if=/dev/zero of=/dev/mapper/diskname bs=4k count=1 I did try that, but with no luck. Now, two things : - Do I have to keep the access to this volume shared/allowed to all the hypervisors dedicated to this volume? - What is the problem with the pvcreate command? -- Nicolas Ecarnot

1 1

[Users] Template restore
by Alex Leonhardt 17 Jan '13

17 Jan '13

Hi All, Am having some difficulties with restoring templates - basically, currently, I'm using each new HV (hyper-visor/node) as a separate DC, now, the first host has about 5 VM templates that I need to be able to restore to the 2nd HV I installed today - however - after detaching the export domain and re-attaching (finally) to the 2nd HV, I still am unable to import the templates into the 2nd HV (remember, separate data center) as it complains that the "system" - the overall ovirt-engine - already contains templates with the same ID, if I manually fake a different ID, it complains about the name, if I manually amend the name, it wont show at all ... :\ so - how can I make the templates available to the 2nd DC to create VMs from it (this is the end goal) ... on top of it - i dont think that when importing templates, you should have to make the name unique, especially since they currently seem DC dependent, so in a different DC they should be able to have the same name; and, when restoring Templates, the system should assign new IDs to the Templates imported, and only use the originals as a verification step if the target DC is the same as the src DC. Any help would be very appreciated. Ta! Alex -- | RHCE | Senior Systems Engineer | www.vcore.co | www.vsearchcloud.com |

4 5

[Users] About ISOs
by Juan Jose 17 Jan '13

17 Jan '13

Hello everybody again, I have uploaded two isos to my ISO domain but I have had problems uploading one of they. How do I delete this iso from datacenter and system?, is there some utililty to do this, or some procedure? Many thanks in avanced, Juanjo.

2 1