- Users - oVirt List Archives

[Users] Could not login into the iscsi domain
by Saurabh 01 Oct '13

01 Oct '13

Hi guyz, I have setup my ovirt engine with NFS as datacenter storage, so the default datacenter has nfs storage. Now have created a test datacenter inside ovirt with Type = iscsi. When I try to add new storage domain to this datacenter, I am able to discover the Lun but could not log in. Any help will be much appreciated. Thanks Saurabh

2 2

Re: [Users] VMs and volumes disappearing
by Martijn Grendelman 01 Oct '13

01 Oct '13

Hi, >> I have recently set up an oVirt environment, I think in a pretty >> standard fashion, with engine 3.3 on one host, one oVirt host on a >> physical machine, both running CentOS 6.4, using NFS for all storage >> domains. > > Please provide rpm -qa on the ovirt rpms (ovirt engine). martijn@ovirt:~> rpm -qa | grep ovirt ovirt-log-collector-3.3.0-1.el6.noarch ovirt-engine-3.3.0-1.el6.noarch ovirt-host-deploy-1.1.1-1.el6.noarch ovirt-engine-cli-3.3.0.4-1.el6.noarch ovirt-engine-userportal-3.3.0-1.el6.noarch ovirt-engine-tools-3.3.0-1.el6.noarch ovirt-engine-setup-3.3.0-4.el6.noarch ovirt-engine-sdk-python-3.3.0.6-1.el6.noarch ovirt-image-uploader-3.3.0-1.el6.noarch ovirt-engine-restapi-3.3.0-1.el6.noarch ovirt-engine-webadmin-portal-3.3.0-1.el6.noarch ovirt-host-deploy-java-1.1.1-1.el6.noarch ovirt-engine-backend-3.3.0-1.el6.noarch ovirt-release-el6-8-1.noarch ovirt-iso-uploader-3.3.0-1.el6.noarch ovirt-engine-dbscripts-3.3.0-1.el6.noarch ovirt-engine-lib-3.3.0-4.el6.noarch >> Today I was playing around with snapshots, when I noticed that the >> Snapshots panel didn't show any of the snapshots I created, not even the >> 'Current - Active VM' snapshot that all VMs have. > > Not sure why this has happened. How do you know that snapshot > creation was completed? Did you look at the events tab? (Asking to be > sure) engine.log will be quite helpful here. I find engine.log somewhat hard to read, to be honest, and documentation is hard to find, but I think I found some clues. I tried to create 4 snapshots of a certain VM, 2 of which completed normally and 2 of which failed: "Failed with VDSM error SNAPSHOT_FAILED and code 48" However, what I find most upsetting, is that the VMs that disappeared were not the subject of my experiments. I was creating snapshots of a single VM, and the VMs that disappeared were unrelated. As a matter of fact, the VM I was experimenting with IS THE ONLY ONE that survived. By the way, the Snapshots panel has been displaying snapshots correctly for a while, but when I logged in this morning, it appeared empty again, for all VMs. Is there anything I can check to see what causes this? >> Not sure what to do, I decided to restart the ovirt-engine process. >> >> When I logged back on to the administrator panel, I was shocked to >> see 2endWith of my 4 VMs completely missing from the inventory. I >> haven't been able to find back a single trace of either machine, >> neither in the portal nor on disk. It seems like they never >> existed. The storage of both VMs seems to be erased from the data >> domain. > Not sure why storage domain was erased. About Vms disappeared - there > were previous discussions on that at users(a)ovirt.org. In a nutshell, > due to a bug (that was already fixed) prior to the restart you might > have had records at the table that contained value of > "empty guid" (a string in UUID format with only 0 and - ) at the > vdsm_task_id_column. This means that the task is not associated with > a real SPM task, and when the engine restarts, if for a given flow > (let's say - snapshot creation) there are tasks with such > vdsm_task_id, the flow will end with failure. For some flows , > ending with failure means erasing the vm (for example - real failure > of importing a vm). By the way, similar issue can probably occur with > disks as well, as there are flows that run async tasks that deal with > disks. I think I have an idea about what happended now. The 2 disappeared VMs have been imported into oVirt using virt-v2v. The 3rd one that's now missing a disk volume was not, but I have been playing with storage migration in the past. Yesterday's engine.log seems to suggest, that all of these tasks (importing the 2 VMs and trying to move a volume) have been restarted immediately after restarting Engine. After failure, the VMs and volume were removed. It seems to fit the above description of the bug. So... What can I do to prevent this from happening again? Should I periodically check the 'async_tasks' table for anomalies? Is there a bugfix I can apply, or should I wait for a new release of oVirt? If the latter, when is that expected to happen? Thanks, Martijn.

2 1

[Users] Ovirt guest agent for 3.2 el6
by noc 01 Oct '13

01 Oct '13

Is it possible to add an ovirt-guest-agent-1.0.8-el6.rpm to the ovirt 3.2 repository? I'm asking because I tried the ovirt-guest-agent installation on a VM by slightly modifying the repo file to point to the 3.3 directory and the dependencies that were used were only from epel. Regards, Joop

5 8

[Users] VMs and volumes disappearing
by Martijn Grendelman 30 Sep '13

30 Sep '13

Hi, I have recently set up an oVirt environment, I think in a pretty standard fashion, with engine 3.3 on one host, one oVirt host on a physical machine, both running CentOS 6.4, using NFS for all storage domains. Today I was playing around with snapshots, when I noticed that the Snapshots panel didn't show any of the snapshots I created, not even the 'Current - Active VM' snapshot that all VMs have. Not sure what to do, I decided to restart the ovirt-engine process. When I logged back on to the administrator panel, I was shocked to see 2 of my 4 VMs completely missing from the inventory. I haven't been able to find back a single trace of either machine, neither in the portal nor on disk. It seems like they never existed. The storage of both VMs seems to be erased from the data domain. A 3rd VM is down and refuses to start: "Exit message: Volume 337a410f-1598-4a7f-9afd-c0160c329563 is corrupted or missing." and in vdsm.log on the host: OSError: [Errno 2] No such file or directory: '/rhev/data-center/5849b030-626e-47cb-ad90-3ce782d831b3/d523a48d-7a34-4bb0-9d48-2092934af816/images/e803ad34-94e5-4180-b26f-7271bfca5923/337a410f-1598-4a7f-9afd-c0160c329563' So it seems something is seriously f*cked up. Now what? Any ideas what may have caused this? And more importantly, how do I prevent something like this from happening again? Perhaps a needless addition, but I am very scared to host anything remotely important on oVirt now. Regards, Martijn.

2 1

[Users] Unable to Resize VM Disk in oVirt 3.3 (Upgraded from 3.2)
by H. Haven Liu 30 Sep '13

30 Sep '13

Hello, I upgraded our installation of oVirt from 3.2 to 3.3, and one of the features I was looking forward to was the ability to resize VM disk. However, it appears that the feature is still not available to me. I selected the "Virtual Machines" tab, selected a VM, selected the "Disks" sub-tab, and selected a disk; but the "Edit" button is grayed out. The disk status is "OK" and the VM status is "Up". Help is appreciated.

3 5

[Users] API vm.statistics : memory.used value when changing balloon of VM
by Hervé Leclerc 30 Sep '13

30 Sep '13

Hello Context : oVirt Engine Version: 3.3.0-4.el6 Hypervisor VDSM : vdsm.x86_64 - 4.12.1-2.el6 A vm : - Memory Size : 1024 Mo - Physical Memory Guaranteed : 128 Mo ;) - Memory balloon device enabled the vm is running with nearly no activity to have a constant memory used Testcase 1 : Initial run No change to the balloon Total Memory = Balloon 1024 Mo Data from vdsClient getVmStats balloonInfo = {'balloon_max': '1048576', 'balloon_min': '131072', 'balloon_target': '1048576', 'balloon_cur': '1048576'} memoryStats = {'swap_out': '0', 'majflt': '0', 'mem_free': '920308', 'swap_in': '0', 'pageflt': '7', 'mem_total': '1020576', 'mem_unused': '863500'} Here : mem_total - mem_unused = 157076 correct Data get from api (REST or Python : statistics.'memory.used') Memory used 128849018.0 = 123 Mo -------------------------------------------------------------- If i modify the balloon by the command vdsClient setBalloonTarget 524288 (512*1024) i got vds balloonInfo = {'balloon_max': '1048576', 'balloon_min': '131072', 'balloon_target': '524288', 'balloon_cur': '524288'} memoryStats = {'swap_out': '0', 'majflt': '0', 'mem_free': '396044', 'swap_in': '0', 'pageflt': '7', 'mem_total': '496288', 'mem_unused': '339228'} mem_total - mem_unused = 157076 correct value API.statistics Memory used = 665719930.0 = 635 Mo ==> (512+123) -------------------------------------------------------------- Setting a balloon to 262144 (256*1024) balloonInfo = {'balloon_max': '1048576', 'balloon_min': '131072', 'balloon_target': '262144', 'balloon_cur': '262144'} memoryStats = {'swap_out': '0', 'majflt': '0', 'mem_free': '133916', 'swap_in': '0', 'pageflt': '6', 'mem_total': '234144', 'mem_unused': '76224'} mem_total - mem_unused = correct value API.statistics: Memory used = 934155386.0 = 891 Mo (768+123) To get the correct value from the api i need to fdo [ (Memory Used/1024)- (Balloon Max - Balloon Current) ] / 1024 ------------- Of course display in manager is also wrong No Balloon parameter modified http://screencast.com/t/rGhKJgeB2ol Balloon 512 http://screencast.com/t/L7geTfnI Balloon 256 http://screencast.com/t/8jBllKXtGt7 Should we consider this as a bug ? Do you plan to change the formula to compupte the memory used ? Regards Hervé Leclerc CTO Alter Way 1, rue royale 9 ème étage 92210 St Cloud +33 1 78152407 +33 6 83979598 <http://www.alterway.fr/signatures/url/1>

