- Users - oVirt List Archives

[Users] fencing: HP ilo100 status does NMI, reboots computer
by Ted Miller 23 Jan '14

23 Jan '14

--------------040009030705040405030507 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit I am having trouble getting fencing to work on my HP DL180 g6 servers. They have ilo100 controllers. The documentation mentions ipmi compliance, but there are problems. The ipmilan driver gets a response, but it is the wrong response. A status request results in the NMI line being asserted, which (in standard PC architecture) is the same as pressing the reset button (which these servers don't have). Here are some log excerpts: 16:33 just after re-running re-install from engine, which ended: *From oVirt GUI "Events" tab *Host s1 installed State was set to up for host s1. Host s3 from cluster Default was *chosen* as a proxy to execute Status command on Host s1 Host s1 power management was verified successfully 16:34 *on ssh screen:* Message from syslogd@s1 at Jan 21 16:34:14 ... kernel:Uhhuh. NMI received for unknown reason 31 on CPU 0. Message from syslogd@s1 at Jan 21 16:34:14 ... kernel:Do you have a strange power saving mode enabled? Message from syslogd@s1 at Jan 21 16:34:14 ... kernel:Dazed and confused, but trying to continue ***from IPMI web interface event log:* Generic 01/21/2014 21:34:15 Gen ID 0x21 Bus Uncorrectable Error Assertion Generic 01/21/2014 21:34:15 IOH_NMI_DETECT State Asserted Assertion * From oVirt GUI "Events" tab *Host s1 is non responsive Host s3 from cluster Default was chosen as a proxy to execute Restart command on Host s1 Host s3 from cluster Default was chosen as a proxy to execute Stop command on Host s1 Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1 Host s1 was stopped by engine Manual fence for host s1 was started Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1 Host s3 from cluster Default was chosen as a proxy to execute Start command on Host s1 Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1 Host s1 was started by engine Host s1 is rebooting State was set to up for host s1. Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1 16:41 saw kernel panic output on remote KVM terminal computer rebooted itself I have searched for ilo100, but find nothing related to ovirt, so am clueless as to what is the "correct" driver for this hardware. So far I have seen this mostly on server1 (s1), but that is also the one I have cycled up and down most often. I have also seen where the commands are apparently issued too fast (these servers are fairly slow booting). For example, I found that one server was powered down when the boot process had gotten to the stage where the RAID controller screen was up, so it had not had time to complete the boot that was already in progress. Ted Miller Elkhart, IN, USA --------------040009030705040405030507 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#FFFFFF"> I am having trouble getting fencing to work on my HP DL180 g6 servers.  They have ilo100 controllers.  The documentation mentions ipmi compliance, but there are problems.<br> <br> The ipmilan driver gets a response, but it is the wrong response.  A status request results in the NMI line being asserted, which (in standard PC architecture) is the same as pressing the reset button (which these servers don't have).<br> <br> Here are some log excerpts:<br> <br> <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;">16:33<br> </td> <td style="vertical-align: top;">just after re-running re-install from engine, which ended:<br> <b>From oVirt GUI "Events" tab<br> </b>Host s1 installed<br> State was set to up for host s1.<br> Host s3 from cluster Default was <b>chosen</b> as a proxy to execute Status command on Host s1<br> Host s1 power management was verified successfully<br> </td> </tr> <tr> <td style="vertical-align: top;">16:34<br> </td> <td style="vertical-align: top;"><b>on ssh screen:</b><br> Message from syslogd@s1 at Jan 21 16:34:14 ...<br>  kernel:Uhhuh. NMI received for unknown reason 31 on CPU 0.<br> <br> Message from syslogd@s1 at Jan 21 16:34:14 ...<br>  kernel:Do you have a strange power saving mode enabled?<br> <br> Message from syslogd@s1 at Jan 21 16:34:14 ...<br>  kernel:Dazed and confused, but trying to continue<br> <br> <b></b><b>from IPMI web interface event log:</b><br> <table id="Table1" class="datatable" cellpadding="5"> <tbody> <tr> <td>Generic</td> <td>01/21/2014</td> <td>21:34:15</td> <td>Gen ID 0x21</td> <td>Bus Uncorrectable Error</td> <td>Assertion</td> </tr> <tr> <td>Generic</td> <td>01/21/2014</td> <td>21:34:15</td> <td>IOH_NMI_DETECT</td> <td>State Asserted</td> <td>Assertion</td> </tr> </tbody> </table> <b><br> From oVirt GUI "Events" tab<br> </b>Host s1 is non responsive<br> Host s3 from cluster Default was chosen as a proxy to execute Restart command on Host s1<br> Host s3 from cluster Default was chosen as a proxy to execute Stop command on Host s1<br> Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1<br> Host s1 was stopped by engine<br> Manual fence for host s1 was started<br> Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1<br> Host s3 from cluster Default was chosen as a proxy to execute Start command on Host s1<br> Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1<br> Host s1 was started by engine<br> Host s1 is rebooting<br> State was set to up for host s1.<br> Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1<br> </td> </tr> <tr> <td style="vertical-align: top;">16:41<br> </td> <td style="vertical-align: top;">saw kernel panic output on remote KVM terminal<br> computer rebooted itself</td> </tr> </tbody> </table> <br> I have searched for ilo100, but find nothing related to ovirt, so am clueless as to what is the "correct" driver for this hardware.<br> <br> So far I have seen this mostly on server1 (s1), but that is also the one I have cycled up and down most often.<br> <br> I have also seen where the commands are apparently issued too fast (these servers are fairly slow booting).  For example, I found that one server was powered down when the boot process had gotten to the stage where the RAID controller screen was up, so it had not had time to complete the boot that was already in progress.<br> <br> Ted Miller<br> Elkhart, IN, USA<br> <br> </body> </html> --------------040009030705040405030507--

