- Users - oVirt List Archives

[Users] Instructions to add a remote controlled power strip not in the native list?
by David Smith 16 Apr '14

16 Apr '14

We use Raritan / Dominion PX remote power blocks, is there a way to easily add support for these? On a feature request side, seems like adding support for generic wouldn't be too hard; just ask for what the login/password prompts look like, what the main prompt is, and the command sequence to turn on and off a port as well as logout.

6 40

Export domain. Same LUN but different NFS server : update SQL table?
by Nicolas Ecarnot 16 Apr '14

16 Apr '14

Hi, Our NFS storage domain is stored as a LUN, and served via a NFS server. I have to change this NFS server, but I don't need to change the LUN. After setting this NFS export domain in maintenance and detached, is it safe to just update the database table "storage_server_connections" and restart the engine? Regards, PS : I read no answer to this : http://lists.ovirt.org/pipermail/users/2014-March/022610.html -- Nicolas Ecarnot

1 2

off topic = newbie with bugzilla, gerrit and ovirt VDSM 4.14
by Tamer Lima 16 Apr '14

16 Apr '14

Hi, I have a problem with an automatic yum vdsm upgrade (4.13 to 4.14) on ovirt 3.3 : Host x.x.x.x is installed with VDSM version (4.14) and cannot join cluster Default which is compatible with VDSM versions [4.13,4.9,4.11,4.12,4.10]. I am searching the solution and one of them (from bz Bug 1083008 ) points to gerrit site(http://gerrit.ovirt.org/#/c/23456/) I do not have any experience in solving bugs, neither bz, gerrit, github.... How to initialize in this world and solve the ovirt problem ? another thing : does downgrade or remove vdms package excludes the installed virtual machines ? I know about ovirt 3.4 is the new release, but I want to learn how to solve some bugs when new releases is not launched; (off course I am afraid to upgrade to ovirt 3.4 too :) ) Tamer

4 6

Re: [ovirt-users] SPM error
by Maurice James 16 Apr '14

16 Apr '14

What did you do to try to fix the sanlock? Anything is better than nothing at this point ----- Original Message ----- From: "Ted Miller" <tmiller(a)hcjb.org> To: "Maurice James" <mjames(a)media-node.com> Sent: Friday, April 11, 2014 7:27:24 PM Subject: Re: [ovirt-users] SPM error I did receive some help on one stage of rebuilding my sanlock, but there were too many other things wrong to get it started again. Only advice I have is -- look at your sanlock logs, and see if you can find anything there that is helpful. On 4/11/2014 7:23 PM, Maurice James wrote: > Nooooooo. > > > Sent from my Galaxy S®III > > -------- Original message -------- > From: Ted Miller <tmiller(a)hcjb.org> > Date:04/11/2014 7:08 PM (GMT-05:00) > To: Maurice James <mjames(a)media-node.com> > Subject: Re: [ovirt-users] SPM error > > > > I didn't, really. I did something wrong along the way, and ended up having > to rebuild the engine and hosts. (My problems were due to a glusterfs > split-brain.) > Ted Miller > > On 4/11/2014 6:03 PM, Maurice James wrote: >> How did you fix it? >> >> >> Sent from my Galaxy S®III >> >> -------- Original message -------- >> From: Ted Miller <tmiller(a)hcjb.org> >> Date:04/11/2014 6:00 PM (GMT-05:00) >> To: users(a)ovirt.org >> Subject: Re: [ovirt-users] SPM error >> >> >> >> On 4/11/2014 2:05 PM, Maurice James wrote: >>> I have an error trying to bring the master DC back online. After several >>> reboots, no luck. I took the other cluster members offline to try to >>> troubleshoot. The remaining host is constantly in contention with itself >>> for SPM >>> >>> >>> ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] >>> (DefaultQuartzScheduler_Worker-40) [38d400ea] >>> IrsBroker::Failed::GetStoragePoolInfoVDS due to: >>> IrsSpmStartFailedException: IRSGenericException: IRSErrorException: >>> SpmStart failed >>> >> I'm no expert, but the last time I beat my head on that rock, something was >> wrong with my sanlock storage. YMMV >> Ted Miller >> Elkhart, IN, USA >> -- "He is no fool who gives what he cannot keep, to gain what he cannot lose." - - Jim Elliot For more information about Jim Elliot and his unusual life, see http://www.christianliteratureandliving.com/march2003/carolyn.html. Ted Miller Design Engineer HCJB Global Technology Center, a ministry of Reach Beyond 2830 South 17th St Elkhart, IN 46517 574--970-4272 my desk 574--970-4252 receptionist

5 13

[Users] Otopi pre-seeded answers and firewall settings
by Giuseppe Ragusa 16 Apr '14

16 Apr '14

--_a5ec309a-8526-4910-aaa4-2d74d77ba60d_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all=2C I'm trying to automate as much as possible of ovirt-hosted-engine-setup and= engine-setup by means of otopi answer files passed in using "--config-appe= nd=3Dfilename.conf". I succeded in forcing engine-setup to leave my iptables settings alone with= : OVESETUP_CONFIG/firewallManager=3Dstr:iptables OVESETUP_CONFIG/updateFirewall=3Dbool:False but ovirt-hosted-engine-setup still modified my iptables settings even with= the following options: OVEHOSTED_NETWORK/firewallManager=3Dstr:iptables OVEHOSTED_NETWORK/iptablesEnable=3Dbool:False Maybe I used the wrong option (deduced by looking inside source code). Does anybody have any hint/suggestion? Many thanks in advance=2C Giuseppe = --_a5ec309a-8526-4910-aaa4-2d74d77ba60d_ 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<br>I'm trying to autom= ate as much as possible of ovirt-hosted-engine-setup and engine-setup by me= ans of otopi answer files passed in using "--config-append=3Dfilename.conf"= .<br><br>I succeded in forcing engine-setup to leave my iptables settings a= lone with:<br><br>OVESETUP_CONFIG/firewallManager=3Dstr:iptables<br>OVESETU= P_CONFIG/updateFirewall=3Dbool:False<br><br>but ovirt-hosted-engine-setup s= till modified my iptables settings even with the following options:<br><br>= OVEHOSTED_NETWORK/firewallManager=3Dstr:iptables<br>OVEHOSTED_NETWORK/iptab= lesEnable=3Dbool:False<br><br>Maybe I used the wrong option (deduced by loo= king inside source code).<br><br>Does anybody have any hint/suggestion?<br>= <br>Many thanks in advance=2C<br>Giuseppe<br> </div></body> </html>= --_a5ec309a-8526-4910-aaa4-2d74d77ba60d_--

5 13

VM samba4 is down. Exit message: 'int' object has no attribute 'replace'.
by René Koch 16 Apr '14

16 Apr '14

Hi, I configured Network QoS in my oVirt 3.4 setup, but can't start vms. Here are the steps I did: - Create QoS in Data Centers - Network QoS tab (Name: testing, limits: 10/10/100, 10/10/100) - Add QoS to vNIC Profile using Networks - vNIC Profile - edit When I try to start a vm the following error is shown in vdsm.log: Thread-837844::ERROR::2014-04-14 12:45:51,822::vm::2289::vm.Vm::(_startUnderlyingVm) vmId=`d7034850-c274-48f7-ac0f-b3d4cc57c255`::The vm start process failed Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 2249, in _startUnderlyingVm self._run() File "/usr/share/vdsm/vm.py", line 3135, in _run domxml = hooks.before_vm_start(self._buildCmdLine(), self.conf) File "/usr/share/vdsm/vm.py", line 2965, in _buildCmdLine self._appendDevices(domxml) File "/usr/share/vdsm/vm.py", line 2922, in _appendDevices deviceXML = dev.getXML().toxml(encoding='utf-8') File "/usr/lib64/python2.6/xml/dom/minidom.py", line 45, in toxml return self.toprettyxml("", "", encoding) File "/usr/lib64/python2.6/xml/dom/minidom.py", line 59, in toprettyxml self.writexml(writer, "", indent, newl) File "/usr/share/vdsm/vm.py", line 5268, in __hacked_writexml node.writexml(writer, indent + addindent, addindent, newl) File "/usr/share/vdsm/vm.py", line 5268, in __hacked_writexml node.writexml(writer, indent + addindent, addindent, newl) File "/usr/share/vdsm/vm.py", line 5256, in __hacked_writexml xml.dom.minidom._write_data(writer, attrs[a_name].value) File "/usr/lib64/python2.6/xml/dom/minidom.py", line 301, in _write_data data = data.replace("&", "&").replace("<", "<") AttributeError: 'int' object has no attribute 'replace' Thread-837844::DEBUG::2014-04-14 12:45:51,826::vm::2731::vm.Vm::(setDownStatus) vmId=`d7034850-c274-48f7-ac0f-b3d4cc57c255`::Changed state to Down: 'int' object has no attribute 'replace' When removing the QoS (or better say put it to unlimited) my vm is starting fine. My host is running CentOS 6.5 with latest updates. -- Best Regards René Koch Senior Solution Architect ============================================ LIS-Linuxland GmbH Brünner Straße 163, A-1210 Vienna Phone: +43 1 236 91 60 Mobile: +43 660 / 512 21 31 E-Mail: rkoch(a)linuxland.at ============================================

5 5

[Users] Updating AIO from 3.3.4 to 3.4
by Gianluca Cecchi 16 Apr '14

16 Apr '14

Hello, I know that AIO setup is only for experimenting and trying but I find it very useful in several situations. So having a 3.3.4 All-In_one installation on fedora19 and wanting to update it to 3.4 I have some doubts. In release notes I see for general updates: On Fedora 19 you'll need to enable fedora-updates repository for having updated openstack packages --> OK. It is normally already enabled On Fedora 19, you'll need to enable fedora-virt-preview repository for using Fedora 19 as node on 3.4 clusters --> how do I managed this? This is indeed a node too, so I have to enable virt-preview for it? Correct? BTW: Is this note still true in general or did the related virt packages go into fedora-updates, or is it planned in coming days/weeks? When engine-setup is run and detects that a newer version is available and outputs that I have to run yum update ovirt-engine-setup is it correct to say that in AIO setups I should actually run yum update ovirt-engine-setup ovirt-engine-setup-plugin-allinone or is it the latest package not crucial to be updated before new engine-setup is run? At the end of engine update can I simply put the AIO server into maintenance (as a node) and run "yum update" so that vdsm (aka node) packages are updated too and so the server will become a 3.4 enabled node after reboot? Thanks, Gianluca

3 2

almost there
by info＠aliengine.it 16 Apr '14

16 Apr '14

Hello everyone I wrestled alot to come to this point now I am in the process to install the first kvm but when I click on run once it seems unable to find the iso. please help

2 1

Hosted engine
by Maurice James 16 Apr '14

16 Apr '14

------=_Part_847_689313863.1397585333502 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Scenario I have a hosted engine setup with 2 nodes with shared iscsi storage. Question: If I yanked the plug on the host that the hosted engine vm is running on, will it come back up on the remaining host without any intervention? ------=_Part_847_689313863.1397585333502 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div><br>Scenario</div><div>I have a hosted engine setup with 2 nodes with shared iscsi storage.<br></div><div><br></div><div>Question:<br></div><div>If I yanked the plug on the host that the hosted engine vm is running on, will it come back up on the remaining host without any intervention?<br></div></div></body></html> ------=_Part_847_689313863.1397585333502--

5 6

Adding user in engine WEB UI
by Gabi C 15 Apr '14

15 Apr '14

Hello! Besides having "a directory server of some kind" as per http://comments.gmane.org/gmane.comp.emulators.ovirt.user/3850 aren't any other possibilities of adding user, especially a local one? Thanks!

4 5

[Users] Guest Agent for SLES 11 SP3
by Markus Stockhausen 15 Apr '14

15 Apr '14

------=_NextPartTM-000-78d3c075-3b0c-4294-9f84-27837d09c495 Content-Type: multipart/alternative; boundary="_000_12EF8D94C6F8734FB2FF37B9FBEDD173585F34B4EXCHANGEcollogi_" --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585F34B4EXCHANGEcollogi_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, http://lists.ovirt.org/pipermail/users/2013-November/018130.html suggests that there exists a guest agent for SLES 11 SP3. Could someone provide a download link? Thanks. Markus --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585F34B4EXCHANGEcollogi_ 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,<br> <br> <a href=3D"http://lists.ovirt.org/pipermail/users/2013-November/018130.html= " target=3D"_blank">http://lists.ovirt.org/pipermail/users/2013-November/01= 8130.html</a> suggests <br> that there exists a guest agent for SLES 11 SP3. Could someone provide a <b= r> download link?<br> <br> Thanks.<br> <br> Markus<br> <br> <br> </div> </body> </html> --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585F34B4EXCHANGEcollogi_-- ------=_NextPartTM-000-78d3c075-3b0c-4294-9f84-27837d09c495 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-78d3c075-3b0c-4294-9f84-27837d09c495--

2 3

[Users] hosted engine setup (NFS)
by René Koch 15 Apr '14

15 Apr '14

Hi, I installed hosted engine and faced an issue with NFS during installation. First of all, I'm using GlusterFS on my storage and ovirt engine doesn't support GlusterFS yet, only NFS. But for NFS I can't use mountprotpo=tcp as hosted-engine --setup doesn't ask for NFS options. So I manually edited the following file: /usr/share/ovirt-hosted-engine-setup/plugins/ovirt-hosted-engine-setup/storage/storage.py and changed opts.append('vers=3'): if domain_type == 'nfs3': fstype = 'nfs' opts.append('vers=3,mountproto=tcp') My question is now: is it possible to ask for NFS options during setup or do you think this can lead into problems? NFS via TCP worked fine for me for one week until I rebooted the host today (did reboot tests last weeks, too which was fine) and can't start hosted engine anymore (see other mail thread), but I think the other issue is not NFS mountproto related. -- Best Regards René Koch Senior Solution Architect ============================================ LIS-Linuxland GmbH Brünner Straße 163, A-1210 Vienna Phone: +43 1 236 91 60 Mobile: +43 660 / 512 21 31 E-Mail: rkoch(a)linuxland.at ============================================

3 3

Error creating Disks
by Maurice James 14 Apr '14

14 Apr '14

------=_Part_495_1151800014.1397484037085 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit oVirt Engine Version: 3.4.1-0.0.master.20140412010845.git43746c6.el6 While attempting to create a disk on an NFS storage domain, it fails with the following error in the engine.log 2014-04-14 09:58:12,127 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand] (DefaultQuartzScheduler_Worker-72) Failed in HSMGetAllTasksStatusesVDS method 2014-04-14 09:58:12,139 ERROR [org.ovirt.engine.core.bll.SPMAsyncTask] (DefaultQuartzScheduler_Worker-72) BaseAsyncTask::LogEndTaskFailure: Task ee6ce682-bd76-467a-82d2-d227229cb9de (Parent Command AddDisk, Parameters Type org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters) ended with failure: 2014-04-14 09:58:12,159 ERROR [org.ovirt.engine.core.bll.AddDiskCommand] (org.ovirt.thread.pool-6-thread-9) [483e53d6] Ending command with failure: org.ovirt.engine.core.bll.AddDiskCommand 2014-04-14 09:58:12,212 ERROR [org.ovirt.engine.core.bll.AddImageFromScratchCommand] (org.ovirt.thread.pool-6-thread-9) [ab1e0be] Ending command with failure: org.ovirt.engine.core.bll.AddImageFromScratchCommand ------=_Part_495_1151800014.1397484037085 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"font-family: times new roman, new york, times, se= rif; font-size: 12pt; color: #000000"><div><span style=3D"font-family: 'Ari= al Unicode MS', Arial, sans-serif; font-size: small; text-align: -webkit-ce= nter; background-color: #ffffff;" data-mce-style=3D"font-family: 'Arial Uni= code MS', Arial, sans-serif; font-size: small; text-align: -webkit-center; = background-color: #ffffff;">oVirt Engine Version: 3.4.1-0.0.master.20140412= 010845.git43746c6.el6</span></div><div><span style=3D"font-family: 'Arial U= nicode MS', Arial, sans-serif; font-size: small; text-align: -webkit-center= ; background-color: #ffffff;" data-mce-style=3D"font-family: 'Arial Unicode= MS', Arial, sans-serif; font-size: small; text-align: -webkit-center; back= ground-color: #ffffff;"><br></span></div><div><br></div><div>While attempti= ng to create a disk on an NFS storage domain, it fails with the following e= rror in the engine.log</div><div><br></div><div><br></div><div><p style=3D"= margin: 0px;" data-mce-style=3D"margin: 0px;">2014-04-14 09:58:12,127 ERROR= [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSComman= d] (DefaultQuartzScheduler_Worker-72) Failed in HSMGetAllTasksStatusesVDS m= ethod<br>2014-04-14 09:58:12,139 ERROR [org.ovirt.engine.core.bll.SPMAsyncT= ask] (DefaultQuartzScheduler_Worker-72) BaseAsyncTask::LogEndTaskFailure: T= ask ee6ce682-bd76-467a-82d2-d227229cb9de (Parent Command AddDisk, Parameter= s Type org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters) ended w= ith failure:<br>2014-04-14 09:58:12,159 ERROR [org.ovirt.engine.core.bll.Ad= dDiskCommand] (org.ovirt.thread.pool-6-thread-9) [483e53d6] Ending command = with failure: org.ovirt.engine.core.bll.AddDiskCommand<br>2014-04-14 09:58:= 12,212 ERROR [org.ovirt.engine.core.bll.AddImageFromScratchCommand] (org.ov= irt.thread.pool-6-thread-9) [ab1e0be] Ending command with failure: org.ovir= t.engine.core.bll.AddImageFromScratchCommand</p></div><div><br></div><div><= span name=3D"x"></span><div><span style=3D"font-family: 'trebuchet ms', san= s-serif;" data-mce-style=3D"font-family: 'trebuchet ms', sans-serif;"></spa= n></div></div></div></body></html> ------=_Part_495_1151800014.1397484037085--