2 1

[Users] ovirt-guest-agent for Windows
by Liviu Elama 30 Sep '13

30 Sep '13

hi I've been googling for a couple of days now trying to find the ovirt-guest-agent for windows. I have found a few references to rhevm having the tools iso but nothing on ovirt. Is there a guest tools iso for ovirt as well? Cheers Liviu

6 10

[Users] /api/vms Rest API 500 ERROR After upgrade to 3.3
by Matt . 30 Sep '13

30 Sep '13

Hi All, I am facing the following problem: After upgrading to 3.3 the REST API doesn't show the VM's anymore from (one) DC. https://bugzilla.redhat.com/show_bug.cgi?id=1011489 I made a bugreport for this but no status so far. Has anyone seen the same ? Cheers, Matt

1 0

[Users] Export Domain & Upgrade
by Nicholas Kesick 29 Sep '13

29 Sep '13

--_272d8d1f-e015-441a-98fc-e40fecdaa7c2_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable This is the first time I've run through an 'upgrade'=2C so I'm very new to = export domains=2C and I'm having some trouble getting one connected to 3.3.= I had hoped to add this to the wiki=2C but it hasn't been as straightforwa= rd as I thought. On my oVirt 3.2 install=2C I created a NFS export (/var/lib/exports/DAONE) = and exported my VMs to it. I created a tarball of everything in DAONE=2C an= d then formatted the system and installed Fedora 19=2C and then oVirt 3.3. = Created the NFS resource (/var/lib/exports/DAONE)=2C extracted the tarball= =2C and followed these directions to clear the storage domain. However when= I try to add it=2C the webadmin reports the following error: "Error while executing action New NFS Storage Domain: Error in creating a= =0A= Storage Domain. The selected storage path is not empty (probably =0A= contains another Storage Domain). Either remove the existing Storage =0A= Domain from this path=2C or change the Storage path)." Any suggestions? I wonder if anything changed for 3.3 that need to be in th= e instructions? I also tried making another export domain (/var/lib/exports/export) and dum= ping everything into the UUID under that=2C but no VMs showed up to import. #showmount -e f19-ovirt.mkesick.net Export list for f19-ovirt.mkesick.net: /var/lib/exports/storage 0.0.0.0/0.0.0.0 /var/lib/exports/iso 0.0.0.0/0.0.0.0 /var/lib/exports/export 0.0.0.0/0.0.0.0 /var/lib/exports/DAONE 0.0.0.0/0.0.0.0 [root@f19-ovirt dom_md]# cat metadata CLASS=3DBackup DESCRIPTION=3DDaOne IOOPTIMEOUTSEC=3D1 LEASERETRIES=3D3 LEASETIMESEC=3D5 LOCKPOLICY=3D LOCKRENEWALINTERVALSEC=3D5 MASTER_VERSION=3D0 POOL_UUID=3D REMOTE_PATH=3Dlocalhost:/var/lib/exports/DAONE ROLE=3DRegular SDUUID=3D8e4f6fbd-b635-4f47-b113-ba146ee1c0cf TYPE=3DNFS VERSION=3D0 = --_272d8d1f-e015-441a-98fc-e40fecdaa7c2_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'>This is the first time I've run = through an 'upgrade'=2C so I'm very new to export domains=2C and I'm having= some trouble getting one connected to 3.3. I had hoped to add this to the = wiki=2C but it hasn't been as straightforward as I thought. On my oV= irt 3.2 install=2C I created a NFS export (/var/lib/exports/DAONE) and expo= rted my VMs to it. I created a tarball of everything in DAONE=2C and then f= ormatted the system and installed Fedora 19=2C and then oVirt 3.3. Created = the NFS resource (/var/lib/exports/DAONE)=2C extracted the tarball=2C and <= a href=3D"http://www.ovirt.org/How_to_clear_the_storage_domain_pool_config_= of_an_exported_nfs_domain">followed these directions</a> to clear the stora= ge domain. However when I try to add it=2C the webadmin reports the followi= ng error: "Error while executing action New NFS Storage Domain: Erro= r in creating a=0A= Storage Domain. The selected storage path is not empty (probably =0A= contains another Storage Domain). Either remove the existing Storage =0A= Domain from this path=2C or change the Storage path)." Any suggestio= ns? I wonder if anything changed for 3.3 that need to be in the instruction= s? I also tried making another export domain (/var/lib/exports/expor= t) and dumping everything into the UUID under that=2C but no VMs showed up = to import. #showmount -e f19-ovirt.mkesick.net Export list for f1= 9-ovirt.mkesick.net: /var/lib/exports/storage 0.0.0.0/0.0.0.0 /var/li= b/exports/iso&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B 0.0.0.0/0.0.0.0 /var/lib/e= xports/export&nbsp=3B 0.0.0.0/0.0.0.0 /var/lib/exports/DAONE&nbsp=3B&nbs= p=3B 0.0.0.0/0.0.0.0 [root@f19-ovirt dom_md]# cat metadata CLASS= =3DBackup DESCRIPTION=3DDaOne IOOPTIMEOUTSEC=3D1 LEASERETRIES=3D3<= br>LEASETIMESEC=3D5 LOCKPOLICY=3D LOCKRENEWALINTERVALSEC=3D5 MASTE= R_VERSION=3D0 POOL_UUID=3D REMOTE_PATH=3Dlocalhost:/var/lib/exports/D= AONE ROLE=3DRegular SDUUID=3D8e4f6fbd-b635-4f47-b113-ba146ee1c0cf = TYPE=3DNFS VERSION=3D0 </div></body> </html>= --_272d8d1f-e015-441a-98fc-e40fecdaa7c2_--

