Hi Joop,
Looks like the problem is because of the glusterfs version you are
using. vdsm could not parse the output from gluster.
Can you update the glusterfs to
http://bits.gluster.org/pub/gluster/glusterfs/v3.4.0qa7/x86_64/ and
check it out?
Thanks,
Kanagaraj
On 02/01/2013 03:23 PM,
Hola,
Could you make some pastebins with the contents of the files
/etc/sysconfig/network-scripts/ifcfg* ?
Also, virsh -r net-list and the log generated on the process
of losing the connection when creating a guest.
Best,
Toni
- Original Message -
From: Juan Jose jj197...@gmail.com
On 1-2-2013 11:07, Kanagaraj wrote:
Hi Joop,
Looks like the problem is because of the glusterfs version you are
using. vdsm could not parse the output from gluster.
Can you update the glusterfs to
http://bits.gluster.org/pub/gluster/glusterfs/v3.4.0qa7/x86_64/ and
check it out?
How??
I
On 02/01/2013 05:13 PM, noc wrote:
On 1-2-2013 11:07, Kanagaraj wrote:
Hi Joop,
Looks like the problem is because of the glusterfs version you are
using. vdsm could not parse the output from gluster.
Can you update the glusterfs to
Shireesh Anjal wrote:
On 02/01/2013 05:13 PM, noc wrote:
On 1-2-2013 11:07, Kanagaraj wrote:
Hi Joop,
Looks like the problem is because of the glusterfs version you are
using. vdsm could not parse the output from gluster.
Can you update the glusterfs to
Shireesh Anjal wrote:
On 02/01/2013 05:13 PM, noc wrote:
On 1-2-2013 11:07, Kanagaraj wrote:
Hi Joop,
Looks like the problem is because of the glusterfs version you are
using. vdsm could not parse the output from gluster.
Can you update the glusterfs to
On 02/01/2013 06:47 PM, Joop wrote:
Shireesh Anjal wrote:
On 02/01/2013 05:13 PM, noc wrote:
On 1-2-2013 11:07, Kanagaraj wrote:
Hi Joop,
Looks like the problem is because of the glusterfs version you are
using. vdsm could not parse the output from gluster.
Can you update the glusterfs
Hi
My environnement is Fedora18 / Ovirt 3.2 and VDSM vdsm-4.10.3-6.fc18.x86_64.
I use a storage on fiber channel. When creating a VM the disk is created by
ovirt.
When starting the VM the disk has not the permission to be accessed by vdsm.
In fact the device for the disk has root:disks as
Hi
It looks like this bug report :
https://bugzilla.redhat.com/show_bug.cgi?id=903716
Kevin
2013/2/1 Kevin Maziere Aubry kevin.mazi...@alterway.fr
Hi
My environnement is Fedora18 / Ovirt 3.2 and
VDSM vdsm-4.10.3-6.fc18.x86_64.
I use a storage on fiber channel. When creating a VM the
On 02/01/2013 07:38 PM, Kanagaraj wrote:
On 02/01/2013 06:47 PM, Joop wrote:
Shireesh Anjal wrote:
On 02/01/2013 05:13 PM, noc wrote:
On 1-2-2013 11:07, Kanagaraj wrote:
Hi Joop,
Looks like the problem is because of the glusterfs version you are
using. vdsm could not parse the output from
Both nodes are identical and can fully communicate with each other.
Since the normal non p2p live migration works both hosts can reach each
other via the connection URI.
Perhaps I am missing something here?
- DHC
___
Users mailing list
Users@ovirt.org
On 02/01/2013 09:29 PM, Dead Horse wrote:
To test further I loaded up two more identical servers with EL 6.3 and the
same package versions originally indicated. The difference here is that I
did not turn these into ovirt nodes. EG: installing VDSM.
- All configurations were left at defaults
Hello,
I seem to remember in RHEV 3.0 that when you configured an IPA domain,
its admin was automatically configured as an admin for RHEV itself.
Is it true and in case does remain true for oVirt?
I configured IPA as shipped on CentOS 6.3+updates
ipa-server-2.2.0-17.el6_3.1.x86_64
I successfully
13 matches
Mail list logo