5 40

Disable auth basic in API
by Jose Manuel Marquez Alhambra 14 Apr '14

14 Apr '14

Hi, I’m testing a connection broker that uses oVirt's API. At the moment, the connection broker doesn’t work because it doesn’t send the basic authentication to oVirt's API. I contacted the developers and they're investigating the error. While they solve the error, I would like to continue testing the connection broker. Is there any way to disable auth basic in oVirt's API? I’m using it in a testing environment (oVirt 3.4 at CentOS 6), so I’m not worried about security risks. Thank you. Regards, Jose

3 3

minimum DNS requirements for /etc/hosts
by Jeremiah Jahn 14 Apr '14

14 Apr '14

So like the nut job I am, I host my dns server on a virtual machine that is now hosted by ovirt, I also have a few gateway machine in there as well for routing traffic between internal networks. With virt-manager, DNS rarely seemed to be an issue. I'd connect to a host IP, and bring up the vm, no problem. Ovirt on the other hand takes forever if dns is down. So i've passed around a /etc/hosts file to resolve any ip address that ovirt might be looking for while dns is out. I'd like to verify at an abstract level, what needs to be in said file, to keep everything from timing out, or just taking forever. name and FQDN of each host name and FQDN of engine host name and FQDN of each storage domain. Is this enough, or are there other places/things the ovirt node and hosts might be trying to resolve? thanks, -jj-

