Re: [vdsm] Help needed to debug segfault when using ctypes
I haven't worked much on using ctypes in python.. but did you try to
look into the core to see where exactly the segfault is happening.. that
might give some clues for further debug.
On 08/22/2013 05:53 PM, Aravinda wrote:
Hi,
In following patch I am using ctypes to load libgfapi(GlusterFS API)
to get the Gluster volume statvfs information.
http://gerrit.ovirt.org/#/c/17822
I am getting *segfault* when I run
vdsClient 0 glusterVolumeSizeInfoGet volumeName=gv1
But I checked as below and it is working.
cd /usr/share/vdsm
python
>> from gluster import gfapi
>> print gfapi.volumeStatvfs("gv1")
posix.statvfs_result(f_bsize=4096L, f_frsize=4096L,
f_blocks=25803070L, f_bfree=19130426L, f_bavail=17819706L,
f_files=6553600L, f_ffree=5855876L, f_favail=5855876L,
f_flag=4096L, f_namemax=255L)
Please suggest how I can debug this issue.
--
Regards
Aravinda
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] Help needed to debug segfault when using ctypes
Hi,
In following patch I am using ctypes to load libgfapi(GlusterFS API) to
get the Gluster volume statvfs information.
http://gerrit.ovirt.org/#/c/17822
I am getting *segfault* when I run
vdsClient 0 glusterVolumeSizeInfoGet volumeName=gv1
But I checked as below and it is working.
cd /usr/share/vdsm
python
>> from gluster import gfapi
>> print gfapi.volumeStatvfs("gv1")
posix.statvfs_result(f_bsize=4096L, f_frsize=4096L,
f_blocks=25803070L, f_bfree=19130426L, f_bavail=17819706L,
f_files=6553600L, f_ffree=5855876L, f_favail=5855876L, f_flag=4096L,
f_namemax=255L)
Please suggest how I can debug this issue.
--
Regards
Aravinda
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] suggesting new Vdsm maintaniner(s)
- Original Message - > From: "Michal Skrivanek" > To: "Dan Kenigsberg" , "Itamar Heim" , > bo...@ovirt.org > Cc: vdsm-de...@fedorahosted.org > Sent: Thursday, August 22, 2013 9:53:50 AM > Subject: Re: [vdsm] suggesting new Vdsm maintaniner(s) > > > On Aug 8, 2013, at 11:00 , Dan Kenigsberg wrote: > > > On Thu, Aug 01, 2013 at 04:55:07PM +0300, Dan Kenigsberg wrote: > >> Nominating Toni Puimedon and/or Mark Wu as maintainers > >> == > >> > >> During their recent year-or-two of participation in Vdsm development, > >> both Toni and Mark has demonstrated a genuine care for the health and > >> evolution of the the project. > >> > >> They both carry this hard-to-quantify quality of serious-mindedness when > >> reviewing patches. > >> > >> Toni's 73 committed patches touch everything that is related to network > >> configuration and reporting > >> > >> 27 vdsm/configNetwork.py > >> 11 lib/vdsm/netinfo.py > >> 8 vdsm/API.py > >> 8 tests/configNetworkTests.py > >> 7 vdsm/netinfo.py > >> 7 vdsm/netconf/ifcfg.py > >> 5 vdsm/libvirtvm.py > >> 4 vdsm/netmodels.py > >> > >> ... similar to Mark's 80: > >> > >> 16 vdsm/configNetwork.py > >> 12 vdsm/netconf/ifcfg.py > >> 12 vdsm/libvirtvm.py > >> 7 vdsm/clientIF.py > >> 6 lib/vdsm/netinfo.py > >> 5 vdsm/caps.py > >> 5 vdsm/API.py > >> 4 vdsm/vm.py > >> 4 vdsm/netmodels.py > >> 4 vdsm/Makefile.am > >> > >> I suggest that both of them obtain +2/-2 rights, in the understanding > >> that they are to be used on net-related parts of the code. This is > >> particularly important given my nearing, relatively long, vacation. > >> > >> What do you say? > > > > We've got no objectation, but neither an overwhelming support. Maybe > > it's due to the summer season. > > Likely. My late loud +1 > > > > To me, it is important to tell whether Toni/Mark only reviewed a patch > > (+1) or are completely standing behind it, and going to fix bugs in it > > if the author is run over by a bus (God forbid). > > > > Itamar and other board members: if there is no objection within, say, > > one week, would you grant the duo +2 rights? > > Sounds like the time is now… Agreed, delaying it just overloads Federico during the recent period. With adding new maintainers I hope we'll have more attendance in vdsm calls and contributes will receive faster response and help Thanks, Yaniv Bronhaim. > > > > Dan. > > ___ > > vdsm-devel mailing list > > vdsm-devel@lists.fedorahosted.org > > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > > ___ > vdsm-devel mailing list > vdsm-devel@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] vdsClient networking (addNetwork with existing bond)
Here you go:
vdsClient -s 0 setupNetworks
networks='{rhevm:{bonding:bond2,bootproto:dhcp,bridged:True}}'
bondings='{bond2:{nics:eth1+eth2}}'
- Original Message -
From: "Sandro Bonazzola"
To: "VDSM Project Development"
Sent: Thursday, August 22, 2013 9:44:06 AM
Subject: [vdsm] vdsClient networking (addNetwork with existing bond)
Hi,
I'm trying to fix https://bugzilla.redhat.com/999577 which in short is
failing to create bridge specifying a bond interface as nic using vdsClient.
The failing command line is:
'/usr/bin/vdsClient', '-s', 'localhost', 'addNetwork', 'bridge=rhevm', 'vlan=',
'bond=',
'nics=bond2', 'force=False', 'bridged=True', 'BOOTPROTO=dhcp', 'ONBOOT=yes',
'blockingdhcp=true'
I suppose that 'nics=bond2' and 'bond=' are wrong.
I'm searching for a man page or something like that for understanding how to
prepare the command line without success.
http://www.ovirt.org/VdsClient is outdated and says anything about networking.
I've seen in http://www.ovirt.org/Vdsm_Network that using a bond should be
supported but for the supported topologies
there are no command line examples.
For:
bridge1 --- bond --- nic1
\
-- nic2
I suppose that the command line should have 'bond=bond' 'nics=nic1,nic2' is
this right?
If the bond already exists is it enough specifying 'bond=bond', 'nics=' ?
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
