- Users - oVirt List Archives

[Users] Network profile lost after host edit
by Simon Barrett 20 Jan '14

20 Jan '14

--_000_D86C48DF8800164BBE50B87623F7AC9548080D6Eln2wio001devtra_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a problem where VM network profiles are lost when editing a host. E.= G. * VM is running fine on the correct network. Network Interfaces tab= shows "nic1" and "Network Name" shows the correct network profile. * I shutdown the VM then right click and Edit. * The General settings for the node shows "nic1 <Empty>". If I then= edit config, something like increasing memory or changing CPU cores then c= lick on OK, the VM configuration is saved without a network profile. * When I boot the VM I cannot connect to it. * I then have to edit the node again configure back in the correct = network profile. Does anyone know if this is a known issue? If not, any suggestions as to ho= w I correct this so that the original network profile definition is retaine= d after an edit? Many thanks, Simon --_000_D86C48DF8800164BBE50B87623F7AC9548080D6Eln2wio001devtra_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> I have a problem where VM network profiles are lost = when editing a host. E.G.<o:p></o:p> <o:p> </o:p> <![if !supportLists]>·         <![endif]>VM is running fine on the correct network. N= etwork Interfaces tab shows “nic1” and “Network Name&#822= 1; shows the correct network profile.<o:p></o:p> <![if !supportLists]>·         <![endif]>I shutdown the VM then right click and Edit.= <o:p></o:p> <![if !supportLists]>·         <![endif]>The General settings for the node shows &#82= 20;nic1 <Empty>”. If I then edit config, something like increas= ing memory or changing CPU cores then click on OK, the VM configuration is = saved without a network profile.<o:p></o:p> <![if !supportLists]>·         <![endif]>When I boot the VM I cannot connect to it.<o= :p></o:p> <![if !supportLists]>·         <![endif]>I then have to edit the node again configure= back in the correct network profile.<o:p></o:p> <o:p> </o:p> Does anyone know if this is a known issue? If not, a= ny suggestions as to how I correct this so that the original network profil= e definition is retained after an edit?<o:p></o:p> <o:p> </o:p> Many thanks,<o:p></o:p> <o:p> </o:p> Simon<o:p></o:p> <o:p> </o:p> </div> </body> </html> --_000_D86C48DF8800164BBE50B87623F7AC9548080D6Eln2wio001devtra_--

4 11

[Users] VM Migration failed
by Edgars M. 20 Jan '14

20 Jan '14

Hi I am experiencing issues with manual VM migration. VM fails to migrate to other node in the same Cluster. Here are some relevant engine.log entries: ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-73) Rerun vm a31cfd62-26fc-4396-8a83-1aed68c7fd39. Called from vds novmnode1 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (pool-6-thread-49) Failed in MigrateStatusVDS method ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (pool-6-thread-49) Error code migrateErr and error message VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Fatal error during migration ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (pool-6-thread-49) Command MigrateStatusVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Fatal error during migration Both Engine and Node are running CentOS 6.5 x64. oVirt Engine Version: 3.3.2-1.el6. VDSM version 4.13.2-1. I restarted engine and vdsm, that did not help. Also in vdsm log file I see the following errors related to the same VM ID: Thread-27::ERROR::2014-01-17 16:37:06,271::sampling::355::vm.Vm::(collect) vmId=`a31cfd62-26fc-4396-8a83-1aed68c7fd39`::Stats function failed: <AdvancedStatsFunction _highWrite at 0x26efb58> Any hints? BR Edgars

5 20

[Users] How to Modify Network with Hosted Engine
by Andrew Lau 20 Jan '14

20 Jan '14

Hi, Now that I finally stepped through and have a working hosted engine setup (after opening numerous BZs).. How do I modify network configuration (eg. assign new VLANs to hosts), when I attempt to modify a network it gives the error: Error while executing action Setup Networks: Network is currently being used Is there a recommended way to set up these extra networks, or must all of these be not managed by the engine? Thanks, Andrew

3 7

[Users] Fwd: Disk error
by Koen Vanoppen 20 Jan '14

20 Jan '14

