- Users - oVirt List Archives

Stalled disk migration
by Nicolás 09 Oct '16

09 Oct '16

Hi, We've done a major datastore migration recently between 2 iSCSI-based datastores. We've successfully migrated 35 machines, however, 5 of them seem to have stalled. All we can see in the events tab tab is: Moving Disk bla_Disk1 from iscsi01 to iscsi02 Disks are small enough (25-27Gb) to assume this won't progress since it's been more than 30 hs. since the migration began, other VMs took approximately 1-1.5 hours to fully migrate a disk, so this seems to be stalled. The bad thing is that I can't find a way to "unstall" it. Disks are in a perpetual "migrating" status and there's no way to stop the migration (at least from the webadmin). I don't actually care if stopping the migration breaks those 5 machines since they are disposable, I just need to stop that event. I already tried restarting the ovirt-engine and it didn't work. Log doesn't seem to provide nothing relevant. Is there a way to do that? I wouldn't mind if I need to modify some record directly into the DB. Thanks! Nicolás

1 1

Decommissioning etherpad and old wiki
by Marc Dequènes (Duck) 09 Oct '16

09 Oct '16

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --UOElIP8pfCi0Hnf0njaNdv1OtAD7rJrx1 Content-Type: multipart/mixed; boundary="DXPDFOvgWAbgIdNBFpHK6kmdCLbSpUNV8"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org>, users(a)ovirt.org, wiki(a)ovirt.org Message-ID: <8a0a46d8-317c-690f-ce6b-c42580971bc2(a)redhat.com> Subject: Decommissioning etherpad and old wiki --DXPDFOvgWAbgIdNBFpHK6kmdCLbSpUNV8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, The wiki content was already converted into the website, and remaining broken links & co were fixed (thanks Garrett). It was merely kept in case some content was forgotten (read-only). The Etherpad was barely used and a pain to upgrade/maintain, so the infra team with the last remaining user decided to close it. They are to be removed soon. In fact we already stopped them to track the remaining users, and no one complained. It can be restarted on demand before the removal date. On 2016-10-26 the resources will be purged. Backup has been made, so nothing is lost but unless there is a good reason it won't be used. Btw, the wiki@ mailing-list was unused and is now read-only. If you have any concern, please contact the infra mailing-list. \_o< --DXPDFOvgWAbgIdNBFpHK6kmdCLbSpUNV8-- --UOElIP8pfCi0Hnf0njaNdv1OtAD7rJrx1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJX9hEiAAoJEFXp+fesHEQ/foMQAIW0GsRnyqnz1IuPVOFYVm1i BJueCUsGy4T61HHUtUKXslg5+dYkmiql+7Ws8LzuGGgQAyaVEnY3g5gLemFtjabv AlDa9LfiFWgLxO7cavLOsi1e3imcyaMtrWguxPYYQWpdJRR1hndNIiykIaR708yy bofjo5h16gMHmo3sQN1CRgnALQbnr5EZCSxLQ0HcP1JbyJ9oBylOU2Pfma3yNPT3 5vtezNTmFZC5Te8vzGfWnDrVlcgve1j5SawCwDpYTjZSAA0BGTU5GFOAIlDAdj7N Mi+6nSL9PZONpYp+Xo/3VsjOBL22N3wDtOdcKQwagSmF5SIEEmt0tCSFRMxmheUd 7fYkMYd49P3whMJQHXbHNJG8GSk9bGbeC1UD85/Nd9HgKNgkgqUfFC5Sy8Kn1jTh 0m2Eoqz3AH4xLub1PhzHikdcKvwuzZ5F+1v8c4PM7XznecvQAjahkHpASjYS8oz/ 5iwv7kIC2fdF32zW8TvQRIuvkRNuVxmHGFY4nG0QH/f2Ehvv73mNEVEE92vhV1A/ XHgmZRNrR3p50W6YQnF3pyiNhtAzgYlX09uu9ksd2Xr75TemAlTmTSXJJ/eAaVPE bsWOlgvLaHTI85cVebZakt1TpFg8XRjZjBJFHOf27uewjRxMiobFC9QW6OfdOMVS 5oRjO/8Zvzwi7IucRikT =wF1q -----END PGP SIGNATURE----- --UOElIP8pfCi0Hnf0njaNdv1OtAD7rJrx1--

2 2

Re: [ovirt-users] documentation change suggestion / question
by Karli Sjöberg 09 Oct '16

