- Users - oVirt List Archives

ovirt 4.1 - is power management essential for hosted engine clustering ?
by Joseph Kelly 27 Feb '17

27 Feb '17

--_000_14881789467733340cameltradingscreencom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGVsbG8sDQoNCkkndmUgaGF2ZSBhIGhvc3RlZCBlbmdpbmUgdGhhdHMgdXAgYW5kIHJ1bm5pbmcg b24gYSBob3N0IGNhbGxlZCBob3N0ZWQtZW5naW5lMS4gSSBpbnN0YWxsZWQgaG9zdGVkLWVuZ2lu ZTIgdmlhIHRoZSB3ZWJhZG1pbiBndWkgYnV0IGFtIHVuYWJsZSB0byBmYWlsLW92ZXIgdGhlIGhv c3RlZC1lbmdpbmUuDQpIb3dldmVyIGhvc3RlZCBlbmdpbmUtaG9zdGVkMiBpcyBiZWluZyBzZW5z ZWQgYXMgYSBub2RlIGluIHRoZSBkZWZhdWx0IGNsdXN0ZXIgYW5kIEkgaGF2ZSBlbmFibGVkIEhB IHJlc2VydmF0aW9uLCBhcyBwZXIgdGhpcyBtYWlsOg0KDQpodHRwczovL3d3dy5tYWlsLWFyY2hp dmUuY29tL3VzZXJzQG92aXJ0Lm9yZy9tc2czNDg0Ny5odG1sDQoNCkJ1dCBpcyBwb3dlciBtYW5h Z2VtZW50IGVzc2VudGlhbCBmb3IgaG9zdGVkIGVuZ2luZSBjbHVzdGVyaW5nID8NCg0KQW5kIEkg Z2V0IHRoaXMgZXJyb3IgYmVsb3cgd2hlbiB0cnlpbmcgdG8gZmFpbG92ZXINCg0KIkNhbm5vdCBt aWdyYXRlIFZNLiBUaGVyZSBpcyBubyBob3N0IHRoYXQgc2F0aXNmaWVzIGN1cnJlbnQgc2NoZWR1 bGluZyBjb25zdHJhaW50cy4gU2VlIGJlbG93IGZvciBkZXRhaWxzOg0KDQpUaGUgaG9zdCBob3N0 ZWQtZW5naW5lMiBkaWQgbm90IHNhdGlzZnkgaW50ZXJuYWwgZmlsdGVyIEhBIGJlY2F1c2UgaXQg aXMgbm90IGEgSG9zdGVkIEVuZ2luZSBob3N0Li4NClRoZSBob3N0IGhvc3RlZC1lbmdpbmUxIGRp ZCBub3Qgc2F0aXNmeSBpbnRlcm5hbCBmaWx0ZXIgSEEgYmVjYXVzZSBpdCBpcyBub3QgYSBIb3N0 ZWQgRW5naW5lIGhvc3QuIg0KDQpUaGFua3MsDQpKb2UuDQoNCi0tDQoNCg0KSi4gS2VsbHkNCklu ZnJhc3RydWN0dXJlIEVuZ2luZWVyDQpUcmFkaW5nU2NyZWVuDQp3d3cudHJhZGluZ3NjcmVlbi5j b208aHR0cDovL3d3dy50cmFkaW5nc2NyZWVuLmNvbT4NCktEWCBSb3Bwb25naSAyMjggQmxkZy4g NkYNCjItMi04IFJvcHBvbmdpLCBNaW5hdG8ta3UsIFRva3lvIDEwNi0wMDMyLCBKYXBhbg0Kb2Zm aWNlOiArODEtMy00NTQwLTg1MTMNCmVtYWlsOiBqb3NlcGgua2VsbHlAdHJhZGluZ3NjcmVlbi5j b208bWFpbHRvOmpvc2VwaC5rZWxseUB0cmFkaW5nc2NyZWVuLmNvbT4NCg0KRm9sbG93IFRyYWRp bmdTY3JlZW4gb24gVHdpdHRlciwgRmFjZWJvb2ssIG9yIG91ciBibG9nLCBUcmFkaW5nIFNtYXJ0 ZXINCg0KVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIG9ubHkgZm9yIHRoZSByZWNpcGllbnQocykg bmFtZWQgYWJvdmUgYW5kIG1heQ0KY29udGFpbiBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24uIElm IHlvdSBhcmUgbm90IGFuIGludGVuZGVkIHJlY2lwaWVudCwNCnlvdSBzaG91bGQgbm90IHJldmll dywgZGlzdHJpYnV0ZSBvciBjb3B5IHRoaXMgbWVzc2FnZS4gUGxlYXNlIG5vdGlmeQ0KdGhlIHNl bmRlciBpbW1lZGlhdGVseSBieSBlLW1haWwgaWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBtZXNz YWdlIGluDQplcnJvciBhbmQgZGVsZXRlIGl0IGZyb20geW91ciBzeXN0ZW0uDQoNCg0KDQo= --_000_14881789467733340cameltradingscreencom_ Content-Type: text/html; charset="utf-8" Content-ID: <15C18DC516D292408FACD79B5C3FD16D@localhost> Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUUkFOU0lUSU9OQUwv L0VOIj4NCjxodG1sPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNv bnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHRU5FUkFUT1Ii IGNvbnRlbnQ9Ikd0a0hUTUwvNC44LjUiPg0KPC9oZWFkPg0KPGJvZHk+DQpIZWxsbyw8YnI+DQo8 YnI+DQpJJ3ZlIGhhdmUgYSBob3N0ZWQgZW5naW5lIHRoYXRzIHVwIGFuZCBydW5uaW5nIG9uIGEg aG9zdCBjYWxsZWQgaG9zdGVkLWVuZ2luZTEuIEkgaW5zdGFsbGVkIGhvc3RlZC1lbmdpbmUyIHZp YSB0aGUgd2ViYWRtaW4gZ3VpIGJ1dCBhbSB1bmFibGUgdG8gZmFpbC1vdmVyIHRoZSBob3N0ZWQt ZW5naW5lLjxicj4NCkhvd2V2ZXIgaG9zdGVkIGVuZ2luZS1ob3N0ZWQyIGlzIGJlaW5nIHNlbnNl ZCBhcyBhIG5vZGUgaW4gdGhlIGRlZmF1bHQgY2x1c3RlciBhbmQgSSBoYXZlIGVuYWJsZWQgSEEg cmVzZXJ2YXRpb24sIGFzIHBlciB0aGlzIG1haWw6PGJyPg0KPGJyPg0KPGEgaHJlZj0iaHR0cHM6 Ly93d3cubWFpbC1hcmNoaXZlLmNvbS91c2Vyc0BvdmlydC5vcmcvbXNnMzQ4NDcuaHRtbCI+aHR0 cHM6Ly93d3cubWFpbC1hcmNoaXZlLmNvbS91c2Vyc0BvdmlydC5vcmcvbXNnMzQ4NDcuaHRtbDwv YT48YnI+DQo8YnI+DQpCdXQgaXMgcG93ZXIgbWFuYWdlbWVudCBlc3NlbnRpYWwgZm9yIGhvc3Rl ZCBlbmdpbmUgY2x1c3RlcmluZyA/IDxicj4NCjxicj4NCkFuZCBJIGdldCB0aGlzIGVycm9yIGJl bG93IHdoZW4gdHJ5aW5nIHRvIGZhaWxvdmVyPGJyPg0KPGJyPg0KJnF1b3Q7Q2Fubm90IG1pZ3Jh dGUgVk0uIFRoZXJlIGlzIG5vIGhvc3QgdGhhdCBzYXRpc2ZpZXMgY3VycmVudCBzY2hlZHVsaW5n IGNvbnN0cmFpbnRzLiBTZWUgYmVsb3cgZm9yIGRldGFpbHM6PGJyPg0KPGJyPg0KVGhlIGhvc3Qg aG9zdGVkLWVuZ2luZTIgZGlkIG5vdCBzYXRpc2Z5IGludGVybmFsIGZpbHRlciBIQSBiZWNhdXNl IGl0IGlzIG5vdCBhIEhvc3RlZCBFbmdpbmUgaG9zdC4uPGJyPg0KVGhlIGhvc3QgaG9zdGVkLWVu Z2luZTEgZGlkIG5vdCBzYXRpc2Z5IGludGVybmFsIGZpbHRlciBIQSBiZWNhdXNlIGl0IGlzIG5v dCBhIEhvc3RlZCBFbmdpbmUgaG9zdC4mcXVvdDs8YnI+DQo8YnI+DQpUaGFua3MsPGJyPg0KSm9l Ljxicj4NCjxicj4NCjx0YWJsZSBjZWxsc3BhY2luZz0iMCIgY2VsbHBhZGRpbmc9IjAiIHdpZHRo PSIxMDAlIj4NCjx0Ym9keT4NCjx0cj4NCjx0ZD4tLQ0KPHByZT4NCjxiPkouIEtlbGx5PC9iPg0K SW5mcmFzdHJ1Y3R1cmUgRW5naW5lZXINClRyYWRpbmdTY3JlZW4NCjxhIGhyZWY9Imh0dHA6Ly93 d3cudHJhZGluZ3NjcmVlbi5jb20iPnd3dy50cmFkaW5nc2NyZWVuLmNvbTwvYT4NCktEWCBSb3Bw b25naSAyMjggQmxkZy4gNkYNCjItMi04IFJvcHBvbmdpLCBNaW5hdG8ta3UsIFRva3lvIDEwNi0w MDMyLCBKYXBhbg0Kb2ZmaWNlOiAmIzQzOzgxLTMtNDU0MC04NTEzDQplbWFpbDogPGEgaHJlZj0i bWFpbHRvOmpvc2VwaC5rZWxseUB0cmFkaW5nc2NyZWVuLmNvbSI+am9zZXBoLmtlbGx5QHRyYWRp bmdzY3JlZW4uY29tPC9hPg0KDQpGb2xsb3cgVHJhZGluZ1NjcmVlbiBvbiBUd2l0dGVyLCBGYWNl Ym9vaywgb3Igb3VyIGJsb2csIFRyYWRpbmcgU21hcnRlcg0KDQpUaGlzIG1lc3NhZ2UgaXMgaW50 ZW5kZWQgb25seSBmb3IgdGhlIHJlY2lwaWVudChzKSBuYW1lZCBhYm92ZSBhbmQgbWF5DQpjb250 YWluIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbi4gSWYgeW91IGFyZSBub3QgYW4gaW50ZW5kZWQg cmVjaXBpZW50LA0KeW91IHNob3VsZCBub3QgcmV2aWV3LCBkaXN0cmlidXRlIG9yIGNvcHkgdGhp cyBtZXNzYWdlLiBQbGVhc2Ugbm90aWZ5DQp0aGUgc2VuZGVyIGltbWVkaWF0ZWx5IGJ5IGUtbWFp bCBpZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIG1lc3NhZ2UgaW4NCmVycm9yIGFuZCBkZWxldGUg aXQgZnJvbSB5b3VyIHN5c3RlbS4NCg0KPC9wcmU+DQo8L3RkPg0KPC90cj4NCjwvdGJvZHk+DQo8 L3RhYmxlPg0KPC9ib2R5Pg0KPC9odG1sPg0K --_000_14881789467733340cameltradingscreencom_--