3 2

Re: [ovirt-users] minimum DNS requirements for /etc/hosts
by Jeremiah Jahn 14 Apr '14

14 Apr '14

I only use names for storage, but didn't have entries for the engine yet, So I think ssh was slow since it couldn't do reverse DNS lookups against the engine where my consoles are coming from. Thanks for the input. I wanted to verify before testing since this is a production environment. It seems like even the XMLRPC code must try and do a reverse DNS against the engine as well, not just ssh. Seems like the engine hosts also needs said hosts file as well.. On Mon, Apr 14, 2014 at 8:23 AM, René Koch <rkoch(a)linuxland.at> wrote: > On 04/14/2014 03:08 PM, Jeremiah Jahn wrote: >> >> So like the nut job I am, I host my dns server on a virtual machine >> that is now hosted by ovirt, I also have a few gateway machine in >> there as well for routing traffic between internal networks. With >> virt-manager, DNS rarely seemed to be an issue. I'd connect to a host >> IP, and bring up the vm, no problem. Ovirt on the other hand takes >> forever if dns is down. So i've passed around a /etc/hosts file to >> resolve any ip address that ovirt might be looking for while dns is >> out. I'd like to verify at an abstract level, what needs to be in >> said file, to keep everything from timing out, or just taking forever. >> >> name and FQDN of each host >> name and FQDN of engine host >> name and FQDN of each storage domain. >> >> Is this enough, or are there other places/things the ovirt node and >> hosts might be trying to resolve? > > > Afaik this should be enough. > Just remember that e.g. ssh login will still be slow if the DNS server isn't > reachable as you have to wait until it reaches a timeout. > > My oVirt setup doesn't have any DNS entry - just the hosts and engine in > /etc/hosts. But I don't use DNS names at all only IP addresses... > > > Regards, > René > >> >> thanks, >> -jj- >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >

1 0

Re: [ovirt-users] [Users] hosted engine setup (NFS)
by Sandro Bonazzola 14 Apr '14

14 Apr '14

