[Users] Hello All I am new to ovirt and have a question
I have recently set up an ovirt engine server and one host. The ovirt engine server was installed on a small Intell Atom quad core with 4 gigs of ram box. The ovirt engine server is running on Fedora 16 and engine was installed from rpms after I added the repo. Also I have installed one host or node if you prefer That is an AMD quad core with 8 gigs of ram and has virtualization. I have tried installing from ovirt node 2.2.1 iso but ethernet card can not be intialized even though it is detected. This is a realtek card and it shows up fine in fedora 16. The iso is still a bit buggy for me so I tried installing fedora 16 and then the vdsm rpm packages from repository. I have correctly set up a bridge on fedora 16 and by the way your instructions are wrong for bridge setup. I will be glad to send you guys a correct config for the wiki if neccessary for fedora 16. Vdsm is running and I installed host from the ovirt gui by adding new host entered ip config an.d it appeared in the ovirt web manager. What it does not do properly is install on the Ovirt web manager I get installing then it says install failed. I have tried reinstalling from the ovirt web manager to no avail. The wiki is a good start but directions are lacking I must say. Is there any more config that needs to be done on the vdsm.conf file in etc/vdsm/vdsm.conf or does it just "detect" when the Ovirt web manager calls for it? I am probably missing something on my end I am guessing. Also what log files would be helpful to look at? I will be trying this out also on a new asus server with two 8 core amd opterons and 32 gigs of ram shortly so I will let you know how that goes also. This project is great I just need to get a working host and I want to write a simpler install write up for this project that in my opinion is what it is lacking. Let me know, -- Dominic Kaiser Greater Boston Vineyard Director of Operations cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
--Apple-Mail-69E08F1E-4E50-4DF1-856E-682ACCE9638D Content-Transfer-Encoding: base64 Content-Type: text/plain; charset=us-ascii DQoNCkhpIERvbWluaWMsIA0KDQpDb3VsZCB5b3UgcGxlYXNlIGF0dGFjaCBpbnN0YWxsYXRpb24g bG9ncyBvbiB0aGUgaG9zdCBzaWRlID8gWW91IGNhbiBmaW5kIHRoZW0gdW5kZXIgL3RtcC8gLSBp dCdzIHZkc19pbnN0YWxsZXIubG9nLCB2ZHNfYm9vdHN0cmFwLmxvZyBhbmQgdmRzX2Jvb3RzdHJh cF9jb21wbGV0ZS5sb2cuDQoNCg0KT24gSmFuIDE0LCAyMDEyLCBhdCAyMzowNCwgRG9taW5pYyBL YWlzZXIgPGRvbWluaWNAYm9zdG9udmluZXlhcmQub3JnPiB3cm90ZToNCg0KPiBJIGhhdmUgcmVj ZW50bHkgc2V0IHVwIGFuIG92aXJ0IGVuZ2luZSBzZXJ2ZXIgYW5kIG9uZSBob3N0LiAgVGhlIG92 aXJ0IGVuZ2luZSBzZXJ2ZXIgd2FzIGluc3RhbGxlZCBvbiBhIHNtYWxsIEludGVsbCBBdG9tIHF1 YWQgY29yZSB3aXRoIDQgZ2lncyBvZiByYW0gYm94LiAgVGhlIG92aXJ0IGVuZ2luZSBzZXJ2ZXIg aXMgcnVubmluZyBvbiBGZWRvcmEgMTYgYW5kIGVuZ2luZSB3YXMgaW5zdGFsbGVkIGZyb20gcnBt cyBhZnRlciBJIGFkZGVkIHRoZSByZXBvLiAgQWxzbyBJIGhhdmUgaW5zdGFsbGVkIG9uZSBob3N0 IG9yIG5vZGUgaWYgeW91IHByZWZlciBUaGF0IGlzIGFuIEFNRCBxdWFkIGNvcmUgd2l0aCA4IGdp Z3Mgb2YgcmFtIGFuZCBoYXMgdmlydHVhbGl6YXRpb24uICBJIGhhdmUgdHJpZWQgaW5zdGFsbGlu ZyBmcm9tIG92aXJ0IG5vZGUgMi4yLjEgaXNvIGJ1dCBldGhlcm5ldCBjYXJkIGNhbiBub3QgYmUg aW50aWFsaXplZCBldmVuIHRob3VnaCBpdCBpcyBkZXRlY3RlZC4gIFRoaXMgaXMgYSByZWFsdGVr IGNhcmQgYW5kIGl0IHNob3dzIHVwIGZpbmUgaW4gZmVkb3JhIDE2LiAgVGhlIGlzbyBpcyBzdGls bCBhIGJpdCBidWdneSBmb3IgbWUgc28gSSB0cmllZCBpbnN0YWxsaW5nIGZlZG9yYSAxNiBhbmQg dGhlbiB0aGUgdmRzbSBycG0gcGFja2FnZXMgZnJvbSByZXBvc2l0b3J5LiAgSSBoYXZlIGNvcnJl Y3RseSBzZXQgdXAgYSBicmlkZ2Ugb24gZmVkb3JhIDE2IGFuZCBieSB0aGUgd2F5IHlvdXIgaW5z dHJ1Y3Rpb25zIGFyZSB3cm9uZyBmb3IgYnJpZGdlIHNldHVwLiAgSSB3aWxsIGJlIGdsYWQgdG8g c2VuZCB5b3UgZ3V5cyBhIGNvcnJlY3QgY29uZmlnIGZvciB0aGUgd2lraSBpZiBuZWNjZXNzYXJ5 IGZvciBmZWRvcmEgMTYuICBWZHNtIGlzIHJ1bm5pbmcgYW5kIEkgaW5zdGFsbGVkIGhvc3QgZnJv bSB0aGUgb3ZpcnQgZ3VpIGJ5IGFkZGluZyBuZXcgaG9zdCBlbnRlcmVkIGlwIGNvbmZpZyBhbi5k IGl0IGFwcGVhcmVkIGluIHRoZSBvdmlydCB3ZWIgbWFuYWdlci4gIFdoYXQgaXQgZG9lcyBub3Qg ZG8gcHJvcGVybHkgaXMgaW5zdGFsbCBvbiB0aGUgT3ZpcnQgd2ViIG1hbmFnZXIgSSBnZXQgaW5z dGFsbGluZyB0aGVuIGl0IHNheXMgaW5zdGFsbCBmYWlsZWQuICBJIGhhdmUgdHJpZWQgcmVpbnN0 YWxsaW5nIGZyb20gdGhlIG92aXJ0IHdlYiBtYW5hZ2VyIHRvIG5vIGF2YWlsLiAgVGhlIHdpa2kg aXMgYSBnb29kIHN0YXJ0IGJ1dCBkaXJlY3Rpb25zIGFyZSBsYWNraW5nIEkgbXVzdCBzYXkuICBJ cyB0aGVyZSBhbnkgbW9yZSBjb25maWcgdGhhdCBuZWVkcyB0byBiZSBkb25lIG9uIHRoZSB2ZHNt LmNvbmYgZmlsZSBpbiBldGMvdmRzbS92ZHNtLmNvbmYgb3IgZG9lcyBpdCBqdXN0ICJkZXRlY3Qi IHdoZW4gdGhlIE92aXJ0IHdlYiBtYW5hZ2VyIGNhbGxzIGZvciBpdD8gIEkgYW0gcHJvYmFibHkg bWlzc2luZyBzb21ldGhpbmcgb24gbXkgZW5kIEkgYW0gZ3Vlc3NpbmcuICBBbHNvIHdoYXQgbG9n IGZpbGVzIHdvdWxkIGJlIGhlbHBmdWwgdG8gbG9vayBhdD8gIEkgd2lsbCBiZSB0cnlpbmcgdGhp cyBvdXQgYWxzbyBvbiBhIG5ldyBhc3VzIHNlcnZlciB3aXRoIHR3byA4IGNvcmUgYW1kIG9wdGVy b25zIGFuZCAzMiBnaWdzIG9mIHJhbSBzaG9ydGx5IHNvIEkgd2lsbCBsZXQgeW91IGtub3cgaG93 IHRoYXQgZ29lcyBhbHNvLiAgVGhpcyBwcm9qZWN0IGlzIGdyZWF0IEkganVzdCBuZWVkIHRvIGdl dCBhIHdvcmtpbmcgaG9zdCBhbmQgSSB3YW50IHRvIHdyaXRlIGEgc2ltcGxlciBpbnN0YWxsIHdy aXRlIHVwIGZvciB0aGlzIHByb2plY3QgdGhhdCBpbiBteSBvcGluaW9uIGlzIHdoYXQgaXQgaXMg bGFja2luZy4gDQo+IA0KPiBMZXQgbWUga25vdywNCj4gDQo+IC0tIA0KPiBEb21pbmljIEthaXNl cg0KPiBHcmVhdGVyIEJvc3RvbiBWaW5leWFyZA0KPiBEaXJlY3RvciBvZiBPcGVyYXRpb25zDQo+ IA0KPiBjZWxsOiA2MTctMjMwLTE0MTINCj4gZmF4OiA2MTctMjUyLTAyMzgNCj4gZW1haWw6IGRv bWluaWNAYm9zdG9udmluZXlhcmQub3JnDQo+IA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gVXNlcnMgbWFpbGluZyBsaXN0DQo+IFVzZXJz QG92aXJ0Lm9yZw0KPiBodHRwOi8vbGlzdHMub3ZpcnQub3JnL21haWxtYW4vbGlzdGluZm8vdXNl cnMNCg== --Apple-Mail-69E08F1E-4E50-4DF1-856E-682ACCE9638D Content-Transfer-Encoding: base64 Content-Type: text/html; charset=utf-8 PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5IGJnY29sb3I9IiNGRkZGRkYiPjxkaXY+PGJyPjxicj5I aSBEb21pbmljLCZuYnNwOzwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+Q291bGQgeW91IHBsZWFz ZSBhdHRhY2ggaW5zdGFsbGF0aW9uIGxvZ3Mgb24gdGhlIGhvc3Qgc2lkZSA/IFlvdSBjYW4gZmlu ZCB0aGVtIHVuZGVyIC90bXAvIC0gaXQncyB2ZHNfaW5zdGFsbGVyLmxvZywgdmRzX2Jvb3RzdHJh cC5sb2cgYW5kIHZkc19ib290c3RyYXBfY29tcGxldGUubG9nLjwvZGl2PjxkaXY+PGJyPjwvZGl2 PjxkaXY+PGJyPk9uIEphbiAxNCwgMjAxMiwgYXQgMjM6MDQsIERvbWluaWMgS2Fpc2VyICZsdDs8 YSBocmVmPSJtYWlsdG86ZG9taW5pY0Bib3N0b252aW5leWFyZC5vcmciPmRvbWluaWNAYm9zdG9u dmluZXlhcmQub3JnPC9hPiZndDsgd3JvdGU6PGJyPjxicj48L2Rpdj48ZGl2PjwvZGl2PjxibG9j a3F1b3RlIHR5cGU9ImNpdGUiPjxkaXY+SSBoYXZlIHJlY2VudGx5IHNldCB1cCBhbiBvdmlydCBl bmdpbmUgc2VydmVyIGFuZCBvbmUgaG9zdC4gJm5ic3A7VGhlIG92aXJ0IGVuZ2luZSBzZXJ2ZXIg d2FzIGluc3RhbGxlZCBvbiBhIHNtYWxsIEludGVsbCBBdG9tIHF1YWQgY29yZSB3aXRoIDQgZ2ln cyBvZiByYW0gYm94LiAmbmJzcDtUaGUgb3ZpcnQgZW5naW5lIHNlcnZlciBpcyBydW5uaW5nIG9u IEZlZG9yYSAxNiBhbmQgZW5naW5lIHdhcyBpbnN0YWxsZWQgZnJvbSBycG1zIGFmdGVyIEkgYWRk ZWQgdGhlIHJlcG8uICZuYnNwO0Fsc28gSSBoYXZlIGluc3RhbGxlZCBvbmUgaG9zdCBvciBub2Rl IGlmIHlvdSBwcmVmZXIgVGhhdCBpcyBhbiBBTUQgcXVhZCBjb3JlIHdpdGggOCBnaWdzIG9mIHJh bSBhbmQgaGFzIHZpcnR1YWxpemF0aW9uLiAmbmJzcDtJIGhhdmUgdHJpZWQgaW5zdGFsbGluZyBm cm9tIG92aXJ0IG5vZGUgMi4yLjEgaXNvIGJ1dCBldGhlcm5ldCBjYXJkIGNhbiBub3QgYmUgaW50 aWFsaXplZCBldmVuIHRob3VnaCBpdCBpcyBkZXRlY3RlZC4gJm5ic3A7VGhpcyBpcyBhIHJlYWx0 ZWsgY2FyZCBhbmQgaXQgc2hvd3MgdXAgZmluZSBpbiBmZWRvcmEgMTYuICZuYnNwO1RoZSBpc28g aXMgc3RpbGwgYSBiaXQgYnVnZ3kgZm9yIG1lIHNvIEkgdHJpZWQgaW5zdGFsbGluZyBmZWRvcmEg MTYgYW5kIHRoZW4gdGhlIHZkc20gcnBtIHBhY2thZ2VzIGZyb20gcmVwb3NpdG9yeS4gJm5ic3A7 SSBoYXZlIGNvcnJlY3RseSBzZXQgdXAgYSBicmlkZ2Ugb24gZmVkb3JhIDE2IGFuZCBieSB0aGUg d2F5IHlvdXIgaW5zdHJ1Y3Rpb25zIGFyZSB3cm9uZyBmb3IgYnJpZGdlIHNldHVwLiAmbmJzcDtJ IHdpbGwgYmUgZ2xhZCB0byBzZW5kIHlvdSBndXlzIGEgY29ycmVjdCBjb25maWcgZm9yIHRoZSB3 aWtpIGlmIG5lY2Nlc3NhcnkgZm9yIGZlZG9yYSAxNi4gJm5ic3A7VmRzbSBpcyBydW5uaW5nIGFu ZCBJIGluc3RhbGxlZCBob3N0IGZyb20gdGhlIG92aXJ0IGd1aSBieSBhZGRpbmcgbmV3IGhvc3Qg ZW50ZXJlZCBpcCBjb25maWcgYW4uZCBpdCBhcHBlYXJlZCBpbiB0aGUgb3ZpcnQgd2ViIG1hbmFn ZXIuICZuYnNwO1doYXQgaXQgZG9lcyBub3QgZG8gcHJvcGVybHkgaXMgaW5zdGFsbCBvbiB0aGUg T3ZpcnQgd2ViIG1hbmFnZXIgSSBnZXQgaW5zdGFsbGluZyB0aGVuIGl0IHNheXMgaW5zdGFsbCBm YWlsZWQuICZuYnNwO0kgaGF2ZSB0cmllZCByZWluc3RhbGxpbmcgZnJvbSB0aGUgb3ZpcnQgd2Vi IG1hbmFnZXIgdG8gbm8gYXZhaWwuICZuYnNwO1RoZSB3aWtpIGlzIGEgZ29vZCBzdGFydCBidXQg ZGlyZWN0aW9ucyBhcmUgbGFja2luZyBJIG11c3Qgc2F5LiAmbmJzcDtJcyB0aGVyZSBhbnkgbW9y ZSBjb25maWcgdGhhdCBuZWVkcyB0byBiZSBkb25lIG9uIHRoZSB2ZHNtLmNvbmYgZmlsZSBpbiBl dGMvdmRzbS92ZHNtLmNvbmYgb3IgZG9lcyBpdCBqdXN0ICJkZXRlY3QiIHdoZW4gdGhlIE92aXJ0 IHdlYiBtYW5hZ2VyIGNhbGxzIGZvciBpdD8gJm5ic3A7SSBhbSBwcm9iYWJseSBtaXNzaW5nIHNv bWV0aGluZyBvbiBteSBlbmQgSSBhbSBndWVzc2luZy4gJm5ic3A7QWxzbyB3aGF0IGxvZyBmaWxl cyB3b3VsZCBiZSBoZWxwZnVsIHRvIGxvb2sgYXQ/ICZuYnNwO0kgd2lsbCBiZSB0cnlpbmcgdGhp cyBvdXQgYWxzbyBvbiBhIG5ldyBhc3VzIHNlcnZlciB3aXRoIHR3byA4IGNvcmUgYW1kIG9wdGVy b25zIGFuZCAzMiBnaWdzIG9mIHJhbSBzaG9ydGx5IHNvIEkgd2lsbCBsZXQgeW91IGtub3cgaG93 IHRoYXQgZ29lcyBhbHNvLiAmbmJzcDtUaGlzIHByb2plY3QgaXMgZ3JlYXQgSSBqdXN0IG5lZWQg dG8gZ2V0IGEgd29ya2luZyBob3N0IGFuZCBJIHdhbnQgdG8gd3JpdGUgYSBzaW1wbGVyIGluc3Rh bGwgd3JpdGUgdXAgZm9yIHRoaXMgcHJvamVjdCB0aGF0IGluIG15IG9waW5pb24gaXMgd2hhdCBp dCBpcyBsYWNraW5nLiZuYnNwOzxkaXY+DQo8YnI+PC9kaXY+PGRpdj5MZXQgbWUga25vdyw8YnIg Y2xlYXI9ImFsbCI+PGRpdj48YnI+PC9kaXY+LS0gPGJyPkRvbWluaWMgS2Fpc2VyPGJyPkdyZWF0 ZXIgQm9zdG9uIFZpbmV5YXJkPGJyPkRpcmVjdG9yIG9mIE9wZXJhdGlvbnM8YnI+PGJyPmNlbGw6 IDYxNy0yMzAtMTQxMjxicj5mYXg6IDYxNy0yNTItMDIzODxicj5lbWFpbDogPGEgaHJlZj0ibWFp bHRvOmRvbWluaWNAYm9zdG9udmluZXlhcmQub3JnIj5kb21pbmljQGJvc3RvbnZpbmV5YXJkLm9y ZzwvYT48YnI+DQo8YnI+PGJyPg0KPC9kaXY+DQo8L2Rpdj48L2Jsb2NrcXVvdGU+PGJsb2NrcXVv dGUgdHlwZT0iY2l0ZSI+PGRpdj48c3Bhbj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXzwvc3Bhbj48YnI+PHNwYW4+VXNlcnMgbWFpbGluZyBsaXN0PC9zcGFu Pjxicj48c3Bhbj48YSBocmVmPSJtYWlsdG86VXNlcnNAb3ZpcnQub3JnIj5Vc2Vyc0BvdmlydC5v cmc8L2E+PC9zcGFuPjxicj48c3Bhbj48YSBocmVmPSJodHRwOi8vbGlzdHMub3ZpcnQub3JnL21h aWxtYW4vbGlzdGluZm8vdXNlcnMiPmh0dHA6Ly9saXN0cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0 aW5mby91c2VyczwvYT48L3NwYW4+PGJyPjwvZGl2PjwvYmxvY2txdW90ZT48L2JvZHk+PC9odG1s Pg== --Apple-Mail-69E08F1E-4E50-4DF1-856E-682ACCE9638D--
On Saturday 14 January 2012 16:04:27 Dominic Kaiser wrote:
I have recently set up an ovirt engine server and one host. The ovirt engine server was installed on a small Intell Atom quad core with 4 gigs of ram box. The ovirt engine server is running on Fedora 16 and engine was installed from rpms after I added the repo. Also I have installed one host or node if you prefer That is an AMD quad core with 8 gigs of ram and has virtualization. I have tried installing from ovirt node 2.2.1 iso but ethernet card can not be intialized even though it is detected. This is a realtek card and it shows up fine in fedora 16. The iso is still a bit buggy for me so I tried installing fedora 16 and then the vdsm rpm packages from repository. I have correctly set up a bridge on fedora 16 and by the way your instructions are wrong for bridge setup. I will be glad to send you guys a correct config for the wiki if neccessary for fedora 16. Vdsm is running and I installed host from the ovirt gui by adding new host entered ip config an.d it appeared in the ovirt web manager. What it does not do properly is install on the Ovirt web manager I get installing then it says install failed. I have tried reinstalling from the ovirt web manager to no avail. The wiki is a good start but directions are lacking I must say. Is there any more config that needs to be done on the vdsm.conf file in etc/vdsm/vdsm.conf or does it just "detect" when the Ovirt web manager calls for it? I am probably missing something on my end I am guessing. Also what log files would be helpful to look at? I will be trying this out also on a new asus server with two 8 core amd opterons and 32 gigs of ram shortly so I will let you know how that goes also. This project is great I just need to get a working host and I want to write a simpler install write up for this project that in my opinion is what it is lacking.
Let me know,
Hi Dominic, If I get you right, you have set a bridge and manually installed vdsm using RPM's. When you add a host from the web UI, it's actually trying to do what you did, but it should be a problem. So... let's try to figure out the real issue; If you SSH into your vdsm host (node), you'll find under /tmp the installation log files. Please verify there's no sensitive data there, and send to list. We'll continue based on the logs. Doron.
Ok here are the log files. It installs most packages and then hangs up on libjpeg? libjpeg is installed including dev package. This is a bare-metal node running fedora 16 with vdsm packages installed from repo. Your node .iso 2.2.1 does not initialize realtek nic cards so I can not use that. The 2.2.1 .iso sees the nic card but that is it. So I went the route of installing the full fedora 16 distro and installing vdsm packages from repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I go to the ovirt management gui and install the node it fails at this step. I can see the node in ovirt management gui just an fyi so not a problem with detection. It seems that the vdsm server will not start due to libjpeg install failure but mabey I am wrong. Let me know what you think, Dominic On Sun, Jan 15, 2012 at 4:11 AM, Doron Fediuck <dfediuck@redhat.com> wrote:
I have recently set up an ovirt engine server and one host. The ovirt engine server was installed on a small Intell Atom quad core with 4 gigs of ram box. The ovirt engine server is running on Fedora 16 and engine was installed from rpms after I added the repo. Also I have installed one host or node if you prefer That is an AMD quad core with 8 gigs of ram and has virtualization. I have tried installing from ovirt node 2.2.1 iso but ethernet card can not be intialized even though it is detected. This is a realtek card and it shows up fine in fedora 16. The iso is still a bit buggy for me so I tried installing fedora 16 and then the vdsm rpm
from repository. I have correctly set up a bridge on fedora 16 and by
On Saturday 14 January 2012 16:04:27 Dominic Kaiser wrote: packages the
way your instructions are wrong for bridge setup. I will be glad to send you guys a correct config for the wiki if neccessary for fedora 16. Vdsm is running and I installed host from the ovirt gui by adding new host entered ip config an.d it appeared in the ovirt web manager. What it does not do properly is install on the Ovirt web manager I get installing then it says install failed. I have tried reinstalling from the ovirt web manager to no avail. The wiki is a good start but directions are lacking I must say. Is there any more config that needs to be done on the vdsm.conf file in etc/vdsm/vdsm.conf or does it just "detect" when the Ovirt web manager calls for it? I am probably missing something on my end I am guessing. Also what log files would be helpful to look at? I will be trying this out also on a new asus server with two 8 core amd opterons and 32 gigs of ram shortly so I will let you know how that goes also. This project is great I just need to get a working host and I want to write a simpler install write up for this project that in my opinion is what it is lacking.
Let me know,
Hi Dominic, If I get you right, you have set a bridge and manually installed vdsm using RPM's. When you add a host from the web UI, it's actually trying to do what you did, but it should be a problem. So... let's try to figure out the real issue; If you SSH into your vdsm host (node), you'll find under /tmp the installation log files. Please verify there's no sensitive data there, and send to list. We'll continue based on the logs.
Doron.
-- Dominic Kaiser Greater Boston Vineyard Director of Operations cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote:
Ok here are the log files. It installs most packages and then hangs up on libjpeg? libjpeg is installed including dev package. This is a bare-metal node running fedora 16 with vdsm packages installed from repo. Your node .iso 2.2.1 does not initialize realtek nic cards so I can not use that. The 2.2.1 .iso sees the nic card but that is it. So I went the route of installing the full fedora 16 distro and installing vdsm packages from repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I go to the ovirt management gui and install the node it fails at this step. I can see the node in ovirt management gui just an fyi so not a problem with detection. It seems that the vdsm server will not start due to libjpeg install failure but mabey I am wrong.
Let me know what you think,
Dominic
Hi Dominic, This is where your installation fails: ParsingError: File contains parsing errors: /etc/vdsm/vdsm.conf [line 42]: ' default_bridge = engine\n' [line 93]: ' ssl = false\n' [line 191]: ' management_port = 54321\n' [line 193]: ' management_ip = 10.3.0.245\n' Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed'/> Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? Did you really add a string '\n' or is it just the way the error propmts? -- /d "Air conditioned environment - Do NOT open Windows!"
On 01/17/2012 05:46 PM, Doron Fediuck wrote:
On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote:
Ok here are the log files. It installs most packages and then hangs up on libjpeg? libjpeg is installed including dev package. This is a bare-metal node running fedora 16 with vdsm packages installed from repo. Your node .iso 2.2.1 does not initialize realtek nic cards so I can not use that. The 2.2.1 .iso sees the nic card but that is it. So I went the route of installing the full fedora 16 distro and installing vdsm packages from repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I go to the ovirt management gui and install the node it fails at this step. I can see the node in ovirt management gui just an fyi so not a problem with detection. It seems that the vdsm server will not start due to libjpeg install failure but mabey I am wrong.
Let me know what you think,
Dominic
Hi Dominic, This is where your installation fails: ParsingError: File contains parsing errors: /etc/vdsm/vdsm.conf [line 42]: ' default_bridge = engine\n' [line 93]: ' ssl = false\n' [line 191]: ' management_port = 54321\n' [line 193]: ' management_ip = 10.3.0.245\n' Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed'/>
Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? Did you really add a string '\n' or is it just the way the error propmts?
Did you edit the "vdsm.conf" file by hand? If so, do you have spaces at the beginning of some line right after the beginning of a section? Apparently you do in line 42. That breaks the Python config parser. -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
On 01/17/2012 05:46 PM, Doron Fediuck wrote:
On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote:
Ok here are the log files. It installs most packages and then hangs up on libjpeg? libjpeg is installed including dev package. This is a bare-metal node running fedora 16 with vdsm packages installed from repo. Your node .iso 2.2.1 does not initialize realtek nic cards so I can not use that. The 2.2.1 .iso sees the nic card but that is it. So I went the route of installing the full fedora 16 distro and installing vdsm packages from repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I go to the ovirt management gui and install the node it fails at this step. I can see the node in ovirt management gui just an fyi so not a problem with detection. It seems that the vdsm server will not start due to libjpeg install failure but mabey I am wrong.
Let me know what you think,
Dominic
Hi Dominic, This is where your installation fails: ParsingError: File contains parsing errors: /etc/vdsm/vdsm.conf [line 42]: ' default_bridge = engine\n' [line 93]: ' ssl = false\n' [line 191]: ' management_port = 54321\n' [line 193]: ' management_ip = 10.3.0.245\n' Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed'/>
Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? Did you really add a string '\n' or is it just the way the error propmts?
Did you edit the "vdsm.conf" file by hand? If so, do you have spaces at the beginning of some line right after the beginning of a section? Apparently you do in line 42. That breaks the Python config parser.
Thanks all, I have tried the new ovirt node 2.2.1-3 nightly build today and it finally recognized my realtek nic card. So I have moved to try to get node to install. Still a fail I might add. It adds to the ovirt gui but fails install and says the ovirt hyperviser is not a supported platform. That is kind of funny since it is fedora 16. And yes I had edited the vdsm.conf by hand was that wrong to do? Should I have used vi instead? I would like to get ovirt node running since it is working now lighter install. This is what I get: 2012-Jan-17, 12:28:59 Failed to install Host vm3.bostonvineyard.org. Step: INSTALLER; Details: Unsupported platform: oVirtNodeHypervisor. If it registers from ovirt node should it not show up in the ovirt Management gui? Or do you still have to add it as usual? So that is what I did and that is the error I recieved. Let me know what you think, Dominic On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> wrote:
On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote:
Ok here are the log files. It installs most packages and then hangs up on libjpeg? libjpeg is installed including dev package. This is a bare-metal node running fedora 16 with vdsm packages installed from repo. Your node .iso 2.2.1 does not initialize realtek nic cards so I can not use that. The 2.2.1 .iso sees the nic card but that is it. So I went the route of installing the full fedora 16 distro and installing vdsm packages from repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I go to the ovirt management gui and install the node it fails at this step. I can see the node in ovirt management gui just an fyi so not a problem with detection. It seems that the vdsm server will not start due to libjpeg install failure but mabey I am wrong.
Let me know what you think,
Dominic
Hi Dominic, This is where your installation fails: ParsingError: File contains parsing errors: /etc/vdsm/vdsm.conf [line 42]: ' default_bridge = engine\n' [line 93]: ' ssl = false\n' [line 191]: ' management_port = 54321\n' [line 193]: ' management_ip = 10.3.0.245\n' Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed'/>
Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? Did you really add a string '\n' or is it just the way the error propmts?
--
/d
"Air conditioned environment - Do NOT open Windows!"
-- Dominic Kaiser Greater Boston Vineyard Director of Operations cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
On 01/17/2012 06:39 PM, Dominic Kaiser wrote:
I have tried the new ovirt node 2.2.1-3 nightly build today and it finally recognized my realtek nic card. So I have moved to try to get node to install. Still a fail I might add. It adds to the ovirt gui but fails install and says the ovirt hyperviser is not a supported platform. That is kind of funny since it is fedora 16. And yes I had edited the vdsm.conf by hand was that wrong to do? Should I have used vi instead? I would like to get ovirt node running since it is working now lighter install. This is what I get:
No problem with hand editing the "vdsm.conf" (although that shouldn't be needed). Just make sure that you don't introduce spaces at the beginning of the lines, before the names of the parameters, as the program that reads the configuration doesn't like that.
2012-Jan-17, 12:28:59 Failed to install Host vm3.bostonvineyard.org. Step: INSTALLER; Details: Unsupported platform: oVirtNodeHypervisor.
If it registers from ovirt node should it not show up in the ovirt Management gui? Or do you still have to add it as usual? So that is what I did and that is the error I recieved.
Let me know what you think,
Dominic
On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> wrote:
On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote:
Ok here are the log files. It installs most packages and then hangs up on libjpeg? libjpeg is installed including dev package. This is a bare-metal node running fedora 16 with vdsm packages installed from repo. Your node .iso 2.2.1 does not initialize realtek nic cards so I can not use that. The 2.2.1 .iso sees the nic card but that is it. So I went the route of installing the full fedora 16 distro and installing vdsm packages from repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I go to the ovirt management gui and install the node it fails at this step. I can see the node in ovirt management gui just an fyi so not a problem with detection. It seems that the vdsm server will not start due to libjpeg install failure but mabey I am wrong.
Let me know what you think,
Dominic
Hi Dominic, This is where your installation fails: ParsingError: File contains parsing errors: /etc/vdsm/vdsm.conf [line 42]: ' default_bridge = engine\n' [line 93]: ' ssl = false\n' [line 191]: ' management_port = 54321\n' [line 193]: ' management_ip = 10.3.0.245\n' Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed'/>
Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? Did you really add a string '\n' or is it just the way the error propmts?
--
/d
"Air conditioned environment - Do NOT open Windows!"
-- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
On Tue, 2012-01-17 at 12:39 -0500, Dominic Kaiser wrote:
Thanks all,
I have tried the new ovirt node 2.2.1-3 nightly build today and it finally recognized my realtek nic card. So I have moved to try to get node to install. Still a fail I might add. It adds to the ovirt gui but fails install and says the ovirt hyperviser is not a supported platform. That is kind of funny since it is fedora 16. And yes I had edited the vdsm.conf by hand was that wrong to do? Should I have used vi instead? I would like to get ovirt node running since it is working now lighter install. This is what I get:
2012-Jan-17, 12:28:59 Failed to install Host vm3.bostonvineyard.org. Step: INSTALLER; Details: Unsupported platform: oVirtNodeHypervisor.
If it registers from ovirt node should it not show up in the ovirt Management gui? Or do you still have to add it as usual? So that is what I did and that is the error I recieved.
oVirt Node supports 2 ways of registering. 1. Set the hostname and port of the management server The Node registers itself to the engine and the admin then only has to approve it. 2. Set a password and use add host from the engine The node does no registration. The admin for engine manually adds the node as they would a regular Fedora node. As for the actual error, I've seen other problems with that build of ovirt-node that I'm working on so I haven't tried to register it yet. I'll try it though. Mike
Let me know what you think,
Dominic
On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> wrote: On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote: > Ok here are the log files. It installs most packages and then hangs up on > libjpeg? libjpeg is installed including dev package. This is a bare-metal > node running fedora 16 with vdsm packages installed from repo. Your node > .iso 2.2.1 does not initialize realtek nic cards so I can not use that. > The 2.2.1 .iso sees the nic card but that is it. So I went the route of > installing the full fedora 16 distro and installing vdsm packages from > repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I > go to the ovirt management gui and install the node it fails at this step. > I can see the node in ovirt management gui just an fyi so not a problem > with detection. It seems that the vdsm server will not start due to > libjpeg install failure but mabey I am wrong. > > Let me know what you think, > > Dominic >
Hi Dominic, This is where your installation fails: ParsingError: File contains parsing errors: /etc/vdsm/vdsm.conf [line 42]: ' default_bridge = engine\n' [line 93]: ' ssl = false\n' [line 191]: ' management_port = 54321\n' [line 193]: ' management_ip = 10.3.0.245\n' Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed'/>
Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? Did you really add a string '\n' or is it just the way the error propmts?
--
/d
"Air conditioned environment - Do NOT open Windows!"
-- Dominic Kaiser Greater Boston Vineyard Director of Operations
cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tue, 2012-01-17 at 12:51 -0500, Mike Burns wrote:
On Tue, 2012-01-17 at 12:39 -0500, Dominic Kaiser wrote:
Thanks all,
I have tried the new ovirt node 2.2.1-3 nightly build today and it finally recognized my realtek nic card. So I have moved to try to get node to install. Still a fail I might add. It adds to the ovirt gui but fails install and says the ovirt hyperviser is not a supported platform. That is kind of funny since it is fedora 16. And yes I had edited the vdsm.conf by hand was that wrong to do? Should I have used vi instead? I would like to get ovirt node running since it is working now lighter install. This is what I get:
2012-Jan-17, 12:28:59 Failed to install Host vm3.bostonvineyard.org. Step: INSTALLER; Details: Unsupported platform: oVirtNodeHypervisor.
If it registers from ovirt node should it not show up in the ovirt Management gui? Or do you still have to add it as usual? So that is what I did and that is the error I recieved.
oVirt Node supports 2 ways of registering.
1. Set the hostname and port of the management server The Node registers itself to the engine and the admin then only has to approve it.
This appears to not be working at the moment. There are 404 errors in the log. I'll file a bug for the vdsm team to look into this.
2. Set a password and use add host from the engine The node does no registration. The admin for engine manually adds the node as they would a regular Fedora node.
This is not working out of the box. I get the same error you do about it being an unsupported platform. I filed a bug [1] for this issue with a patch as well[2]. This patch can be applied directly on the engine system to get around the problem. oVirtNodeHypervisor is simply missing from the list of supported systems. [1] https://bugzilla.redhat.com/show_bug.cgi?id=782660 [2] http://gerrit.ovirt.org/#change,1117 Mike
As for the actual error, I've seen other problems with that build of ovirt-node that I'm working on so I haven't tried to register it yet. I'll try it though.
Mike
Let me know what you think,
Dominic
On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> wrote: On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote: > Ok here are the log files. It installs most packages and then hangs up on > libjpeg? libjpeg is installed including dev package. This is a bare-metal > node running fedora 16 with vdsm packages installed from repo. Your node > .iso 2.2.1 does not initialize realtek nic cards so I can not use that. > The 2.2.1 .iso sees the nic card but that is it. So I went the route of > installing the full fedora 16 distro and installing vdsm packages from > repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I > go to the ovirt management gui and install the node it fails at this step. > I can see the node in ovirt management gui just an fyi so not a problem > with detection. It seems that the vdsm server will not start due to > libjpeg install failure but mabey I am wrong. > > Let me know what you think, > > Dominic >
Hi Dominic, This is where your installation fails: ParsingError: File contains parsing errors: /etc/vdsm/vdsm.conf [line 42]: ' default_bridge = engine\n' [line 93]: ' ssl = false\n' [line 191]: ' management_port = 54321\n' [line 193]: ' management_ip = 10.3.0.245\n' Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed'/>
Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? Did you really add a string '\n' or is it just the way the error propmts?
--
/d
"Air conditioned environment - Do NOT open Windows!"
-- Dominic Kaiser Greater Boston Vineyard Director of Operations
cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tuesday 17 January 2012 22:51:39 Mike Burns wrote:
On Tue, 2012-01-17 at 12:51 -0500, Mike Burns wrote:
On Tue, 2012-01-17 at 12:39 -0500, Dominic Kaiser wrote:
Thanks all,
I have tried the new ovirt node 2.2.1-3 nightly build today and it finally recognized my realtek nic card. So I have moved to try to get node to install. Still a fail I might add. It adds to the ovirt gui but fails install and says the ovirt hyperviser is not a supported platform. That is kind of funny since it is fedora 16. And yes I had edited the vdsm.conf by hand was that wrong to do? Should I have used vi instead? I would like to get ovirt node running since it is working now lighter install. This is what I get:
2012-Jan-17, 12:28:59 Failed to install Host vm3.bostonvineyard.org. Step: INSTALLER; Details: Unsupported platform: oVirtNodeHypervisor.
If it registers from ovirt node should it not show up in the ovirt Management gui? Or do you still have to add it as usual? So that is what I did and that is the error I recieved.
oVirt Node supports 2 ways of registering.
1. Set the hostname and port of the management server The Node registers itself to the engine and the admin then only has to approve it.
This appears to not be working at the moment. There are 404 errors in the log. I'll file a bug for the vdsm team to look into this.
2. Set a password and use add host from the engine The node does no registration. The admin for engine manually adds the node as they would a regular Fedora node.
This is not working out of the box. I get the same error you do about it being an unsupported platform. I filed a bug [1] for this issue with a patch as well[2]. This patch can be applied directly on the engine system to get around the problem. oVirtNodeHypervisor is simply missing from the list of supported systems.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=782660 [2] http://gerrit.ovirt.org/#change,1117
Mike
Patch was merged. Mike, thanks and you can close the bz. Dominic, you should fetch & rebase to latest code to get Mike's fix.
As for the actual error, I've seen other problems with that build of ovirt-node that I'm working on so I haven't tried to register it yet. I'll try it though.
Mike
Let me know what you think,
Dominic
On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> wrote: On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote: > Ok here are the log files. It installs most packages and then hangs up on > libjpeg? libjpeg is installed including dev package. This is a bare-metal > node running fedora 16 with vdsm packages installed from repo. Your node > .iso 2.2.1 does not initialize realtek nic cards so I can not use that. > The 2.2.1 .iso sees the nic card but that is it. So I went the route of > installing the full fedora 16 distro and installing vdsm packages from > repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I > go to the ovirt management gui and install the node it fails at this step. > I can see the node in ovirt management gui just an fyi so not a problem > with detection. It seems that the vdsm server will not start due to > libjpeg install failure but mabey I am wrong. > > Let me know what you think, > > Dominic >
Hi Dominic, This is where your installation fails: ParsingError: File contains parsing errors: /etc/vdsm/vdsm.conf [line 42]: ' default_bridge = engine\n' [line 93]: ' ssl = false\n' [line 191]: ' management_port = 54321\n' [line 193]: ' management_ip = 10.3.0.245\n' Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed'/>
Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? Did you really add a string '\n' or is it just the way the error propmts?
--
/d
"Air conditioned environment - Do NOT open Windows!"
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users --
/d Why doesn't DOS ever say "EXCELLENT command or filename!"
Ok so I will try the new iso. For now I have intalled the stable vdsm packages instead of nightly. I was able to get vdsm to register and the node is up. Sweet Victory! I would like to use the ovirt node iso in the future though. I have begun to test with one node. Still trying to connect to ISCSI Storage though. I am trying to figure out all the requirements for ovirt. Can we use local storage for one node to test? Also I have a proper bridge setup for fedora 16 can we post to the wiki or is it one of you whom does that? Thanks, Dominic On Tue, Jan 17, 2012 at 10:51 PM, Mike Burns <mburns@redhat.com> wrote:
On Tue, 2012-01-17 at 12:51 -0500, Mike Burns wrote:
On Tue, 2012-01-17 at 12:39 -0500, Dominic Kaiser wrote:
Thanks all,
I have tried the new ovirt node 2.2.1-3 nightly build today and it finally recognized my realtek nic card. So I have moved to try to get node to install. Still a fail I might add. It adds to the ovirt gui but fails install and says the ovirt hyperviser is not a supported platform. That is kind of funny since it is fedora 16. And yes I had edited the vdsm.conf by hand was that wrong to do? Should I have used vi instead? I would like to get ovirt node running since it is working now lighter install. This is what I get:
2012-Jan-17, 12:28:59 Failed to install Host vm3.bostonvineyard.org. Step: INSTALLER; Details: Unsupported platform: oVirtNodeHypervisor.
If it registers from ovirt node should it not show up in the ovirt Management gui? Or do you still have to add it as usual? So that is what I did and that is the error I recieved.
oVirt Node supports 2 ways of registering.
1. Set the hostname and port of the management server The Node registers itself to the engine and the admin then only has to approve it.
This appears to not be working at the moment. There are 404 errors in the log. I'll file a bug for the vdsm team to look into this.
2. Set a password and use add host from the engine The node does no registration. The admin for engine manually adds
the
node as they would a regular Fedora node.
This is not working out of the box. I get the same error you do about it being an unsupported platform. I filed a bug [1] for this issue with a patch as well[2]. This patch can be applied directly on the engine system to get around the problem. oVirtNodeHypervisor is simply missing from the list of supported systems.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=782660 [2] http://gerrit.ovirt.org/#change,1117
Mike
As for the actual error, I've seen other problems with that build of ovirt-node that I'm working on so I haven't tried to register it yet. I'll try it though.
Mike
Let me know what you think,
Dominic
On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> wrote: On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote: > Ok here are the log files. It installs most packages and then hangs up on > libjpeg? libjpeg is installed including dev package. This is a bare-metal > node running fedora 16 with vdsm packages installed from repo. Your node > .iso 2.2.1 does not initialize realtek nic cards so I can not use that. > The 2.2.1 .iso sees the nic card but that is it. So I went the route of > installing the full fedora 16 distro and installing vdsm packages from > repo. I am bridged correctly and ssl=false in the vdsm.conf. Now when I > go to the ovirt management gui and install the node it fails at this step. > I can see the node in ovirt management gui just an fyi so not a problem > with detection. It seems that the vdsm server will not start due to > libjpeg install failure but mabey I am wrong. > > Let me know what you think, > > Dominic >
Hi Dominic, This is where your installation fails: ParsingError: File contains parsing errors: /etc/vdsm/vdsm.conf [line 42]: ' default_bridge = engine\n' [line 93]: ' ssl = false\n' [line 191]: ' management_port = 54321\n' [line 193]: ' management_ip = 10.3.0.245\n' Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP component='CreateConf' status='FAIL' message='Basic configuration failed'/>
Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? Did you really add a string '\n' or is it just the way the error propmts?
--
/d
"Air conditioned environment - Do NOT open Windows!"
-- Dominic Kaiser Greater Boston Vineyard Director of Operations
cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Dominic Kaiser Greater Boston Vineyard Director of Operations cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
On Wed, 2012-01-18 at 13:42 -0500, Dominic Kaiser wrote:
Ok so I will try the new iso. For now I have intalled the stable vdsm packages instead of nightly. I was able to get vdsm to register and the node is up. Sweet Victory! I would like to use the ovirt node iso in the future though. I have begun to test with one node. Still trying to connect to ISCSI Storage though. I am trying to figure out all the requirements for ovirt. Can we use local storage for one node to test?
Yes, Local storage is supported, though I'm not familiar with the setup necessary.
Also I have a proper bridge setup for fedora 16 can we post to the wiki or is it one of you whom does that?
Anyone can update the wiki. Just let me or someone else know what username and email address you want to use for your wiki account and we'll create it for you. This manual creation is to attempt to minimize spamming of the wiki. Mike
Thanks,
Dominic
On Tue, Jan 17, 2012 at 10:51 PM, Mike Burns <mburns@redhat.com> wrote: On Tue, 2012-01-17 at 12:51 -0500, Mike Burns wrote: > On Tue, 2012-01-17 at 12:39 -0500, Dominic Kaiser wrote: > > Thanks all, > > > > > > I have tried the new ovirt node 2.2.1-3 nightly build today and it > > finally recognized my realtek nic card. So I have moved to try to get > > node to install. Still a fail I might add. It adds to the ovirt gui > > but fails install and says the ovirt hyperviser is not a supported > > platform. That is kind of funny since it is fedora 16. And yes I had > > edited the vdsm.conf by hand was that wrong to do? Should I have used > > vi instead? I would like to get ovirt node running since it is > > working now lighter install. This is what I get: > > > > > > 2012-Jan-17, 12:28:59 > > Failed to install Host > > vm3.bostonvineyard.org. > > Step: INSTALLER; > > Details: Unsupported > > platform: > > oVirtNodeHypervisor. > > > > > > > > If it registers from ovirt node should it not show up in the ovirt > > Management gui? Or do you still have to add it as usual? So that is > > what I did and that is the error I recieved. > > oVirt Node supports 2 ways of registering. > > 1. Set the hostname and port of the management server > The Node registers itself to the engine and the admin then only has to > approve it.
This appears to not be working at the moment. There are 404 errors in the log. I'll file a bug for the vdsm team to look into this.
> > 2. Set a password and use add host from the engine > The node does no registration. The admin for engine manually adds the > node as they would a regular Fedora node.
This is not working out of the box. I get the same error you do about it being an unsupported platform. I filed a bug [1] for this issue with a patch as well[2]. This patch can be applied directly on the engine system to get around the problem. oVirtNodeHypervisor is simply missing from the list of supported systems.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=782660 [2] http://gerrit.ovirt.org/#change,1117
Mike > > > As for the actual error, I've seen other problems with that build of > ovirt-node that I'm working on so I haven't tried to register it yet. > I'll try it though. > > Mike > > > > > > > Let me know what you think, > > > > > > Dominic > > > > On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> > > wrote: > > On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote: > > > Ok here are the log files. It installs most packages and > > then hangs up on > > > libjpeg? libjpeg is installed including dev package. This > > is a bare-metal > > > node running fedora 16 with vdsm packages installed from > > repo. Your node > > > .iso 2.2.1 does not initialize realtek nic cards so I can > > not use that. > > > The 2.2.1 .iso sees the nic card but that is it. So I went > > the route of > > > installing the full fedora 16 distro and installing vdsm > > packages from > > > repo. I am bridged correctly and ssl=false in the > > vdsm.conf. Now when I > > > go to the ovirt management gui and install the node it fails > > at this step. > > > I can see the node in ovirt management gui just an fyi so > > not a problem > > > with detection. It seems that the vdsm server will not > > start due to > > > libjpeg install failure but mabey I am wrong. > > > > > > Let me know what you think, > > > > > > Dominic > > > > > > > Hi Dominic, > > This is where your installation fails: > > ParsingError: File contains parsing > > errors: /etc/vdsm/vdsm.conf > > [line 42]: ' default_bridge = engine\n' > > [line 93]: ' ssl = false\n' > > [line 191]: ' management_port = 54321\n' > > [line 193]: ' management_ip = 10.3.0.245\n' > > Sun, 15 Jan 2012 08:01:27 DEBUG <BSTRAP > > component='CreateConf' status='FAIL' message='Basic > > configuration failed'/> > > > > Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? > > Did you really add a string '\n' or is it just the way the > > error propmts? > > > > -- > > > > /d > > > > "Air conditioned environment - Do NOT open Windows!" > > > > > > > > > > > > -- > > Dominic Kaiser > > Greater Boston Vineyard > > Director of Operations > > > > cell: 617-230-1412 > > fax: 617-252-0238 > > email: dominic@bostonvineyard.org > > > > > > > > _______________________________________________ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
-- Dominic Kaiser Greater Boston Vineyard Director of Operations
cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 01/18/2012 08:54 PM, Mike Burns wrote:
On Wed, 2012-01-18 at 13:42 -0500, Dominic Kaiser wrote:
Ok so I will try the new iso. For now I have intalled the stable vdsm packages instead of nightly. I was able to get vdsm to register and the node is up. Sweet Victory! I would like to use the ovirt node iso in the future though. I have begun to test with one node. Still trying to connect to ISCSI Storage though. I am trying to figure out all the requirements for ovirt. Can we use local storage for one node to test?
Yes, Local storage is supported, though I'm not familiar with the setup necessary.
long story: - add data center of local storage type - add cluster to that data center - add host to that cluster - add storage domain of type local using that host short story: - move any host to maintenance and click "configure local storage" Einav - is 'configure local storage' wizard already implemented in the web admin? caveat: need to check the default assumed path for ovirt node (which cannot be changed for ovirt node, only for 'normal' nodes) has been fixed for ovirt and is configured in the node by default with correct permissions for vdsm.
Also I have a proper bridge setup for fedora 16 can we post to the wiki or is it one of you whom does that?
Anyone can update the wiki. Just let me or someone else know what username and email address you want to use for your wiki account and we'll create it for you. This manual creation is to attempt to minimize spamming of the wiki.
Mike
Thanks,
Dominic
On Tue, Jan 17, 2012 at 10:51 PM, Mike Burns<mburns@redhat.com> wrote: On Tue, 2012-01-17 at 12:51 -0500, Mike Burns wrote: > On Tue, 2012-01-17 at 12:39 -0500, Dominic Kaiser wrote: > > Thanks all, > > > > > > I have tried the new ovirt node 2.2.1-3 nightly build today and it > > finally recognized my realtek nic card. So I have moved to try to get > > node to install. Still a fail I might add. It adds to the ovirt gui > > but fails install and says the ovirt hyperviser is not a supported > > platform. That is kind of funny since it is fedora 16. And yes I had > > edited the vdsm.conf by hand was that wrong to do? Should I have used > > vi instead? I would like to get ovirt node running since it is > > working now lighter install. This is what I get: > > > > > > 2012-Jan-17, 12:28:59 > > Failed to install Host > > vm3.bostonvineyard.org. > > Step: INSTALLER; > > Details: Unsupported > > platform: > > oVirtNodeHypervisor. > > > > > > > > If it registers from ovirt node should it not show up in the ovirt > > Management gui? Or do you still have to add it as usual? So that is > > what I did and that is the error I recieved. > > oVirt Node supports 2 ways of registering. > > 1. Set the hostname and port of the management server > The Node registers itself to the engine and the admin then only has to > approve it.
This appears to not be working at the moment. There are 404 errors in the log. I'll file a bug for the vdsm team to look into this.
> > 2. Set a password and use add host from the engine > The node does no registration. The admin for engine manually adds the > node as they would a regular Fedora node.
This is not working out of the box. I get the same error you do about it being an unsupported platform. I filed a bug [1] for this issue with a patch as well[2]. This patch can be applied directly on the engine system to get around the problem. oVirtNodeHypervisor is simply missing from the list of supported systems.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=782660 [2] http://gerrit.ovirt.org/#change,1117
Mike > > > As for the actual error, I've seen other problems with that build of > ovirt-node that I'm working on so I haven't tried to register it yet. > I'll try it though. > > Mike > > > > > > > Let me know what you think, > > > > > > Dominic > > > > On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> > > wrote: > > On Tuesday 17 January 2012 11:31:43 Dominic Kaiser wrote: > > > Ok here are the log files. It installs most packages and > > then hangs up on > > > libjpeg? libjpeg is installed including dev package. This > > is a bare-metal > > > node running fedora 16 with vdsm packages installed from > > repo. Your node > > > .iso 2.2.1 does not initialize realtek nic cards so I can > > not use that. > > > The 2.2.1 .iso sees the nic card but that is it. So I went > > the route of > > > installing the full fedora 16 distro and installing vdsm > > packages from > > > repo. I am bridged correctly and ssl=false in the > > vdsm.conf. Now when I > > > go to the ovirt management gui and install the node it fails > > at this step. > > > I can see the node in ovirt management gui just an fyi so > > not a problem > > > with detection. It seems that the vdsm server will not > > start due to > > > libjpeg install failure but mabey I am wrong. > > > > > > Let me know what you think, > > > > > > Dominic > > > > > > > Hi Dominic, > > This is where your installation fails: > > ParsingError: File contains parsing > > errors: /etc/vdsm/vdsm.conf > > [line 42]: ' default_bridge = engine\n' > > [line 93]: ' ssl = false\n' > > [line 191]: ' management_port = 54321\n' > > [line 193]: ' management_ip = 10.3.0.245\n' > > Sun, 15 Jan 2012 08:01:27 DEBUG<BSTRAP > > component='CreateConf' status='FAIL' message='Basic > > configuration failed'/> > > > > Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? > > Did you really add a string '\n' or is it just the way the > > error propmts? > > > > -- > > > > /d > > > > "Air conditioned environment - Do NOT open Windows!" > > > > > > > > > > > > -- > > Dominic Kaiser > > Greater Boston Vineyard > > Director of Operations > > > > cell: 617-230-1412 > > fax: 617-252-0238 > > email: dominic@bostonvineyard.org > > > > > > > > _______________________________________________ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
-- Dominic Kaiser Greater Boston Vineyard Director of Operations
cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
----- Original Message ----- From: "Itamar Heim" <iheim@redhat.com> Sent: Wednesday, January 18, 2012 9:53:17 PM
On 01/18/2012 08:54 PM, Mike Burns wrote:
On Wed, 2012-01-18 at 13:42 -0500, Dominic Kaiser wrote:
Ok so I will try the new iso. For now I have intalled the stable vdsm packages instead of nightly. I was able to get vdsm to register and the node is up. Sweet Victory! I would like to use the ovirt node iso in the future though. I have begun to test with one node. Still trying to connect to ISCSI Storage though. I am trying to figure out all the requirements for ovirt. Can we use local storage for one node to test?
Yes, Local storage is supported, though I'm not familiar with the setup necessary.
long story: - add data center of local storage type - add cluster to that data center - add host to that cluster - add storage domain of type local using that host
short story: - move any host to maintenance and click "configure local storage"
Einav - is 'configure local storage' wizard already implemented in the web admin?
Not yet (in progress). "long story" can be used instead for now.
caveat: need to check the default assumed path for ovirt node (which cannot be changed for ovirt node, only for 'normal' nodes) has been fixed for ovirt and is configured in the node by default with correct permissions for vdsm.
Also I have a proper bridge setup for fedora 16 can we post to the wiki or is it one of you whom does that?
Anyone can update the wiki. Just let me or someone else know what username and email address you want to use for your wiki account and we'll create it for you. This manual creation is to attempt to minimize spamming of the wiki.
Mike
Thanks,
Dominic
On Tue, Jan 17, 2012 at 10:51 PM, Mike Burns<mburns@redhat.com> wrote: On Tue, 2012-01-17 at 12:51 -0500, Mike Burns wrote: > On Tue, 2012-01-17 at 12:39 -0500, Dominic Kaiser > wrote: > > Thanks all, > > > > > > I have tried the new ovirt node 2.2.1-3 nightly > > build today and it > > finally recognized my realtek nic card. So I have > > moved to try to get > > node to install. Still a fail I might add. It > > adds to the ovirt gui > > but fails install and says the ovirt hyperviser is > > not a supported > > platform. That is kind of funny since it is fedora > > 16. And yes I had > > edited the vdsm.conf by hand was that wrong to do? > > Should I have used > > vi instead? I would like to get ovirt node running > > since it is > > working now lighter install. This is what I get: > > > > > > 2012-Jan-17, 12:28:59 > > Failed to install Host > > vm3.bostonvineyard.org. > > Step: INSTALLER; > > Details: Unsupported > > platform: > > oVirtNodeHypervisor. > > > > > > > > If it registers from ovirt node should it not show > > up in the ovirt > > Management gui? Or do you still have to add it as > > usual? So that is > > what I did and that is the error I recieved. > > oVirt Node supports 2 ways of registering. > > 1. Set the hostname and port of the management server > The Node registers itself to the engine and the > admin then only has to > approve it.
This appears to not be working at the moment. There are 404 errors in the log. I'll file a bug for the vdsm team to look into this.
> > 2. Set a password and use add host from the engine > The node does no registration. The admin for > engine manually adds the > node as they would a regular Fedora node.
This is not working out of the box. I get the same error you do about it being an unsupported platform. I filed a bug [1] for this issue with a patch as well[2]. This patch can be applied directly on the engine system to get around the problem. oVirtNodeHypervisor is simply missing from the list of supported systems.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=782660 [2] http://gerrit.ovirt.org/#change,1117
Mike > > > As for the actual error, I've seen other problems with > that build of > ovirt-node that I'm working on so I haven't tried to register it yet. > I'll try it though. > > Mike > > > > > > > Let me know what you think, > > > > > > Dominic > > > > On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> > > wrote: > > On Tuesday 17 January 2012 11:31:43 Dominic > > Kaiser wrote: > > > Ok here are the log files. It installs > > > most packages and > > then hangs up on > > > libjpeg? libjpeg is installed including > > > dev package. This > > is a bare-metal > > > node running fedora 16 with vdsm > > > packages installed from > > repo. Your node > > > .iso 2.2.1 does not initialize realtek > > > nic cards so I can > > not use that. > > > The 2.2.1 .iso sees the nic card but > > > that is it. So I went > > the route of > > > installing the full fedora 16 distro and installing vdsm > > packages from > > > repo. I am bridged correctly and > > > ssl=false in the > > vdsm.conf. Now when I > > > go to the ovirt management gui and > > > install the node it fails > > at this step. > > > I can see the node in ovirt management > > > gui just an fyi so > > not a problem > > > with detection. It seems that the vdsm > > > server will not > > start due to > > > libjpeg install failure but mabey I am > > > wrong. > > > > > > Let me know what you think, > > > > > > Dominic > > > > > > > Hi Dominic, > > This is where your installation fails: > > ParsingError: File contains parsing > > errors: /etc/vdsm/vdsm.conf > > [line 42]: ' default_bridge = > > engine\n' > > [line 93]: ' ssl = false\n' > > [line 191]: ' management_port = > > 54321\n' > > [line 193]: ' management_ip = > > 10.3.0.245\n' > > Sun, 15 Jan 2012 08:01:27 DEBUG<BSTRAP > > component='CreateConf' status='FAIL' message='Basic > > configuration failed'/> > > > > Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? > > Did you really add a string '\n' or is it > > just the way the > > error propmts? > > > > -- > > > > /d > > > > "Air conditioned environment - Do NOT open Windows!" > > > > > > > > > > > > -- > > Dominic Kaiser > > Greater Boston Vineyard > > Director of Operations > > > > cell: 617-230-1412 > > fax: 617-252-0238 > > email: dominic@bostonvineyard.org > > > > > > > > _______________________________________________ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
-- Dominic Kaiser Greater Boston Vineyard Director of Operations
cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Got a local storage node added. Now my data center is ready. Virtual machine is added can remote to it via spice in user portal but cdrom does not detect error 0003. When I put in cdrom or usb it detects that something is there because the gui change disk is highlighted. Is the cdrom a virtio device and that is why? Also is the a way to import existing .img I have created before with virtmanager? Let me know and thanks for the help, Dominic On Wed, Jan 18, 2012 at 2:59 PM, Einav Cohen <ecohen@redhat.com> wrote:
----- Original Message ----- From: "Itamar Heim" <iheim@redhat.com> Sent: Wednesday, January 18, 2012 9:53:17 PM
On 01/18/2012 08:54 PM, Mike Burns wrote:
On Wed, 2012-01-18 at 13:42 -0500, Dominic Kaiser wrote:
Ok so I will try the new iso. For now I have intalled the stable vdsm packages instead of nightly. I was able to get vdsm to register and the node is up. Sweet Victory! I would like to use the ovirt node iso in the future though. I have begun to test with one node. Still trying to connect to ISCSI Storage though. I am trying to figure out all the requirements for ovirt. Can we use local storage for one node to test?
Yes, Local storage is supported, though I'm not familiar with the setup necessary.
long story: - add data center of local storage type - add cluster to that data center - add host to that cluster - add storage domain of type local using that host
short story: - move any host to maintenance and click "configure local storage"
Einav - is 'configure local storage' wizard already implemented in the web admin?
Not yet (in progress). "long story" can be used instead for now.
caveat: need to check the default assumed path for ovirt node (which cannot be changed for ovirt node, only for 'normal' nodes) has been fixed for ovirt and is configured in the node by default with correct permissions for vdsm.
Also I have a proper bridge setup for fedora 16 can we post to the wiki or is it one of you whom does that?
Anyone can update the wiki. Just let me or someone else know what username and email address you want to use for your wiki account and we'll create it for you. This manual creation is to attempt to minimize spamming of the wiki.
Mike
Thanks,
Dominic
On Tue, Jan 17, 2012 at 10:51 PM, Mike Burns<mburns@redhat.com> wrote: On Tue, 2012-01-17 at 12:51 -0500, Mike Burns wrote: > On Tue, 2012-01-17 at 12:39 -0500, Dominic Kaiser > wrote: > > Thanks all, > > > > > > I have tried the new ovirt node 2.2.1-3 nightly > > build today and it > > finally recognized my realtek nic card. So I have > > moved to try to get > > node to install. Still a fail I might add. It > > adds to the ovirt gui > > but fails install and says the ovirt hyperviser is > > not a supported > > platform. That is kind of funny since it is fedora > > 16. And yes I had > > edited the vdsm.conf by hand was that wrong to do? > > Should I have used > > vi instead? I would like to get ovirt node running > > since it is > > working now lighter install. This is what I get: > > > > > > 2012-Jan-17, 12:28:59 > > Failed to install Host > > vm3.bostonvineyard.org. > > Step: INSTALLER; > > Details: Unsupported > > platform: > > oVirtNodeHypervisor. > > > > > > > > If it registers from ovirt node should it not show > > up in the ovirt > > Management gui? Or do you still have to add it as > > usual? So that is > > what I did and that is the error I recieved. > > oVirt Node supports 2 ways of registering. > > 1. Set the hostname and port of the management server > The Node registers itself to the engine and the > admin then only has to > approve it.
This appears to not be working at the moment. There are 404 errors in the log. I'll file a bug for the vdsm team to look into this.
> > 2. Set a password and use add host from the engine > The node does no registration. The admin for > engine manually adds the > node as they would a regular Fedora node.
This is not working out of the box. I get the same error you do about it being an unsupported platform. I filed a bug [1] for this issue with a patch as well[2]. This patch can be applied directly on the engine system to get around the problem. oVirtNodeHypervisor is simply missing from the list of supported systems.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=782660 [2] http://gerrit.ovirt.org/#change,1117
Mike > > > As for the actual error, I've seen other problems with > that build of > ovirt-node that I'm working on so I haven't tried to register it yet. > I'll try it though. > > Mike > > > > > > > Let me know what you think, > > > > > > Dominic > > > > On Tue, Jan 17, 2012 at 11:46 AM, Doron Fediuck <dfediuck@redhat.com> > > wrote: > > On Tuesday 17 January 2012 11:31:43 Dominic > > Kaiser wrote: > > > Ok here are the log files. It installs > > > most packages and > > then hangs up on > > > libjpeg? libjpeg is installed including > > > dev package. This > > is a bare-metal > > > node running fedora 16 with vdsm > > > packages installed from > > repo. Your node > > > .iso 2.2.1 does not initialize realtek > > > nic cards so I can > > not use that. > > > The 2.2.1 .iso sees the nic card but > > > that is it. So I went > > the route of > > > installing the full fedora 16 distro and installing vdsm > > packages from > > > repo. I am bridged correctly and > > > ssl=false in the > > vdsm.conf. Now when I > > > go to the ovirt management gui and > > > install the node it fails > > at this step. > > > I can see the node in ovirt management > > > gui just an fyi so > > not a problem > > > with detection. It seems that the vdsm > > > server will not > > start due to > > > libjpeg install failure but mabey I am > > > wrong. > > > > > > Let me know what you think, > > > > > > Dominic > > > > > > > Hi Dominic, > > This is where your installation fails: > > ParsingError: File contains parsing > > errors: /etc/vdsm/vdsm.conf > > [line 42]: ' default_bridge = > > engine\n' > > [line 93]: ' ssl = false\n' > > [line 191]: ' management_port = > > 54321\n' > > [line 193]: ' management_ip = > > 10.3.0.245\n' > > Sun, 15 Jan 2012 08:01:27 DEBUG<BSTRAP > > component='CreateConf' status='FAIL' message='Basic > > configuration failed'/> > > > > Now I'm wondering how did you edit /etc/vdsm/vdsm.conf? > > Did you really add a string '\n' or is it > > just the way the > > error propmts? > > > > -- > > > > /d > > > > "Air conditioned environment - Do NOT open Windows!" > > > > > > > > > > > > -- > > Dominic Kaiser > > Greater Boston Vineyard > > Director of Operations > > > > cell: 617-230-1412 > > fax: 617-252-0238 > > email: dominic@bostonvineyard.org > > > > > > > > _______________________________________________ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
-- Dominic Kaiser Greater Boston Vineyard Director of Operations
cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Dominic Kaiser Greater Boston Vineyard Director of Operations cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org
On 01/19/2012 08:57 PM, Dominic Kaiser wrote:
Got a local storage node added. Now my data center is ready. Virtual machine is added can remote to it via spice in user portal but cdrom does not detect error 0003. When I put in cdrom or usb it detects that something is there because the gui change disk is highlighted. Is the cdrom a virtio device and that is why?
to mount an iso disk, you need to place it in the NFS iso domain (you can attach same iso domain to multiple data centers). iirc, the ovirt setup allows you to create an NFS ISO domain on the engine itself, but you will still need to attach it to relevant data centers. you can use the iso uploader utility to make sure you upload it correctly wrt permissions, folder, etc.
Also is the a way to import existing .img I have created before with virtmanager?
there is virt-v2v (mbooth) and image uploader (kroberts). I think both are "close", but not sure they are up to this yet.
Let me know and thanks for the help,
participants (8)
-
Dominic Kaiser -
Doron Fediuck -
Einav Cohen -
Haim Ateya -
Itamar Heim -
Juan Hernandez -
Juan Hernandez -
Mike Burns