3 4

[Users] Reconfirming membership to do excessive bounces
by Pat Pierson 22 Jan '14

22 Jan '14

Sorry if this is a simple answer but I could not find anything on google about this. I keep having to reconfirm my membership with this list because I assume google is kicking back messages. Message is as follows: Your membership in the mailing list Users has been disabled due to excessive bounces The last bounce received from you was dated 21-Jan-2014. You will not get any more messages from this list until you re-enable your membership. You will receive 3 more reminders like this before your membership in the list is deleted. To re-enable your membership, you can simply respond to this message (leaving the Subject: line intact), or visit the confirmation page at Has anyone else had this issue with this list and gmail? if so how can i fix it? -- Patrick Pierson

2 1

[Users] membership disabled due to bouces again..
by Gianluca Cecchi 22 Jan '14

22 Jan '14

Already spotted this problem before... I just found that I lose e-mails from Tue Jan 21 11:45:10 EST 2014 to Wed Jan 22 15:35:51 EST 2014 And received only some minutes ago (22/Jan/2014 21:26 Italy Time) an e-mail regarding my disabled membership apparently occurred at Mon, Jan 20, 2014 at 4:11 PM so that I didn't either know before .... Any way to solve this? I have to mix e-mail received and archives... Gianluca

1 0

[Users] Black VM Install Console
by David Li 22 Jan '14

22 Jan '14

Hi, My first time to install a VM on ovirt has encountered a problem. I tried to open up a console to continue the install process. But all I got is a blank window and a request to save a file which I did. The window remained blank and I couldn't see any activities. I went to the node itself and tried to see if I could use virsh tool to understand what's going on. But I was asked for a username and password to perform any actions. Any idea what I should do at this time? David

9 36

Re: [Users] Problem with python-cpopen dependency on f19 AIO stable
by Martijn Grendelman 22 Jan '14

22 Jan '14