Il 14/04/2014 14:23, René Koch ha scritto: > > On 04/14/2014 12:39 PM, Sandro Bonazzola wrote: >> Il 03/03/2014 12:39, René Koch ha scritto: >>> Hi, >>> >>> I installed hosted engine and faced an issue with NFS during installation. >>> >>> First of all, I'm using GlusterFS on my storage and ovirt engine doesn't support GlusterFS yet, only NFS. >>> >>> But for NFS I can't use mountprotpo=tcp as hosted-engine --setup doesn't ask for NFS options. >>> >>> So I manually edited the following file: >>> /usr/share/ovirt-hosted-engine-setup/plugins/ovirt-hosted-engine-setup/storage/storage.py >>> >>> and changed opts.append('vers=3'): >>> >>> if domain_type == 'nfs3': >>> fstype = 'nfs' >>> opts.append('vers=3,mountproto=tcp') >>> >>> My question is now: is it possible to ask for NFS options during setup or do you think this can lead into problems? NFS via TCP worked fine for me for >>> one week until I rebooted the host today (did reboot tests last weeks, too which was fine) and can't start hosted engine anymore (see other mail >>> thread), but I think the other issue is not NFS mountproto related. >>> >>> >> >> Well, in hosted-engine setup we don't ask for additional options because we don't store them. >> We just ask for nfs3 or nfs4 because we pass that value as protocol version to VDSM connectStorageServer verb. >> The above change affects only the temporary mount done for validating the domain. > > Thanks a lot for the information. > > Btw, I can mount mit GlusterFS 3.4.2 NFS share now without specifying -o mountproto=tcp. Is upd now possible or is the protocol determined > automatically now? I didn't test if hosted-engine-setup is able to mount GlusterFS NFS shares now without hacks, too - only discovered this new > behavior on my hosts. I don't know > > Slightly off-topic question: > The storage options are stored in /etc/ovirt-hosted-engine/hosted-engine.conf, right? If I want to change the ip address of my storage I simply put > engine into global maintenance mode, change IP in hosted-engine.conf and re-enable hsoted-engine vm again? Or are there more steps required? yes, storage info are stored in /etc/ovirt-hosted-engine/hosted-engine.conf. By the way, if you want to propagate the info on new hypervisors when you run deploy on them, you should also update the answer file in /etc/ovirt-hosted-engine/answers.conf so it will be configured automatically in newly installed hypervisors > > > Regards, > René > >> -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Re: [Users] 2 virtual monitors for Fedora guest
by Gianluca Cecchi 14 Apr '14

14 Apr '14

Some prelimianry tests at my side. oVirt 3.4 on fedora 19 AIO. Datacenter and cluster configured as 3.4 level Some packages on it libvirt-1.1.3.2-1.fc19.x86_64 qemu-kvm-1.6.1-2.fc19.x86_64 vdsm-4.14.6-0.fc19.x86_64 spice-server-0.12.4-3.fc19.x86_64 guest is an updated Fedora 19 system configured based on blank template and OS=Linux and xorg-x11-drv-qxl-0.1.1-3.fc19.x86_64 spice-vdagent-0.14.0-5.fc19.x86_64 Client is an updated Fedora 20 box with virt-viewer-0.6.0-1.fc20.x86_64 If I select the "Single PCI" checkbox in console options of guest and connect from the Fedora 20 client I don't see at all an option in remote-viewer to open a second display and no new display detected in guest. And lspci on guest indeed gives only one video controller. BTW: what is this option for, apart the meaning? If I deselect the "Single PCI" checkbox I get the "Display 2" option in remote-viewer but it is greyed out. No new monitor in "detect displays" of guest. In this last situation I have on host this qem-kvm command line: qemu 16664 1 48 21:04 ? 00:02:42 /usr/bin/qemu-system-x86_64 -machine accel=kvm -name f19 -S -machine pc-1.0,accel=kvm,usb=off -cpu Opteron_G3 -m 2048 -realtime mlock=off -smp 1,maxcpus=160,sockets=160,cores=1,threads=1 -uuid 55d8b95b-f420-4208-a2fb-5f370d05f5d8 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=19-8,serial=E0E1001E-8C00-002A-6F9A-90E6BAC9F1E1,uuid=55d8b95b-f420-4208-a2fb-5f370d05f5d8 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/f19.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-04-08T19:04:45,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -device usb-ccid,id=ccid0 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/_data_DATA2/b24b94c7-5935-4940-9152-36ecd370ba7c/images/5e99a818-9fd1-47bb-99dc-50bd25374c2f/a2baa1e5-569f-4081-97a7-10ec2a20daab,if=none,id=drive-virtio-disk0,format=raw,serial=5e99a818-9fd1-47bb-99dc-50bd25374c2f,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:a8:01:55,bus=pci.0,addr=0x3 -chardev spicevmc,id=charsmartcard0,name=smartcard -device ccid-card-passthru,chardev=charsmartcard0,id=smartcard0,bus=ccid0.0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/55d8b95b-f420-4208-a2fb-5f370d05f5d8.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/55d8b95b-f420-4208-a2fb-5f370d05f5d8.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice tls-port=5901,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,bus=pci.0,addr=0x2 -device qxl,id=video1,ram_size=67108864,vram_size=33554432,bus=pci.0,addr=0x8 -device AC97,id=sound0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 On guest: [root@localhost ~]# lspci 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 03) 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 01) 00:05.0 Communication controller: Red Hat, Inc Virtio console 00:06.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:07.0 RAM memory: Red Hat, Inc Virtio memory balloon 00:08.0 Display controller: Red Hat, Inc. QXL paravirtual graphic card (rev 03) See here Xorg.0.log generated on guest: https://drive.google.com/file/d/0BwoPbcrMv8mvTm9VbE53ZmVKcVk/edit?usp=shari… In particular I see in it many: [ 64.234] (II) qxl(0): qxl_xf86crtc_resize: Placeholder resize 1024x768 [ 87.280] qxl_surface_create: Bad bpp: 1 (1) [ 87.280] qxl_surface_create: Bad bpp: 1 (1) [ 87.949] qxl_surface_create: Bad bpp: 1 (1) [ 110.469] qxl_surface_create: Bad bpp: 1 (1) [ 110.478] qxl_surface_create: Bad bpp: 1 (1) [ 146.096] - 0th attempt [ 146.096] - OOM at 962 511 24 (= 1474746 bytes) [ 146.096] Cache contents: null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null 1008 997 1007 1005 1018 1003 1009 1011 1001 1012 1019 1016 1006 1013 total: 14 [ 146.107] - 1th attempt [ 146.107] - OOM at 962 511 24 (= 1474746 bytes) Gianluca

5 10

Call for Papers Extension: USENIX Lisa
by Brian Proffitt 14 Apr '14

14 Apr '14

All: Just a note to let you know that the CfP for USENIX LISA has been extended to this Friday, April 18, 2014, 11:59 p.m. PDT https://www.usenix.org/conference/lisa14/call-for-participation/papers-post… So you have a little more time to get a presentation in! BKP -- Brian Proffitt - oVirt Community Manager Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

1 0

List disk images residing on specific lun
by Amedeo Salvati 13 Apr '14

13 Apr '14

Hello, does anyone know if it's possible, using ovirt-shell or api, to list every disk image residing on specific FC LUN? best regards Amedeo Salvati

3 5

dependency error when upgrade ovirt 3.3 -> 3.4 (CentOS)
by H. Haven Liu 13 Apr '14

13 Apr '14

Hello, I'm trying to upgrade an ovirt 3.3 installation to 3.4, but getting a dependency error. I tried to update the ovirt-engine-setup package to v 3.4.0-1.el6, which requires ovirt-engine-setup-plugin-ovirt-engine = 3.4.0-1.el6, which requires ovirt-engine >= 3.3.2. However, it appears that ovirt-engine 3.3 is in the versionlock list and cannot be updated. Should I manually disable the versionlock plugin, or am I missing something? Thanks, Haven

2 1

[Users] oVirt 3.4 Templates break Foreman Provisioning/Adding host
by Matt . 13 Apr '14

13 Apr '14