2 2

Hosting an oVirt test cluster on single machine running Fedora 25 with nested virtualization enabled.
by john 27 Feb '17

27 Feb '17

Hi everybody, I'm having a nightmarish time trying to test oVirt and RHEV on my main machine which i just upgraded to Fedora 25 (before realising oVirt is still on F24). Nevertheless, it seems to me I shouldn't have a problem if i just use F24/RHEV/oVirt nodes running under my F25 machine. The F25 physical host is a pretty powerful machine, 8 (HT) cores, SSD storage, 16 GB ram (bit light on RAM but this should be just sufficient to run the engine & host, and say one test host) Main problem is that i just cannot seem to add a new host to this cluster. I am using the F25 physical host to export NFS4 storage (on SSD), for the oVirt cluster. So currently, I have, all on one physical machine: 1) ovirt-engine-host vm - this is the F24 host which i ran hosted-engine --deploy in. So, if the physical host is layer 0 (L0), this is L1. VM has been given 3 CPUs, 6GB of RAM 2) ovirt-engine vm- this is the vm inside ovirt-engine-host, and this vm is the main ovirt admin engine/appliance. The image for this appliance was obtained from: ovirt-engine-appliance-4.1-20170201.1.fc24.noarch.rpm So this vm is at L2. According to the ovirt Manager web admin page, this is running: oVirt Engine Version:4.1.0.3-1.el7.centos When i ran the hosted-engine --deploy, I specified 2 CPUs, 4GB of RAM, however, when i look at this host in the management webpqage, it reports 3 CPU, and 6GB of RAM, so the hosted engine deploy script seems to have ignored my wishes and given this vm the full resources of its host vm, which is a little annoying but shouldnt be causing a problem at this stage. Basically, this seems to be working. I can login to the oVirt Manager webpage and see my whole datacenter, storage, cluster, etc. I've been able to add a data domain, and an iso storage domain, and when i did this, the new data storage domain became the Master, and the hosted_storage domain (holding my ovirt-engine host) appeared out of nowhere in the UI. So i now have 3 storage domains - the hosted_engine, the master, and iso storage. So anyway, this is where the problems start. No matter what I try, I can't seem to add a host to this cluster, which seems to be working fine otherwise. On all my F24 hosts Ive installed python2-dnf which is required by oVirt on F24, installed nfs-utils so it can mount nfs shares, enabled ovirt repository, setup static IP address, tweaked /etc/hosts so all my hosts can see each other without relying on the physical KVM host's DNS. I have tried: 1) create a new F24 VM under my physical host, so, at L1. I called this ovirt-host-01. I have enabled CPU host-passthrough in KVM so this VM can also run nested VMs, which is of course, the main objective. I've given this VM 3 CPUs, and 6GB of RAM. Go to Management webpage and try to add this as a new host. It ALMOST succeeds, but at the end it fails to mount my hosted_storage domain. It correctly mounts the main master data domain, and the iso domain, but fails to mount the hosted_storage domain. I can mount this domain manually, and I just can't work out why this fails, it's incredibly frustrating. 2) create a new host using the latest oVirt node iso: ovirt-node-ng-installer-ovirt-4.0-2017011712.iso node has 25 GB disk,3 CPUs, 6GB of RAM. Cockpit admin webpage reports it is an "oVirt Node 4.0.6.1" The node seems to be running fine, but i can't seem to add it to my main cluster. The VDSM service is failing because it's not a member of any domain. The main "System" tab in CockPit lists all the details, but for Domain, it says: "Join Domain". Nowhere in this CockPit admin webpage does there appear to be any way to actually specify the domain to join. So, I go to my main engine Admin page, and try to add this node as a new host. It attempts to do so, but fails, after trying to trying to install the package collectd, which is in epel. So i enable epel, even though I'm sure something must be drastically wrong here, because this oVirt node should have everything it needs already installed on it. Trying to reinstall again, it fails with the exact same error in the deployment log, saying collectd cannot be found even though it is available from epel & epel repo is enabled. Summary: This is incredibly frustrating. Why is it so hard to add a host to an oVirt cluster. This should be child's play. What is going on? I have seen another email to this list saying you have to run hosted engine deploy on bare metal (L0), so the engine vm is at L1, or the HA features of vdsm are pointless, but I'm not clear why that is, I was hoping i should be able to get some sort of power management setup eventually, KVM & virsh should be able to provide full power management of the hosts even if i had to kludge together a few scripts myself. Plus that still shouldn't prevent me from setting up this test cluster surely. I know i haven't configured power management properly on the hosts i'm adding, but, so what, they should at least work for testing purposes. If we set aside the power management issues for now, I can't see why there should be issues setting up this whole cluster under KVM on a single physical host. The nested virtualisation is working perfectly. Apologies for the long email, but i thought it best to get most of the details out there, so ppl won't have to go back & forth asking questions just to see what i am trying to do. Any questions re details i've left out though, pls feel free to ask. If anyone can offer any halp or advice it'd be greatly appreciated, ta and cheers! J