I have the same issue on a CentOS node after updating it to 6.5: > Resolving Dependencies > --> Running transaction check > ---> Package python-cpopen.x86_64 0:1.2.3-4.el6 will be obsoleted > ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.el6 will be obsoleting > --> Finished Dependency Resolution > > Dependencies Resolved > > ======================================================================================================================================================== > Package Arch Version Repository Size > ======================================================================================================================================================== > Installing: > vdsm-python-cpopen x86_64 4.13.0-11.el6 ovirt-stable 19 k > replacing python-cpopen.x86_64 1.2.3-4.el6 > > Transaction Summary > ======================================================================================================================================================== > Install 1 Package(s) > > Total download size: 19 k > Is this ok [y/N]: y On a subsequent run of 'yum update', python-cpopen will replace vdsm-python-cpopen, and so on. Cheers, Martijn. Vinzenz Feenstra schreef op 5-12-2013 8:34: > Forwading to vdsm-devel > > On 12/04/2013 08:59 AM, Gianluca Cecchi wrote: >> Hello, >> since yesterday evening I have this sort of dependency problem with updates >> >> yum update >> say >> >> Resolving Dependencies >> --> Running transaction check >> ---> Package python-cpopen.x86_64 0:1.2.3-4.fc19 will be obsoleting >> ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 will be obsoleted >> --> Finished Dependency Resolution >> >> Dependencies Resolved >> >> ============================================================================================================================= >> Package Arch Version >> Repository Size >> ============================================================================================================================= >> Installing: >> python-cpopen x86_64 >> 1.2.3-4.fc19 updates 19 k >> replacing vdsm-python-cpopen.x86_64 4.13.0-11.fc19 >> >> Transaction Summary >> ============================================================================================================================= >> Install 1 Package >> >> If I go ahead and run yum update again I have: >> >> Dependencies Resolved >> >> ============================================================================================================================= >> Package Arch Version >> Repository Size >> ============================================================================================================================= >> Installing: >> vdsm-python-cpopen x86_64 >> 4.13.0-11.fc19 ovirt-stable 20 k >> replacing python-cpopen.x86_64 1.2.3-4.fc19 >> >> Transaction Summary >> ============================================================================================================================= >> Install 1 Package >> >> and so again in a loop.... >> >> Gianluca >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > >

3 2

[Users] oVirt 3.3.3 Release Candidate is now available
by Sandro Bonazzola 22 Jan '14

22 Jan '14

The oVirt team is pleased to announce that the 3.3.3 Release Candidate is now available in ovirt-updates-testing [1]. Feel free to join us testing it[2] and verifying the bugzilla entries actually under verification [3]. Release notes for this update are available on the wiki [4]. A new oVirt Node build will be available soon as well. [1] http://resources.ovirt.org/releases/updates-testing [2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing [3] http://red.ht/KEesdK [4] http://www.ovirt.org/OVirt_3.3.3_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] Gluster volume snapshots feature UX feedback
by Malini Rao 22 Jan '14

22 Jan '14

Hi Shubendu, I saw your invite for your walkthrough on the feature - Gluster volume snapshots and also followed the feature link on the wiki and reviewed it. From the UX/ UI perspective, it looks good and I had only a couple of comments. The remove snapshot section seems to indicate an ability to delete multiple snapshots at once and I am not sure we support any batch actions as of now elsewhere in the tool. Ctrl+click is not supported on lists today I think. So, I wanted to find out if you were going to introduce this for your feature. If yes, then we should ensure all other grids are enabled with this multi-select capability. If not, we should refrain from introducing something just for this feature for the sake of consistency and across feature product cohesiveness. The other feedback I have is on the snapshot configuration dialog. It will be great if any units can be added to the right of the field because one is a number and the other is a percentage but the field labels are so similar sounding. The field labels with the dashes in between the words also make it look very homegrown and seems like we are exposing some internal labels to our users. Last but not least, since the terminology of 'snapshots' overlaps with VM snapshots, we should just ensure that no similar action does wildly different things although it seems like snapshotting here is much more simple. Hope this is helpful, Thanks Malini

2 1

[Users] Error when trying to create a new ISO storage domain
by Willard Dennis 21 Jan '14

21 Jan '14