09 Oct '16

--_000_9cff90f6acfe44c2ab30837610301bceexch24sluse_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 DQpEZW4gOCBva3QuIDIwMTYgMTk6MTUgc2tyZXYgQ2hhcmxlcyBLb3psZXIgPGNrb3psZXJpaWlA Z21haWwuY29tPjoNCj4NCj4gR29vZ2xpbmcgIm92aXJ0IHdpbmRvd3MgYWdlbnQiIHRoaXMgaXMg dGhlIGZpcnN0IGxpbmsgdGhhdCBwb3BzIHVwOiBodHRwOi8vd3d3Lm92aXJ0Lm9yZy9kb2N1bWVu dGF0aW9uL2ludGVybmFsL2d1ZXN0LWFnZW50L2d1ZXN0LWFnZW50LWZvci13aW5kb3dzLw0KPg0K PiBUaGlzIGRvYyBzZWVtcyBub24taW50dWl0aXZlIGFuZCBvdmVyIGNvbXBsaWNhdGVkDQo+DQo+ IFNwZWNpZmljYWxseSwgdGhlIFJlZEhhdCBkb2N1bWVudGF0aW9uIHRoYXQgaXMgNCBsaW5rcyBi ZWxvdyBpcyBzaW1wbGUgYXMgImluc3RhbGwgdGhpcyBwYWNrYWdlIGFuZCBtb3VudCB0aGUgaXNv IjogaHR0cHM6Ly9jb21tdW5pdHkucmVkaGF0LmNvbS9ibG9nLzIwMTUvMDUvaG93LXRvLWluc3Rh bGwtYW5kLXVzZS1vdmlydHMtd2luZG93cy1ndWVzdC10b29scy8NCj4NCj4gVGhlIGZvcm1lciB3 YXMgdXBkYXRlZCBhcyBlYXJseSBhcyBKdW5lIG9mIHRoaXMgeWVhcg0KPg0KPiAxLikgVGhlIFJl ZEhhdCBkb2N1bWVudCB3b3JrZWQgZm9yIG1lIHNvIEkgZG9udCB0aGluayBvVmlydCA0LnggY2Fu dCB1c2UgdGhlIHNhbWUNCj4gMi4pIFdoeSBoYXZlIHNlcGFyYXRlIGFyZWFzIG9mIGRvY3VtZW50 YXRpb24gdGhhdCBhcmUgc28gZGlmZmVyZW50IGZyb20gZWFjaCBvdGhlcj8gVGhpcyBoYXMgY2F1 c2VkIG1lIGlzc3VlcyBpbiB0aGUgcGFzdCB3aGVyZWJ5IEkgZm91bmQgUkggZG9jcyB0aGF0IHdl cmUgbXVjaCBtb3JlIGNsZWFyIGFuZCBjb25jaXNlDQoNClRoYXQncyBiZWNhdXNlIGFsbCBvVmly dCBkb2N1bWVudGF0aW9uIGlzIGNvbW11bml0eSBkcml2ZW4uIFRoaXMgc3BlY2lmaWMgcGFnZSB3 YXMgd3JpdHRlbiBieSBhIGd1eSBJIGhhcHBlbiB0byBrbm93IHF1aXRlIHdlbGwgKEkgd3JvdGUg aXQpOikNCg0KVGhpcyB3YXMgd3JpdHRlbiBiYWNrIHdoZW4gdGhlcmUgd2FzIG5vIGVhc3kgdG8g aW5zdGFsbCBwYWNrYWdlLCB3aGVyZSB5b3UgaGFkIHRvIGRvIHRoYXQgYnkgaGFuZCwgYW5kIGlm IHlvdSB3YW50IHRvLCB5b3Ugc3RpbGwgY2FuLCB0aGUgbWV0aG9kIHN0aWxsIHdvcmtzLiBCdXQg SSBhZ3JlZSB0aGF0IGlmIHRoZXJlJ3MgYW4gZWFzaWVyIHdheSB0b2RheSwgSSB0aGluayB3ZSBz aG91bGQgZ28gd2l0aCB0aGF0IGZpcnN0IGFuZCBrZWVwIHRoaXMgY29tcGlsaW5nIG1ldGhvZCBh cyB0aGUgZmFsbGJhY2suDQoNCj4gMy4pIElzIHRoZXJlIGFueW9uZSB3aG8gbWlnaHQgd2FudCB0 byBtZXJnZSBSSCBkb2NzIHdpdGggb1ZpcnQgZG9jcyB3aGVyZSB0aGUgUkggZG9jcyBhcmUgYmV0 dGVyIHRoYW4gb1ZpcnQ/DQoNCkhvcGluZyBzb21lb25lIEBSSCBjYW4gYW5zd2VyIHRoaXMsIGJl Y2F1c2UgSSBkb24ndCBrbm93IGlmIEknbSBhbGxvd2VkIHRvIGRvIHRoYXQ/DQoNCi9LDQoNCj4N Cj4gVGhhbmtzIHNvIG11Y2ggZm9yIHByb3ZpZGluZyBzdWNoIGEgZ3JlYXQgcHJvZHVjdCEgSSBq dXN0IGZlZWwgc29tZXRpbWVzIHRoZSBkb2NzIGFyZSBhIGxpdHRsZSBtb3JlIGRldmVsb3Blci1j ZW50cmljIHdoZXJlYXMgdGhlIFJlZEhhdCBkb2NzIGFyZSBtb3JlIGVhc2lseSByZWFkYWJsZQ0K --_000_9cff90f6acfe44c2ab30837610301bceexch24sluse_ Content-Type: text/html; charset="utf-8" Content-ID: <7C7FB8E8E6F9084D92C4FF0EBE6AE5CC(a)ad.slu.se> Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPHAgZGlyPSJsdHIi Pjxicj4NCkRlbiA4IG9rdC4gMjAxNiAxOToxNSBza3JldiBDaGFybGVzIEtvemxlciAmbHQ7Y2tv emxlcmlpaUBnbWFpbC5jb20mZ3Q7Ojxicj4NCiZndDs8YnI+DQomZ3Q7IEdvb2dsaW5nICZxdW90 O292aXJ0IHdpbmRvd3MgYWdlbnQmcXVvdDsgdGhpcyBpcyB0aGUgZmlyc3QgbGluayB0aGF0IHBv cHMgdXA6Jm5ic3A7aHR0cDovL3d3dy5vdmlydC5vcmcvZG9jdW1lbnRhdGlvbi9pbnRlcm5hbC9n dWVzdC1hZ2VudC9ndWVzdC1hZ2VudC1mb3Itd2luZG93cy88YnI+DQomZ3Q7PGJyPg0KJmd0OyBU aGlzIGRvYyBzZWVtcyBub24taW50dWl0aXZlIGFuZCBvdmVyIGNvbXBsaWNhdGVkPGJyPg0KJmd0 Ozxicj4NCiZndDsgU3BlY2lmaWNhbGx5LCB0aGUgUmVkSGF0IGRvY3VtZW50YXRpb24gdGhhdCBp cyA0IGxpbmtzIGJlbG93IGlzIHNpbXBsZSBhcyAmcXVvdDtpbnN0YWxsIHRoaXMgcGFja2FnZSBh bmQgbW91bnQgdGhlIGlzbyZxdW90OzombmJzcDtodHRwczovL2NvbW11bml0eS5yZWRoYXQuY29t L2Jsb2cvMjAxNS8wNS9ob3ctdG8taW5zdGFsbC1hbmQtdXNlLW92aXJ0cy13aW5kb3dzLWd1ZXN0 LXRvb2xzLzxicj4NCiZndDs8YnI+DQomZ3Q7IFRoZSBmb3JtZXIgd2FzIHVwZGF0ZWQgYXMgZWFy bHkgYXMgSnVuZSBvZiB0aGlzIHllYXImbmJzcDs8YnI+DQomZ3Q7PGJyPg0KJmd0OyAxLikgVGhl IFJlZEhhdCBkb2N1bWVudCB3b3JrZWQgZm9yIG1lIHNvIEkgZG9udCB0aGluayBvVmlydCA0Lngg Y2FudCB1c2UgdGhlIHNhbWU8YnI+DQomZ3Q7IDIuKSBXaHkgaGF2ZSBzZXBhcmF0ZSBhcmVhcyBv ZiBkb2N1bWVudGF0aW9uIHRoYXQgYXJlIHNvIGRpZmZlcmVudCBmcm9tIGVhY2ggb3RoZXI/IFRo aXMgaGFzIGNhdXNlZCBtZSBpc3N1ZXMgaW4gdGhlIHBhc3Qgd2hlcmVieSBJIGZvdW5kIFJIIGRv Y3MgdGhhdCB3ZXJlIG11Y2ggbW9yZSBjbGVhciBhbmQgY29uY2lzZSZuYnNwOzwvcD4NCjxwIGRp cj0ibHRyIj5UaGF0J3MgYmVjYXVzZSBhbGwgb1ZpcnQgZG9jdW1lbnRhdGlvbiBpcyBjb21tdW5p dHkgZHJpdmVuLiBUaGlzIHNwZWNpZmljIHBhZ2Ugd2FzIHdyaXR0ZW4gYnkgYSBndXkgSSBoYXBw ZW4gdG8ga25vdyBxdWl0ZSB3ZWxsIChJIHdyb3RlIGl0KTopPC9wPg0KPHAgZGlyPSJsdHIiPlRo aXMgd2FzIHdyaXR0ZW4gYmFjayB3aGVuIHRoZXJlIHdhcyBubyBlYXN5IHRvIGluc3RhbGwgcGFj a2FnZSwgd2hlcmUgeW91IGhhZCB0byBkbyB0aGF0IGJ5IGhhbmQsIGFuZCBpZiB5b3Ugd2FudCB0 bywgeW91IHN0aWxsIGNhbiwgdGhlIG1ldGhvZCBzdGlsbCB3b3Jrcy4gQnV0IEkgYWdyZWUgdGhh dCBpZiB0aGVyZSdzIGFuIGVhc2llciB3YXkgdG9kYXksIEkgdGhpbmsgd2Ugc2hvdWxkIGdvIHdp dGggdGhhdCBmaXJzdA0KIGFuZCBrZWVwIHRoaXMgY29tcGlsaW5nIG1ldGhvZCBhcyB0aGUgZmFs bGJhY2suPC9wPg0KPHAgZGlyPSJsdHIiPiZndDsgMy4pIElzIHRoZXJlIGFueW9uZSB3aG8gbWln aHQgd2FudCB0byBtZXJnZSBSSCBkb2NzIHdpdGggb1ZpcnQgZG9jcyB3aGVyZSB0aGUgUkggZG9j cyBhcmUgYmV0dGVyIHRoYW4gb1ZpcnQ/PC9wPg0KPHAgZGlyPSJsdHIiPkhvcGluZyBzb21lb25l IEBSSCBjYW4gYW5zd2VyIHRoaXMsIGJlY2F1c2UgSSBkb24ndCBrbm93IGlmIEknbSBhbGxvd2Vk IHRvIGRvIHRoYXQ/PC9wPg0KPHAgZGlyPSJsdHIiPi9LPC9wPg0KPHAgZGlyPSJsdHIiPiZndDs8 YnI+DQomZ3Q7IFRoYW5rcyBzbyBtdWNoIGZvciBwcm92aWRpbmcgc3VjaCBhIGdyZWF0IHByb2R1 Y3QhIEkganVzdCBmZWVsIHNvbWV0aW1lcyB0aGUgZG9jcyBhcmUgYSBsaXR0bGUgbW9yZSBkZXZl bG9wZXItY2VudHJpYyB3aGVyZWFzIHRoZSBSZWRIYXQgZG9jcyBhcmUgbW9yZSBlYXNpbHkgcmVh ZGFibGUmbmJzcDs8L3A+DQo8L2JvZHk+DQo8L2h0bWw+DQo= --_000_9cff90f6acfe44c2ab30837610301bceexch24sluse_--