---------- Forwarded message ---------- From: Koen Vanoppen <vanoppen.koen(a)gmail.com> Date: 2014/1/20 Subject: Re: [Users] Disk error To: dron(a)redhat.com Status ok... 2014/1/20 Dafna Ron <dron(a)redhat.com> > and what is the snapshot/disk status in the UI? > > > > > On 01/20/2014 11:08 AM, Koen Vanoppen wrote: > >> Error while executing action: >> >> KV-virt-v2v: >> >> * Cannot remove Snapshot. Disk KV-virt-v2v_Disk2 is being moved or >> copied. >> * Cannot remove Snapshot. Disk LargeTemplate_Disk1 is being moved or >> copied. >> >> >> >> 2014/1/20 Koen Vanoppen <vanoppen.koen(a)gmail.com <mailto: >> vanoppen.koen(a)gmail.com>> >> >> >> Yes, it did. Twice actually. But I already tried that one. This is >> the result: >> >> Error while executing action: >> >> KV-virt-v2v: >> >> * Cannot remove Snapshot. Disk KV-virt-v2v_Disk2 is being moved >> or copied. >> * Cannot remove Snapshot. Disk LargeTemplate_Disk1 is being >> moved or copied. >> >> >> >> >> 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@redhat.com>> >> >> >> you said that you shut down the vm after you tried migrating? >> can you look at the vm in the UI and see if you have a >> snapshot created during the migration? >> if so, can you try to delete just the snapshot? >> >> >> >> >> >> On 01/20/2014 10:58 AM, Koen Vanoppen wrote: >> >> [root@soyuz ~]# lvs | grep >> ff674bce-aa94-4b46-9f9d-d4182eab1e49 >> Couldn't find device with uuid >> Y5m0SH-HbWl-8PNL-fGkk-oXNF-WyQk-Snhncm. >> ff674bce-aa94-4b46-9f9d-d4182eab1e49 >> f8ddd1d1-5266-493b-879b-f79c128751e2 -wi-ao--- 50,00g >> >> Maybe it's already to another hypervisor or disk domain? >> If there is a *SAVE* way to remove these two disk, tell >> me. The data on it it's not THAT important. >> >> >> >> >> 2014/1/20 Dafna Ron <dron(a)redhat.com >> <mailto:dron@redhat.com> <mailto:dron@redhat.com >> >> <mailto:dron@redhat.com>>> >> >> >> the disk ff674bce-aa94-4b46-9f9d-d4182eab1e49 does not >> exist in >> the domain - which is the master domain >> My guess that it has to do with the failed migration. >> >> can you run lvs and grep for >> ff674bce-aa94-4b46-9f9d-d4182eab1e49 >> lets see where this disk is... >> >> >> >> >> On 01/20/2014 10:44 AM, Koen Vanoppen wrote: >> >> [root@soyuz ~]# vdsClient -s 0 getStorageDomainInfo >> f8ddd1d1-5266-493b-879b-f79c128751e2 >> uuid = f8ddd1d1-5266-493b-879b-f79c128751e2 >> vguuid = i6QHH9-1fZR-HLcn-6Xuo-7jU7-66iu-iuzWfQ >> lver = 13 >> state = OK >> version = 3 >> role = Master >> pool = ['5849b030-626e-47cb-ad90-3ce782d831b3'] >> spm_id = 1 >> type = ISCSI >> class = Data >> master_ver = 1 >> name = StoragePoolEva01 >> >> Thanx for the help! >> >> >> 2014/1/20 Dafna Ron <dron(a)redhat.com >> <mailto:dron@redhat.com> <mailto:dron@redhat.com >> <mailto:dron@redhat.com>> >> <mailto:dron@redhat.com <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>>>> >> >> >> >> can you please run: >> >> vdsClient -s 0 getStorageDomainInfo >> f8ddd1d1-5266-493b-879b-f79c128751e2 >> >> >> >> On 01/20/2014 10:33 AM, Koen Vanoppen wrote: >> >> [root@soyuz ~]# vdsClient -s 0 >> getStorageDomainsList >> f3fd055b-2764-44ed-9d77-81bd58984842 >> 94de241c-bf5c-4630-9af3-7e31b902ae77 >> f8ddd1d1-5266-493b-879b-f79c128751e2 >> 50cf24a4-d1ef-4105-a9a5-b81d91339175 >> 83b1867f-4aea-400e-9ce0-efbd5add4216 >> >> (soyuz=vdsmhost3) >> >> >> 2014/1/20 Dafna Ron <dron(a)redhat.com >> <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>> >> <mailto:dron@redhat.com <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>>> >> <mailto:dron@redhat.com >> <mailto:dron@redhat.com> <mailto:dron@redhat.com >> <mailto:dron@redhat.com>> >> <mailto:dron@redhat.com <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>>>>> >> >> >> >> let's try to sift through :) >> >> can you run vdsClient -s 0 >> getStorageDomainsList? >> >> >> >> >> >> On 01/20/2014 09:52 AM, Meital >> Bourvine wrote: >> >> It seems that your setup is >> completely messed >> up. I >> see the >> following 3 errors all the time (I >> couldn't >> actually >> find the >> live storage migration error, >> since there are >> too many >> errors): >> >> Thread-118::ERROR::2014-01-20 >> 07:59:17,066::sampling::355::vm.Vm::(collect) >> vmId=`f8c6190c-b722-4fcd-af17-21572151fcef`::Stats >> function >> failed: <AdvancedStatsFunction >> _highWrite at >> 0x27b41b8> >> Traceback (most recent call last): >> File >> "/usr/share/vdsm/sampling.py", line >> 351, in collect >> statsFunction() >> File >> "/usr/share/vdsm/sampling.py", line 226, in >> __call__ >> retValue = >> self._function(*args, **kwargs) >> File "/usr/share/vdsm/vm.py", >> line 509, in >> _highWrite >> if not vmDrive.blockDev or >> vmDrive.format >> != 'cow': >> AttributeError: 'Drive' object has no >> attribute 'format' >> >> PolicyEngine::DEBUG::2014-01-20 >> 07:59:17,198::libvirtconnection::108:: >> libvirtconnection::(wrapper) >> Unknown libvirterror: ecode: 8 >> edom: 10 level: >> 2 message: >> invalid argument: cannot set >> memory higher >> than max memory >> PolicyEngine::ERROR::2014-01-20 >> 07:59:17,199::vm::4359::vm.Vm::(reportError) >> vmId=`ce626f90-41c4-4417-9e53-bf4066ad062d`::Set new >> balloon >> target failed >> Traceback (most recent call last): >> File "/usr/share/vdsm/vm.py", >> line 4371, in >> setBalloonTarget >> self._dom.setMemory(target) >> File "/usr/share/vdsm/vm.py", >> line 835, in f >> ret = attr(*args, **kwargs) >> File >> "/usr/lib64/python2.6/site-packages/vdsm/ >> libvirtconnection.py", >> line >> 76, in wrapper >> ret = f(*args, **kwargs) >> File >> "/usr/lib64/python2.6/site-packages/libvirt.py", >> line >> 1410, in setMemory >> if ret == -1: raise libvirtError >> ('virDomainSetMemory() >> failed', dom=self) >> libvirtError: invalid argument: >> cannot set memory >> higher than >> max memory >> >> Thread-51::ERROR::2014-01-20 >> 07:59:22,109::sampling::355::vm.Vm::(collect) >> vmId=`493128c0-aba9-4b38-bf18-2778b910917f`::Stats >> function >> failed: <AdvancedStatsFunction >> _highWrite at >> 0x27b41b8> >> Traceback (most recent call last): >> File >> "/usr/share/vdsm/sampling.py", line >> 351, in collect >> statsFunction() >> File >> "/usr/share/vdsm/sampling.py", line 226, in >> __call__ >> retValue = >> self._function(*args, **kwargs) >> File "/usr/share/vdsm/vm.py", >> line 513, in >> _highWrite >> self._vm._dom.blockInfo(vmDrive.path, 0) >> File "/usr/share/vdsm/vm.py", >> line 835, in f >> ret = attr(*args, **kwargs) >> File >> "/usr/lib64/python2.6/site-packages/vdsm/ >> libvirtconnection.py", >> line >> 76, in wrapper >> ret = f(*args, **kwargs) >> File >> "/usr/lib64/python2.6/site-packages/libvirt.py", >> line >> 1797, in blockInfo >> if ret is None: raise libvirtError >> ('virDomainGetBlockInfo() failed', dom=self) >> libvirtError: invalid argument: >> invalid path >> /rhev/data-center/mnt/blockSD/f8ddd1d1-5266-493b-879b- >> f79c128751e2/images/b8da8541-9a0d-4c18-8aa8-50fc6225f18a/ >> ff674bce-aa94-4b46-9f9d-d4182eab1e49 >> not assigned to domain >> >> >> ------------------------------------------------------------ >> ------------ >> >> >> >> *From: *"Koen Vanoppen" >> <vanoppen.koen(a)gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>>>> >> *To: *users(a)ovirt.org >> <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>>, "Meital >> >> Bourvine" <mbourvin(a)redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>> <mailto:mbourvin@redhat.com >> >> <mailto:mbourvin@redhat.com> >> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>> >> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>>>> >> *Sent: *Monday, January 20, >> 2014 9:39:10 AM >> *Subject: *Re: [Users] Disk error >> >> >> vdsm-4.13.0-11.el6.x86_64 >> :-) >> >> >> >> 2014/1/20 Meital Bourvine >> <mbourvin(a)redhat.com <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>>>>> >> >> >> >> First of all, I opened a >> bug about 'Drive' >> object has no >> attribute 'format': >> https://bugzilla.redhat.com/show_bug.cgi?id=1055437 >> >> Please send me the output >> of `rpm -q >> vdsm` so I'll >> update the >> version in the bug. >> >> Also, it's better to send >> the logs to >> the list >> (and >> not only >> to me), so more people >> will be able to >> help >> you debug it. >> >> ----- Original Message ----- >> > From: "Dafna Ron" >> <dron(a)redhat.com <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>> >> <mailto:dron@redhat.com >> <mailto:dron@redhat.com> <mailto:dron@redhat.com >> <mailto:dron@redhat.com>>> >> <mailto:dron@redhat.com >> <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>> >> <mailto:dron@redhat.com <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>>>> >> <mailto:dron@redhat.com >> <mailto:dron@redhat.com> <mailto:dron@redhat.com >> <mailto:dron@redhat.com>> >> <mailto:dron@redhat.com <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>>> >> <mailto:dron@redhat.com >> <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>> >> <mailto:dron@redhat.com <mailto:dron@redhat.com> >> <mailto:dron@redhat.com <mailto:dron@redhat.com>>>>>> >> >> > To: "Meital Bourvine" >> <mbourvin(a)redhat.com <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>>> >> <mailto: >> mbourvin(a)redhat.com <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com> >> <mailto:mbourvin@redhat.com >> <mailto:mbourvin@redhat.com>>>>>> >> > Cc: "Koen Vanoppen" >> <vanoppen.koen(a)gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>>> >> <mailto: >> vanoppen.koen(a)gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>>>>>, users(a)ovirt.org >> <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>>>>> >> >> >> > Sent: Monday, January >> 20, 2014 >> 8:49:32 AM >> > Subject: Re: [Users] >> Disk error >> > >> > from the errors you are >> getting, >> disk status >> in db >> is locked. >> > >> > >> > On 01/20/2014 08:38 AM, >> Meital >> Bourvine wrote: >> > > Hi Koen, >> > > >> > > What is the error that >> you got >> when live >> storage >> migration >> failed? >> > > Can you please attach >> vdsm.log and >> engine.log >> > > >> > > *From: *"Koen Vanoppen" >> <vanoppen.koen(a)gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>>> >> <mailto: >> vanoppen.koen(a)gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>> >> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com> >> <mailto:vanoppen.koen@gmail.com >> <mailto:vanoppen.koen@gmail.com>>>>>> >> > > *To: *users(a)ovirt.org >> <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>>>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>>> >> >> >> > > *Sent: *Monday, >> January 20, 2014 >> 5:30:51 AM >> > > *Subject: *[Users] >> Disk error >> > > >> > > Hi all! >> > > >> > > I got a kind of a >> strange >> error in ovirt. >> THere was a >> problem with >> > > a vm that was >> complaining >> about low disk >> space. (in >> terms of >> > > storage space of the >> storage >> center). >> So I did >> a live >> migration of >> > > the vm's disk. This >> failed, so >> I did a >> shutdown of the >> vm, to see >> > > if that would help, >> but now I >> can't >> get the VM >> back up >> again. >> > > Neither can I remove >> the disk or >> deactivate >> the dis. >> This is the >> > > error: >> > > Keep in mind that >> the vm is >> down and >> he had 2 >> disks... >> > > >> > > While trying to >> deactivate the >> disk: >> > > >> > > Error while >> executing action: >> > > >> > > KV-virt-v2v: >> > > >> > > * Cannot hot >> unplug Virtual >> Machine >> Disk. Disk >> KV-virt-v2v_Disk2 >> > > is being moved >> or copied. >> > > >> > > >> > > When I try to simply >> remove >> the vm: >> > > >> > > Error while >> executing action: >> > > >> > > KV-virt-v2v: >> > > >> > > * Cannot remove >> VM. Disk >> KV-virt-v2v_Disk2 >> is being >> moved or copied. >> > > * Cannot remove >> VM. Disk >> LargeTemplate_Disk1 is >> being moved or >> > > copied. >> > > >> > > >> > > Kind regards, >> > > >> > > Koen >> > > >> > > >> _______________________________________________ >> > > Users mailing list >> > > Users(a)ovirt.org >> <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>>> >> >> >> > > >> http://lists.ovirt.org/mailman/listinfo/users >> > > >> > > >> > > >> > > >> > > >> _______________________________________________ >> > > Users mailing list >> > > Users(a)ovirt.org >> <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>>> >> >> >> > > >> http://lists.ovirt.org/mailman/listinfo/users >> > >> > >> > -- >> > Dafna Ron >> > >> >> >> >> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> >> http://lists.ovirt.org/mailman/listinfo/users >> >> >> >> -- Dafna Ron >> >> >> us >> >> -- Dafna Ron >> >> >> >> >> -- Dafna Ron >> >> >> >> >> -- Dafna Ron >> >> >> >> > > -- > Dafna Ron >