2 2

upgrading from 3.6 -> 4.1, vm restarts at 4.0 mandatory?
by Darrell Budic 26 Feb '17

26 Feb '17

I’m upgrading my main cluster from 3.6 to 4.1, and I’m currently at 4.0. I’ve upgraded the cluster and datacenter compatibility versions to 4.0, and now all my VMs are pending restart to update their configs to 4.0. My question is “Do I need to do this here, or can I go ahead and update the engine and host nodes to 4.1, update compatibility to 4.1, and then restart all the VMs to get them on 4.1”? Or is that unsafe, will I screw them up if I go to 4.1 compatibility in this state? Thanks, -Darrell

2 2

oVirt 4.1 Release Stops at Installing host on enrrolling serial console certificate
by Manuel Luis Aznar 26 Feb '17

26 Feb '17

Hello there, I am doing a very litle installation at home, just with one machine (Asus X99-E WS and Intel Core i7 6850K), all is fine until I reached the installation of the host (adding host). The web admin interface get stopped and the last event is Enrrolling Serial Console Certificate and in few litle seconds the web admin interface stops responding. To make the web admin interface back again I need to do engine-cleanup and engine-setup... Hope somebody can help me, Thanks Manuel

1 0

Restoring Hosted Engine to failed
by Logan Kuhn 26 Feb '17

