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 - wit
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 , oVirt Mailing List
Från: Nicholas Kesick
Sänt av: users-boun...@ovirt.org
Datum: 201
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
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: u
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
behavio
On Fri, Aug 10, 2012 at 9:45 AM, Itamar Heim wrote:
> 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 ex
Yes, this VDSM in EL 6.3 only knows about 3.0 cluster level.
- Original Message -
> From: "Dead Horse"
> To: "Andrew Cathrow"
> Cc: users@ovirt.org, "Robert Middleswarth"
> Sent: Friday, August 10, 2012 9:28:23 AM
> Subject: Re: [Users] EL 6.3+ nodes and 3.1 compatibility?
> This is
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 wrote:
>
> - Original Message -
>
> > From: "Dead Horse"
> >
- Original Message -
> From: "Dead Horse"
> To: "Robert Middleswarth"
> 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.
wh
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.
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_
6
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
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 R
- Original Message -
> From: "Shu Ming"
> To: "Winfried de Heiden"
> 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 her
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 w
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 w
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
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
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
19 matches
Mail list logo
