On Tue, Jul 07, 2015 at 05:13:28PM +0100, Dan Kenigsberg wrote:
> On Tue, Jul 07, 2015 at 10:14:54AM +0200, NUNIN Roberto wrote:
> > >
> > > On Mon, Jul 06, 2015 at 10:33:59AM +0200, NUNIN Roberto wrote:
> > > > Hi Dan
> > > >
> > > > Sorry for question: what do you mean for interface vnet ?
>
On Thu, Jul 09, 2015 at 08:57:50AM -0400, Fabian Deutsch wrote:
> - Original Message -
> > On Wed, Jul 08, 2015 at 09:11:42AM +0300, Michael S. Tsirkin wrote:
> > > On Tue, Jul 07, 2015 at 05:13:28PM +0100, Dan Kenigsberg wrote:
> > > > On Tue, Jul 07, 2015 at 10:14:54AM +0200, NUNIN Robert
Hi.
ovirt3.5
Have two servers(node1 and node2) that are runnig Centos6.6.
1. engine on node2. Disables network node1, engine restarts after some
time node1 and everything works fine.
2. engine on node1. Disables network node1, engine moved to node2, node1
but does not reset, although attempts
Hello,
We have a small oVirt deplopyment, with 2 INTEL CPUs and 1 AMD, therefor
we defined 2 clusters.
One of the Intel machines is running the management as well (We called
this SOL).
This deployment is connected to a NAS through NFS shares.
Suddenly (no more than 2 days) SOL is reported as
Hello,
We have a small oVirt deplopyment, with 2 INTEL CPUs and 1 AMD, therefor
we defined 2 clusters.
One of the Intel machines is running the management as well (We called
this SOL).
This deployment is connected to a NAS through NFS shares.
Suddenly (no more than 2 days) SOL is reported as
Привет, Роман Николаевич. Попробуй ознакомиться с этим.Nathanael hi,There is an open bug on this scenario :https://bugzilla.redhat.com/show_bug.cgi?id=609689Here are manual steps for overcome this issue:https://access.redhat.com/solutions/376873We are working on a solution for 3.6http://www.ovirt.o
Great, thanks Fabian!
-Patrick
> On Jul 9, 2015, at 1:28 PM, Fabian Deutsch wrote:
>
> - Original Message -
>> Any chance that 3.5.3 EL7 node will get a release soon?
>
> Hey Patrick,
>
> currently we are not publishing "official" isos to resources.ovirt.org,
> instead please
> use t
- Original Message -
> Any chance that 3.5.3 EL7 node will get a release soon?
Hey Patrick,
currently we are not publishing "official" isos to resources.ovirt.org, instead
please
use the ISOs build in our CI:
http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.5_create-iso-el7_merged/
This
The installation ended up correctly with ovirt-release35-005-1.noarch.rpm you
provided.
Thanks.
--
Stefano Stagnaro
Prisma Telecom Testing S.r.l.
Via Petrocchi, 4
20127 Milano – Italy
Tel. 02 26113507 int 339
e-mail: stefa...@prismatelecomtesting.com
skype: stefano.stagnaro
On gio, 2015-07-0
Any chance that 3.5.3 EL7 node will get a release soon?
-Patrick
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Yes,
It is displayed in the engine:
[image: Inline image 1]
The VM is not really running - the IP addresses that are being reported are
from another VM that was recently removed. All attempts to control the VM
have failed. It does not have any NICS or disk associated with it - so this
seems to b
Il 09/07/2015 11:48, Stefano Stagnaro ha scritto:
> Hi,
>
> adding epel-6 gives another error:
>
> Error: Package: vdsm-gluster-4.16.20-0.el6.noarch (@ovirt-3.5)
>Requires: vdsm = 4.16.20-0.el6
>Removing: vdsm-4.16.20-0.el6.x86_64 (@ovirt-3.5)
>vdsm = 4.16.
Il 09/07/2015 11:48, Stefano Stagnaro ha scritto:
> Hi,
>
> adding epel-6 gives another error:
>
> Error: Package: vdsm-gluster-4.16.20-0.el6.noarch (@ovirt-3.5)
>Requires: vdsm = 4.16.20-0.el6
>Removing: vdsm-4.16.20-0.el6.x86_64 (@ovirt-3.5)
>vdsm = 4.16.
Can you sea via engine, on what host run VM?
Anyway if you have really run VM on host you can try to figure it with 'ps aux
| grep qemu', if it will return you some process, you can just kill process via
'kill pid'.
I hope it will help you.
- Original Message -
From: "Mark Steele"
To: "
Il 09/07/2015 11:48, Stefano Stagnaro ha scritto:
> Hi,
>
> adding epel-6 gives another error:
>
> Error: Package: vdsm-gluster-4.16.20-0.el6.noarch (@ovirt-3.5)
>Requires: vdsm = 4.16.20-0.el6
>Removing: vdsm-4.16.20-0.el6.x86_64 (@ovirt-3.5)
>vdsm = 4.16.
Il 09/07/2015 11:48, Stefano Stagnaro ha scritto:
> Hi,
>
> adding epel-6 gives another error:
>
> Error: Package: vdsm-gluster-4.16.20-0.el6.noarch (@ovirt-3.5)
>Requires: vdsm = 4.16.20-0.el6
>Removing: vdsm-4.16.20-0.el6.x86_64 (@ovirt-3.5)
>vdsm = 4.16.
Artyom,
Thank you - I don't have vdsClient installed - can you point me to the
download?
***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook
Please check host where VM run(vdsClient -s 0 list table), and you can destroy
it via vdsClient(vdsClient -s 0 destroy vm_id).
Thanks
- Original Message -
From: "Mark Steele"
To: users@ovirt.org
Sent: Thursday, July 9, 2015 4:38:32 PM
Subject: [ovirt-users] This VM is not managed by the
I have a VM that was not started and is now showing as running. When I
attempt to suspend or stop it in the ovirt-shell, I get the message:
status: 400
reason: bad request
detail: Cannot hibernate VM. This VM is not managed by the engine.
Not sure how the VM was initially created on the ovirt man
Hi Shubhendu,
thanks for your reply.
The hosts are in Maintance Mode. When i try to remove the host i get:
° Are you sure you want to remove the following items? => I press OK
And i get:
Error while executing action: node02
Cannot remove Host. Server having Gluster volume.
I cant see an
- Original Message -
> On Wed, Jul 08, 2015 at 09:11:42AM +0300, Michael S. Tsirkin wrote:
> > On Tue, Jul 07, 2015 at 05:13:28PM +0100, Dan Kenigsberg wrote:
> > > On Tue, Jul 07, 2015 at 10:14:54AM +0200, NUNIN Roberto wrote:
> > > > >
> > > > > On Mon, Jul 06, 2015 at 10:33:59AM +0200, N
Hello, all
Please help,
After increase in the size LUN(from 209G to 364G), its size in the console
oVirt has not changed, but at "Edit domain", its new size is visible
What to make, that there was well new empty seat on LUN?
Roman Drovalev
On Wed, Jul 08, 2015 at 09:11:42AM +0300, Michael S. Tsirkin wrote:
> On Tue, Jul 07, 2015 at 05:13:28PM +0100, Dan Kenigsberg wrote:
> > On Tue, Jul 07, 2015 at 10:14:54AM +0200, NUNIN Roberto wrote:
> > > >
> > > > On Mon, Jul 06, 2015 at 10:33:59AM +0200, NUNIN Roberto wrote:
> > > > > Hi Dan
>
Once all the hosts are in maintenance mode, select all the hosts in that
cluster and use the force option for removing the hosts.
This would allow removal of hosts from the engine but gluster cluster
remains intact.
Regards,
Shubhendu
On 07/09/2015 04:23 PM, m...@ohnewald.net wrote:
Is this a
We are running oVirt Version 3.5.0.1-1.el6.
I have a VM on one of my hosts that appears to be stuck. The VM shows
running, however I am unable to successfully shutdown, powerdown, or
otherwise change the status of the VM.
It is not pinging. The guest OS is Ubuntu 14.04 and the ovirt agent is
inst
Is this a stupid question or why isnt anyone responding?
By the way. I am running ovirt 3.5.2
Thanks,
Mario
Am 08.07.15 um 11:48 schrieb m...@ohnewald.net:
Anyone? :)
Am 07.07.15 um 11:54 schrieb m...@ohnewald.net:
Hello List,
I have a 2 node replica Gluster Cluster in a Datacenter which
The libs are available for epel6 as well I remember.
Worth giving a try.
Regards,
Shubhendu
On 07/09/2015 03:50 PM, Shubhendu Tripathi wrote:
I installed librcu using the below command -
yum install
ftp://ftp.muug.mb.ca/mirror/fedora/epel/7/x86_64/u/userspace-rcu-0.7.9-1.el7.x86_64.rpm
Rega
I installed librcu using the below command -
yum install
ftp://ftp.muug.mb.ca/mirror/fedora/epel/7/x86_64/u/userspace-rcu-0.7.9-1.el7.x86_64.rpm
Regards,
Shubhendu
On 07/08/2015 04:09 PM, Stefano Stagnaro wrote:
Hi,
host installation in a glusterfs cluster is failing due to dependecies erro
Hi,
adding epel-6 gives another error:
Error: Package: vdsm-gluster-4.16.20-0.el6.noarch (@ovirt-3.5)
Requires: vdsm = 4.16.20-0.el6
Removing: vdsm-4.16.20-0.el6.x86_64 (@ovirt-3.5)
vdsm = 4.16.20-0.el6
Updated By: vdsm-4.16.20-1.git3a90f62.el6.x86_
Hi,
since Fedora 21 is not going to be officially supported in 3.6 / master, in
order to save resources for our CI systems we're going to drop builds for
engine related packages starting from July 31.
You may still continue developing engine on Fedora 21 by manually building
required dependencie
30 matches
Mail list logo
