[libvirt] Memory corruption with CVS tip + python

Chris Lalancette clalance at redhat.com
Wed Aug 6 11:58:15 UTC 2008


All,
    FYI, I'm running into some memory corruption when using CVS tip and trying
to use an older virt-install command.  I won't have time to debug this today, so
I thought I would mention it on-list in case someone else wants to take a crack
at it.

My system is an AMD system running RHEL-5.2 x86_64 bits, so it has
python-virtinst-0.300.2-8.el5 installed.

Basically, I did this:

# cvs co libvirt
# cd libvirt
# ./autogen.sh
# make dist

>From here, I took the resulting .tar.gz, and dumped it into
/usr/src/redhat/SOURCES, and then took the SPEC file from the Fedora 9 sources.
 I had to modify the very top of it (since RHEL-5 rpmbuild didn't like the
macros for whatever reason), but if I read the logic right, I put these flags at
the top:

%define with_polkit 0
%define with_proxy yes
%define with_qemu 0

Then I built and installed a libvirt and libvirt-python RPM with this.  Finally,
I restarted libvirtd, and then tried to run the following command:

[root at amd1 libvirt]# virt-install -n test -f /var/lib/xen/images/test.img -s 10
-r 768 -v -c /var/lib/xen/images/boot.iso -d --vnc
Wed, 06 Aug 2008 07:59:10 DEBUG    DistroInstaller location is a local
file/path: /var/lib/xen/images/boot.iso


Starting install...
Segmentation fault
[root at amd1 libvirt]#

It happens every time, so it should be fairly easy to track down.

Chris Lalancette




More information about the libvir-list mailing list