Fnaly I fix my problem with following step

1) Check your maximum shared memory :
$ |sudo cat /proc/sys/kernel/shmmax
33554432|

You need to increase the shared memory to fix this.

2) To fix it temporarily, run this command :
$ |sudo sysctl -w kernel.shmmax=134217728|

3) To fix this permenantly, set this in your configuration:
$ |sudo vi /etc/sysctl.conf
kernel.shmmax = 134217728

|


On 28-01-2014 15:02, users-requ...@ovirt.org wrote:
Send Users mailing list submissions to
        users@ovirt.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.ovirt.org/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
        users-requ...@ovirt.org

You can reach the person managing the list at
        users-ow...@ovirt.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."


Today's Topics:

    1. Re: Multi-Host Network Configuration (Piotr Kliczewski)
    2. ovirt-3.3.3 release postponed due to blockers (Sandro Bonazzola)
    3. Re: Vm's being paused (Neil)


----------------------------------------------------------------------

Message: 1
Date: Tue, 28 Jan 2014 13:28:43 +0100
From: Piotr Kliczewski <piotr.kliczew...@gmail.com>
To: Dan Kenigsberg <dan...@redhat.com>
Cc: users@ovirt.org
Subject: Re: [Users] Multi-Host Network Configuration
Message-ID:
        <caku0_rnogobq35prwuac+rvxeoqd00z3cjdaf4nezg+3bsz...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jan 27, 2014 at 7:20 PM, Dan Kenigsberg <dan...@redhat.com> wrote:
On Mon, Jan 27, 2014 at 04:23:47PM +0100, Piotr Kliczewski wrote:
Hi,

I played with multi host network config and used two boxes to test it.
One el6 (vdsm) and f19 (engine, vdsm). During the test I noticed that
vdsm on f19 haven't joined to cluster (known issue). I performed
modification of vlan and MTU. Both boxes were modified but I noticed
that by accident I modified ovirtmgmt network and I noticed that I
lost connectivity. el6 box recovered whereas f19 haven't. I think it
was because the vdsm was local to the engine.
That may be so. To make sure, I'd love to see your vdsm.log and
supervdsm.log of the time of the modification.

I do not have the logs anymore but will try to recreate it and send
you the logs.

I spend sometime trying
to recover network configuration.
Thanks for testing this feature.

------------------------------

Message: 2
Date: Tue, 28 Jan 2014 13:55:43 +0100
From: Sandro Bonazzola <sbona...@redhat.com>
To: arch <a...@ovirt.org>, engine-devel <engine-de...@ovirt.org>,
        "Users@ovirt.org" <Users@ovirt.org>,    VDSM Project Development
        <vdsm-de...@lists.fedorahosted.org>
Subject: [Users] ovirt-3.3.3 release postponed due to blockers
Message-ID: <52e7a8cf.6040...@redhat.com>
Content-Type: text/plain; charset=ISO-8859-15

Hi,
oVirt 3.3.3 release need to be postponed.
A recent release of python-cpopen-1.3 is breaking dependency resolution on EL6 
and F19 so vdsm can't be installed and node can't be composed.
A recent change in vdsm-python-cpopen added the needed conflict against 
python-cpopen and removed Provides / Obsoletes on python-cpopen.
But no new releases of python-cpopen is available fixing the correct Provides / 
Obsoletes pair.

oVirt 3.3.2 / stable is affected too.

Please fix
Bug 1056470 - python-cpopen-1.3 is not providing obsoleted package.
Bug 1056464 - python-cpopen-1.3 is not providing obsoleted package.
ASAP.



_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to