26 Feb '17

Hi I'm in the process of trying to restore our previous hosted engine onto new, permanent, storage. I've followed this guide: https://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engi… It went pretty smoothly up until the hosted engine deploy tried to add the host to the environment. The error was Unable to add HEVM to the manager. However, I can login to the environment just fine, but it does not have the HEVM and the host it's currently running on is down. I've attached the hosted engine setup log. Let me know if there are any other logs that will be helpful Logan

3 3

ovirt 4.1.0.4 error..
by Thomas Davis 26 Feb '17

26 Feb '17

I am getting this error message: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at [Source: java.io.StringReader@4c65dbb1; line: 1, column: 2] in both screen after login on ovirt, and in the engine.log. Any ideas one what it is looking for this? This ovirt setup has gone from 3.5 -> 3.6 -> 4.0 -> 4.1. I am currently blocked on doing any VM management in ovirt due to this.. thomas

2 3

Recognize HE iSCSI volume size change
by Chris Adams 24 Feb '17

24 Feb '17

I'm testing upgrading an oVirt 3.5 setup, and I have run into a problem when going from 3.5 to 3.6 on a physical machine configured for the hosted engine. I upgraded the engine itself okay, but when I upgraded the first physical machine, it cannot be re-activated; it gets an error connecting to the storage domain. Checking the logs, it looks like it is looping trying to create a new LV in the HE VG. I assume this is for moving the HE config to the shared storage? It is failing because it is trying to create a 1G LV, but the VG only has 512M free space. I extended the iSCSI volume, but there doesn't appear to be anyway to get the HE nodes to recognize this; they both still see the original size, no matter what I try. Is there a way to get them to see the larger PV, so the new LV(s) can be created? -- Chris Adams <cma(a)cmadams.net>