--_84d40e63-2fba-48dd-8b16-7e7d22a9a18a_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all=2C I am trying to define a new ISO storage domain. I go to System > Storage=2C= click on the "New Domain" link=2C and fill in the requisite fields. "Domai= n Function / Storage Type" drop is set to "ISO / NFS"=2C and I verified tha= t I have the proper NFS path to the export on the NFS server I want to use.= However=2C when I click the "OK" button=2C I am getting the following popu= p: -----Error while executing action Add Storage Connection: Permission settin= gs on the specified path do not allow access to the storage.Verify permissi= on settings on the specified storage path.----- I have verified that I can manually mount the NFS filesystem on the host de= fined in the "Use Host" drop [as root]=2C and I have looked in /var/log/mes= sages (on the mounting host=2C as well as the NFS server=2C and do not see = any errors... Please not that the NFS export is a pre-existing share on the= NFS server=2C and does contain pre-existing data (ISOs=2C etc.) How can I debug this? = --_84d40e63-2fba-48dd-8b16-7e7d22a9a18a_ 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'>Hi all=2C<div><br></div><div>I a= m trying to define a new ISO storage domain. I go to System &gt=3B Storage= =2C click on the "New Domain" link=2C and fill in the requisite fields. "Do= main Function / Storage Type" drop is set to "ISO / NFS"=2C and I verified = that I have the proper NFS path to the export on the NFS server I want to u= se. However=2C when I click the "OK" button=2C I am getting the following p= opup:<br><div><br></div><div>-----</div><div><div>Error while executing act= ion Add Storage Connection: Permission settings on the specified path do no= t allow access to the storage.</div><div>Verify permission settings on the = specified storage path.</div></div></div><div>-----</div><div><br></div><di= v>I have verified that I can manually mount the NFS filesystem on the host = defined in the "Use Host" drop [as root]=2C and I have looked in /var/log/m= essages (on the mounting host=2C as well as the NFS server=2C and do not se= e any errors... Please not that the NFS export is a pre-existing share on t= he NFS server=2C and does contain pre-existing data (ISOs=2C etc.)</div><di= v><br></div><div>How can I debug this?</div> </div></body> </html>= --_84d40e63-2fba-48dd-8b16-7e7d22a9a18a_--

3 5

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

21 Jan '14

since the error suggests that the disk is locked, and UI is reporting that it's not, it seems that the issue is with some table in the db which still has the disk marked as locked while the disk status is taken from a different table. Allon, any idea what table this can be? On 01/20/2014 11:21 AM, Koen Vanoppen wrote: > Status ok... > > > 2014/1/20 Dafna Ron <dron(a)redhat.com <mailto:dron@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@gmail.com> > <mailto:vanoppen.koen@gmail.com > <mailto:vanoppen.koen@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> <mailto:dron@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>> > <mailto:dron@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>>> > <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>>>>> > > > > 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>>>> > <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>>>>>> > > > > 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>>>> > > <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@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>>>>>, "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>>>>>> > *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>>>>> > > <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 > <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>>>>> > <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 > <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@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>>>> <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>>>>>>> > > 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@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@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@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>>>>> > <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 <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@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@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@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>>>>> > <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 <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>>>>> > <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 <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>>>>> > <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 <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>>>> > <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 > > > us > > -- Dafna Ron > > > > > -- Dafna Ron > > > > > -- Dafna Ron > > > > > > -- > Dafna Ron > > -- Dafna Ron

3 8

[Users] libvirt migration port configuration and virPortAllocator
by Gianluca Cecchi 21 Jan '14

21 Jan '14

Hello, following the bugzilla here: https://bugzilla.redhat.com/show_bug.cgi?id=1019053 we have " This is now fixed by v1.1.3-188-g0196845 and v1.1.3-189-ge3ef20d " Does this mean that f19 that has libvirt-1.0.5.8-1.fc19.x86_64 is out? Any time soon to update it? I see at http://libvirt.org/sources/ files such as libvirt-1.1.4-1.fc19.x86_64.rpm since beginning of November... any particular reason for no packages neither in updates-testing repo? Also, Fedora 20 has libvirt-1.1.3.2-1.fc20.x86_64.rpm Did it receive the patch update? I see nothing particular in its changelog... Thanks in advance, Gianluca

5 6