1 0

Re: [Users] Disk error
by Koen Vanoppen 20 Jan '14

20 Jan '14

Error while executing action: KV-virt-v2v: - Cannot remove Snapshot. Disk KV-virt-v2v_Disk2 is being moved or copied. - Cannot remove Snapshot. Disk LargeTemplate_Disk1 is being moved or copied. 2014/1/20 Koen Vanoppen <vanoppen.koen(a)gmail.com> > Yes, it did. Twice actually. But I already tried that one. This is the > result: > > Error while executing action: > > KV-virt-v2v: > > - Cannot remove Snapshot. Disk KV-virt-v2v_Disk2 is being moved or > copied. > - Cannot remove Snapshot. Disk LargeTemplate_Disk1 is being moved or > copied. > > > > > 2014/1/20 Dafna Ron <dron(a)redhat.com> > >> you said that you shut down the vm after you tried migrating? >> can you look at the vm in the UI and see if you have a snapshot created >> during the migration? >> if so, can you try to delete just the snapshot? >> >> >> >> >> >> On 01/20/2014 10:58 AM, Koen Vanoppen wrote: >> >>> [root@soyuz ~]# lvs | grep ff674bce-aa94-4b46-9f9d-d4182eab1e49 >>> Couldn't find device with uuid Y5m0SH-HbWl-8PNL-fGkk-oXNF-WyQk-Snhncm. >>> ff674bce-aa94-4b46-9f9d-d4182eab1e49 f8ddd1d1-5266-493b-879b-f79c128751e2 >>> -wi-ao--- 50,00g >>> >>> Maybe it's already to another hypervisor or disk domain? If there is a >>> *SAVE* way to remove these two disk, tell me. The data on it it's not THAT >>> important. >>> >>> >>> >>> >>> 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@redhat.com>> >>> >>> >>> the disk ff674bce-aa94-4b46-9f9d-d4182eab1e49 does not exist in >>> the domain - which is the master domain >>> My guess that it has to do with the failed migration. >>> >>> can you run lvs and grep for ff674bce-aa94-4b46-9f9d-d4182eab1e49 >>> lets see where this disk is... >>> >>> >>> >>> >>> On 01/20/2014 10:44 AM, Koen Vanoppen wrote: >>> >>> [root@soyuz ~]# vdsClient -s 0 getStorageDomainInfo >>> f8ddd1d1-5266-493b-879b-f79c128751e2 >>> uuid = f8ddd1d1-5266-493b-879b-f79c128751e2 >>> vguuid = i6QHH9-1fZR-HLcn-6Xuo-7jU7-66iu-iuzWfQ >>> lver = 13 >>> state = OK >>> version = 3 >>> role = Master >>> pool = ['5849b030-626e-47cb-ad90-3ce782d831b3'] >>> spm_id = 1 >>> type = ISCSI >>> class = Data >>> master_ver = 1 >>> name = StoragePoolEva01 >>> >>> Thanx for the help! >>> >>> >>> 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@redhat.com> >>> <mailto:dron@redhat.com <mailto:dron@redhat.com>>> >>> >>> >>> >>> can you please run: >>> >>> vdsClient -s 0 getStorageDomainInfo >>> f8ddd1d1-5266-493b-879b-f79c128751e2 >>> >>> >>> >>> On 01/20/2014 10:33 AM, Koen Vanoppen wrote: >>> >>> [root@soyuz ~]# vdsClient -s 0 getStorageDomainsList >>> f3fd055b-2764-44ed-9d77-81bd58984842 >>> 94de241c-bf5c-4630-9af3-7e31b902ae77 >>> f8ddd1d1-5266-493b-879b-f79c128751e2 >>> 50cf24a4-d1ef-4105-a9a5-b81d91339175 >>> 83b1867f-4aea-400e-9ce0-efbd5add4216 >>> >>> (soyuz=vdsmhost3) >>> >>> >>> 2014/1/20 Dafna Ron <dron(a)redhat.com >>> <mailto:dron@redhat.com> <mailto:dron@redhat.com >>> <mailto:dron@redhat.com>> >>> <mailto:dron@redhat.com <mailto:dron@redhat.com> >>> <mailto:dron@redhat.com <mailto:dron@redhat.com>>>> >>> >>> >>> >>> let's try to sift through :) >>> >>> can you run vdsClient -s 0 getStorageDomainsList? >>> >>> >>> >>> >>> >>> On 01/20/2014 09:52 AM, Meital Bourvine wrote: >>> >>> It seems that your setup is completely messed >>> up. I >>> see the >>> following 3 errors all the time (I couldn't >>> actually >>> find the >>> live storage migration error, since there are >>> too many >>> errors): >>> >>> Thread-118::ERROR::2014-01-20 >>> 07:59:17,066::sampling::355::vm.Vm::(collect) >>> vmId=`f8c6190c-b722-4fcd-af17- >>> 21572151fcef`::Stats >>> function >>> failed: <AdvancedStatsFunction _highWrite at >>> 0x27b41b8> >>> Traceback (most recent call last): >>> File "/usr/share/vdsm/sampling.py", line >>> 351, in collect >>> statsFunction() >>> File "/usr/share/vdsm/sampling.py", line 226, >>> in >>> __call__ >>> retValue = self._function(*args, **kwargs) >>> File "/usr/share/vdsm/vm.py", line 509, in >>> _highWrite >>> if not vmDrive.blockDev or vmDrive.format >>> != 'cow': >>> AttributeError: 'Drive' object has no >>> attribute 'format' >>> >>> PolicyEngine::DEBUG::2014-01-20 >>> 07:59:17,198:: >>> libvirtconnection::108::libvirtconnection::(wrapper) >>> Unknown libvirterror: ecode: 8 edom: 10 level: >>> 2 message: >>> invalid argument: cannot set memory higher >>> than max memory >>> PolicyEngine::ERROR::2014-01-20 >>> 07:59:17,199::vm::4359::vm.Vm::(reportError) >>> vmId=`ce626f90-41c4-4417-9e53-bf4066ad062d`::Set >>> new >>> balloon >>> target failed >>> Traceback (most recent call last): >>> File "/usr/share/vdsm/vm.py", line 4371, in >>> setBalloonTarget >>> self._dom.setMemory(target) >>> File "/usr/share/vdsm/vm.py", line 835, in f >>> ret = attr(*args, **kwargs) >>> File >>> "/usr/lib64/python2.6/site- >>> packages/vdsm/libvirtconnection.py", >>> line >>> 76, in wrapper >>> ret = f(*args, **kwargs) >>> File >>> "/usr/lib64/python2.6/site-packages/libvirt.py", line >>> 1410, in setMemory >>> if ret == -1: raise libvirtError >>> ('virDomainSetMemory() >>> failed', dom=self) >>> libvirtError: invalid argument: cannot set memory >>> higher than >>> max memory >>> >>> Thread-51::ERROR::2014-01-20 >>> 07:59:22,109::sampling::355::vm.Vm::(collect) >>> vmId=`493128c0-aba9-4b38-bf18- >>> 2778b910917f`::Stats >>> function >>> failed: <AdvancedStatsFunction _highWrite at >>> 0x27b41b8> >>> Traceback (most recent call last): >>> File "/usr/share/vdsm/sampling.py", line >>> 351, in collect >>> statsFunction() >>> File "/usr/share/vdsm/sampling.py", line 226, >>> in >>> __call__ >>> retValue = self._function(*args, **kwargs) >>> File "/usr/share/vdsm/vm.py", line 513, in >>> _highWrite >>> self._vm._dom.blockInfo(vmDrive.path, 0) >>> File "/usr/share/vdsm/vm.py", line 835, in f >>> ret = attr(*args, **kwargs) >>> File >>> "/usr/lib64/python2.6/site- >>> packages/vdsm/libvirtconnection.py", >>> line >>> 76, in wrapper >>> ret = f(*args, **kwargs) >>> File >>> "/usr/lib64/python2.6/site-packages/libvirt.py", line >>> 1797, in blockInfo >>> if ret is None: raise libvirtError >>> ('virDomainGetBlockInfo() failed', dom=self) >>> libvirtError: invalid argument: invalid path >>> /rhev/data-center/mnt/blockSD/ >>> f8ddd1d1-5266-493b-879b-f79c128751e2/images/b8da8541- >>> 9a0d-4c18-8aa8-50fc6225f18a/ff674bce-aa94-4b46-9f9d-d4182eab1e49 >>> not assigned to domain >>> >>> >>> ------------------------------ >>> ------------------------------------------ >>> >>> >>> >>> *From: *"Koen Vanoppen" >>> <vanoppen.koen(a)gmail.com <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com>> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com>>>> >>> *To: *users(a)ovirt.org >>> <mailto:users@ovirt.org> <mailto:users@ovirt.org >>> <mailto:users@ovirt.org>> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>, "Meital >>> >>> Bourvine" <mbourvin(a)redhat.com >>> <mailto:mbourvin@redhat.com> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com >>> >>> <mailto:mbourvin@redhat.com> >>> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com>>>> >>> *Sent: *Monday, January 20, 2014 9:39:10 AM >>> *Subject: *Re: [Users] Disk error >>> >>> >>> vdsm-4.13.0-11.el6.x86_64 >>> :-) >>> >>> >>> >>> 2014/1/20 Meital Bourvine >>> <mbourvin(a)redhat.com <mailto:mbourvin@redhat.com> >>> <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com >>> >> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com>>> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com>>>>> >>> >>> >>> >>> First of all, I opened a bug about >>> 'Drive' >>> object has no >>> attribute 'format': >>> https://bugzilla.redhat.com/show_bug.cgi?id=1055437 >>> >>> Please send me the output of `rpm -q >>> vdsm` so I'll >>> update the >>> version in the bug. >>> >>> Also, it's better to send the logs to >>> the list >>> (and >>> not only >>> to me), so more people will be able to >>> help >>> you debug it. >>> >>> ----- Original Message ----- >>> > From: "Dafna Ron" <dron(a)redhat.com >>> <mailto:dron@redhat.com> >>> <mailto:dron@redhat.com <mailto:dron@redhat.com>> >>> <mailto:dron@redhat.com >>> <mailto:dron@redhat.com> <mailto:dron@redhat.com >>> <mailto:dron@redhat.com>>> >>> <mailto:dron@redhat.com <mailto:dron@redhat.com> >>> <mailto:dron@redhat.com <mailto:dron@redhat.com>> >>> <mailto:dron@redhat.com >>> <mailto:dron@redhat.com> <mailto:dron@redhat.com >>> <mailto:dron@redhat.com>>>>> >>> > To: "Meital Bourvine" >>> <mbourvin(a)redhat.com <mailto:mbourvin@redhat.com> >>> <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com >>> >> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com>>> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com> >>> <mailto:mbourvin@redhat.com >>> <mailto:mbourvin@redhat.com>>>>> >>> > Cc: "Koen Vanoppen" >>> <vanoppen.koen(a)gmail.com <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com>> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com>>> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com>> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com>>>>>, users(a)ovirt.org >>> <mailto:users@ovirt.org> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >>> <mailto:users@ovirt.org >>> <mailto:users@ovirt.org> <mailto:users@ovirt.org >>> <mailto:users@ovirt.org>>> >>> <mailto:users@ovirt.org >>> <mailto:users@ovirt.org> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>> >>> >>> >>> > Sent: Monday, January 20, 2014 >>> 8:49:32 AM >>> > Subject: Re: [Users] Disk error >>> > >>> > from the errors you are getting, >>> disk status >>> in db >>> is locked. >>> > >>> > >>> > On 01/20/2014 08:38 AM, Meital >>> Bourvine wrote: >>> > > Hi Koen, >>> > > >>> > > What is the error that you got >>> when live >>> storage >>> migration >>> failed? >>> > > Can you please attach vdsm.log and >>> engine.log >>> > > >>> > > *From: *"Koen Vanoppen" >>> <vanoppen.koen(a)gmail.com >>> <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com>> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com <mailto:vanoppen.koen@gmail.com >>> >>> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com>> >>> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com> >>> <mailto:vanoppen.koen@gmail.com >>> <mailto:vanoppen.koen@gmail.com>>>>> >>> > > *To: *users(a)ovirt.org >>> <mailto:users@ovirt.org> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org>>> >>> <mailto:users@ovirt.org >>> <mailto:users@ovirt.org> <mailto:users@ovirt.org >>> <mailto:users@ovirt.org>> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>> >>> >>> >>> > > *Sent: *Monday, January 20, 2014 >>> 5:30:51 AM >>> > > *Subject: *[Users] Disk error >>> > > >>> > > Hi all! >>> > > >>> > > I got a kind of a strange >>> error in ovirt. >>> THere was a >>> problem with >>> > > a vm that was complaining >>> about low disk >>> space. (in >>> terms of >>> > > storage space of the storage >>> center). >>> So I did >>> a live >>> migration of >>> > > the vm's disk. This failed, so >>> I did a >>> shutdown of the >>> vm, to see >>> > > if that would help, but now I >>> can't >>> get the VM >>> back up >>> again. >>> > > Neither can I remove the disk or >>> deactivate >>> the dis. >>> This is the >>> > > error: >>> > > Keep in mind that the vm is >>> down and >>> he had 2 >>> disks... >>> > > >>> > > While trying to deactivate the >>> disk: >>> > > >>> > > Error while executing action: >>> > > >>> > > KV-virt-v2v: >>> > > >>> > > * Cannot hot unplug Virtual >>> Machine >>> Disk. Disk >>> KV-virt-v2v_Disk2 >>> > > is being moved or copied. >>> > > >>> > > >>> > > When I try to simply remove >>> the vm: >>> > > >>> > > Error while executing action: >>> > > >>> > > KV-virt-v2v: >>> > > >>> > > * Cannot remove VM. Disk >>> KV-virt-v2v_Disk2 >>> is being >>> moved or copied. >>> > > * Cannot remove VM. Disk >>> LargeTemplate_Disk1 is >>> being moved or >>> > > copied. >>> > > >>> > > >>> > > Kind regards, >>> > > >>> > > Koen >>> > > >>> > > >>> _______________________________________________ >>> > > Users mailing list >>> > > Users(a)ovirt.org >>> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >>> <mailto:Users@ovirt.org>> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >>> <mailto:Users@ovirt.org >>> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >>> <mailto:Users@ovirt.org>> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> >>> >>> >>> > > >>> http://lists.ovirt.org/mailman/listinfo/users >>> > > >>> > > >>> > > >>> > > >>> > > >>> _______________________________________________ >>> > > Users mailing list >>> > > Users(a)ovirt.org >>> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >>> <mailto:Users@ovirt.org>> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >>> <mailto:Users@ovirt.org >>> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >>> <mailto:Users@ovirt.org>> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> >>> >>> >>> > > >>> http://lists.ovirt.org/mailman/listinfo/users >>> > >>> > >>> > -- >>> > Dafna Ron >>> > >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org <mailto:Users@ovirt.org> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >>> >>> -- Dafna Ron >>> >>> >>> us >>> >>> -- Dafna Ron >>> >>> >>> >>> >>> -- Dafna Ron >>> >>> >>> >> >> -- >> Dafna Ron >> > >

