[Users] EL 6.3+ nodes and 3.1 compatibility?
With ovirt 3.1 EL 6.3 nodes will only work with a data center set to 3.0 compatibility mode. Is there any reason(s) why EL 6.3+ nodes would not be allowed in a 3.1 compatibility level cluster? This assumes non use of gluster since adding vdsm-gluster to an EL 6 node requires some work package update/version wise (not impossible). - DHC ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] EL 6.3+ nodes and 3.1 compatibility?
On Aug 10, 2012, at 08:02 , Dead Horse wrote: With ovirt 3.1 EL 6.3 nodes will only work with a data center set to 3.0 compatibility mode. Is there any reason(s) why EL 6.3+ nodes would not be allowed in a 3.1 compatibility level cluster? Why would they only work in 3.0 compatibility? 3.1 nodes work in 3.1 cluster level because, well, they are the same version. Or I didn't get the question and please elaborate:) This assumes non use of gluster since adding vdsm-gluster to an EL 6 node requires some work package update/version wise (not impossible). - DHC ___ 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] [oVirt 3.1] Start VM
Hi, I installed oVirt 3.1 under CentOS 6.3 (from dre repos) and when I want to start a VM the following error is displayed: VM TestVM is down. Exit message: internal error Process exited while reading console log output: Supported machines are: pc RHEL 6.3.0 PC (alias of rhel6.3.0) rhel6.3.0 RHEL 6.3.0 PC (default) rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC rhel5.4.4 RHEL 5.4.4 PC rhel5.4.0 RHEL 5.4.0 PC . What could it be ? Regards. -- AGD ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt 3.1 and live snapshots
I am afraid you should upgrade qemu manually to 1.1 at least. On 2012-8-10 17:41, Winfried de Heiden wrote: Hi all, As mentioned in the oVirt 3.1 release notes: Live snapshotting of virtual machines running on virtualization hosts with QEMU 1.1 or higher is now supported. What about Fedora 17? The Fedora version is still at 1.01: rpm -qi qemu-system-x86 Name: qemu-system-x86 Epoch : 2 Version : 1.0.1 Release : 1.fc17 Architecture: x86_64 Install Date: vr 10 aug 2012 11:33:59 CEST Group : Development/Tools Size: 13594005 License : GPLv2+ and LGPLv2+ and BSD Signature : RSA/SHA256, ma 30 jul 2012 20:05:08 CEST, Key ID 50e94c991aca3465 Source RPM : qemu-1.0.1-1.fc17.src.rpm Build Date : ma 30 jul 2012 03:34:33 CEST Build Host : x86-01.phx2.fedoraproject.org Relocations : (not relocatable) Packager: Fedora Project Vendor : Fedora Project URL : http://www.qemu.org/ Summary : QEMU system emulator for x86 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- --- Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shum...@cn.ibm.com or shum...@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification
Ok, i reinstalled the host to try to reproduce the problem. I blocked again the 8443 on ovirt manager machine. Configured the ovirt engine options on the host and gave me the error that couldn't download the certificate. I run virsh capabilities and worked ok. Then i rebooted the host and now when i run virsh capabilities it gives me segfault. On dmesg i get this message: virsh -r capabilities runs ok. -Original Message- From: Ricardo Esteves ricardo.m.este...@gmail.com To: Dan Kenigsberg dan...@redhat.com Cc: Justin Clift jcl...@redhat.com, Itamar Heim ih...@redhat.com, users@ovirt.org Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification Date: Thu, 09 Aug 2012 17:31:30 +0100 Now it's difficult to reproduce the problem, unless i install the host again. The problem seemed to be, when i configured the ovirt engine options on the host it failed to download the certificate because port 8443 was blocked on ovirt engine machine. virsh -r capabilites worked ok at that time but virsh capabilites crashed with segfault -Original Message- From: Dan Kenigsberg dan...@redhat.com To: Ricardo Esteves ricardo.m.este...@gmail.com, Justin Clift jcl...@redhat.com Cc: Itamar Heim ih...@redhat.com, users@ovirt.org Subject: Re: [Users] oVIrt 3.1 - Xeon E5530 - Wrong cpu identification Date: Thu, 9 Aug 2012 19:00:42 +0300 On Thu, Aug 09, 2012 at 02:17:44PM +0100, Ricardo Esteves wrote: Ok, i fixed the ssl problem, my ovirt manager machine iptables was blocking the 8443 port. Neither issue is a good-enough reason for virsh to segfault. Could you provide more information so that some can solve that bug? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] EL 6.3+ nodes and 3.1 compatibility?
On 08/10/2012 09:16 AM, Michal Skrivanek wrote: On Aug 10, 2012, at 08:02 , Dead Horse wrote: With ovirt 3.1 EL 6.3 nodes will only work with a data center set to 3.0 compatibility mode. Is there any reason(s) why EL 6.3+ nodes would not be allowed in a 3.1 compatibility level cluster? Why would they only work in 3.0 compatibility? 3.1 nodes work in 3.1 cluster level because, well, they are the same version. Or I didn't get the question and please elaborate:) which version of VDSM do you have on these nodes? what does 'vdsClient -s 0 getVdsCaps' return on them? This assumes non use of gluster since adding vdsm-gluster to an EL 6 node requires some work package update/version wise (not impossible). - DHC ___ 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
Re: [Users] ovirt 3.1 and live snapshots
- Original Message - From: Shu Ming shum...@linux.vnet.ibm.com To: Winfried de Heiden w...@dds.nl Cc: users@ovirt.org Sent: Friday, August 10, 2012 6:02:18 AM Subject: Re: [Users] ovirt 3.1 and live snapshots I am afraid you should upgrade qemu manually to 1.1 at least. Use the virt-preview repository here http://fedoraproject.org/wiki/Virtualization_Preview_Repository On 2012-8-10 17:41, Winfried de Heiden wrote: Hi all, As mentioned in the oVirt 3.1 release notes: Live snapshotting of virtual machines running on virtualization hosts with QEMU 1.1 or higher is now supported. What about Fedora 17? The Fedora version is still at 1.01: rpm -qi qemu-system-x86 Name: qemu-system-x86 Epoch : 2 Version : 1.0.1 Release : 1.fc17 Architecture: x86_64 Install Date: vr 10 aug 2012 11:33:59 CEST Group : Development/Tools Size: 13594005 License : GPLv2+ and LGPLv2+ and BSD Signature : RSA/SHA256, ma 30 jul 2012 20:05:08 CEST, Key ID 50e94c991aca3465 Source RPM : qemu-1.0.1-1.fc17.src.rpm Build Date : ma 30 jul 2012 03:34:33 CEST Build Host : x86-01.phx2.fedoraproject.org Relocations : (not relocatable) Packager: Fedora Project Vendor : Fedora Project URL : http://www.qemu.org/ Summary : QEMU system emulator for x86 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- --- Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shum...@cn.ibm.com or shum...@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC ___ 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
Re: [Users] [oVirt 3.1] Start VM
On 08/10/2012 12:37 PM, Andres Gonzalez wrote: Hi, I installed oVirt 3.1 under CentOS 6.3 (from dre repos) and when I want to start a VM the following error is displayed: VM TestVM is down. Exit message: internal error Process exited while reading console log output: Supported machines are: pc RHEL 6.3.0 PC (alias of rhel6.3.0) rhel6.3.0 RHEL 6.3.0 PC (default) rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC rhel5.4.4 RHEL 5.4.4 PC rhel5.4.0 RHEL 5.4.0 PC . What could it be ? Regards. the .el6 emulated machine is different. the guidelines used to include something like this? psql -U postgres engine -c update vdc_options set option_value='rhel6.2.0' where option_name LIKE 'EmulatedMachine'; ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] EL 6.3+ nodes and 3.1 compatibility?
On 08/10/2012 02:02 AM, Dead Horse wrote: With ovirt 3.1 EL 6.3 nodes will only work with a data center set to 3.0 compatibility mode. Is there any reason(s) why EL 6.3+ nodes would not be allowed in a 3.1 compatibility level cluster? This assumes non use of gluster since adding vdsm-gluster to an EL 6 node requires some work package update/version wise (not impossible). - DHC ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users What repo are you using? What build number? I have used both gluster and 3.1 compatibily nodes on top of CentOS 6.3. http://www.middleswarth.net/content/installing-ovirt-31-and-glusterfs-using-either-nfs-or-posix-native-file-system -- Thanks Robert Middleswarth @rmiddle (twitter/IRC) ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] EL 6.3+ nodes and 3.1 compatibility?
When I try adding an EL 6.3 based node to an ovirt 3.1 cluster, ovirt
complains that the host must be run in 3.0 compatibility mode and then
bombs out.
The version of VDSM on the node is:
vdsm-4.9-113.1.el6.x86_64
vdsm-cli-4.9-113.1.el6.x86_64
Other misc versions:
kernel-2.6.32-279.2.1.el6.x86_
64
libvirt-0.9.10-21.el6_3.3.x86_64
libvirt-python-0.9.10-21.el6_3.3.x86_64
qemu-img-0.12.1.2-2.295.el6_3.1.x86_64
qemu-kvm-0.12.1.2-2.295.el6_3.1.x86_64
gpxe-roms-qemu-0.9.7-6.9.el6.noarch
qemu-kvm-tools-0.12.1.2-2.295.el6_3.1.x86_64
spice-server-0.10.1-10.el6.x86_64
'vdsClient -s 0 getVdsCaps' is does not seem to work since I have SSL
disabled for vdsm so here is the output from the vdsm.log:
Thread-13::DEBUG::2012-08-10 00:46:26,202::clientIF::59::vds::(wrapper)
return getVdsCapabilities with {'status': {'message': 'Done', 'code': 0},
'info': {'HBAInventory': {'iSCSI': [{'InitiatorName':
'iqn.1994-05.com.redhat:decf7eb6ff3f'}], 'FC': []}, 'packages2': {'kernel':
{'release': '279.2.1.el6.x86_64', 'buildtime': 1342732135.0, 'version':
'2.6.32'}, 'spice-server': {'release': '10.el6', 'buildtime': '1340343617',
'version': '0.10.1'}, 'vdsm': {'release': '113.1.el6', 'buildtime':
'1344576418', 'version': '4.9'}, 'qemu-kvm': {'release': '2.295.el6_3.1',
'buildtime': '1343643134', 'version': '0.12.1.2'}, 'libvirt': {'release':
'21.el6_3.3', 'buildtime': '1342618149', 'version': '0.9.10'}, 'qemu-img':
{'release': '2.295.el6_3.1', 'buildtime': '1343643134', 'version':
'0.12.1.2'}}, 'cpuModel': 'Intel(R) Xeon(R) CPU E5540 @
2.53GHz', 'hooks': {}, 'vmTypes': ['kvm'], 'supportedProtocols': ['2.2',
'2.3'], 'networks': {'ovirtmgmt': {'addr': '192.168.1.22', 'cfg':
{'IPV6INIT': 'no', 'IPADDR': '192.168.1.22', 'DELAY': '0', 'PREFIX': '24',
'BOOTPROTO': 'none', 'STP': 'off', 'DEVICE': 'ovirtmgmt', 'TYPE': 'Bridge',
'ONBOOT': 'yes'}, 'ports': ['eth0'], 'netmask': '255.255.255.0', 'stp':
'off', 'gateway': '192.168.1.1'}, 'virbr0': {'addr': '192.168.122.1',
'cfg': {}, 'ports': ['virbr0-nic'], 'netmask': '255.255.255.0', 'stp':
'on', 'gateway': '0.0.0.0'}}, 'uuid':
'FF28----00212883B51A_00:21:28:83:B5:16', 'nics': {'eth3':
{'hwaddr': '00:21:28:83:B5:19', 'netmask': '', 'speed': 0, 'addr': ''},
'eth2': {'hwaddr': '00:21:28:83:B5:18', 'netmask': '', 'speed': 0, 'addr':
''}, 'eth1': {'hwaddr': '00:21:28:83:B5:17', 'netmask': '', 'speed': 0,
'addr': ''}, 'eth0': {'hwaddr': '00:21:28:83:B5:16', 'netmask': '',
'speed': 1000, 'addr': ''}}, 'software_revision': '113.1', 'management_ip':
'', 'clusterLevels': ['3.0'], 'cpuFlags':
u'fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,nx,rdtscp,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,xtopology,nonstop_tsc,aperfmperf,pni,dtes64,monitor,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,dca,sse4_1,sse4_2,popcnt,lahf_lm,ida,dts,tpr_shadow,vnmi,flexpriority,ept,vpid,model_486,model_pentium,model_pentium2,model_pentium3,model_pentiumpro,model_qemu32,model_cpu64-rhel5,model_cpu64-rhel6,model_kvm32,model_coreduo,model_kvm64,model_core2duo,model_n270,model_Conroe,model_Penryn,model_Nehalem,model_Opteron_G1',
'ISCSIInitiatorName': 'iqn.1994-05.com.redhat:decf7eb6ff3f', 'memSize':
'36140', 'reservedMem': '256', 'bondings': {'bond4': {'hwaddr':
'00:00:00:00:00:00', 'cfg': {}, 'netmask': '', 'addr': '', 'slaves': []},
'bond0': {'hwaddr': '00:00:00:00:00:00', 'cfg': {}, 'netmask': '', 'addr':
'', 'slaves': []}, 'bond1': {'hwaddr': '00:00:00:00:00:00', 'cfg': {},
'netmask': '', 'addr': '', 'slaves': []}, 'bond2': {'hwaddr':
'00:00:00:00:00:00', 'cfg': {}, 'netmask': '', 'addr': '', 'slaves': []},
'bond3': {'hwaddr': '00:00:00:00:00:00', 'cfg': {}, 'netmask': '', 'addr':
'', 'slaves': []}}, 'software_version': '4.9', 'cpuSpeed': '1600.000',
'cpuSockets': '2', 'vlans': {}, 'cpuCores': '8', 'kvmEnabled': 'true',
'guestOverhead': '65', 'supportedRHEVMs': ['3.0'], 'version_name': 'Snow
Man', 'emulatedMachines': [u'rhel6.3.0', u'pc', u'rhel6.2.0', u'rhel6.1.0',
u'rhel6.0.0', u'rhel5.5.0', u'rhel5.4.4', u'rhel5.4.0'], 'operatingSystem':
{'release': '1', 'version': '6.3', 'name': 'RHEL'}}}
Thread-14::DEBUG::2012-08-10 00:46:26,335::clientIF::54::vds::(wrapper)
[192.168.1.20]::call getVdsCapabilities with () {}
Thread-14::DEBUG::2012-08-10
00:46:26,353::utils::579::Storage.Misc.excCmd::(execCmd) '/bin/rpm -q --qf
%{NAME}\t%{VERSION}\t%{RELEASE}\t%{BUILDTIME}\n qemu-kvm' (cwd None)
- DHC
On Fri, Aug 10, 2012 at 6:41 AM, Itamar Heim ih...@redhat.com wrote:
On 08/10/2012 09:16 AM, Michal Skrivanek wrote:
On Aug 10, 2012, at 08:02 , Dead Horse wrote:
With ovirt 3.1 EL 6.3 nodes will only work with a data center set to 3.0
compatibility mode. Is there any reason(s) why EL 6.3+ nodes would not be
allowed in a 3.1 compatibility level cluster?
Why would they only work in 3.0 compatibility? 3.1 nodes work in 3.1
cluster level because, well, they are the same version.
Or I didn't get the question and please
Re: [Users] EL 6.3+ nodes and 3.1 compatibility?
I am not using the dreyou repo. Rather a pure EL 6.3 and it's associated packages. - DHC On Fri, Aug 10, 2012 at 8:07 AM, Robert Middleswarth rob...@middleswarth.net wrote: On 08/10/2012 02:02 AM, Dead Horse wrote: With ovirt 3.1 EL 6.3 nodes will only work with a data center set to 3.0 compatibility mode. Is there any reason(s) why EL 6.3+ nodes would not be allowed in a 3.1 compatibility level cluster? This assumes non use of gluster since adding vdsm-gluster to an EL 6 node requires some work package update/version wise (not impossible). - DHC ___ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users What repo are you using? What build number? I have used both gluster and 3.1 compatibily nodes on top of CentOS 6.3. http://www.middleswarth.net/content/installing-ovirt-31-and-glusterfs-using-either-nfs-or-posix-native-file-system -- Thanks Robert Middleswarth @rmiddle (twitter/IRC) ___ 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
Re: [Users] EL 6.3+ nodes and 3.1 compatibility?
- Original Message - From: Dead Horse deadhorseconsult...@gmail.com To: Robert Middleswarth rob...@middleswarth.net Cc: users@ovirt.org Sent: Friday, August 10, 2012 9:22:30 AM Subject: Re: [Users] EL 6.3+ nodes and 3.1 compatibility? I am not using the dreyou repo. Rather a pure EL 6.3 and it's associated packages. where are you getting your VDSM packages from - because the 3.1 packages aren't in RHEL or it's clones. - DHC On Fri, Aug 10, 2012 at 8:07 AM, Robert Middleswarth rob...@middleswarth.net wrote: On 08/10/2012 02:02 AM, Dead Horse wrote: With ovirt 3.1 EL 6.3 nodes will only work with a data center set to 3.0 compatibility mode. Is there any reason(s) why EL 6.3+ nodes would not be allowed in a 3.1 compatibility level cluster? This assumes non use of gluster since adding vdsm-gluster to an EL 6 node requires some work package update/version wise (not impossible). - DHC ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users What repo are you using? What build number? I have used both gluster and 3.1 compatibily nodes on top of CentOS 6.3. http://www.middleswarth.net/content/installing-ovirt-31-and-glusterfs-using-either-nfs-or-posix-native-file-system -- Thanks Robert Middleswarth @rmiddle (twitter/IRC) ___ 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
Re: [Users] EL 6.3+ nodes and 3.1 compatibility?
This is a pure RHEL 6.3 node. Given that I gather in order to make this work I need to build the newer vdsm 4.10.x and update/build the other according dependent packages? - DHC On Fri, Aug 10, 2012 at 8:23 AM, Andrew Cathrow acath...@redhat.com wrote: - Original Message - From: Dead Horse deadhorseconsult...@gmail.com To: Robert Middleswarth rob...@middleswarth.net Cc: users@ovirt.org Sent: Friday, August 10, 2012 9:22:30 AM Subject: Re: [Users] EL 6.3+ nodes and 3.1 compatibility? I am not using the dreyou repo. Rather a pure EL 6.3 and it's associated packages. where are you getting your VDSM packages from - because the 3.1 packages aren't in RHEL or it's clones. - DHC On Fri, Aug 10, 2012 at 8:07 AM, Robert Middleswarth rob...@middleswarth.net wrote: On 08/10/2012 02:02 AM, Dead Horse wrote: With ovirt 3.1 EL 6.3 nodes will only work with a data center set to 3.0 compatibility mode. Is there any reason(s) why EL 6.3+ nodes would not be allowed in a 3.1 compatibility level cluster? This assumes non use of gluster since adding vdsm-gluster to an EL 6 node requires some work package update/version wise (not impossible). - DHC ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users What repo are you using? What build number? I have used both gluster and 3.1 compatibily nodes on top of CentOS 6.3. http://www.middleswarth.net/content/installing-ovirt-31-and-glusterfs-using-either-nfs-or-posix-native-file-system -- Thanks Robert Middleswarth @rmiddle (twitter/IRC) ___ 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] ovirt 3.1 engine install fails - fedora 17 with selinux disabled
Hi Thanks to all for the great work getting 3.1 out the door, 3.0 is working well for us and looking forward to playing with all the new features. At the moment, am having a small problem during initial engine setup where it fails if selinux is configured as disabled - is this intended behaviour? - selinux disabled - reports nfs domain setup as failed [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip- Configuring the Default ISO Domain... [ ERROR ] -- snip [root@ovirt-m-2 ~]# engine-cleanup - After setting CONFIG_NFS=no, in the answer file; it gives an explicit error about selinux during the HTTPD phase (OVERRIDE_HTTPD_CONFIG=yes) [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip Handling HTTPD... [ ERROR ] Failed to enable SELinux boolean -- snip - - set selinux to permissive and reboot - install succeeds (OVERRIDE_HTTPD_CONFIG=yes, CONFIG_NFS=yes) Cheers, Dave __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled
David, Are you using the 3.5.0 kernel? There is currently an issue related to NFS which is preventing oVirt 3.1 from working correctly. if you are using 3.5.0, try using an older kernel and see if that works until an updated kernel is pushed. - Nick From: david.elli...@shazamteam.com To: users@ovirt.org Date: Fri, 10 Aug 2012 15:40:49 +0100 Subject: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled Hi Thanks to all for the great work getting 3.1 out the door, 3.0 is working well for us and looking forward to playing with all the new features. At the moment, am having a small problem during initial engine setup where it fails if selinux is configured as disabled - is this intended behaviour? - selinux disabled - reports nfs domain setup as failed [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip- Configuring the Default ISO Domain... [ ERROR ] -- snip [root@ovirt-m-2 ~]# engine-cleanup - After setting CONFIG_NFS=no, in the answer file; it gives an explicit error about selinux during the HTTPD phase (OVERRIDE_HTTPD_CONFIG=yes) [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip Handling HTTPD... [ ERROR ] Failed to enable SELinux boolean -- snip - - set selinux to permissive and reboot - install succeeds (OVERRIDE_HTTPD_CONFIG=yes, CONFIG_NFS=yes) Cheers, Dave __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ ___ 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] Ang: ovirt 3.1 engine install fails - fedora 17 with selinux disabled
Hi! I encountered the same problem, and I found this bug: https://bugzilla.redhat.com/show_bug.cgi?id=835100 reported by Ofer Schreiber. So it is not intended. I do have another problem, related to this,though! I can't set my SELinux to permissive...? In the /etc/selinux/conf file, I change and put in permissive, save the file and reboot. When the system starts sestatus reports disabled...? I tried this a couple of times, and I don't know why it's sort of stuck there... Idea's...? regards Johan -users-boun...@ovirt.org skrev: - Till: users@ovirt.org Från: David Elliott Sänt av: users-boun...@ovirt.org Datum: 2012.08.10 16:41 Ärende: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled Hi Thanks to all for the great work getting 3.1 out the door, 3.0 is working well for us and looking forward to playing with all the new features. At the moment, am having a small problem during initial engine setup where it fails if selinux is configured as disabled - is this intended behaviour? - selinux disabled - reports nfs domain setup as failed [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip- Configuring the Default ISO Domain... [ ERROR ] -- snip [root@ovirt-m-2 ~]# engine-cleanup - After setting CONFIG_NFS=no, in the answer file; it gives an explicit error about selinux during the HTTPD phase (OVERRIDE_HTTPD_CONFIG=yes) [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip Handling HTTPD... [ ERROR ] Failed to enable SELinux boolean -- snip - - set selinux to permissive and reboot - install succeeds (OVERRIDE_HTTPD_CONFIG=yes, CONFIG_NFS=yes) Cheers, Dave __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ ___ 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
Re: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled
Hi! That 3.5 kernel issue is, what I have understood, more related to nfs as storage domain, not the problem Davis is refering to. Rgrds Johan -users-boun...@ovirt.org skrev: - Till: David Elliott david.elli...@shazamteam.com, oVirt Mailing List users@ovirt.org Från: Nicholas Kesick Sänt av: users-boun...@ovirt.org Datum: 2012.08.10 16:51 Ärende: Re: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled David, Are you using the 3.5.0 kernel? There is currently an issue related to NFS which is preventing oVirt 3.1 from working correctly. if you are using 3.5.0, try using an older kernel and see if that works until an updated kernel is pushed. - Nick From: david.elli...@shazamteam.com To: users@ovirt.org Date: Fri, 10 Aug 2012 15:40:49 +0100 Subject: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled Hi Thanks to all for the great work getting 3.1 out the door, 3.0 is working well for us and looking forward to playing with all the new features. At the moment, am having a small problem during initial engine setup where it fails if selinux is configured as disabled - is this intended behaviour? - selinux disabled - reports nfs domain setup as failed [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip- Configuring the Default ISO Domain... [ ERROR ] -- snip [root@ovirt-m-2 ~]# engine-cleanup - After setting CONFIG_NFS=no, in the answer file; it gives an explicit error about selinux during the HTTPD phase (OVERRIDE_HTTPD_CONFIG=yes) [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip Handling HTTPD... [ ERROR ] Failed to enable SELinux boolean -- snip - - set selinux to permissive and reboot - install succeeds (OVERRIDE_HTTPD_CONFIG=yes, CONFIG_NFS=yes) Cheers, Dave __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ ___ 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
Re: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled
Hi That occurred to me as well, but kernel is 3.3.4-5.fc17.x86_64 I've tried this a few times now - and the behaviour is consistent - fails with selinux disabled - either at the nfs iso domain phase , or if configured without nfs iso - at the httpd step - succeeds with selinux permissive - with both nfs iso domain and httpd configured Cheers, Dave -Original Message- From: Johan Kragsterman [mailto:johan.kragster...@capvert.se] Sent: 10 August 2012 16:25 To: Nicholas Kesick Cc: David Elliott; oVirt Mailing List Subject: Re: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled Hi! That 3.5 kernel issue is, what I have understood, more related to nfs as storage domain, not the problem Davis is refering to. Rgrds Johan -users-boun...@ovirt.org skrev: - Till: David Elliott david.elli...@shazamteam.com, oVirt Mailing List users@ovirt.org Från: Nicholas Kesick Sänt av: users-boun...@ovirt.org Datum: 2012.08.10 16:51 Ärende: Re: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled David, Are you using the 3.5.0 kernel? There is currently an issue related to NFS which is preventing oVirt 3.1 from working correctly. if you are using 3.5.0, try using an older kernel and see if that works until an updated kernel is pushed. - Nick From: david.elli...@shazamteam.com To: users@ovirt.org Date: Fri, 10 Aug 2012 15:40:49 +0100 Subject: [Users] ovirt 3.1 engine install fails - fedora 17 with selinux disabled Hi Thanks to all for the great work getting 3.1 out the door, 3.0 is working well for us and looking forward to playing with all the new features. At the moment, am having a small problem during initial engine setup where it fails if selinux is configured as disabled - is this intended behaviour? - selinux disabled - reports nfs domain setup as failed [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip- Configuring the Default ISO Domain... [ ERROR ] -- snip [root@ovirt-m-2 ~]# engine-cleanup - After setting CONFIG_NFS=no, in the answer file; it gives an explicit error about selinux during the HTTPD phase (OVERRIDE_HTTPD_CONFIG=yes) [root@ovirt-m-2 ~]# engine-setup --answer-file=ovirt-answers.ovirt-m-2.shazamteam.com -- snip Handling HTTPD... [ ERROR ] Failed to enable SELinux boolean -- snip - - set selinux to permissive and reboot - install succeeds (OVERRIDE_HTTPD_CONFIG=yes, CONFIG_NFS=yes) Cheers, Dave __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ ___ 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 __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