4 8

Re: [ovirt-users] Disable guest agent not installed warning
by Karli Sjöberg 24 Feb '17

24 Feb '17

--_000_6ae132c671124470a8710a2101a78e1bexch24sluse_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 DQpEZW4gMjMgZmViLiAyMDE3IDY6MTAgZW0gc2tyZXYgTmlyIFNvZmZlciA8bnNvZmZlckByZWRo YXQuY29tPjoNCj4NCj4gT24gVGh1LCBGZWIgMjMsIDIwMTcgYXQgNjo0NyBQTSwgS2FybGkgU2rD tmJlcmcgPGthcmxpLnNqb2JlcmdAc2x1LnNlPiB3cm90ZToNCj4gPg0KPiA+IERlbiAyMyBmZWIu IDIwMTcgNDowOSBlbSBza3JldiBOaXIgU29mZmVyIDxuc29mZmVyQHJlZGhhdC5jb20+Og0KPiA+ Pg0KPiA+PiBPbiBUaHUsIEZlYiAyMywgMjAxNyBhdCA0OjM4IFBNLCBLYXJsaSBTasO2YmVyZyA8 a2FybGkuc2pvYmVyZ0BzbHUuc2U+DQo+ID4+IHdyb3RlOg0KPiA+PiA+IE9uIFRodSwgMjAxNy0w Mi0yMyBhdCAxMzo0NiArMDAwMCwgTWlzYWsgS2hhY2hhdHJ5YW4gd3JvdGU6DQo+ID4+ID4+IEhp IHRoZXJlLiBBbnlib2R5IGtub3dzIGhvdyB0byBzdXBwcmVzcyBndWVzdCBhZ2VudCBub3QgaW5z dGFsbGVkDQo+ID4+ID4+IHdhcm5pbmcgZm9yIFZNPyBJIGhhdmUgb25lIFZNIGJhc2VkIG9uIEZy ZWVCU0QsIHdoZXJlIGkgY2FuJ3QgaW5zdGFsbA0KPiA+PiA+PiBpdCBhbmQgdGhlIHdhcm5pbmcg aXMganVzdCBhbm5veWluZy4NCj4gPj4NCj4gPj4gSSBsZWFybmVkIHRvZGF5IHRoYXQgSEEgZG9l cyBub3Qgd29yayBwcm9wZXJseSBpZiBndWVzdCBhZ2VudCBpcyBub3QNCj4gPj4gaW5zdGFsbGVk LA0KPiA+PiBzbyB5b3Ugc2hvdWxkIGJlIGNhcmVmdWwgYWJvdXQgdGhlIHdhcm5pbmcuDQo+ID4+ DQo+ID4+IE5pcg0KPiA+DQo+ID4gVWhtLCB3aGF0IG1ha2VzIHlvdSBzYXkgdGhhdCBleGFjdGx5 PyBJJ3ZlIGJlZW4gcnVubmluZyBvVmlydCBzaW5jZSBnb2QNCj4gPiBrbm93cyBob3cgbG9uZyBu b3csIGZhY2VkIGNvdW50bGVzcyBvZiB0aW1lcyB3aGVyZSBIQSB3b3JrZWQgcGVyZmVjdGx5IGZp bmUuDQo+ID4gSWYgdGhpcyBpcyBhIG5ldyAiZmVhdHVyZSIsIHlvdSBoYXZlIG15IHNpbmNlcmVz dCB0aHVtYnMgZG93biBvbiB0aGF0IG9uZTopDQo+DQo+IElmIHRoZSB2bSBpcyB0ZXJtaW5hdGVk IG9uIHRoZSBob3N0LCB3ZSB3aWxsIHRyZWF0IHRoYXQgYXMgbm9ybWFsIHRlcm1pbmF0aW9uDQo+ IChlLmcuIHBvd2Vyb2ZmIHdpdGhpbiB0aGUgdm0pLCBhbmQgd2lsbCBub3Qgc3RhcnQgdGhlIHZt IG9uIGFub3RoZXIgaG9zdC4NCj4NCj4gWW91IHByb2JhYmx5IGRvIG5vdCBub3RpY2UgdGhpcyBz aW5jZSBub2JvZHkgaXMga2lsbGluZyB5b3VyIHZtcy4NCj4NCj4gTmlyDQoNClNvIGEgJ2tpbGwg LTknIG9yIHFlbXUgYnVnLCBodWg/IEdvb2QgdG8ga25vdywgYnV0IEkgY29uc2lkZXIgaXQgYSBz bWFsbCByaXNrLg0KDQpCVFcgTWlzYWssIHlvdSBzaG91bGQgYmUgYWJsZSB0byBnZXQgdGhlIGd1 ZXN0IGFnZW50IHJ1bm5pbmcgaW4gRnJlZUJTRCAxMSwgc2luY2UgdGhleSBhZGRlZCBWaXJ0SU8g c2VyaWFsIG5vdywgaGF2ZW4ndCB0cmllZCBpdCBteXNlbGYsIGEgYml0IHByZW9jY3VwaWVkIGF0 IHRoZSBtb21lbnQuDQoNCi9LDQo= --_000_6ae132c671124470a8710a2101a78e1bexch24sluse_ Content-Type: text/html; charset="utf-8" Content-ID: <A04CD01C21FF574790EE7397654C834D(a)ad.slu.se> Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPHAgZGlyPSJsdHIi Pjxicj4NCkRlbiAyMyBmZWIuIDIwMTcgNjoxMCBlbSBza3JldiBOaXIgU29mZmVyICZsdDtuc29m ZmVyQHJlZGhhdC5jb20mZ3Q7Ojxicj4NCiZndDs8YnI+DQomZ3Q7IE9uIFRodSwgRmViIDIzLCAy MDE3IGF0IDY6NDcgUE0sIEthcmxpIFNqw7ZiZXJnICZsdDtrYXJsaS5zam9iZXJnQHNsdS5zZSZn dDsgd3JvdGU6PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IERlbiAyMyBmZWIuIDIwMTcg NDowOSBlbSBza3JldiBOaXIgU29mZmVyICZsdDtuc29mZmVyQHJlZGhhdC5jb20mZ3Q7Ojxicj4N CiZndDsgJmd0OyZndDs8YnI+DQomZ3Q7ICZndDsmZ3Q7IE9uIFRodSwgRmViIDIzLCAyMDE3IGF0 IDQ6MzggUE0sIEthcmxpIFNqw7ZiZXJnICZsdDtrYXJsaS5zam9iZXJnQHNsdS5zZSZndDs8YnI+ DQomZ3Q7ICZndDsmZ3Q7IHdyb3RlOjxicj4NCiZndDsgJmd0OyZndDsgJmd0OyBPbiBUaHUsIDIw MTctMDItMjMgYXQgMTM6NDYgJiM0MzswMDAwLCBNaXNhayBLaGFjaGF0cnlhbiB3cm90ZTo8YnI+ DQomZ3Q7ICZndDsmZ3Q7ICZndDsmZ3Q7IEhpIHRoZXJlLiBBbnlib2R5IGtub3dzIGhvdyB0byBz dXBwcmVzcyBndWVzdCBhZ2VudCBub3QgaW5zdGFsbGVkPGJyPg0KJmd0OyAmZ3Q7Jmd0OyAmZ3Q7 Jmd0OyB3YXJuaW5nIGZvciBWTT8gSSBoYXZlIG9uZSBWTSBiYXNlZCBvbiBGcmVlQlNELCB3aGVy ZSBpIGNhbid0IGluc3RhbGw8YnI+DQomZ3Q7ICZndDsmZ3Q7ICZndDsmZ3Q7IGl0IGFuZCB0aGUg d2FybmluZyBpcyBqdXN0IGFubm95aW5nLjxicj4NCiZndDsgJmd0OyZndDs8YnI+DQomZ3Q7ICZn dDsmZ3Q7IEkgbGVhcm5lZCB0b2RheSB0aGF0IEhBIGRvZXMgbm90IHdvcmsgcHJvcGVybHkgaWYg Z3Vlc3QgYWdlbnQgaXMgbm90PGJyPg0KJmd0OyAmZ3Q7Jmd0OyBpbnN0YWxsZWQsPGJyPg0KJmd0 OyAmZ3Q7Jmd0OyBzbyB5b3Ugc2hvdWxkIGJlIGNhcmVmdWwgYWJvdXQgdGhlIHdhcm5pbmcuPGJy Pg0KJmd0OyAmZ3Q7Jmd0Ozxicj4NCiZndDsgJmd0OyZndDsgTmlyPGJyPg0KJmd0OyAmZ3Q7PGJy Pg0KJmd0OyAmZ3Q7IFVobSwgd2hhdCBtYWtlcyB5b3Ugc2F5IHRoYXQgZXhhY3RseT8gSSd2ZSBi ZWVuIHJ1bm5pbmcgb1ZpcnQgc2luY2UgZ29kPGJyPg0KJmd0OyAmZ3Q7IGtub3dzIGhvdyBsb25n IG5vdywgZmFjZWQgY291bnRsZXNzIG9mIHRpbWVzIHdoZXJlIEhBIHdvcmtlZCBwZXJmZWN0bHkg ZmluZS48YnI+DQomZ3Q7ICZndDsgSWYgdGhpcyBpcyBhIG5ldyAmcXVvdDtmZWF0dXJlJnF1b3Q7 LCB5b3UgaGF2ZSBteSBzaW5jZXJlc3QgdGh1bWJzIGRvd24gb24gdGhhdCBvbmU6KTxicj4NCiZn dDs8YnI+DQomZ3Q7IElmIHRoZSB2bSBpcyB0ZXJtaW5hdGVkIG9uIHRoZSBob3N0LCB3ZSB3aWxs IHRyZWF0IHRoYXQgYXMgbm9ybWFsIHRlcm1pbmF0aW9uPGJyPg0KJmd0OyAoZS5nLiBwb3dlcm9m ZiB3aXRoaW4gdGhlIHZtKSwgYW5kIHdpbGwgbm90IHN0YXJ0IHRoZSB2bSBvbiBhbm90aGVyIGhv c3QuPGJyPg0KJmd0Ozxicj4NCiZndDsgWW91IHByb2JhYmx5IGRvIG5vdCBub3RpY2UgdGhpcyBz aW5jZSBub2JvZHkgaXMga2lsbGluZyB5b3VyIHZtcy48YnI+DQomZ3Q7PGJyPg0KJmd0OyBOaXI8 L3A+DQo8cCBkaXI9Imx0ciI+U28gYSAna2lsbCAtOScgb3IgcWVtdSBidWcsIGh1aD8gR29vZCB0 byBrbm93LCBidXQgSSBjb25zaWRlciBpdCBhIHNtYWxsIHJpc2suPC9wPg0KPHAgZGlyPSJsdHIi PkJUVyBNaXNhaywgeW91IHNob3VsZCBiZSBhYmxlIHRvIGdldCB0aGUgZ3Vlc3QgYWdlbnQgcnVu bmluZyBpbiBGcmVlQlNEIDExLCBzaW5jZSB0aGV5IGFkZGVkIFZpcnRJTyBzZXJpYWwgbm93LCBo YXZlbid0IHRyaWVkIGl0IG15c2VsZiwgYSBiaXQgcHJlb2NjdXBpZWQgYXQgdGhlIG1vbWVudC48 L3A+DQo8cCBkaXI9Imx0ciI+L0s8L3A+DQo8L2JvZHk+DQo8L2h0bWw+DQo= --_000_6ae132c671124470a8710a2101a78e1bexch24sluse_--