2 1

Re: [Users] Disk error
by Dafna Ron 20 Jan '14

20 Jan '14

you said that you shut down the vm after you tried migrating? can you look at the vm in the UI and see if you have a snapshot created during the migration? if so, can you try to delete just the snapshot? On 01/20/2014 10:58 AM, Koen Vanoppen wrote: > [root@soyuz ~]# lvs | grep ff674bce-aa94-4b46-9f9d-d4182eab1e49 > Couldn't find device with uuid Y5m0SH-HbWl-8PNL-fGkk-oXNF-WyQk-Snhncm. > ff674bce-aa94-4b46-9f9d-d4182eab1e49 > f8ddd1d1-5266-493b-879b-f79c128751e2 -wi-ao--- 50,00g > > Maybe it's already to another hypervisor or disk domain? If there is a > *SAVE* way to remove these two disk, tell me. The data on it it's not > THAT important. > > > > > 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@redhat.com>> > > the disk ff674bce-aa94-4b46-9f9d-d4182eab1e49 does not exist in > the domain - which is the master domain > My guess that it has to do with the failed migration. > > can you run lvs and grep for ff674bce-aa94-4b46-9f9d-d4182eab1e49 > lets see where this disk is... > > > > > On 01/20/2014 10:44 AM, Koen Vanoppen wrote: > > [root@soyuz ~]# vdsClient -s 0 getStorageDomainInfo > f8ddd1d1-5266-493b-879b-f79c128751e2 > uuid = f8ddd1d1-5266-493b-879b-f79c128751e2 > vguuid = i6QHH9-1fZR-HLcn-6Xuo-7jU7-66iu-iuzWfQ > lver = 13 > state = OK > version = 3 > role = Master > pool = ['5849b030-626e-47cb-ad90-3ce782d831b3'] > spm_id = 1 > type = ISCSI > class = Data > master_ver = 1 > name = StoragePoolEva01 > > Thanx for the help! > > > 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>> > > > can you please run: > > vdsClient -s 0 getStorageDomainInfo > f8ddd1d1-5266-493b-879b-f79c128751e2 > > > > On 01/20/2014 10:33 AM, Koen Vanoppen wrote: > > [root@soyuz ~]# vdsClient -s 0 getStorageDomainsList > f3fd055b-2764-44ed-9d77-81bd58984842 > 94de241c-bf5c-4630-9af3-7e31b902ae77 > f8ddd1d1-5266-493b-879b-f79c128751e2 > 50cf24a4-d1ef-4105-a9a5-b81d91339175 > 83b1867f-4aea-400e-9ce0-efbd5add4216 > > (soyuz=vdsmhost3) > > > 2014/1/20 Dafna Ron <dron(a)redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>>> > > > > let's try to sift through :) > > can you run vdsClient -s 0 getStorageDomainsList? > > > > > > On 01/20/2014 09:52 AM, Meital Bourvine wrote: > > It seems that your setup is completely messed > up. I > see the > following 3 errors all the time (I couldn't > actually > find the > live storage migration error, since there are > too many > errors): > > Thread-118::ERROR::2014-01-20 > 07:59:17,066::sampling::355::vm.Vm::(collect) > vmId=`f8c6190c-b722-4fcd-af17-21572151fcef`::Stats > function > failed: <AdvancedStatsFunction _highWrite at > 0x27b41b8> > Traceback (most recent call last): > File "/usr/share/vdsm/sampling.py", line > 351, in collect > statsFunction() > File "/usr/share/vdsm/sampling.py", line 226, in > __call__ > retValue = self._function(*args, **kwargs) > File "/usr/share/vdsm/vm.py", line 509, in > _highWrite > if not vmDrive.blockDev or vmDrive.format > != 'cow': > AttributeError: 'Drive' object has no > attribute 'format' > > PolicyEngine::DEBUG::2014-01-20 > > 07:59:17,198::libvirtconnection::108::libvirtconnection::(wrapper) > Unknown libvirterror: ecode: 8 edom: 10 level: > 2 message: > invalid argument: cannot set memory higher > than max memory > PolicyEngine::ERROR::2014-01-20 > 07:59:17,199::vm::4359::vm.Vm::(reportError) > > vmId=`ce626f90-41c4-4417-9e53-bf4066ad062d`::Set new > balloon > target failed > Traceback (most recent call last): > File "/usr/share/vdsm/vm.py", line 4371, in > setBalloonTarget > self._dom.setMemory(target) > File "/usr/share/vdsm/vm.py", line 835, in f > ret = attr(*args, **kwargs) > File > > "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", > line > 76, in wrapper > ret = f(*args, **kwargs) > File > "/usr/lib64/python2.6/site-packages/libvirt.py", line > 1410, in setMemory > if ret == -1: raise libvirtError > ('virDomainSetMemory() > failed', dom=self) > libvirtError: invalid argument: cannot set memory > higher than > max memory > > Thread-51::ERROR::2014-01-20 > 07:59:22,109::sampling::355::vm.Vm::(collect) > vmId=`493128c0-aba9-4b38-bf18-2778b910917f`::Stats > function > failed: <AdvancedStatsFunction _highWrite at > 0x27b41b8> > Traceback (most recent call last): > File "/usr/share/vdsm/sampling.py", line > 351, in collect > statsFunction() > File "/usr/share/vdsm/sampling.py", line 226, in > __call__ > retValue = self._function(*args, **kwargs) > File "/usr/share/vdsm/vm.py", line 513, in > _highWrite > self._vm._dom.blockInfo(vmDrive.path, 0) > File "/usr/share/vdsm/vm.py", line 835, in f > ret = attr(*args, **kwargs) > File > > "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", > line > 76, in wrapper > ret = f(*args, **kwargs) > File > "/usr/lib64/python2.6/site-packages/libvirt.py", line > 1797, in blockInfo > if ret is None: raise libvirtError > ('virDomainGetBlockInfo() failed', dom=self) > libvirtError: invalid argument: invalid path > > /rhev/data-center/mnt/blockSD/f8ddd1d1-5266-493b-879b-f79c128751e2/images/b8da8541-9a0d-4c18-8aa8-50fc6225f18a/ff674bce-aa94-4b46-9f9d-d4182eab1e49 > not assigned to domain > > > > ------------------------------------------------------------------------ > > > > *From: *"Koen Vanoppen" > <vanoppen.koen(a)gmail.com <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>> > *To: *users(a)ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>, "Meital > > Bourvine" <mbourvin(a)redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>> > *Sent: *Monday, January 20, 2014 9:39:10 AM > *Subject: *Re: [Users] Disk error > > > vdsm-4.13.0-11.el6.x86_64 > :-) > > > > 2014/1/20 Meital Bourvine > <mbourvin(a)redhat.com <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>>> > > > > First of all, I opened a bug about 'Drive' > object has no > attribute 'format': > https://bugzilla.redhat.com/show_bug.cgi?id=1055437 > > Please send me the output of `rpm -q > vdsm` so I'll > update the > version in the bug. > > Also, it's better to send the logs to > the list > (and > not only > to me), so more people will be able to > help > you debug it. > > ----- Original Message ----- > > From: "Dafna Ron" <dron(a)redhat.com > <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>>>> > > To: "Meital Bourvine" > <mbourvin(a)redhat.com <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>>> > > Cc: "Koen Vanoppen" > <vanoppen.koen(a)gmail.com <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>>>, users(a)ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>> > > > Sent: Monday, January 20, 2014 > 8:49:32 AM > > Subject: Re: [Users] Disk error > > > > from the errors you are getting, > disk status > in db > is locked. > > > > > > On 01/20/2014 08:38 AM, Meital > Bourvine wrote: > > > Hi Koen, > > > > > > What is the error that you got > when live > storage > migration > failed? > > > Can you please attach vdsm.log and > engine.log > > > > > > *From: *"Koen Vanoppen" > <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com <mailto:vanoppen.koen@gmail.com>>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>>> > > > *To: *users(a)ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>>> > > > > > *Sent: *Monday, January 20, 2014 > 5:30:51 AM > > > *Subject: *[Users] Disk error > > > > > > Hi all! > > > > > > I got a kind of a strange > error in ovirt. > THere was a > problem with > > > a vm that was complaining > about low disk > space. (in > terms of > > > storage space of the storage > center). > So I did > a live > migration of > > > the vm's disk. This failed, so > I did a > shutdown of the > vm, to see > > > if that would help, but now I > can't > get the VM > back up > again. > > > Neither can I remove the disk or > deactivate > the dis. > This is the > > > error: > > > Keep in mind that the vm is > down and > he had 2 > disks... > > > > > > While trying to deactivate the > disk: > > > > > > Error while executing action: > > > > > > KV-virt-v2v: > > > > > > * Cannot hot unplug Virtual > Machine > Disk. Disk > KV-virt-v2v_Disk2 > > > is being moved or copied. > > > > > > > > > When I try to simply remove > the vm: > > > > > > Error while executing action: > > > > > > KV-virt-v2v: > > > > > > * Cannot remove VM. Disk > KV-virt-v2v_Disk2 > is being > moved or copied. > > > * Cannot remove VM. Disk > LargeTemplate_Disk1 is > being moved or > > > copied. > > > > > > > > > Kind regards, > > > > > > Koen > > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > <mailto:Users@ovirt.org > <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > -- > > Dafna Ron > > > > > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > http://lists.ovirt.org/mailman/listinfo/users > > > > -- Dafna Ron > > > us > > -- Dafna Ron > > > > > -- > Dafna Ron > > -- Dafna Ron