2 1

documentation change suggestion / question
by Charles Kozler 08 Oct '16

08 Oct '16

Googling "ovirt windows agent" this is the first link that pops up: http://www.ovirt.org/documentation/internal/guest-agent/guest-agent-for-win… This doc seems non-intuitive and over complicated Specifically, the RedHat documentation that is 4 links below is simple as "install this package and mount the iso": https://community.redhat.com/blog/2015/05/how-to-install-and-use-ovirts-win… The former was updated as early as June of this year 1.) The RedHat document worked for me so I dont think oVirt 4.x cant use the same 2.) Why have separate areas of documentation that are so different from each other? This has caused me issues in the past whereby I found RH docs that were much more clear and concise 3.) Is there anyone who might want to merge RH docs with oVirt docs where the RH docs are better than oVirt? Thanks so much for providing such a great product! I just feel sometimes the docs are a little more developer-centric whereas the RedHat docs are more easily readable

1 0

How to add a tcp type serial to a vm in ovirt 4.0?
by lifuqiong 08 Oct '16

08 Oct '16

This is a multipart message in MIME format. ------=_NextPart_000_04AE_01D221B2.B69E7920 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, We can easily add a Serial Hardware in virt-manager, when adding the serial, the vm's xml add these lines as follows: . <serial type='tcp'> <source mode='bind' host='127.0.0.1' service='4555' /> <protocol type='telnet' /> </serial> ... But I can't add a tcp serial in ovirt 4.0 when I create a VM, even after I reading http://www.ovirt.org/documentation/admin-guide/serial-console-setup/ Hope someone can help me. Thank you Mark ------=_NextPart_000_04AE_01D221B2.B69E7920 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META = HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 = (filtered medium)"><style></style></head><body lang=3DZH-CN link=3Dblue = vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div = class=3DWordSection1>Hi, = <o:p></o:p>         We can = easily add a Serial Hardware in virt-manager, when adding the serial, = the vm’s xml add these lines as follows:<o:p></o:p>…<o:p></o:p><serial = type=3D’tcp’><o:p></o:p>         <source = mode=3D’bind’ host=3D’127.0.0.1’ = service=3D’4555’ /><o:p></o:p>         = <protocol type=3D’telnet’ /><o:p></o:p></serial><o:p></o:p>…..<o:p></o:p>         = <o:p></o:p>         But I = can’t add a tcp serial in ovirt 4.0 when I create a VM, even after = I reading <a = href=3D"http://www.ovirt.org/documentation/admin-guide/serial-console-set= up/">http://www.ovirt.org/documentation/admin-guide/serial-console-setup/= </a><o:p></o:p><o:p> </o:p>Hope someone can help me. <o:p></o:p>Thank you<o:p></o:p>Mark<o:p></o:p><o:p> </o:p></div></body></html> ------=_NextPart_000_04AE_01D221B2.B69E7920--