3 3

Re: [Users] could not add iscsi disk in ovirt.
by Dafna Ron 29 Sep '13

29 Sep '13

you don't have to reconfigure engine to create iscsi pool. you can create multiple pools, the only limitation is that you will need a host for the each of the DCs. but you can move one host from one DC to another... so if you have 2 hosts just create a new DC and move one of the hosts there. I think that the direct lun is only for iscsi and fiber but I can give you a 100% certainty answer on Monday. I don't think its supported for NFS... I can check for you on Monday for sure. On 09/27/2013 03:28 PM, Saurabh wrote: > On 27/09/13 19:52, Dafna Ron wrote: >> wait :) >> >> the first screen shot was of local storage and internal disk type - >> not related at all to the direct lun feature. >> >> the second screen shot is for iscsi storage pool. >> it shows a current connected lun that you have. >> >> try this: >> >> create a new target lun. >> log in to the webadmin -> disks tab -> new disk >> select the Default DC (which is your iscsi storage type) -> expend >> the "discover tartest" >> put in your storage server (where you created the lun) -> discover >> you should than see a list of targets -> log in >> select the target and press OK. >> >> >> On 09/27/2013 03:11 PM, Saurabh wrote: >>> On 27/09/13 19:14, Dafna Ron wrote: >>>> the output is empty in both your outpit and the logs. >>>> >>>> This is the part in the log that shows that you do not have any >>>> devices: return: [] >>>> >>>> when you create a new disk and select the NFS DC- can you please >>>> send me the screen shot of that? >>>> >>>> >>>> On 09/27/2013 02:41 PM, Saurabh wrote: >>>>> On 27/09/13 18:40, Dafna Ron wrote: >>>>>> I am not sure direct lun will be supported for an NFS pool... can >>>>>> you try the same from iscsi pool? >>>>>> >>>>>> is this lun being used somewhere else or did you create a new one? >>>>>> you can run vdsClient -s 0 getDeviceList to see the list of the >>>>>> available luns and if the status is free or not. >>>>>> (it should also in the logs (engine and vdsm) when you discover >>>>>> the luns from the webadmin. >>>>>> >>>>>> >>>>>> On 09/27/2013 01:43 PM, Saurabh wrote: >>>>>>> >>>>>>> Hi guys, I am running ovirt with NFS as storage pool. Everything >>>>>>> is working quite fine for me. The only problem is I could not >>>>>>> add the a new iscsi disk in Disk tab. When I go to the Disk tab >>>>>>> there is an option of adding new disk from internal storage and >>>>>>> another option is add External (Direct Lun). When I opt for the >>>>>>> External (Direct LUN), I am able to discover the Lun but could >>>>>>> not log in to that lun using the ovirt web console. Whereas when >>>>>>> I try to login to that lun using the isciadm in command line I >>>>>>> am able to login. Any help?? >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Users mailing list >>>>>>> Users(a)ovirt.org >>>>>>> http://lists.ovirt.org/mailman/listinfo/users >>>>>> >>>>>> >>>>> I have created a new Lun for this purpose only and it is not being >>>>> used anywhere. >>>>> In order to try an iscsi pool I will have to reconfigure the >>>>> engine, because during the engine setup I opted for nfs. >>>>> >>>>> This is the output when I run this command. >>>>> >>>>> [root@ovirt ~]# vdsClient -s 0 getDeviceList >>>>> [] >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> this is log snippet from engine.log when I discover and try to >>>>> login to that lun. >>>>> >>>>> >>>>> ################################################################################################# >>>>> >>>>> 013-09-27 14:34:55,592 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] >>>>> (ajp--127.0.0.1-8702-11) START, >>>>> DiscoverSendTargetsVDSCommand(HostName = 192.168.100.59, HostId = >>>>> 168842b9-071b-4c64-a22d-07ae1e63830b, connection={ id: null, >>>>> connection: 192.168.100.160, iqn: null, vfsType: null, >>>>> mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: >>>>> null };), log id: 2e12b97 >>>>> 2013-09-27 14:34:55,653 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] >>>>> (ajp--127.0.0.1-8702-11) FINISH, DiscoverSendTargetsVDSCommand, >>>>> return: [{ id: null, connection: 192.168.100.160, iqn: >>>>> iqn.2013.26.ovirt.techblue.lv001, vfsType: null, mountOptions: >>>>> null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };], log >>>>> id: 2e12b97 >>>>> 2013-09-27 14:36:25,877 INFO >>>>> [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand] >>>>> (ajp--127.0.0.1-8702-2) Running command: >>>>> ConnectStorageToVdsCommand internal: false. Entities affected : >>>>> ID: aaa00000-0000-0000-0000-123456789aaa Type: System >>>>> 2013-09-27 14:36:25,880 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] >>>>> (ajp--127.0.0.1-8702-2) START, >>>>> ConnectStorageServerVDSCommand(HostName = 192.168.100.59, HostId = >>>>> 168842b9-071b-4c64-a22d-07ae1e63830b, storagePoolId = >>>>> 00000000-0000-0000-0000-000000000000, storageType = ISCSI, >>>>> connectionList = [{ id: null, connection: 192.168.100.160, iqn: >>>>> iqn.2013.26.ovirt.techblue.lv001, vfsType: null, mountOptions: >>>>> null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log >>>>> id: 5fca13a4 >>>>> 2013-09-27 14:36:26,012 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] >>>>> (ajp--127.0.0.1-8702-2) FINISH, ConnectStorageServerVDSCommand, >>>>> return: {00000000-0000-0000-0000-000000000000=0}, log id: 5fca13a4 >>>>> 2013-09-27 14:36:26,098 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (ajp--127.0.0.1-8702-12) >>>>> START, GetDeviceListVDSCommand(HostName = 192.168.100.59, HostId = >>>>> 168842b9-071b-4c64-a22d-07ae1e63830b, storageType=ISCSI), log id: >>>>> 20fb893b >>>>> 2013-09-27 14:36:29,376 INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (ajp--127.0.0.1-8702-12) >>>>> FINISH, GetDeviceListVDSCommand, return: [], log id: 20fb893b >>>>> >>>>> ###################################################################################################### >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> Here I am sending you the two screenshots, one is when I am adding >>> the disk from the Local-storage that is NFS, and another is the >>> Direct lun. >>> You can see that I am able to discover it but could not log into it. >>> >> >> > ok so there is no means we can use an iscsi disk in a Data center > whoose default storage is NFS? -- Dafna Ron

3 2