1 0

Re: [Users] Disk error
by Dafna Ron 20 Jan '14

20 Jan '14

the disk ff674bce-aa94-4b46-9f9d-d4182eab1e49 does not exist in the domain - which is the master domain My guess that it has to do with the failed migration. can you run lvs and grep for ff674bce-aa94-4b46-9f9d-d4182eab1e49 lets see where this disk is... On 01/20/2014 10:44 AM, Koen Vanoppen wrote: > [root@soyuz ~]# vdsClient -s 0 getStorageDomainInfo > f8ddd1d1-5266-493b-879b-f79c128751e2 > uuid = f8ddd1d1-5266-493b-879b-f79c128751e2 > vguuid = i6QHH9-1fZR-HLcn-6Xuo-7jU7-66iu-iuzWfQ > lver = 13 > state = OK > version = 3 > role = Master > pool = ['5849b030-626e-47cb-ad90-3ce782d831b3'] > spm_id = 1 > type = ISCSI > class = Data > master_ver = 1 > name = StoragePoolEva01 > > Thanx for the help! > > > 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@redhat.com>> > > can you please run: > > vdsClient -s 0 getStorageDomainInfo > f8ddd1d1-5266-493b-879b-f79c128751e2 > > > > On 01/20/2014 10:33 AM, Koen Vanoppen wrote: > > [root@soyuz ~]# vdsClient -s 0 getStorageDomainsList > f3fd055b-2764-44ed-9d77-81bd58984842 > 94de241c-bf5c-4630-9af3-7e31b902ae77 > f8ddd1d1-5266-493b-879b-f79c128751e2 > 50cf24a4-d1ef-4105-a9a5-b81d91339175 > 83b1867f-4aea-400e-9ce0-efbd5add4216 > > (soyuz=vdsmhost3) > > > 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>> > > > let's try to sift through :) > > can you run vdsClient -s 0 getStorageDomainsList? > > > > > > On 01/20/2014 09:52 AM, Meital Bourvine wrote: > > It seems that your setup is completely messed up. I > see the > following 3 errors all the time (I couldn't actually > find the > live storage migration error, since there are too many > errors): > > Thread-118::ERROR::2014-01-20 > 07:59:17,066::sampling::355::vm.Vm::(collect) > vmId=`f8c6190c-b722-4fcd-af17-21572151fcef`::Stats > function > failed: <AdvancedStatsFunction _highWrite at 0x27b41b8> > Traceback (most recent call last): > File "/usr/share/vdsm/sampling.py", line 351, in collect > statsFunction() > File "/usr/share/vdsm/sampling.py", line 226, in > __call__ > retValue = self._function(*args, **kwargs) > File "/usr/share/vdsm/vm.py", line 509, in _highWrite > if not vmDrive.blockDev or vmDrive.format != 'cow': > AttributeError: 'Drive' object has no attribute 'format' > > PolicyEngine::DEBUG::2014-01-20 > > 07:59:17,198::libvirtconnection::108::libvirtconnection::(wrapper) > Unknown libvirterror: ecode: 8 edom: 10 level: 2 message: > invalid argument: cannot set memory higher than max memory > PolicyEngine::ERROR::2014-01-20 > 07:59:17,199::vm::4359::vm.Vm::(reportError) > vmId=`ce626f90-41c4-4417-9e53-bf4066ad062d`::Set new > balloon > target failed > Traceback (most recent call last): > File "/usr/share/vdsm/vm.py", line 4371, in > setBalloonTarget > self._dom.setMemory(target) > File "/usr/share/vdsm/vm.py", line 835, in f > ret = attr(*args, **kwargs) > File > > "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line > 76, in wrapper > ret = f(*args, **kwargs) > File > "/usr/lib64/python2.6/site-packages/libvirt.py", line > 1410, in setMemory > if ret == -1: raise libvirtError > ('virDomainSetMemory() > failed', dom=self) > libvirtError: invalid argument: cannot set memory > higher than > max memory > > Thread-51::ERROR::2014-01-20 > 07:59:22,109::sampling::355::vm.Vm::(collect) > vmId=`493128c0-aba9-4b38-bf18-2778b910917f`::Stats > function > failed: <AdvancedStatsFunction _highWrite at 0x27b41b8> > Traceback (most recent call last): > File "/usr/share/vdsm/sampling.py", line 351, in collect > statsFunction() > File "/usr/share/vdsm/sampling.py", line 226, in > __call__ > retValue = self._function(*args, **kwargs) > File "/usr/share/vdsm/vm.py", line 513, in _highWrite > self._vm._dom.blockInfo(vmDrive.path, 0) > File "/usr/share/vdsm/vm.py", line 835, in f > ret = attr(*args, **kwargs) > File > > "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line > 76, in wrapper > ret = f(*args, **kwargs) > File > "/usr/lib64/python2.6/site-packages/libvirt.py", line > 1797, in blockInfo > if ret is None: raise libvirtError > ('virDomainGetBlockInfo() failed', dom=self) > libvirtError: invalid argument: invalid path > > /rhev/data-center/mnt/blockSD/f8ddd1d1-5266-493b-879b-f79c128751e2/images/b8da8541-9a0d-4c18-8aa8-50fc6225f18a/ff674bce-aa94-4b46-9f9d-d4182eab1e49 > not assigned to domain > > > > ------------------------------------------------------------------------ > > > > *From: *"Koen Vanoppen" <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > *To: *users(a)ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>, "Meital > > Bourvine" <mbourvin(a)redhat.com > <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>> > *Sent: *Monday, January 20, 2014 9:39:10 AM > *Subject: *Re: [Users] Disk error > > > vdsm-4.13.0-11.el6.x86_64 > :-) > > > > 2014/1/20 Meital Bourvine <mbourvin(a)redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>> > > > > First of all, I opened a bug about 'Drive' > object has no > attribute 'format': > https://bugzilla.redhat.com/show_bug.cgi?id=1055437 > > Please send me the output of `rpm -q vdsm` so I'll > update the > version in the bug. > > Also, it's better to send the logs to the list > (and > not only > to me), so more people will be able to help > you debug it. > > ----- Original Message ----- > > From: "Dafna Ron" <dron(a)redhat.com > <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>> > <mailto:dron@redhat.com <mailto:dron@redhat.com> > <mailto:dron@redhat.com <mailto:dron@redhat.com>>>> > > To: "Meital Bourvine" <mbourvin(a)redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com>> > <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com> <mailto:mbourvin@redhat.com > <mailto:mbourvin@redhat.com>>>> > > Cc: "Koen Vanoppen" <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>>, users(a)ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > <mailto:users@ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>>> > > > Sent: Monday, January 20, 2014 8:49:32 AM > > Subject: Re: [Users] Disk error > > > > from the errors you are getting, disk status > in db > is locked. > > > > > > On 01/20/2014 08:38 AM, Meital Bourvine wrote: > > > Hi Koen, > > > > > > What is the error that you got when live > storage > migration > failed? > > > Can you please attach vdsm.log and engine.log > > > > > > *From: *"Koen Vanoppen" > <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com <mailto:vanoppen.koen@gmail.com>> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com> > > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>> > > > *To: *users(a)ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>> > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>> > > > > > *Sent: *Monday, January 20, 2014 > 5:30:51 AM > > > *Subject: *[Users] Disk error > > > > > > Hi all! > > > > > > I got a kind of a strange error in ovirt. > THere was a > problem with > > > a vm that was complaining about low disk > space. (in > terms of > > > storage space of the storage center). > So I did > a live > migration of > > > the vm's disk. This failed, so I did a > shutdown of the > vm, to see > > > if that would help, but now I can't > get the VM > back up > again. > > > Neither can I remove the disk or > deactivate > the dis. > This is the > > > error: > > > Keep in mind that the vm is down and > he had 2 > disks... > > > > > > While trying to deactivate the disk: > > > > > > Error while executing action: > > > > > > KV-virt-v2v: > > > > > > * Cannot hot unplug Virtual Machine > Disk. Disk > KV-virt-v2v_Disk2 > > > is being moved or copied. > > > > > > > > > When I try to simply remove the vm: > > > > > > Error while executing action: > > > > > > KV-virt-v2v: > > > > > > * Cannot remove VM. Disk > KV-virt-v2v_Disk2 > is being > moved or copied. > > > * Cannot remove VM. Disk > LargeTemplate_Disk1 is > being moved or > > > copied. > > > > > > > > > Kind regards, > > > > > > Koen > > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > -- > > Dafna Ron > > > > > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > http://lists.ovirt.org/mailman/listinfo/users > > > > -- Dafna Ron > > > us > > -- > Dafna Ron > > -- Dafna Ron