1 0

RE > Multiple export domains limit?
by aleksey.maksimov＠it-kb.ru 07 Oct '16

07 Oct '16

Hello oVirt guru`s! http://lists.ovirt.org/pipermail/users/2015-November/036056.html Is there a progress on this issue?

2 1

Can't add host - Failed to read hardware information
by David Pinkerton 07 Oct '16

07 Oct '16

I'm trying to add a host to a freshly built cluster. yum install finishes, then the message " Failed to read hardware information" is displayed - host has installation failed. If I try to re-install I get the same message and the host goes non-responsive. engine log: 2016-10-07 21:13:46,525 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [2854e702] Connecting to /192.168.21.71 2016-10-07 21:13:46,526 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler4) [3fa97b73] Command 'GetCapabilitiesVDSCommand(HostName = rhv1, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', hostId='96358424-a14e-4d29-957f-3d7ddac99c12', vds='Host[rhv1,96358424-a14e-4d29-957f-3d7ddac99c12]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed 2016-10-07 21:13:46,526 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (DefaultQuartzScheduler4) [3fa97b73] Failure to refresh Vds runtime info: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed 2016-10-07 21:13:46,526 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (DefaultQuartzScheduler4) [3fa97b73] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createNetworkException(VdsBrokerCommand.java:157) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:120) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33) [dal.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:451) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VdsManager.refreshCapabilities(VdsManager.java:653) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring.refreshVdsRunTimeInfo(HostMonitoring.java:121) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring.refresh(HostMonitoring.java:85) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VdsManager.onTimer(VdsManager.java:238) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) [:1.8.0_102] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] at org.ovirt.engine.core.utils.timer.JobWrapper.invokeMethod(JobWrapper.java:77) [scheduler.jar:] at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:51) [scheduler.jar:] at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_102] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] Caused by: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed at org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient.connect(ReactorClient.java:165) [vdsm-jsonrpc-java-client.jar:] at org.ovirt.vdsm.jsonrpc.client.JsonRpcClient.getClient(JsonRpcClient.java:134) [vdsm-jsonrpc-java-client.jar:] at org.ovirt.vdsm.jsonrpc.client.JsonRpcClient.call(JsonRpcClient.java:81) [vdsm-jsonrpc-java-client.jar:] at org.ovirt.engine.core.vdsbroker.jsonrpc.FutureMap.<init>(FutureMap.java:70) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.jsonrpc.JsonRpcVdsServer.getCapabilities(JsonRpcVdsServer.java:258) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand.executeVdsBrokerCommand(GetCapabilitiesVDSCommand.java:15) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:110) [vdsbroker.jar:] ... 18 more 2016-10-07 21:13:49,531 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [2854e702] Connecting to /192.168.21.71 vdsm.log jsonrpc.Executor/3::INFO::2016-10-07 20:45:31,554::__init__::513::jsonrpc.JsonRpcServer::(_serveRequest) RPC call Host.getCapabilities succeeded in 0.06 seconds jsonrpc.Executor/4::DEBUG::2016-10-07 20:45:32,566::__init__::530::jsonrpc.JsonRpcServer::(_handle_request) Calling 'Host.getHardwareInfo' in bridge with {} jsonrpc.Executor/4::ERROR::2016-10-07 20:45:32,673::API::1340::vds::(getHardwareInfo) failed to retrieve hardware info Traceback (most recent call last): File "/usr/share/vdsm/API.py", line 1337, in getHardwareInfo hw = supervdsm.getProxy().getHardwareInfo() File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in <lambda> **kwargs) File "<string>", line 2, in getHardwareInfo File "/usr/lib64/python2.7/multiprocessing/managers.py", line 759, in _callmethod kind, result = conn.recv() EOFError jsonrpc.Executor/4::INFO::2016-10-07 20:45:32,680::__init__::513::jsonrpc.JsonRpcServer::(_serveRequest) RPC call Host.getHardwareInfo failed (error 57) in 0.11 seconds jsonrpc.Executor/6::DEBUG::2016-10-07 20:45:33,783::__init__::530::jsonrpc.JsonRpcServer::(_handle_request) Calling 'Host.getCapabilities' in bridge with {} MainThread::DEBUG::2016-10-07 20:45:36,211::vdsm::73::vds::(sigtermHandler) Received signal 15 I'm also seeing segfaults in supervdsm on the host's console. -- David Pinkerton +61-488-904-232 <http://apac.redhat.com/>

2 1

change broker.conf configuration on shared storage
by emanuel.santosvarina＠mahle.com 07 Oct '16

07 Oct '16

This is a multipart message in MIME format. --=_alternative 004F9B75C1258043_= Content-Type: text/plain; charset="US-ASCII" hi all, hmm, broker.conf is now on the shared storage and not replicated on each host local file system. how to make changes to the conf, e.g. the notify key? thanks, emanuel --=_alternative 004F9B75C1258043_= Content-Type: text/html; charset="US-ASCII" hi all, hmm, broker.conf is now on the shared storage and not replicated on each host local file system. how to make changes to the conf, e.g.  the notify key? thanks, emanuel --=_alternative 004F9B75C1258043_=--

3 5

VMs paused due to IO issues - Dell Equallogic controller failover
by Gary Lloyd 07 Oct '16

07 Oct '16

Hi We have Ovirt 3.65 with a Dell Equallogic SAN and we use Direct Luns for all our VMs. At the weekend during early hours an Equallogic controller failed over to its standby on one of our arrays and this caused about 20 of our VMs to be paused due to IO problems. I have also noticed that this happens during Equallogic firmware upgrades since we moved onto Ovirt 3.65. As recommended by Dell disk timeouts within the VMs are set to 60 seconds when they are hosted on an EqualLogic SAN. Is there any other timeout value that we can configure in vdsm.conf to stop VMs from getting paused when a controller fails over ? Also is there anything that we can tweak to automatically unpause the VMs once connectivity with the arrays is re-established ? At the moment we are running a customized version of storageServer.py, as Ovirt has yet to include iscsi multipath support for Direct Luns out of the box. Many Thanks *Gary Lloyd* ________________________________________________ I.T. Systems:Keele University Finance & IT Directorate Keele:Staffs:IC1 Building:ST5 5NB:UK +44 1782 733063 <%2B44%201782%20733073> ________________________________________________

4 7

VM SSO
by Maxence Sartiaux 07 Oct '16

07 Oct '16

Hello, I try to use the VM SSO but no login, still on the logon screen ... I'm on ovirt 4.0.3, connected to an AD (Samba 4.5) + VMs Windows 7/10 stateless sysprep-ed to integrate to the domain and obviously the guest-agent is installed. My AD user can connect to the user panel, take a vm and connect to the console but no sign on on the windows. (the "Connect Automatically" option is ticked) Also, i don't know why but my username on ovirt panel has a double domain "u1@labo.lan@labo.lan" <- is this my problem ? The AD configuration is the configuration from the extension setup wizard, no custom config, no mapping Any ideas ? Thank you

2 1