thr3ads.net - Xen users - [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems [Apr 2008]

If this information is useful, please help other people find it:
Share via:

William Heath

2008-Apr-01 08:22 UTC

[Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Hi All,

I managed to get centos 5.1 to install via the quickstart approach described
here:

http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU

I then followed the post install instructions and have the following config
file:

cat xen501
#kernel = "/boot/vmlinuz-xen-install"
#ramdisk = "/boot/initrd-xen-install"
#extra = "text ks=http://192.168.0.124/minimal-ks.cfg"
name = "xen501"
memory = "128"
disk = [ ''tap:aio:/data/vm/xen501.img,xvda,w'', ]
vif = [ ''bridge=xenbr0'', ]
bootloader="/usr/bin/pygrub"
vcpus=1
on_reboot = ''destroy''
on_crash = ''destroy''

I then did xm create xen501  and saw this:

Using config file "xen501".
*** glibc detected *** /usr/bin/python: double free or corruption (out):
0xb7d25100 ***
======= Backtrace: ========/lib/tls/i686/nosegneg/libc.so.6[0xb7e0f34d]
/lib/tls/i686/nosegneg/libc.so.6(cfree+0x90)[0xb7e12a00]
/usr/lib/python2.5/site-packages/grub/fsys/ext2/_pyext2.so[0xb7cb90c1]
/usr/bin/python(PyEval_EvalCodeEx+0x313)[0x80c9903]
/usr/bin/python(PyEval_EvalFrameEx+0x53f9)[0x80c8229]
/usr/bin/python(PyEval_EvalCodeEx+0x775)[0x80c9d65]
/usr/bin/python[0x8111fc1]
/usr/bin/python(PyObject_Call+0x27)[0x805c787]
/usr/bin/python[0x80628e4]
/usr/bin/python(PyObject_Call+0x27)[0x805c787]
/usr/bin/python(PyEval_CallObjectWithKeywords+0x6c)[0x80c1f7c]
/usr/bin/python(PyInstance_New+0x71)[0x8066031]
/usr/bin/python(PyObject_Call+0x27)[0x805c787]
/usr/bin/python(PyEval_EvalFrameEx+0x2031)[0x80c4e61]
/usr/bin/python(PyEval_EvalCodeEx+0x775)[0x80c9d65]
/usr/bin/python(PyEval_EvalCode+0x57)[0x80c9dd7]
/usr/bin/python(PyRun_FileExFlags+0xf8)[0x80e91d8]
/usr/bin/python(PyRun_SimpleFileExFlags+0x187)[0x80e9467]
/usr/bin/python(Py_Main+0x9c0)[0x8059330]
/usr/bin/python(main+0x22)[0x8058862]
/lib/tls/i686/nosegneg/libc.so.6(__libc_start_main+0xdc)[0xb7dbcebc]
/usr/bin/python[0x80587b1]
======= Memory map: =======08048000-0813f000 r-xp 00000000 03:01 2115535   
/usr/bin/python2.5
0813f000-08164000 rw-p 000f6000 03:01 2115535    /usr/bin/python2.5
08164000-08269000 rw-p 08164000 00:00 0          [heap]
b7b00000-b7b21000 rw-p b7b00000 00:00 0
b7b21000-b7c00000 ---p b7b21000 00:00 0
b7c2b000-b7c44000 r-xp 00000000 03:01 2359312    /lib/libext2fs.so.2.4
b7c44000-b7c45000 rw-p 00019000 03:01 2359312    /lib/libext2fs.so.2.4
b7c59000-b7c9e000 r-xp 00000000 03:01 2359529    /lib/libncursesw.so.5.5
b7c9e000-b7ca6000 rw-p 00045000 03:01 2359529    /lib/libncursesw.so.5.5
b7ca6000-b7ca7000 rw-p b7ca6000 00:00 0
b7ca9000-b7cb4000 r-xp 00000000 03:01 2359360    /lib/libgcc_s.so.1
b7cb4000-b7cb5000 rw-p 0000a000 03:01 2359360    /lib/libgcc_s.so.1
b7cb5000-b7cb7000 r-xp 00000000 03:01 2359357    /lib/libcom_err.so.2.1
b7cb7000-b7cb8000 rw-p 00001000 03:01 2359357    /lib/libcom_err.so.2.1
b7cb8000-b7cba000 r-xp 00000000 03:01 2790229
/usr/lib/python2.5/site-packages/grub/fsys/ext2/_pyext2.so
b7cba000-b7cbb000 rw-p 00001000 03:01 2790229
/usr/lib/python2.5/site-packages/grub/fsys/ext2/_pyext2.so
b7cbb000-b7cca000 r-xp 00000000 03:01 2131070
/usr/lib/python2.5/lib-dynload/_curses.so
b7cca000-b7ccb000 rw-p 0000f000 03:01 2131070
/usr/lib/python2.5/lib-dynload/_curses.so
b7ccb000-b7ccf000 r-xp 00000000 03:01 2131043
/usr/lib/python2.5/lib-dynload/collections.so
b7ccf000-b7cd0000 rw-p 00004000 03:01 2131043
/usr/lib/python2.5/lib-dynload/collections.so
b7cd0000-b7cd3000 r-xp 00000000 03:01 2130051
/usr/lib/python2.5/lib-dynload/cStringIO.so
b7cd3000-b7cd4000 rw-p 00003000 03:01 2130051
/usr/lib/python2.5/lib-dynload/cStringIO.so
b7cd4000-b7cd7000 r-xp 00000000 03:01 2131687
/usr/lib/python2.5/lib-dynload/time.so
b7cd7000-b7cd9000 rw-p 00002000 03:01 2131687
/usr/lib/python2.5/lib-dynload/time.so
b7cd9000-b7cdb000 r-xp 00000000 03:01 2131679
/usr/lib/python2.5/lib-dynload/fcntl.so
b7cdb000-b7cdc000 rw-p 00002000 03:01 2131679
/usr/lib/python2.5/lib-dynload/fcntl.so
b7cdc000-b7ce0000 r-xp 00000000 03:01 2131685
/usr/lib/python2.5/lib-dynload/strop.so
b7ce0000-b7ce2000 rw-p 00003000 03:01 2131685
/usr/lib/python2.5/lib-dynload/strop.so
b7ce2000-b7ce9000 r--s 00000000 03:01 2115749    /usr/lib/gconv/gconv-
modules.cache
b7ce9000-b7d24000 r--p 00000000 03:01 2162690
/usr/lib/locale/en_US.utf8/LC_CTYPE
b7d24000-b7da7000 rw-p b7d24000 00:00 0
b7da7000-b7ee5000 r-xp 00000000 03:01 2362984
/lib/tls/i686/nosegneg/libc-2.5.so
b7ee5000-b7ee6000 r--p 0013e000 03:01 2362984
/lib/tls/i686/nosegneg/libc-2.5.so
b7ee6000-b7ee8000 rw-p 0013f000 03:01 2362984
/lib/tls/i686/nosegneg/libc-2.5.so
b7ee8000-b7eeb000 rw-p b7ee8000 00:00 0
b7eeb000-b7f10000 r-xp 00000000 03:01 2362988
/lib/tls/i686/nosegneg/libm-2.5.so
b7f10000-b7f12000 rw-p 00024000 03:01 2362988
/lib/tls/i686/nosegneg/libm-2.5.so
b7f12000-b7f14000 r-xp 00000000 03:01 2363003
/lib/tls/i686/nosegneg/libutil-2.5.so
b7f14000-b7f16000 rw-p 00001000 03:01 2363003
/lib/tls/i686/nosegneg/libutil-2.5.so
b7f16000-b7f17000 rw-p b7f16000 00:00 0
b7f17000-b7f19000 r-xp 00000000 03:01 2362987
/lib/tls/i686/nosegneg/libdl-2.5.so
b7f19000-b7f1b000 rw-p 00001000 03:01 2362987
/lib/tls/i686/nosegneg/libdl-2.5.so
b7f1b000-b7f2f000 r-xp 00000000 03:01 2362998
/lib/tls/i686/nosegneg/libpthread-2.5.so
b7f2f000-b7f31000 rw-p 00013000 03:01 2362998
/lib/tls/i686/nosegneg/libpthread-2.5.so
b7f31000-b7f33000 rw-p b7f31000 00:00 0
b7f35000-b7f37000 r-xp 00000000 03:01 2130047
/usr/lib/python2.5/lib-dynload/_random.so
b7f37000-b7f38000 rw-p 00002000 03:01 2130047
/usr/lib/python2.5/lib-dynload/_random.so
b7f38000-b7f3c000 r-xp 00000000 03:01 2131678
/usr/lib/python2.5/lib-dynload/binascii.so
b7f3c000-b7f3d000 rw-p 00003000 03:01 2131678
/usr/lib/python2.5/lib-dynload/binascii.so
b7f3d000-b7f40000 r-xp 00000000 03:01 2131682
/usr/lib/python2.5/lib-dynload/math.so
b7f40000-b7f41000 rw-p 00002000 03:01 2131682
/usr/lib/python2.5/lib-dynload/math.so
b7f41000-b7f46000 r-xp 00000000 03:01 2130050
/usr/lib/python2.5/lib-dynload/_struct.so
b7f46000-b7f47000 rw-p 00005000 03:01 2130050
/usr/lib/python2.5/lib-dynload/_struct.so
b7f47000-b7f49000 rw-p b7f47000 00:00 0
b7f49000-b7f4a000 r-xp b7f49000 00:00 0          [vdso]
b7f4a000-b7f63000 r-xp 00000000 03:01 2359309    /lib/ld-2.5.so
b7f63000-b7f65000 rw-p 00019000 03:01 2359309    /lib/ld-2.5.so
bfc47000-bfc5d000 rw-p bfc47000 00:00 0          [stack]
No handlers could be found for logger "xend"
Error: Boot loader didn''t return any data!
Usage: xm create <ConfigFile> [options] [vars]

Create a domain based on <ConfigFile>.

Options:

-h, --help           Print this help.
--help_config        Print the available configuration variables (vars)
                     for the configuration script.
-q, --quiet          Quiet.
--path=PATH          Search path for configuration scripts. The value of
                     PATH is a colon-separated directory list.
-f=FILE, --defconfig=FILE
                     Use the given Python configuration script.The
                     configuration script is loaded after arguments have
                     been processed. Each command-line option sets a
                     configuration variable named after its long option
                     name, and these variables are placed in the
                     environment of the script before it is loaded.
                     Variables for options that may be repeated have list
                     values. Other variables can be set using VAR=VAL on
                     the command line. After the script is loaded, option
                     values that were not set on the command line are
                     replaced by the values set in the script.
-F=FILE, --config=FILE
                     Domain configuration to use (SXP).
                     SXP is the underlying configuration format used by
                     Xen.
                     SXP configurations can be hand-written or generated
                     from Python configuration scripts, using the -n
                     (dryrun) option to print the configuration.
-n, --dryrun         Dry run - prints the resulting configuration in SXP
                     but does not create the domain.
-p, --paused         Leave the domain paused after it is created.
-c, --console_autoconnect
                     Connect to the console after the domain is created.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Tait Clarridge

2008-Apr-02 14:50 UTC

head link

RE: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Hi William,

What might help is moving /lib/tls to /lib/tls.disabled

I have read that this might prevent some problems. Give it a go and let me know
if it helps.

Cheers,
Tait Clarridge

From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of William Heath
Sent: Tuesday, April 01, 2008 4:22 AM
To: xen-users@lists.xensource.com; michael.judd@adempiere.com
Subject: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Hi All,

I managed to get centos 5.1 to install via the quickstart approach described
here:

http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU

I then followed the post install instructions and have the following config
file:

cat xen501
#kernel = "/boot/vmlinuz-xen-install"
#ramdisk = "/boot/initrd-xen-install"
#extra = "text ks=http://192.168.0.124/minimal-ks.cfg"
name = "xen501"
memory = "128"
disk = [ ''tap:aio:/data/vm/xen501.img,xvda,w'', ]
vif = [ ''bridge=xenbr0'', ]
bootloader="/usr/bin/pygrub"
vcpus=1
on_reboot = ''destroy''
on_crash = ''destroy''

I then did xm create xen501  and saw this:

Using config file "xen501".
*** glibc detected *** /usr/bin/python: double free or corruption (out):
0xb7d25100 ***
======= Backtrace: ========/lib/tls/i686/nosegneg/libc.so.6[0xb7e0f34d]
/lib/tls/i686/nosegneg/libc.so.6(cfree+0x90)[0xb7e12a00]
/usr/lib/python2.5/site-packages/grub/fsys/ext2/_pyext2.so[0xb7cb90c1]
/usr/bin/python(PyEval_EvalCodeEx+0x313)[0x80c9903]
/usr/bin/python(PyEval_EvalFrameEx+0x53f9)[0x80c8229]
/usr/bin/python(PyEval_EvalCodeEx+0x775)[0x80c9d65]
/usr/bin/python[0x8111fc1]
/usr/bin/python(PyObject_Call+0x27)[0x805c787]
/usr/bin/python[0x80628e4]
/usr/bin/python(PyObject_Call+0x27)[0x805c787]
/usr/bin/python(PyEval_CallObjectWithKeywords+0x6c)[0x80c1f7c]
/usr/bin/python(PyInstance_New+0x71)[0x8066031]
/usr/bin/python(PyObject_Call+0x27)[0x805c787]
/usr/bin/python(PyEval_EvalFrameEx+0x2031)[0x80c4e61]
/usr/bin/python(PyEval_EvalCodeEx+0x775)[0x80c9d65]
/usr/bin/python(PyEval_EvalCode+0x57)[0x80c9dd7]
/usr/bin/python(PyRun_FileExFlags+0xf8)[0x80e91d8]
/usr/bin/python(PyRun_SimpleFileExFlags+0x187)[0x80e9467]
/usr/bin/python(Py_Main+0x9c0)[0x8059330]
/usr/bin/python(main+0x22)[0x8058862]
/lib/tls/i686/nosegneg/libc.so.6(__libc_start_main+0xdc)[0xb7dbcebc]
/usr/bin/python[0x80587b1]
======= Memory map: =======08048000-0813f000 r-xp 00000000 03:01 2115535   
/usr/bin/python2.5
0813f000-08164000 rw-p 000f6000 03:01 2115535    /usr/bin/python2.5
08164000-08269000 rw-p 08164000 00:00 0          [heap]
b7b00000-b7b21000 rw-p b7b00000 00:00 0 
b7b21000-b7c00000 ---p b7b21000 00:00 0 
b7c2b000-b7c44000 r-xp 00000000 03:01 2359312    /lib/libext2fs.so.2.4
b7c44000-b7c45000 rw-p 00019000 03:01 2359312    /lib/libext2fs.so.2.4
b7c59000-b7c9e000 r-xp 00000000 03:01 2359529    /lib/libncursesw.so.5.5
b7c9e000-b7ca6000 rw-p 00045000 03:01 2359529    /lib/libncursesw.so.5.5
b7ca6000-b7ca7000 rw-p b7ca6000 00:00 0 
b7ca9000-b7cb4000 r-xp 00000000 03:01 2359360    /lib/libgcc_s.so.1
b7cb4000-b7cb5000 rw-p 0000a000 03:01 2359360    /lib/libgcc_s.so.1
b7cb5000-b7cb7000 r-xp 00000000 03:01 2359357    /lib/libcom_err.so.2.1
b7cb7000-b7cb8000 rw-p 00001000 03:01 2359357    /lib/libcom_err.so.2.1
b7cb8000-b7cba000 r-xp 00000000 03:01 2790229   
/usr/lib/python2.5/site-packages/grub/fsys/ext2/_pyext2.so
b7cba000-b7cbb000 rw-p 00001000 03:01 2790229   
/usr/lib/python2.5/site-packages/grub/fsys/ext2/_pyext2.so
b7cbb000-b7cca000 r-xp 00000000 03:01 2131070   
/usr/lib/python2.5/lib-dynload/_curses.so
b7cca000-b7ccb000 rw-p 0000f000 03:01 2131070   
/usr/lib/python2.5/lib-dynload/_curses.so
b7ccb000-b7ccf000 r-xp 00000000 03:01 2131043   
/usr/lib/python2.5/lib-dynload/collections.so
b7ccf000-b7cd0000 rw-p 00004000 03:01 2131043   
/usr/lib/python2.5/lib-dynload/collections.so
b7cd0000-b7cd3000 r-xp 00000000 03:01 2130051   
/usr/lib/python2.5/lib-dynload/cStringIO.so
b7cd3000-b7cd4000 rw-p 00003000 03:01 2130051   
/usr/lib/python2.5/lib-dynload/cStringIO.so
b7cd4000-b7cd7000 r-xp 00000000 03:01 2131687   
/usr/lib/python2.5/lib-dynload/time.so
b7cd7000-b7cd9000 rw-p 00002000 03:01 2131687   
/usr/lib/python2.5/lib-dynload/time.so
b7cd9000-b7cdb000 r-xp 00000000 03:01 2131679   
/usr/lib/python2.5/lib-dynload/fcntl.so
b7cdb000-b7cdc000 rw-p 00002000 03:01 2131679   
/usr/lib/python2.5/lib-dynload/fcntl.so
b7cdc000-b7ce0000 r-xp 00000000 03:01 2131685   
/usr/lib/python2.5/lib-dynload/strop.so
b7ce0000-b7ce2000 rw-p 00003000 03:01 2131685   
/usr/lib/python2.5/lib-dynload/strop.so
b7ce2000-b7ce9000 r--s 00000000 03:01 2115749   
/usr/lib/gconv/gconv-modules.cache
b7ce9000-b7d24000 r--p 00000000 03:01 2162690   
/usr/lib/locale/en_US.utf8/LC_CTYPE
b7d24000-b7da7000 rw-p b7d24000 00:00 0 
b7da7000-b7ee5000 r-xp 00000000 03:01 2362984   
/lib/tls/i686/nosegneg/libc-2.5.so
b7ee5000-b7ee6000 r--p 0013e000 03:01 2362984   
/lib/tls/i686/nosegneg/libc-2.5.so
b7ee6000-b7ee8000 rw-p 0013f000 03:01 2362984   
/lib/tls/i686/nosegneg/libc-2.5.so
b7ee8000-b7eeb000 rw-p b7ee8000 00:00 0 
b7eeb000-b7f10000 r-xp 00000000 03:01 2362988   
/lib/tls/i686/nosegneg/libm-2.5.so
b7f10000-b7f12000 rw-p 00024000 03:01 2362988   
/lib/tls/i686/nosegneg/libm-2.5.so
b7f12000-b7f14000 r-xp 00000000 03:01 2363003   
/lib/tls/i686/nosegneg/libutil-2.5.so
b7f14000-b7f16000 rw-p 00001000 03:01 2363003   
/lib/tls/i686/nosegneg/libutil-2.5.so
b7f16000-b7f17000 rw-p b7f16000 00:00 0 
b7f17000-b7f19000 r-xp 00000000 03:01 2362987   
/lib/tls/i686/nosegneg/libdl-2.5.so
b7f19000-b7f1b000 rw-p 00001000 03:01 2362987   
/lib/tls/i686/nosegneg/libdl-2.5.so
b7f1b000-b7f2f000 r-xp 00000000 03:01 2362998   
/lib/tls/i686/nosegneg/libpthread-2.5.so
b7f2f000-b7f31000 rw-p 00013000 03:01 2362998   
/lib/tls/i686/nosegneg/libpthread-2.5.so
b7f31000-b7f33000 rw-p b7f31000 00:00 0 
b7f35000-b7f37000 r-xp 00000000 03:01 2130047   
/usr/lib/python2.5/lib-dynload/_random.so
b7f37000-b7f38000 rw-p 00002000 03:01 2130047   
/usr/lib/python2.5/lib-dynload/_random.so
b7f38000-b7f3c000 r-xp 00000000 03:01 2131678   
/usr/lib/python2.5/lib-dynload/binascii.so
b7f3c000-b7f3d000 rw-p 00003000 03:01 2131678   
/usr/lib/python2.5/lib-dynload/binascii.so
b7f3d000-b7f40000 r-xp 00000000 03:01 2131682   
/usr/lib/python2.5/lib-dynload/math.so
b7f40000-b7f41000 rw-p 00002000 03:01 2131682   
/usr/lib/python2.5/lib-dynload/math.so
b7f41000-b7f46000 r-xp 00000000 03:01 2130050   
/usr/lib/python2.5/lib-dynload/_struct.so
b7f46000-b7f47000 rw-p 00005000 03:01 2130050   
/usr/lib/python2.5/lib-dynload/_struct.so
b7f47000-b7f49000 rw-p b7f47000 00:00 0 
b7f49000-b7f4a000 r-xp b7f49000 00:00 0          [vdso]
b7f4a000-b7f63000 r-xp 00000000 03:01 2359309    /lib/ld-2.5.so
b7f63000-b7f65000 rw-p 00019000 03:01 2359309    /lib/ld-2.5.so
bfc47000-bfc5d000 rw-p bfc47000 00:00 0          [stack]
No handlers could be found for logger "xend"
Error: Boot loader didn''t return any data!
Usage: xm create <ConfigFile> [options] [vars]

Create a domain based on <ConfigFile>.

Options:

-h, --help           Print this help.
--help_config        Print the available configuration variables (vars)
                     for the configuration script.
-q, --quiet          Quiet.
--path=PATH          Search path for configuration scripts. The value of
                     PATH is a colon-separated directory list.
-f=FILE, --defconfig=FILE
                     Use the given Python configuration script.The
                     configuration script is loaded after arguments have
                     been processed. Each command-line option sets a
                     configuration variable named after its long option
                     name, and these variables are placed in the
                     environment of the script before it is loaded.
                     Variables for options that may be repeated have list
                     values. Other variables can be set using VAR=VAL on
                     the command line. After the script is loaded, option
                     values that were not set on the command line are
                     replaced by the values set in the script.
-F=FILE, --config=FILE
                     Domain configuration to use (SXP).
                     SXP is the underlying configuration format used by
                     Xen.
                     SXP configurations can be hand-written or generated
                     from Python configuration scripts, using the -n
                     (dryrun) option to print the configuration.
-n, --dryrun         Dry run - prints the resulting configuration in SXP
                     but does not create the domain.
-p, --paused         Leave the domain paused after it is created.
-c, --console_autoconnect
                     Connect to the console after the domain is created.




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mark Williamson

2008-Apr-06 23:22 UTC

head link

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Hi,
> Using config file "xen501".
> *** glibc detected *** /usr/bin/python: double free or corruption (out):
> 0xb7d25100 ***
<snip scary backtrace>
> No handlers could be found for logger "xend"
> Error: Boot loader didn''t return any data!
> Usage: xm create <ConfigFile> [options] [vars]
<snip more output>

Yow!  That looks nasty.

Did you solve this?  It looks like the Python interpreter is crashing out for 
some reason - I can honestly say I''ve never seen that happen before!

If you''re still having troubles, it''d be good to know what
your host OS is,
what your Python version is and where you got your Xen install from.

Cheers,
Mark

-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

William Heath

2008-Apr-07 04:24 UTC

head link

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

I am on ubuntustudio 7.04 fesity.  I got my xen from using apt on ubuntu.
Python 2.5.1c1 (release25-maint, Apr 12 2007, 21:00:25).  What can I try to
get this to work?

On Sun, Apr 6, 2008 at 4:22 PM, Mark Williamson <
mark.williamson@cl.cam.ac.uk> wrote:
> Hi,
>
> > Using config file "xen501".
> > *** glibc detected *** /usr/bin/python: double free or corruption
(out):
> > 0xb7d25100 ***
>
> <snip scary backtrace>
>
> > No handlers could be found for logger "xend"
> > Error: Boot loader didn''t return any data!
> > Usage: xm create <ConfigFile> [options] [vars]
>
> <snip more output>
>
> Yow!  That looks nasty.
>
> Did you solve this?  It looks like the Python interpreter is crashing out
> for
> some reason - I can honestly say I''ve never seen that happen
before!
>
> If you''re still having troubles, it''d be good to know
what your host OS
> is,
> what your Python version is and where you got your Xen install from.
>
> Cheers,
> Mark
>
> --
> Push Me Pull You - Distributed SCM tool (
>
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmpu/>
> )
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Brent Verner

2008-Apr-07 05:04 UTC

head link

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

On Mon, Apr 7, 2008 at 12:24 AM, William Heath <wgheath@gmail.com>
wrote:> I am on ubuntustudio 7.04 fesity.  I got my xen from using apt on ubuntu.
> Python 2.5.1c1 (release25-maint, Apr 12 2007, 21:00:25).  What can I try to
> get this to work?
Hiya,

  I was seeing a similar error when trying to use pygrub to boot a NetBSD
domU.  It turned out that the bit of code that pulls the kernel from the image
doesn''t support 16k block size for FFS/UFS filesytems...

  What filesystem did you create on your install image?

cheers!
  Brent

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

William Heath

2008-Apr-07 06:04 UTC

head link

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Hi All,

I don''t know what kind of filesystem I have for my xen guest.  How can
I
tell please, would I use kpartx?

-Tim

On Sun, Apr 6, 2008 at 10:04 PM, Brent Verner <brent@netavail.com> wrote:
> On Mon, Apr 7, 2008 at 12:24 AM, William Heath <wgheath@gmail.com>
wrote:
> > I am on ubuntustudio 7.04 fesity.  I got my xen from using apt on
> ubuntu.
> > Python 2.5.1c1 (release25-maint, Apr 12 2007, 21:00:25).  What can I
try
> to
> > get this to work?
>
> Hiya,
>
>  I was seeing a similar error when trying to use pygrub to boot a NetBSD
> domU.  It turned out that the bit of code that pulls the kernel from the
> image
> doesn''t support 16k block size for FFS/UFS filesytems...
>
>  What filesystem did you create on your install image?
>
> cheers!
>   Brent
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mark Williamson

2008-Apr-13 16:37 UTC

head link

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

> I am on ubuntustudio 7.04 fesity.  I got my xen from using apt on ubuntu.
> Python 2.5.1c1 (release25-maint, Apr 12 2007, 21:00:25).  What can I try to
> get this to work?
Well, making sure your packages (both Xen-related and Python-related) are all 
up to date would probably be sensible at this point, in case there''s a
bug
that got fixed.

Cheers,
mark
> On Sun, Apr 6, 2008 at 4:22 PM, Mark Williamson <
>
> mark.williamson@cl.cam.ac.uk> wrote:
> > Hi,
> >
> > > Using config file "xen501".
> > > *** glibc detected *** /usr/bin/python: double free or corruption
> > > (out): 0xb7d25100 ***
> >
> > <snip scary backtrace>
> >
> > > No handlers could be found for logger "xend"
> > > Error: Boot loader didn''t return any data!
> > > Usage: xm create <ConfigFile> [options] [vars]
> >
> > <snip more output>
> >
> > Yow!  That looks nasty.
> >
> > Did you solve this?  It looks like the Python interpreter is crashing
out
> > for
> > some reason - I can honestly say I''ve never seen that happen
before!
> >
> > If you''re still having troubles, it''d be good to
know what your host OS
> > is,
> > what your Python version is and where you got your Xen install from.
> >
> > Cheers,
> > Mark
> >
> > --
> > Push Me Pull You - Distributed SCM tool (
> >
http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >u/> )


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mark Williamson

2008-Apr-13 16:50 UTC

head link

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

You''ve almost certainly got a ext3 filesystem on a CentOS 5.1 guest, so
I
wouldn''t have thought that this would be your problem...

An alternative that you could use to get the domain running would be:

* mount the partition on the virtual disk you installed the guest to (use 
kpartx or lomount to access the partitions, then safely mount it somewhere 
e.g. /mnt/guest)
* copy a vmlinuz-*xen* (a Xenified Linux kernel image, it''ll have a
name
following that pattern) and a initrd-*xen*.img with the same version number 
(a Xenified Linux initrd) out of the guest''s filesystem and onto the
host.
* unmount the guest partition
* Comment out the bootloader= line in your guest config for now.
* Set the kernel= and ramdisk= lines in the guest config to point to the 
locations of the files you just copied.
* Boot the guest.

This should start the guest''s kernel directly, instead of using pygrub
to poke
around in the guest filesystem, so it should work.  It''d still be nice
if we
could solve your problem with pygrub though; have you tried reporting this to 
the Ubuntu Xen package maintainers?  Did updating the system help with this?

You obviously mustn''t mount the guest''s filesystem if the
guest is running or
suspended (it has to be shut down), bear this in mind if you ever need to 
repeat the procedure described above.

Cheers,
Mark

On Monday 07 April 2008, William Heath wrote:> Hi All,
>
> I don''t know what kind of filesystem I have for my xen guest.  How
can I
> tell please, would I use kpartx?
>
> -Tim
>
> On Sun, Apr 6, 2008 at 10:04 PM, Brent Verner <brent@netavail.com>
wrote:
> > On Mon, Apr 7, 2008 at 12:24 AM, William Heath
<wgheath@gmail.com> wrote:
> > > I am on ubuntustudio 7.04 fesity.  I got my xen from using apt on
> >
> > ubuntu.
> >
> > > Python 2.5.1c1 (release25-maint, Apr 12 2007, 21:00:25).  What
can I
> > > try
> >
> > to
> >
> > > get this to work?
> >
> > Hiya,
> >
> >  I was seeing a similar error when trying to use pygrub to boot a
NetBSD
> > domU.  It turned out that the bit of code that pulls the kernel from
the
> > image
> > doesn''t support 16k block size for FFS/UFS filesytems...
> >
> >  What filesystem did you create on your install image?
> >
> > cheers!
> >   Brent

-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mark Williamson

2008-Apr-13 16:51 UTC

head link

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Brent,

What version of Xen were you using?  Where did you get it?  What host OS?

This is really a Xen bug that ought to be fixed (if it has not been fixed 
already), so I guess it''d be good to have more data on exactly what
might
have gone wrong, in case somebody comes across it again.

Cheers,
mark

On Monday 07 April 2008, Brent Verner wrote:> On Mon, Apr 7, 2008 at 12:24 AM, William Heath <wgheath@gmail.com>
wrote:
> > I am on ubuntustudio 7.04 fesity.  I got my xen from using apt on
ubuntu.
> > Python 2.5.1c1 (release25-maint, Apr 12 2007, 21:00:25).  What can I
try
> > to get this to work?
>
> Hiya,
>
>   I was seeing a similar error when trying to use pygrub to boot a NetBSD
> domU.  It turned out that the bit of code that pulls the kernel from the
> image doesn''t support 16k block size for FFS/UFS filesytems...
>
>   What filesystem did you create on your install image?
>
> cheers!
>   Brent


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Brent Verner

2008-Apr-13 21:56 UTC

head link

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

On Sun, Apr 13, 2008 at 12:51 PM, Mark Williamson
<mark.williamson@cl.cam.ac.uk> wrote:
>  What version of Xen were you using?  Where did you get it?  What host OS?
  I first tried this with the 3.2 packages from ubuntu hardy, but I also built
the tools from pristine xen sources and saw the same behaviour.
>  This is really a Xen bug that ought to be fixed (if it has not been fixed
>  already), so I guess it''d be good to have more data on exactly
what might
>  have gone wrong, in case somebody comes across it again.
  This isn''t a xen-specific bug.  The "bug" is that the code
used by pygrub,
which appears to have been largely lifted from grub, can''t read from a
16k
block size UFS/FFS filesystem; in fact, it appears that the 8k block size
is hardcoded in the code and no attempt is made to determine the actual
block size of the UFS filesystem.

  If you''re interested in seeing the bug in action, you can download
the
disk image(s) and a little script to trigger the bug from here:
  http://www.netavail.com/xen/pygrub-bug/

cheers,
  Brent

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Apr 2008 - Ubuntu feisty dom0 and centos 5.1 domU problems

[Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

RE: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems

Re: [Xen-users] Ubuntu feisty dom0 and centos 5.1 domU problems