1 0

[Users] Gluster command [Non interactive user] failed on server ..
by Andrew Lau 20 Jan '14

20 Jan '14

Hi, I'm seeing this weird error on my host which runs the hosted-engine, it only recently showed up and put the host into 'Non Operational' : Gluster command [Non interactive user] failed on server HV01. ovirt-engine.log http://www.fpaste.org/69949/90213863/ Current running VMs continue to run. Has anyone seen this before? Thanks, Andrew

2 2

Re: [Users] Disk error
by Dafna Ron 20 Jan '14

20 Jan '14

can you please run: vdsClient -s 0 getStorageDomainInfo f8ddd1d1-5266-493b-879b-f79c128751e2 On 01/20/2014 10:33 AM, Koen Vanoppen wrote: > [root@soyuz ~]# vdsClient -s 0 getStorageDomainsList > f3fd055b-2764-44ed-9d77-81bd58984842 > 94de241c-bf5c-4630-9af3-7e31b902ae77 > f8ddd1d1-5266-493b-879b-f79c128751e2 > 50cf24a4-d1ef-4105-a9a5-b81d91339175 > 83b1867f-4aea-400e-9ce0-efbd5add4216 > > (soyuz=vdsmhost3) > > > 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@redhat.com>> > > let's try to sift through :) > > can you run vdsClient -s 0 getStorageDomainsList? > > > > > > On 01/20/2014 09:52 AM, Meital Bourvine wrote: > > It seems that your setup is completely messed up. I see the > following 3 errors all the time (I couldn't actually find the > live storage migration error, since there are too many errors): > > Thread-118::ERROR::2014-01-20 > 07:59:17,066::sampling::355::vm.Vm::(collect) > vmId=`f8c6190c-b722-4fcd-af17-21572151fcef`::Stats function > failed: <AdvancedStatsFunction _highWrite at 0x27b41b8> > Traceback (most recent call last): > File "/usr/share/vdsm/sampling.py", line 351, in collect > statsFunction() > File "/usr/share/vdsm/sampling.py", line 226, in __call__ > retValue = self._function(*args, **kwargs) > File "/usr/share/vdsm/vm.py", line 509, in _highWrite > if not vmDrive.blockDev or vmDrive.format != 'cow': > AttributeError: 'Drive' object has no attribute 'format' > > PolicyEngine::DEBUG::2014-01-20 > 07:59:17,198::libvirtconnection::108::libvirtconnection::(wrapper) > Unknown libvirterror: ecode: 8 edom: 10 level: 2 message: > invalid argument: cannot set memory higher than max memory > PolicyEngine::ERROR::2014-01-20 > 07:59:17,199::vm::4359::vm.Vm::(reportError) > vmId=`ce626f90-41c4-4417-9e53-bf4066ad062d`::Set new balloon > target failed > Traceback (most recent call last): > File "/usr/share/vdsm/vm.py", line 4371, in setBalloonTarget > self._dom.setMemory(target) > File "/usr/share/vdsm/vm.py", line 835, in f > ret = attr(*args, **kwargs) > File > "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line > 76, in wrapper > ret = f(*args, **kwargs) > File "/usr/lib64/python2.6/site-packages/libvirt.py", line > 1410, in setMemory > if ret == -1: raise libvirtError ('virDomainSetMemory() > failed', dom=self) > libvirtError: invalid argument: cannot set memory higher than > max memory > > Thread-51::ERROR::2014-01-20 > 07:59:22,109::sampling::355::vm.Vm::(collect) > vmId=`493128c0-aba9-4b38-bf18-2778b910917f`::Stats function > failed: <AdvancedStatsFunction _highWrite at 0x27b41b8> > Traceback (most recent call last): > File "/usr/share/vdsm/sampling.py", line 351, in collect > statsFunction() > File "/usr/share/vdsm/sampling.py", line 226, in __call__ > retValue = self._function(*args, **kwargs) > File "/usr/share/vdsm/vm.py", line 513, in _highWrite > self._vm._dom.blockInfo(vmDrive.path, 0) > File "/usr/share/vdsm/vm.py", line 835, in f > ret = attr(*args, **kwargs) > File > "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line > 76, in wrapper > ret = f(*args, **kwargs) > File "/usr/lib64/python2.6/site-packages/libvirt.py", line > 1797, in blockInfo > if ret is None: raise libvirtError > ('virDomainGetBlockInfo() failed', dom=self) > libvirtError: invalid argument: invalid path > /rhev/data-center/mnt/blockSD/f8ddd1d1-5266-493b-879b-f79c128751e2/images/b8da8541-9a0d-4c18-8aa8-50fc6225f18a/ff674bce-aa94-4b46-9f9d-d4182eab1e49 > not assigned to domain > > > ------------------------------------------------------------------------ > > > > *From: *"Koen Vanoppen" <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com>> > *To: *users(a)ovirt.org <mailto:users@ovirt.org>, "Meital > Bourvine" <mbourvin(a)redhat.com <mailto:mbourvin@redhat.com>> > *Sent: *Monday, January 20, 2014 9:39:10 AM > *Subject: *Re: [Users] Disk error > > > vdsm-4.13.0-11.el6.x86_64 > :-) > > > > 2014/1/20 Meital Bourvine <mbourvin(a)redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com>>> > > > First of all, I opened a bug about 'Drive' object has no > attribute 'format': > https://bugzilla.redhat.com/show_bug.cgi?id=1055437 > > Please send me the output of `rpm -q vdsm` so I'll > update the > version in the bug. > > Also, it's better to send the logs to the list (and > not only > to me), so more people will be able to help you debug it. > > ----- Original Message ----- > > From: "Dafna Ron" <dron(a)redhat.com > <mailto:dron@redhat.com> <mailto:dron@redhat.com > <mailto:dron@redhat.com>>> > > To: "Meital Bourvine" <mbourvin(a)redhat.com > <mailto:mbourvin@redhat.com> > <mailto:mbourvin@redhat.com <mailto:mbourvin@redhat.com>>> > > Cc: "Koen Vanoppen" <vanoppen.koen(a)gmail.com > <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>>, users(a)ovirt.org > <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > > Sent: Monday, January 20, 2014 8:49:32 AM > > Subject: Re: [Users] Disk error > > > > from the errors you are getting, disk status in db > is locked. > > > > > > On 01/20/2014 08:38 AM, Meital Bourvine wrote: > > > Hi Koen, > > > > > > What is the error that you got when live storage > migration > failed? > > > Can you please attach vdsm.log and engine.log > > > > > > *From: *"Koen Vanoppen" > <vanoppen.koen(a)gmail.com <mailto:vanoppen.koen@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@gmail.com>>> > > > *To: *users(a)ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>> > > > > *Sent: *Monday, January 20, 2014 5:30:51 AM > > > *Subject: *[Users] Disk error > > > > > > Hi all! > > > > > > I got a kind of a strange error in ovirt. > THere was a > problem with > > > a vm that was complaining about low disk > space. (in > terms of > > > storage space of the storage center). So I did > a live > migration of > > > the vm's disk. This failed, so I did a > shutdown of the > vm, to see > > > if that would help, but now I can't get the VM > back up > again. > > > Neither can I remove the disk or deactivate > the dis. > This is the > > > error: > > > Keep in mind that the vm is down and he had 2 > disks... > > > > > > While trying to deactivate the disk: > > > > > > Error while executing action: > > > > > > KV-virt-v2v: > > > > > > * Cannot hot unplug Virtual Machine Disk. Disk > KV-virt-v2v_Disk2 > > > is being moved or copied. > > > > > > > > > When I try to simply remove the vm: > > > > > > Error while executing action: > > > > > > KV-virt-v2v: > > > > > > * Cannot remove VM. Disk KV-virt-v2v_Disk2 > is being > moved or copied. > > > * Cannot remove VM. Disk LargeTemplate_Disk1 is > being moved or > > > copied. > > > > > > > > > Kind regards, > > > > > > Koen > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org <mailto:Users@ovirt.org> > <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > -- > > Dafna Ron > > > > > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org <mailto:Users@ovirt.org> > http://lists.ovirt.org/mailman/listinfo/users > > > > -- > Dafna Ron > > us -- Dafna Ron