Hi Guys, On Foreman 1.4.2 it seems that you have issues with oVirt 3.4 when adding a host. When you add this host you will get an error as oVirt now has more templating stuff: VM template.id|name required for add Is there a workaround for this to get the creation of VM go further ? Thanks! Matt

5 13

Re: [ovirt-users] help.. vm trapped in limbo aka can't acquire exclusive lock
by Arik Hadas 13 Apr '14

13 Apr '14

Hi Jeremiah, Thanks for providing the relevant information from the engine log. A fix was just merged to 3.4 branch. For more info about the bug and the solution see: https://bugzilla.redhat.com/1086280 Note that in the meantime you can unlock the VM by restarting the engine as Roy mentioned. Regards, Arik ----- Original Message ----- > > > ----- Forwarded Message ----- > > From: "Jeremiah Jahn" <jeremiah(a)goodinassociates.com> > > To: "Yair Zaslavsky" <yzaslavs(a)redhat.com> > > Cc: users(a)ovirt.org > > Sent: Thursday, April 10, 2014 5:48:24 AM > > Subject: Re: [ovirt-users] help.. vm trapped in limbo aka can't acquire > > exclusive lock > > > > here's the start of the problem. If you really want the WHOLE log I > > can do that too, but this is where I ask it to migrate, and where it > > fails. After which it just keeps repeating that it can't get the lock. > > > > > > > > 2014-04-09 14:18:48,050 INFO > > [org.ovirt.engine.core.bll.MigrateVmCommand] > > (DefaultQuartzScheduler_Worker-33) Lock freed to object EngineLock > > [exclusiveLocks= key: > > 0af0aaf6-85cf-4c67-9744-68a63601ab85 value: VM > > , sharedLocks= ] > > 2014-04-09 14:19:32,177 INFO > > [org.ovirt.engine.core.bll.MigrateVmCommand] (ajp--127.0.0.1-8702-1) > > [4350ffd] Lock Acquired to object EngineLock [exclusiveLocks= key: > > b0108933-deb2-4fa0-ae74-e10cefbb0cea value: VM > > , sharedLocks= ] > > 2014-04-09 14:19:32,199 INFO > > [org.ovirt.engine.core.bll.MigrateVmCommand] > > (org.ovirt.thread.pool-6-thread-16) [4350ffd] Running command: > > MigrateVmCommand internal: false. Entities affected : ID: > > b0108933-deb2-4fa0-ae74-e10cefbb0cea Type: VM > > 2014-04-09 14:19:32,203 INFO > > [org.ovirt.engine.core.bll.scheduling.policyunits.HaReservationWeightPolicyUnit] > > (org.ovirt.thread.pool-6-thread-16) [4350ffd] Started HA reservation > > scoring method > > 2014-04-09 14:19:32,208 INFO > > [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] > > (org.ovirt.thread.pool-6-thread-16) [4350ffd] START, > > MigrateVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31, > > dstVdsId=ce6b5b29-778f-4812-97b5-950f3d3b6c71, > > dstHost=10.10.4.34:54321, migrationMethod=ONLINE, > > tunnelMigration=false, migrationDowntime=0), log id: 745cd0ba > > 2014-04-09 14:19:32,209 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] > > (org.ovirt.thread.pool-6-thread-16) [4350ffd] > > VdsBroker::migrate::Entered > > (vm_guid=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31, > > dstHost=10.10.4.34:54321, method=online > > 2014-04-09 14:19:32,210 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] > > (org.ovirt.thread.pool-6-thread-16) [4350ffd] START, > > MigrateBrokerVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31, > > dstVdsId=ce6b5b29-778f-4812-97b5-950f3d3b6c71, > > dstHost=10.10.4.34:54321, migrationMethod=ONLINE, > > tunnelMigration=false, migrationDowntime=0), log id: 5de39b66 > > 2014-04-09 14:19:32,224 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] > > (org.ovirt.thread.pool-6-thread-16) [4350ffd] FINISH, > > MigrateBrokerVDSCommand, log id: 5de39b66 > > 2014-04-09 14:19:32,228 INFO > > [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] > > (org.ovirt.thread.pool-6-thread-16) [4350ffd] FINISH, > > MigrateVDSCommand, return: MigratingFrom, log id: 745cd0ba > > 2014-04-09 14:19:32,233 INFO > > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > > (org.ovirt.thread.pool-6-thread-16) [4350ffd] Correlation ID: 4350ffd, > > Job ID: 433cbdce-90b3-41ed-bbfe-3a10ea2c6616, Call Stack: null, Custom > > Event ID: -1, Message: Migration started (VM: web.judici, Source: > > kvm01.virt, Destination: kvm04, User: admin). > > 2014-04-09 14:19:33,465 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-62) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm04 > > ignoring it in the refresh until migration is done > > 2014-04-09 14:19:34,268 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-74) VM web.judici > > b0108933-deb2-4fa0-ae74-e10cefbb0cea moved from MigratingFrom --> Up > > 2014-04-09 14:19:34,269 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-74) Adding VM > > b0108933-deb2-4fa0-ae74-e10cefbb0cea to re-run list > > 2014-04-09 14:19:34,269 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] > > (DefaultQuartzScheduler_Worker-74) START, FullListVdsCommand(HostName > > = kvm01.virt, HostId = fa455012-b929-4805-a5c1-50e6c788039a, > > vds=Host[kvm01.virt], vmIds=[b0108933-deb2-4fa0-ae74-e10cefbb0cea]), > > log id: 6936226f > > 2014-04-09 14:19:34,279 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] > > (DefaultQuartzScheduler_Worker-74) FINISH, FullListVdsCommand, return: > > [{displaySecurePort=5905, kvmEnable=true, nicModel=rtl8139,pv, > > keyboardLayout=en-us, displayIp=0, pauseCode=NOERR, nice=0, > > pitReinjection=false, timeOffset=0, transparentHugePages=true, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, acpiEnable=true, custom={}, > > spiceSslCipherSuite=DEFAULT, memSize=8192, displayPort=5904, smp=4, > > emulatedMachine=rhel6.5.0, status=Up, vmType=kvm, > > memGuaranteedSize=1024, display=qxl, pid=30289, smartcardEnable=false, > > smpCoresPerSocket=1, > > spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard, > > maxVCpus=160, clientIp=10.10.4.242, > > devices=[Ljava.lang.Object;@610edb5f, vmName=web.judici, > > cpuType=Penryn}], log id: 6936226f > > 2014-04-09 14:19:34,281 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-74) Received a console Device without > > an address when processing VM b0108933-deb2-4fa0-ae74-e10cefbb0cea > > devices, skipping device: {alias=console0, specParams={}, > > device=console, type=console, > > deviceId=05fba965-133e-4810-a87c-1688be8beb5a} > > 2014-04-09 14:19:34,294 ERROR > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-74) Rerun vm > > b0108933-deb2-4fa0-ae74-e10cefbb0cea. Called from vds kvm01.virt > > 2014-04-09 14:19:34,299 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) START, > > MigrateStatusVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea), log id: 16ec0461 > > 2014-04-09 14:19:34,346 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) Failed in MigrateStatusVDS method > > 2014-04-09 14:19:34,346 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) Command > > org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand > > return value > > StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=12, > > mMessage=Fatal error during migration]] > > 2014-04-09 14:19:34,347 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) HostName = kvm01.virt > > 2014-04-09 14:19:34,348 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) Command > > MigrateStatusVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea) execution failed. > > Exception: VDSErrorException: VDSGenericException: VDSErrorException: > > Failed to MigrateStatusVDS, error = Fatal error during migration, code > > = 12 > > 2014-04-09 14:19:34,349 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) FINISH, MigrateStatusVDSCommand, > > log id: 16ec0461 > > 2014-04-09 14:19:34,353 INFO > > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > > (org.ovirt.thread.pool-6-thread-46) Correlation ID: 4350ffd, Job ID: > > 433cbdce-90b3-41ed-bbfe-3a10ea2c6616, Call Stack: null, Custom Event > > ID: -1, Message: Migration failed due to Error: Fatal error during > > migration. Trying to migrate to another Host (VM: web.judici, Source: > > kvm01.virt, Destination: kvm04). > > 2014-04-09 14:19:34,370 INFO > > [org.ovirt.engine.core.bll.MigrateVmCommand] > > (org.ovirt.thread.pool-6-thread-46) Running command: MigrateVmCommand > > internal: false. Entities affected : ID: > > b0108933-deb2-4fa0-ae74-e10cefbb0cea Type: VM > > 2014-04-09 14:19:34,374 INFO > > [org.ovirt.engine.core.bll.scheduling.policyunits.HaReservationWeightPolicyUnit] > > (org.ovirt.thread.pool-6-thread-46) Started HA reservation scoring > > method > > 2014-04-09 14:19:34,378 INFO > > [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) START, MigrateVDSCommand(HostName > > = kvm01.virt, HostId = fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31, > > dstVdsId=071d8ef9-971e-499b-975a-255ee3d3f895, > > dstHost=10.10.4.35:54321, migrationMethod=ONLINE, > > tunnelMigration=false, migrationDowntime=0), log id: 7ac1f1eb > > 2014-04-09 14:19:34,379 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) VdsBroker::migrate::Entered > > (vm_guid=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31, > > dstHost=10.10.4.35:54321, method=online > > 2014-04-09 14:19:34,380 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) START, > > MigrateBrokerVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31, > > dstVdsId=071d8ef9-971e-499b-975a-255ee3d3f895, > > dstHost=10.10.4.35:54321, migrationMethod=ONLINE, > > tunnelMigration=false, migrationDowntime=0), log id: 3c9d3817 > > 2014-04-09 14:19:34,431 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) FINISH, MigrateBrokerVDSCommand, > > log id: 3c9d3817 > > 2014-04-09 14:19:34,434 INFO > > [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] > > (org.ovirt.thread.pool-6-thread-46) FINISH, MigrateVDSCommand, return: > > MigratingFrom, log id: 7ac1f1eb > > 2014-04-09 14:19:34,438 INFO > > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > > (org.ovirt.thread.pool-6-thread-46) Correlation ID: 4350ffd, Job ID: > > 433cbdce-90b3-41ed-bbfe-3a10ea2c6616, Call Stack: null, Custom Event > > ID: -1, Message: Migration started (VM: web.judici, Source: > > kvm01.virt, Destination: kvm05.virt, User: admin). > > 2014-04-09 14:19:37,582 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-92) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:19:40,617 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-91) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:19:43,640 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-100) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:19:46,680 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-8) [1450e72d] RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:19:49,735 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-26) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:19:52,752 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-23) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:19:55,769 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-35) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:19:58,788 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-50) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:01,837 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-53) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:04,880 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-58) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:07,904 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-68) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:10,921 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-77) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:13,951 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-91) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:16,988 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-100) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:20,033 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-8) [1450e72d] RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:23,052 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-26) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:26,070 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-36) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:29,090 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-45) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:32,135 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-50) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:35,180 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-51) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:38,196 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-71) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:41,215 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-73) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:44,234 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-81) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:47,275 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-97) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:50,316 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-98) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:53,332 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-12) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:56,348 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-18) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:20:59,363 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-36) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:02,404 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-29) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:05,439 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-47) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:08,455 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-60) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:11,476 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-58) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:14,501 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-76) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:17,549 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-77) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:20,598 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-91) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:23,617 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-100) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:26,642 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-6) [5c26eeb2] RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:29,664 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-21) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:32,702 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-25) [e633f03] RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:35,751 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-31) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:38,772 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-48) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:41,790 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-60) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:44,812 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-71) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:47,858 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-72) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:50,903 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-77) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:53,919 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-94) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:56,938 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-5) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:21:59,961 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-14) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:02,997 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-21) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:06,037 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-36) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:09,058 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-45) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:12,075 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-50) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:15,103 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-51) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm05.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:17,696 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-58) VM web.judici > > b0108933-deb2-4fa0-ae74-e10cefbb0cea moved from MigratingFrom --> Up > > 2014-04-09 14:22:17,697 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-58) Adding VM > > b0108933-deb2-4fa0-ae74-e10cefbb0cea to re-run list > > 2014-04-09 14:22:17,698 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] > > (DefaultQuartzScheduler_Worker-58) START, FullListVdsCommand(HostName > > = kvm01.virt, HostId = fa455012-b929-4805-a5c1-50e6c788039a, > > vds=Host[kvm01.virt], vmIds=[b0108933-deb2-4fa0-ae74-e10cefbb0cea]), > > log id: 1688c794 > > 2014-04-09 14:22:17,706 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] > > (DefaultQuartzScheduler_Worker-58) FINISH, FullListVdsCommand, return: > > [{displaySecurePort=5905, kvmEnable=true, nicModel=rtl8139,pv, > > keyboardLayout=en-us, displayIp=0, pauseCode=NOERR, nice=0, > > pitReinjection=false, timeOffset=0, transparentHugePages=true, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, acpiEnable=true, custom={}, > > spiceSslCipherSuite=DEFAULT, memSize=8192, displayPort=5904, smp=4, > > emulatedMachine=rhel6.5.0, status=Up, vmType=kvm, > > memGuaranteedSize=1024, display=qxl, pid=30289, smartcardEnable=false, > > smpCoresPerSocket=1, > > spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard, > > maxVCpus=160, clientIp=10.10.4.242, > > devices=[Ljava.lang.Object;@6de6d11a, vmName=web.judici, > > cpuType=Penryn}], log id: 1688c794 > > 2014-04-09 14:22:17,709 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-58) Received a console Device without > > an address when processing VM b0108933-deb2-4fa0-ae74-e10cefbb0cea > > devices, skipping device: {alias=console0, specParams={}, > > device=console, type=console, > > deviceId=05fba965-133e-4810-a87c-1688be8beb5a} > > 2014-04-09 14:22:17,728 ERROR > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-58) Rerun vm > > b0108933-deb2-4fa0-ae74-e10cefbb0cea. Called from vds kvm01.virt > > 2014-04-09 14:22:17,735 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) START, > > MigrateStatusVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea), log id: 15822aeb > > 2014-04-09 14:22:17,781 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) Failed in MigrateStatusVDS method > > 2014-04-09 14:22:17,782 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) Command > > org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand > > return value > > StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=47, > > mMessage=Migration canceled]] > > 2014-04-09 14:22:17,782 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) HostName = kvm01.virt > > 2014-04-09 14:22:17,783 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) Command > > MigrateStatusVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea) execution failed. > > Exception: VDSErrorException: VDSGenericException: VDSErrorException: > > Failed to MigrateStatusVDS, error = Migration canceled, code = 47 > > 2014-04-09 14:22:17,784 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) FINISH, MigrateStatusVDSCommand, > > log id: 15822aeb > > 2014-04-09 14:22:17,791 INFO > > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > > (org.ovirt.thread.pool-6-thread-29) Correlation ID: 4350ffd, Job ID: > > 433cbdce-90b3-41ed-bbfe-3a10ea2c6616, Call Stack: null, Custom Event > > ID: -1, Message: Migration failed due to Error: Migration not in > > progress. Trying to migrate to another Host (VM: web.judici, Source: > > kvm01.virt, Destination: kvm05.virt). > > 2014-04-09 14:22:17,818 INFO > > [org.ovirt.engine.core.bll.MigrateVmCommand] > > (org.ovirt.thread.pool-6-thread-29) Running command: MigrateVmCommand > > internal: false. Entities affected : ID: > > b0108933-deb2-4fa0-ae74-e10cefbb0cea Type: VM > > 2014-04-09 14:22:17,824 INFO > > [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) START, MigrateVDSCommand(HostName > > = kvm01.virt, HostId = fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31, > > dstVdsId=d5e2830d-e59c-49be-b6e8-0968dbf357aa, > > dstHost=10.10.4.33:54321, migrationMethod=ONLINE, > > tunnelMigration=false, migrationDowntime=0), log id: 7dc46595 > > 2014-04-09 14:22:17,825 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) VdsBroker::migrate::Entered > > (vm_guid=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31, > > dstHost=10.10.4.33:54321, method=online > > 2014-04-09 14:22:17,826 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) START, > > MigrateBrokerVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31, > > dstVdsId=d5e2830d-e59c-49be-b6e8-0968dbf357aa, > > dstHost=10.10.4.33:54321, migrationMethod=ONLINE, > > tunnelMigration=false, migrationDowntime=0), log id: 25038825 > > 2014-04-09 14:22:17,848 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) FINISH, MigrateBrokerVDSCommand, > > log id: 25038825 > > 2014-04-09 14:22:17,853 INFO > > [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] > > (org.ovirt.thread.pool-6-thread-29) FINISH, MigrateVDSCommand, return: > > MigratingFrom, log id: 7dc46595 > > 2014-04-09 14:22:17,859 INFO > > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > > (org.ovirt.thread.pool-6-thread-29) Correlation ID: 4350ffd, Job ID: > > 433cbdce-90b3-41ed-bbfe-3a10ea2c6616, Call Stack: null, Custom Event > > ID: -1, Message: Migration started (VM: web.judici, Source: > > kvm01.virt, Destination: kvm03.virt, User: admin). > > 2014-04-09 14:22:19,226 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-67) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:22,275 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-79) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:25,291 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-83) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:28,314 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-1) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:31,330 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-6) [5c26eeb2] RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:34,360 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-16) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:37,389 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-30) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:40,407 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-31) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:43,425 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-52) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:46,443 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-51) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:49,473 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-71) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:52,514 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-76) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:55,533 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-92) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:22:58,553 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-90) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:01,569 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-10) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:04,596 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-7) [7a463a98] RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:07,626 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-16) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:10,648 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-30) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:13,665 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-41) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:16,693 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-47) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:19,724 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-51) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:22,758 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-65) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:25,778 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-79) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:28,795 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-95) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:31,814 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-87) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:34,848 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-1) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:37,884 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-19) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:40,910 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-22) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:43,930 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-25) [e633f03] RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:46,949 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-45) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:49,982 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-48) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:53,048 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-64) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:56,076 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-66) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:23:59,093 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-72) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:02,112 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-93) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:05,140 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-87) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:08,210 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-3) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:11,240 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-6) [5c26eeb2] RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:14,257 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-21) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:17,277 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-36) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:20,309 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-31) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:23,371 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-48) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:26,391 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-63) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:29,409 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-74) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:32,428 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-72) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:35,467 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-85) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:38,499 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-89) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-2014-04-09 14:24:38,499 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-89) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74- > > e10cefbb0cea is migrating to vds kvm03.virt ignoring it in the refresh > > until migration is done > > 2014-04-09 14:24:41,534 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-1) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:44,561 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-11) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:47,584 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-21) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:50,631 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-25) [e633f03] RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:53,668 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-37) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:56,683 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-55) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:24:59,702 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-57) RefreshVmList vm id > > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm03.virt > > ignoring it in the refresh until migration is done > > 2014-04-09 14:25:00,974 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-59) VM web.judici > > b0108933-deb2-4fa0-ae74-e10cefbb0cea moved from MigratingFrom --> Up > > 2014-04-09 14:25:00,975 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-59) Adding VM > > b0108933-deb2-4fa0-ae74-e10cefbb0cea to re-run list > > 2014-04-09 14:25:00,976 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] > > (DefaultQuartzScheduler_Worker-59) START, FullListVdsCommand(HostName > > = kvm01.virt, HostId = fa455012-b929-4805-a5c1-50e6c788039a, > > vds=Host[kvm01.virt], vmIds=[b0108933-deb2-4fa0-ae74-e10cefbb0cea]), > > log id: 7ef5612e > > 2014-04-09 14:25:00,984 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] > > (DefaultQuartzScheduler_Worker-59) FINISH, FullListVdsCommand, return: > > [{displaySecurePort=5905, kvmEnable=true, nicModel=rtl8139,pv, > > keyboardLayout=en-us, displayIp=0, pauseCode=NOERR, nice=0, > > pitReinjection=false, timeOffset=0, transparentHugePages=true, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, acpiEnable=true, custom={}, > > spiceSslCipherSuite=DEFAULT, memSize=8192, displayPort=5904, smp=4, > > emulatedMachine=rhel6.5.0, status=Up, vmType=kvm, > > memGuaranteedSize=1024, display=qxl, pid=30289, smartcardEnable=false, > > smpCoresPerSocket=1, > > spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard, > > maxVCpus=160, clientIp=10.10.4.242, > > devices=[Ljava.lang.Object;@1fbf5420, vmName=web.judici, > > cpuType=Penryn}], log id: 7ef5612e > > 2014-04-09 14:25:00,988 INFO > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-59) Received a console Device without > > an address when processing VM b0108933-deb2-4fa0-ae74-e10cefbb0cea > > devices, skipping device: {alias=console0, specParams={}, > > device=console, type=console, > > deviceId=05fba965-133e-4810-a87c-1688be8beb5a} > > 2014-04-09 14:25:01,030 ERROR > > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > > (DefaultQuartzScheduler_Worker-59) Rerun vm > > b0108933-deb2-4fa0-ae74-e10cefbb0cea. Called from vds kvm01.virt > > 2014-04-09 14:25:01,038 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-37) START, > > MigrateStatusVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea), log id: 47013f27 > > 2014-04-09 14:25:01,045 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-37) Failed in MigrateStatusVDS method > > 2014-04-09 14:25:01,045 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-37) Command > > org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand > > return value > > StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=47, > > mMessage=Migration canceled]] > > 2014-04-09 14:25:01,046 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-37) HostName = kvm01.virt > > 2014-04-09 14:25:01,046 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-37) Command > > MigrateStatusVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, > > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea) execution failed. > > Exception: VDSErrorException: VDSGenericException: VDSErrorException: > > Failed to MigrateStatusVDS, error = Migration canceled, code = 47 > > 2014-04-09 14:25:01,048 INFO > > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-37) FINISH, MigrateStatusVDSCommand, > > log id: 47013f27 > > 2014-04-09 14:25:01,055 INFO > > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > > (org.ovirt.thread.pool-6-thread-37) Correlation ID: 4350ffd, Job ID: > > 433cbdce-90b3-41ed-bbfe-3a10ea2c6616, Call Stack: null, Custom Event > > ID: -1, Message: Migration failed due to Error: Migration not in > > progress. Trying to migrate to another Host (VM: web.judici, Source: > > kvm01.virt, Destination: kvm03.virt). > > 2014-04-09 14:25:01,061 INFO > > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > > (org.ovirt.thread.pool-6-thread-37) Correlation ID: 4350ffd, Job ID: > > 433cbdce-90b3-41ed-bbfe-3a10ea2c6616, Call Stack: null, Custom Event > > ID: -1, Message: Migration failed due to Error: Migration not in > > progress (VM: web.judici, Source: kvm01.virt, Destination: > > kvm03.virt). > > 2014-04-09 14:34:08,665 INFO > > [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] > > (org.ovirt.thread.pool-6-thread-43) [4045389e] Running command: > > MaintenanceNumberOfVdssCommand internal: false. Entities affected : > > ID: fa455012-b929-4805-a5c1-50e6c788039a Type: VDS > > 2014-04-09 14:34:08,667 INFO > > [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-43) [4045389e] START, > > SetVdsStatusVDSCommand(HostName = kvm01.virt, HostId = > > fa455012-b929-4805-a5c1-50e6c788039a, status=PreparingForMaintenance, > > nonOperationalReason=NONE, stopSpmFailureLogged=true), log id: > > 64965c26 > > 2014-04-09 14:34:08,678 INFO > > [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] > > (org.ovirt.thread.pool-6-thread-43) [4045389e] FINISH, > > SetVdsStatusVDSCommand, log id: 64965c26 > > 2014-04-09 14:34:08,725 INFO > > [org.ovirt.engine.core.bll.MaintenanceVdsCommand] > > (org.ovirt.thread.pool-6-thread-43) [4045389e] Running command: > > MaintenanceVdsCommand internal: true. Entities affected : ID: > > fa455012-b929-4805-a5c1-50e6c788039a Type: VDS > > 2014-04-09 14:34:08,744 INFO > > [org.ovirt.engine.core.bll.InternalMigrateVmCommand] > > (org.ovirt.thread.pool-6-thread-43) [35f06602] Failed to Acquire Lock > > to object EngineLock [exclusiveLocks= key: > > b0108933-deb2-4fa0-ae74-e10cefbb0cea value: VM > > , sharedLocks= ] > > > > On Wed, Apr 9, 2014 at 6:33 PM, Yair Zaslavsky <yzaslavs(a)redhat.com> wrote: > > > Can you please attach full engine.log? > > > > > > Many thanks, > > > Yair > > > > > > > > > ----- Original Message ----- > > >> From: "Jeremiah Jahn" <jeremiah(a)goodinassociates.com> > > >> To: users(a)ovirt.org > > >> Sent: Thursday, April 10, 2014 2:18:48 AM > > >> Subject: [ovirt-users] help.. vm trapped in limbo aka can't acquire > > >> exclusive lock > > >> > > >> I can't start it, I can't migrate it. I tried to migrate it before, > > >> but the machine was stuck in a read only state. The migration failed > > >> because the machine it was being migrated to was also in a read only > > >> state. somewhere in the process the lock obviously got lost, and I > > >> can't get it back... > > >> > > >> > > >> > > >> 2014-04-09 18:11:16,675 INFO [org.ovirt.engine.core.bll.RunVmCommand] > > >> (ajp--127.0.0.1-8702-3) [58b40832] Failed to Acquire Lock to object > > >> EngineLock [exclusiveLocks= key: b0108933-deb2-4fa0-ae74-e10cefbb0cea > > >> value: VM > > >> , sharedLocks= ] > > >> > > >> > > >> 2014-04-09 18:11:16,676 WARN [org.ovirt.engine.core.bll.RunVmCommand] > > >> (ajp--127.0.0.1-8702-3) [58b40832] CanDoAction of action RunVm failed. > > >> Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED,$VmName > > >> web.judici > > >> _______________________________________________ > > >> Users mailing list > > >> Users(a)ovirt.org > > >> http://lists.ovirt.org/mailman/listinfo/users > > >> > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > >

1 0

sql error when viewing system disks
by Jeremiah Jahn 13 Apr '14

13 Apr '14

version 3.4 System->Disks tab->All checked Caused by: org.postgresql.util.PSQLException: The column name disk_storage_type was not found in this ResultSet. at org.postgresql.jdbc2.AbstractJdbc2ResultSet.findColumn(AbstractJdbc2ResultSet.java:2542) at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getInt(AbstractJdbc2ResultSet.java:2406) at org.jboss.jca.adapters.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:1073) at org.ovirt.engine.core.dao.DiskDaoDbFacadeImpl$DiskRowMapper.mapRow(DiskDaoDbFacadeImpl.java:116) [dal.jar:] at org.ovirt.engine.core.dao.DiskDaoDbFacadeImpl$DiskRowMapper.mapRow(DiskDaoDbFacadeImpl.java:106) [dal.jar:] ERROR [org.ovirt.engine.core.bll.SearchQuery] (ajp--127.0.0.1-8702-3) Query SearchQuery failed. Exception message is StatementCallback; bad SQL grammar [SELECT * FROM (SELECT * FROM vds WHERE ( vds_id IN (SELECT vds_with_tags.vds_id FROM vds_with_tags WHERE vds_with_tags.vds_group_name LIKE 'Default' )) ORDER BY vds_name ASC ) as T1 OFFSET (1 -1) LIMIT 100]; nested exception is org.postgresql.util.PSQLException: The column name disk_storage_type was not found in this ResultSet. : org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [SELECT * FROM (SELECT * FROM vds WHERE ( vds_id IN (SELECT vds_with_tags.vds_id FROM vds_with_tags WHERE vds_with_tags.vds_group_name LIKE 'Default' )) ORDER BY vds_name ASC ) as T1 OFFSET (1 -1) LIMIT 100]; nested exception is org.postgresql.util.PSQLException: The column name disk_storage_type was not found in this ResultSet.: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [SELECT * FROM (SELECT * FROM vds WHERE ( vds_id IN (SELECT vds_with_tags.vds_id FROM vds_with_tags WHERE vds_with_tags.vds_group_name LIKE 'Default' )) ORDER BY vds_name ASC ) as T1 OFFSET (1 -1) LIMIT 100]; nested exception is org.postgresql.util.PSQLException: The column name disk_storage_type was not found in this ResultSet.

2 1

compatibility relationship between datacenter, ovirt and cluster
by Tamer Lima 12 Apr '14

12 Apr '14

Hi, yesterday my ovirt was 3.3 my datacenter and cluster (compatibility version) was aligned with ovirt 3.3 today my ovirt is now 3.4. and my datacenter and cluster (compatibility version) remains 3.3 (with the option enabled to change for 3.4) browsing the ovirt admin page I see 2 occurrences of ovirt version: datacenter tab = 3.3 cluster tab =3.3 I would like to understand what means all these versions, the same version for a lot of important things, and how my ovirt works/behaves using different versions. all my doubts together : What means datacenter in version 3.3(or lower version) when ovirt is 3.4 ? what means cluster in version 3.3 when ovirt is 3.4? what means change the "compatibility version" for datacenter? what means change the "compatibility version" for cluster? thanks

4 5