4 4

Troubleshoot failed storage migration
by Christian Grenier 24 Feb '17

24 Feb '17

--_000_3A56B77305AE8C409AD1F3C35371BB611A67E8FESBSB2B2Cincloca_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I had an outage during live storage migration of a VM disk between two iSCS= I. Since the outage prevented Ovirt to cleanly remove stuff on the destination= iSCSI when the failure occurred, I think there's leftovers on the destinat= ion iSCSI. The result is that any further attempt to live storage migrate t= his VM disk fails with error "Cannot create Logical Volume" How can I troubleshoot / fix this ? -- Christian Grenier --_000_3A56B77305AE8C409AD1F3C35371BB611A67E8FESBSB2B2Cincloca_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"FR-CA" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> I had an outage during live sto= rage migration of a VM disk between two iSCSI. <o:p></o:p> <o:p> </o:p> Since the outage prevented Ovir= t to cleanly remove stuff on the destination iSCSI when the failure occurre= d, I think there’s leftovers on the destination iSCSI. The result is = that any further attempt to live storage migrate this VM disk fails with error “Cannot create Logical Volume”<o= :p></o:p> <o:p> </o:p> How can I troubleshoot / fix th= is ?<o:p></o:p> <o:p> </o:p> -- Christian Grenier  <o:p></o:p> <o:p> </o:p> </div> </body> </html> --_000_3A56B77305AE8C409AD1F3C35371BB611A67E8FESBSB2B2Cincloca_--