1 0

[Users] virt-v2v: invalid backend appliance
by Markus Stockhausen 20 Jan '14

20 Jan '14

------=_NextPartTM-000-e048b27c-2262-4ee1-9927-f5f1e482ee61 Content-Type: multipart/alternative; boundary="_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D51D1EXCHANGEcollogi_" --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D51D1EXCHANGEcollogi_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, just tried to run virt-v2v on Fedora 20. Disk conversion works flawlessly but in the end the process fails with: libguestfs: create: flags =3D 0, handle =3D 0x4fe26a0, program =3D perl invalid backend: appliance at /usr/share/perl5/vendor_perl/Sys/VirtConvert/= GuestfsHandle.pm line 83. libguestfs: closing guestfs handle 0x4fe26a0 (state 0) I'm using the same scripts & configuration files with Fedora 19. No problems there. Any ideas what is going wrong? Markus --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D51D1EXCHANGEcollogi_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html dir=3D"ltr"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style id=3D"owaParaStyle" type=3D"text/css">P {margin-top:0;margin-bottom:= 0;}</style> </head> <body ocsi=3D"0" fpstyle=3D"1"> <div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: = 10pt;">Hello, just tried to run virt-v2v on Fedora 20. Disk conversion works flawlessly but in the end the process fails with: libguestfs: create: flags =3D 0, handle =3D 0x4fe26a0, program =3D perl invalid backend: appliance at /usr/share/perl5/vendor_perl/Sys/VirtConvert/= GuestfsHandle.pm line 83. libguestfs: closing guestfs handle 0x4fe26a0 (state 0) I'm using the same scripts & configuration files with Fedora 19. No problems there. Any ideas what is going wrong? Markus </div> </body> </html> --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585D51D1EXCHANGEcollogi_-- ------=_NextPartTM-000-e048b27c-2262-4ee1-9927-f5f1e482ee61 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-e048b27c-2262-4ee1-9927-f5f1e482ee61--

2 3