2 1

Two Problems On New Install
by Charles Tassell 24 Feb '17

24 Feb '17

Hi Everyone, I recently installed oVirt 4.0 on two servers with an iSCSI backstore, and I'm having two issues I'm having trouble tracking down. First, the initial datastore that the hosted engine is running on won't connect. It just says "Unattached" in the GUI, and I can't find an error message anywhere. Not a huge deal, it just means I can't see the hosted engine itself in the GUI. More importantly: I can't migrate VMs. They fail with errors like this in the vdsm.log of the destination host: Thread-60381::ERROR::2017-02-14 21:55:47,921::vm::767::virt.vm::(_startUnderlyingVm) vmId=`59f235cc-3ab2-4dae-b460-62be850e3d5d`::Failed to start a migration destination vm Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 733, in _startUnderlyingVm self._completeIncomingMigration() File "/usr/share/vdsm/virt/vm.py", line 3113, in _completeIncomingMigration self._incomingMigrationFinished.isSet(), usedTimeout) File "/usr/share/vdsm/virt/vm.py", line 3196, in _attachLibvirtDomainAfterMigration raise MigrationError(e.get_error_message()) MigrationError: Domain not found: no domain with matching uuid '59f235cc-3ab2-4dae-b460-62be850e3d5d' If I shut the VM down and start it on the host it works fine, it just won't migrate. I notice I'm also seeing a lot (like every 7 seconds) of this error: JsonRpc (StompReactor)::ERROR::2017-02-14 21:57:33,984::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof Which I can't seem to diagnose. Any ideas?

2 3