thr3ads.net - Xen users - Debian 6.0 with Remus(Xen 4.2) and Jeremy Kernel 2.6.32.57 does not work [Oct 2012]

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

D K

2012-Oct-02 08:31 UTC

Debian 6.0 with Remus(Xen 4.2) and Jeremy Kernel 2.6.32.57 does not work

Hallo Mailinglist:),
I have a question about using Remus and may be about Xen, because the way i use
Remus fails and I think it can be a Xen problem. I hope somebody of you have an
idea of what my problem is and may be have solution.

First I want to describe my enviroment:

Hardware:
PC: I have two Systems with completly identical Hardware
Network: Both Systems are connected by a Switch

Software:
OS: The fully updated Debian 6.0
Dom0 Kernel: I downloaded the Jeremy Kernel in the stable Version 2.6.32.57 with
the following config: http://pgb.game-host.org/xen/config
Xen: Version 4.2.-testing from git

Xen Guest:
OS: The fully updated Debian 6.0 without any modifications
Config: I used the following config http://pgb.game-host.org/xen/debian.cfg (for
simplicity I disabled the vif)

The problem:
The migration with xen works pretty good and without any problems.
I use the following command to create the guest:

xl create debian.cfg
Output:
Parsing config from debian.cfg
got a tsc mode string: "default"
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000-&gt;000000000019bb24
  TOTAL:         0000000000000000-&gt;000000001f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000000fb
  1GB PAGES: 0x0000000000000000
Daemon running with PID 3630

When I want to use remus for example with the following commandlist:
xl remus 6 129.217.43.54

He replicates the vm on the backup host with the following output:
migration target: Ready to receive domain.
Saving to migration stream new xl format (info 0x0/0x0/582)
Loading new save file  (new xl fmt info 0x0/0x0/582)
 Savefile contains xl domain config
got a tsc mode string: "default"

Then after waiting sometime sometimes after one second sometimes after 3 minutes
the following error occured on the primary host:
*** glibc detected *** xl: free(): invalid next size (normal): 0x08f05410 ***
======= Backtrace: ========/lib/i686/nosegneg/libc.so.6(+0x6c0d1)[0xb75560d1]
/lib/i686/nosegneg/libc.so.6(+0x6d928)[0xb7557928]
/lib/i686/nosegneg/libc.so.6(cfree+0x6d)[0xb755aa4d]
/usr/lib/libxenlight.so.2.0(+0x31d1a)[0xb76a8d1a]
/usr/lib/libxenlight.so.2.0(+0x37072)[0xb76ae072]
/usr/lib/libxenlight.so.2.0(+0x37e1b)[0xb76aee1b]
/usr/lib/libxenlight.so.2.0(+0x3848f)[0xb76af48f]
/usr/lib/libxenlight.so.2.0(libxl_domain_remus_start+0x194)[0xb768f2bf]
xl[0x805045e]
xl[0x804d2be]
/lib/i686/nosegneg/libc.so.6(__libc_start_main+0xe6)[0xb7500ca6]
xl[0x804cb91]
======= Memory map: =======08048000-08068000 r-xp 00000000 08:01 753904    
/usr/sbin/xl
08068000-0806a000 rw-p 0001f000 08:01 753904     /usr/sbin/xl
08dcc000-08f1c000 rw-p 00000000 00:00 0          [heap]
b7300000-b7321000 rw-p 00000000 00:00 0 
b7321000-b7400000 ---p 00000000 00:00 0 
b741a000-b744c000 rw-p 00000000 00:00 0 
b744c000-b7469000 r-xp 00000000 08:01 2342915    /lib/libgcc_s.so.1
b7469000-b746a000 rw-p 0001c000 08:01 2342915    /lib/libgcc_s.so.1
b747d000-b747e000 rw-p 00000000 00:00 0 
b747e000-b7491000 r-xp 00000000 08:01 2459916    /usr/lib/libz.so.1.2.3.4
b7491000-b7492000 rw-p 00013000 08:01 2459916    /usr/lib/libz.so.1.2.3.4
b7492000-b7493000 rw-p 00000000 00:00 0 
b7493000-b74a3000 r-xp 00000000 08:01 2342947    /lib/libbz2.so.1.0.4
b74a3000-b74a4000 rw-p 00010000 08:01 2342947    /lib/libbz2.so.1.0.4
b74a4000-b74a6000 r-xp 00000000 08:01 2369149   
/lib/i686/nosegneg/libdl-2.11.3.so
b74a6000-b74a7000 r--p 00001000 08:01 2369149   
/lib/i686/nosegneg/libdl-2.11.3.so
b74a7000-b74a8000 rw-p 00002000 08:01 2369149   
/lib/i686/nosegneg/libdl-2.11.3.so
b74a8000-b74ab000 r-xp 00000000 08:01 2342976    /lib/libuuid.so.1.3.0
b74ab000-b74ac000 rw-p 00002000 08:01 2342976    /lib/libuuid.so.1.3.0
b74ac000-b74ae000 r-xp 00000000 08:01 2369159   
/lib/i686/nosegneg/libutil-2.11.3.so
b74ae000-b74af000 r--p 00001000 08:01 2369159   
/lib/i686/nosegneg/libutil-2.11.3.so
b74af000-b74b0000 rw-p 00002000 08:01 2369159   
/lib/i686/nosegneg/libutil-2.11.3.so
b74b0000-b74b6000 r-xp 00000000 08:01 648516     /usr/lib/libblktapctl.so.1.0.0
b74b6000-b74b7000 rw-p 00005000 08:01 648516     /usr/lib/libblktapctl.so.1.0.0
b74b7000-b74b8000 rw-p 00000000 00:00 0 
b74b8000-b74bd000 r-xp 00000000 08:01 648500     /usr/lib/libxenstore.so.3.0.1
b74bd000-b74be000 rw-p 00004000 08:01 648500     /usr/lib/libxenstore.so.3.0.1
b74be000-b74c1000 rw-p 00000000 00:00 0 
b74c1000-b74e9000 r-xp 00000000 08:01 648496     /usr/lib/libxenguest.so.4.2.0
b74e9000-b74ea000 rw-p 00028000 08:01 648496     /usr/lib/libxenguest.so.4.2.0
b74ea000-b762e000 r-xp 00000000 08:01 2369168   
/lib/i686/nosegneg/libc-2.11.3.so
b762e000-b7630000 r--p 00144000 08:01 2369168   
/lib/i686/nosegneg/libc-2.11.3.so
b7630000-b7631000 rw-p 00146000 08:01 2369168   
/lib/i686/nosegneg/libc-2.11.3.so
b7631000-b7634000 rw-p 00000000 00:00 0 
b7634000-b7649000 r-xp 00000000 08:01 2369158   
/lib/i686/nosegneg/libpthread-2.11.3.so
b7649000-b764a000 r--p 00014000 08:01 2369158   
/lib/i686/nosegneg/libpthread-2.11.3.so
b764a000-b764b000 rw-p 00015000 08:01 2369158   
/lib/i686/nosegneg/libpthread-2.11.3.so
b764b000-b764d000 rw-p 00000000 00:00 0 
b764d000-b7654000 r-xp 00000000 08:01 648489     /usr/lib/libyajl.so.1.0.8
b7654000-b7655000 rw-p 00006000 08:01 648489     /usr/lib/libyajl.so.1.0.8
b7655000-b7656000 rw-p 00000000 00:00 0 
b7656000-b7676000 r-xp 00000000 08:01 647839     /usr/lib/libxenctrl.so.4.2.0
b7676000-b7677000 rw-p 0001f000 08:01 647839     /usr/lib/libxenctrl.so.4.2.0
b7677000-b76c6000 r-xp 00000000 08:01 648526     /usr/lib/libxenlight.so.2.0.0
b76c6000-b76c8000 rw-p 0004f000 08:01 648526     /usr/lib/libxenlight.so.2.0.0
b76c8000-b76d4000 r-xp 00000000 08:01 648530     /usr/lib/libxlutil.so.1.0.0
b76d4000-b76d5000 rw-p 0000b000 08:01 648530     /usr/lib/libxlutil.so.1.0.0
b76dd000-b76de000 ---p 00000000 00:00 0 
b76de000-b76e1000 rw-p 00000000 00:00 0 
b76e1000-b76e2000 ---p 00000000 00:00 0 
b76e2000-b76e6000 rw-p 00000000 00:00 0 
b76e6000-b76e7000 rw-p 00000000 00:00 0 
b76e7000-b76e8000 rw-p 00000000 00:00 0 
b76e8000-b76ec000 rw-p 00000000 00:00 0 
b76ec000-b76ed000 r-xp 00000000 00:00 0          [vdso]
b76ed000-b7708000 r-xp 00000000 08:01 2342928    /lib/ld-2.11.3.so
b7708000-b7709000 r--p 0001b000 08:01 2342928    /lib/ld-2.11.3.so
b7709000-b770a000 rw-p 0001c000 08:01 2342928    /lib/ld-2.11.3.so
bff6e000-bff83000 rw-p 00000000 00:00 0          [stack]
Abgebrochen
root@DKDebian2:/etc/xen# xc: error: 0-length read: Internal error
xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error
xc: error: Error when reading batch size (0 = Success): Internal error
xc: error: error when buffering batch, finishing (0 = Success): Internal error
migration target: Remus Failover for domain 5

I have no solution for this kind of problem and hope somebody can help me.

Thanks to everybody who will answer me :).

Best regards
Daniel


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

Lukas Laukamp

2012-Oct-02 09:39 UTC

head link

Re: Debian 6.0 with Remus(Xen 4.2) and Jeremy Kernel 2.6.32.57 does not work

Am 02.10.2012 10:31, schrieb D K:> Hallo Mailinglist:),
> I have a question about using Remus and may be about Xen, because the 
> way i use Remus fails and I think it can be a Xen problem. I hope 
> somebody of you have an idea of what my problem is and may be have 
> solution.
>
> First I want to describe my enviroment:
>
> Hardware:
> PC: I have two Systems with completly identical Hardware
> Network: Both Systems are connected by a Switch
>
> Software:
> OS: The fully updated Debian 6.0
> Dom0 Kernel: I downloaded the Jeremy Kernel in the stable Version 
> 2.6.32.57 with the following config: http://pgb.game-host.org/xen/config
> Xen: Version 4.2.-testing from git
>
> Xen Guest:
> OS: The fully updated Debian 6.0 without any modifications
> Config: I used the following config 
> http://pgb.game-host.org/xen/debian.cfg (for simplicity I disabled the 
> vif)
>
>
> The problem:
> The migration with xen works pretty good and without any problems.
> I use the following command to create the guest:
>
> xl create debian.cfg
> Output:
> Parsing config from debian.cfg
> got a tsc mode string: "default"
> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>   Loader:        0000000000100000->000000000019bb24
>   TOTAL:         0000000000000000->000000001f800000
>   ENTRY ADDRESS: 0000000000100000
> xc: info: PHYSICAL MEMORY ALLOCATION:
>   4KB PAGES: 0x0000000000000200
>   2MB PAGES: 0x00000000000000fb
>   1GB PAGES: 0x0000000000000000
> Daemon running with PID 3630
>
> When I want to use remus for example with the following commandlist:
> xl remus 6 129.217.43.54
>
> He replicates the vm on the backup host with the following output:
> migration target: Ready to receive domain.
> Saving to migration stream new xl format (info 0x0/0x0/582)
> Loading new save file <incoming migration stream> (new xl fmt info 
> 0x0/0x0/582)
>  Savefile contains xl domain config
> got a tsc mode string: "default"
>
> Then after waiting sometime sometimes after one second sometimes after 
> 3 minutes the following error occured on the primary host:
> *** glibc detected *** xl: free(): invalid next size (normal): 
> 0x08f05410 ***
> ======= Backtrace: ========>
/lib/i686/nosegneg/libc.so.6(+0x6c0d1)[0xb75560d1]
> /lib/i686/nosegneg/libc.so.6(+0x6d928)[0xb7557928]
> /lib/i686/nosegneg/libc.so.6(cfree+0x6d)[0xb755aa4d]
> /usr/lib/libxenlight.so.2.0(+0x31d1a)[0xb76a8d1a]
> /usr/lib/libxenlight.so.2.0(+0x37072)[0xb76ae072]
> /usr/lib/libxenlight.so.2.0(+0x37e1b)[0xb76aee1b]
> /usr/lib/libxenlight.so.2.0(+0x3848f)[0xb76af48f]
> /usr/lib/libxenlight.so.2.0(libxl_domain_remus_start+0x194)[0xb768f2bf]
> xl[0x805045e]
> xl[0x804d2be]
> /lib/i686/nosegneg/libc.so.6(__libc_start_main+0xe6)[0xb7500ca6]
> xl[0x804cb91]
> ======= Memory map: =======> 08048000-08068000 r-xp 00000000 08:01
753904     /usr/sbin/xl
> 08068000-0806a000 rw-p 0001f000 08:01 753904     /usr/sbin/xl
> 08dcc000-08f1c000 rw-p 00000000 00:00 0          [heap]
> b7300000-b7321000 rw-p 00000000 00:00 0
> b7321000-b7400000 ---p 00000000 00:00 0
> b741a000-b744c000 rw-p 00000000 00:00 0
> b744c000-b7469000 r-xp 00000000 08:01 2342915 /lib/libgcc_s.so.1
> b7469000-b746a000 rw-p 0001c000 08:01 2342915 /lib/libgcc_s.so.1
> b747d000-b747e000 rw-p 00000000 00:00 0
> b747e000-b7491000 r-xp 00000000 08:01 2459916 /usr/lib/libz.so.1.2.3.4
> b7491000-b7492000 rw-p 00013000 08:01 2459916 /usr/lib/libz.so.1.2.3.4
> b7492000-b7493000 rw-p 00000000 00:00 0
> b7493000-b74a3000 r-xp 00000000 08:01 2342947 /lib/libbz2.so.1.0.4
> b74a3000-b74a4000 rw-p 00010000 08:01 2342947 /lib/libbz2.so.1.0.4
> b74a4000-b74a6000 r-xp 00000000 08:01 2369149 
> /lib/i686/nosegneg/libdl-2.11.3.so
> b74a6000-b74a7000 r--p 00001000 08:01 2369149 
> /lib/i686/nosegneg/libdl-2.11.3.so
> b74a7000-b74a8000 rw-p 00002000 08:01 2369149 
> /lib/i686/nosegneg/libdl-2.11.3.so
> b74a8000-b74ab000 r-xp 00000000 08:01 2342976 /lib/libuuid.so.1.3.0
> b74ab000-b74ac000 rw-p 00002000 08:01 2342976 /lib/libuuid.so.1.3.0
> b74ac000-b74ae000 r-xp 00000000 08:01 2369159 
> /lib/i686/nosegneg/libutil-2.11.3.so
> b74ae000-b74af000 r--p 00001000 08:01 2369159 
> /lib/i686/nosegneg/libutil-2.11.3.so
> b74af000-b74b0000 rw-p 00002000 08:01 2369159 
> /lib/i686/nosegneg/libutil-2.11.3.so
> b74b0000-b74b6000 r-xp 00000000 08:01 648516 
> /usr/lib/libblktapctl.so.1.0.0
> b74b6000-b74b7000 rw-p 00005000 08:01 648516 
> /usr/lib/libblktapctl.so.1.0.0
> b74b7000-b74b8000 rw-p 00000000 00:00 0
> b74b8000-b74bd000 r-xp 00000000 08:01 648500 /usr/lib/libxenstore.so.3.0.1
> b74bd000-b74be000 rw-p 00004000 08:01 648500 /usr/lib/libxenstore.so.3.0.1
> b74be000-b74c1000 rw-p 00000000 00:00 0
> b74c1000-b74e9000 r-xp 00000000 08:01 648496 /usr/lib/libxenguest.so.4.2.0
> b74e9000-b74ea000 rw-p 00028000 08:01 648496 /usr/lib/libxenguest.so.4.2.0
> b74ea000-b762e000 r-xp 00000000 08:01 2369168 
> /lib/i686/nosegneg/libc-2.11.3.so
> b762e000-b7630000 r--p 00144000 08:01 2369168 
> /lib/i686/nosegneg/libc-2.11.3.so
> b7630000-b7631000 rw-p 00146000 08:01 2369168 
> /lib/i686/nosegneg/libc-2.11.3.so
> b7631000-b7634000 rw-p 00000000 00:00 0
> b7634000-b7649000 r-xp 00000000 08:01 2369158 
> /lib/i686/nosegneg/libpthread-2.11.3.so
> b7649000-b764a000 r--p 00014000 08:01 2369158 
> /lib/i686/nosegneg/libpthread-2.11.3.so
> b764a000-b764b000 rw-p 00015000 08:01 2369158 
> /lib/i686/nosegneg/libpthread-2.11.3.so
> b764b000-b764d000 rw-p 00000000 00:00 0
> b764d000-b7654000 r-xp 00000000 08:01 648489 /usr/lib/libyajl.so.1.0.8
> b7654000-b7655000 rw-p 00006000 08:01 648489 /usr/lib/libyajl.so.1.0.8
> b7655000-b7656000 rw-p 00000000 00:00 0
> b7656000-b7676000 r-xp 00000000 08:01 647839 /usr/lib/libxenctrl.so.4.2.0
> b7676000-b7677000 rw-p 0001f000 08:01 647839 /usr/lib/libxenctrl.so.4.2.0
> b7677000-b76c6000 r-xp 00000000 08:01 648526 /usr/lib/libxenlight.so.2.0.0
> b76c6000-b76c8000 rw-p 0004f000 08:01 648526 /usr/lib/libxenlight.so.2.0.0
> b76c8000-b76d4000 r-xp 00000000 08:01 648530 /usr/lib/libxlutil.so.1.0.0
> b76d4000-b76d5000 rw-p 0000b000 08:01 648530 /usr/lib/libxlutil.so.1.0.0
> b76dd000-b76de000 ---p 00000000 00:00 0
> b76de000-b76e1000 rw-p 00000000 00:00 0
> b76e1000-b76e2000 ---p 00000000 00:00 0
> b76e2000-b76e6000 rw-p 00000000 00:00 0
> b76e6000-b76e7000 rw-p 00000000 00:00 0
> b76e7000-b76e8000 rw-p 00000000 00:00 0
> b76e8000-b76ec000 rw-p 00000000 00:00 0
> b76ec000-b76ed000 r-xp 00000000 00:00 0          [vdso]
> b76ed000-b7708000 r-xp 00000000 08:01 2342928 /lib/ld-2.11.3.so
> b7708000-b7709000 r--p 0001b000 08:01 2342928 /lib/ld-2.11.3.so
> b7709000-b770a000 rw-p 0001c000 08:01 2342928 /lib/ld-2.11.3.so
> bff6e000-bff83000 rw-p 00000000 00:00 0          [stack]
> Abgebrochen
> root@DKDebian2:/etc/xen# xc: error: 0-length read: Internal error
> xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error
> xc: error: Error when reading batch size (0 = Success): Internal error
> xc: error: error when buffering batch, finishing (0 = Success): 
> Internal error
> migration target: Remus Failover for domain 5
>
> I have no solution for this kind of problem and hope somebody can help me.
>
> Thanks to everybody who will answer me :).
>
> Best regards
> Daniel
>
>
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
Hey Daniel,

for me it looks like a libc6 related problem. Which version of libc6 do 
you use and have you tried to backport or install the libc6 version from 
Wheezy or Sid?

Best Regards


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

Daniel Knobe

2012-Oct-11 14:03 UTC

head link

Re: Debian 6.0 with Remus(Xen 4.2) and Jeremy Kernel 2.6.32.57 does not work

Hi,
thank you for the fast answer:) and sorry for my late answer.

I used the paket: libc6-dev (2.11.3-4) from default Debian stable tree. 
I tested the same scenario with Ubuntu 12.04 now and it results in the 
same error. Ubuntu 12.04 uses the paket: libc6 (2.15-0ubuntu10.2).

It seems not to be the problem. Have you or somebody another idea where 
the problem can be?

Best regards,
Daniel

Am 02.10.2012 11:39, schrieb Lukas Laukamp:> Am 02.10.2012 10:31, schrieb D K:
>> Hallo Mailinglist:),
>> I have a question about using Remus and may be about Xen, because the 
>> way i use Remus fails and I think it can be a Xen problem. I hope 
>> somebody of you have an idea of what my problem is and may be have 
>> solution.
>>
>> First I want to describe my enviroment:
>>
>> Hardware:
>> PC: I have two Systems with completly identical Hardware
>> Network: Both Systems are connected by a Switch
>>
>> Software:
>> OS: The fully updated Debian 6.0
>> Dom0 Kernel: I downloaded the Jeremy Kernel in the stable Version 
>> 2.6.32.57 with the following config:
http://pgb.game-host.org/xen/config
>> Xen: Version 4.2.-testing from git
>>
>> Xen Guest:
>> OS: The fully updated Debian 6.0 without any modifications
>> Config: I used the following config 
>> http://pgb.game-host.org/xen/debian.cfg (for simplicity I disabled 
>> the vif)
>>
>>
>> The problem:
>> The migration with xen works pretty good and without any problems.
>> I use the following command to create the guest:
>>
>> xl create debian.cfg
>> Output:
>> Parsing config from debian.cfg
>> got a tsc mode string: "default"
>> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>>   Loader:        0000000000100000->000000000019bb24
>>   TOTAL:         0000000000000000->000000001f800000
>>   ENTRY ADDRESS: 0000000000100000
>> xc: info: PHYSICAL MEMORY ALLOCATION:
>>   4KB PAGES: 0x0000000000000200
>>   2MB PAGES: 0x00000000000000fb
>>   1GB PAGES: 0x0000000000000000
>> Daemon running with PID 3630
>>
>> When I want to use remus for example with the following commandlist:
>> xl remus 6 129.217.43.54
>>
>> He replicates the vm on the backup host with the following output:
>> migration target: Ready to receive domain.
>> Saving to migration stream new xl format (info 0x0/0x0/582)
>> Loading new save file <incoming migration stream> (new xl fmt
info
>> 0x0/0x0/582)
>>  Savefile contains xl domain config
>> got a tsc mode string: "default"
>>
>> Then after waiting sometime sometimes after one second sometimes 
>> after 3 minutes the following error occured on the primary host:
>> *** glibc detected *** xl: free(): invalid next size (normal): 
>> 0x08f05410 ***
>> ======= Backtrace: ========>>
/lib/i686/nosegneg/libc.so.6(+0x6c0d1)[0xb75560d1]
>> /lib/i686/nosegneg/libc.so.6(+0x6d928)[0xb7557928]
>> /lib/i686/nosegneg/libc.so.6(cfree+0x6d)[0xb755aa4d]
>> /usr/lib/libxenlight.so.2.0(+0x31d1a)[0xb76a8d1a]
>> /usr/lib/libxenlight.so.2.0(+0x37072)[0xb76ae072]
>> /usr/lib/libxenlight.so.2.0(+0x37e1b)[0xb76aee1b]
>> /usr/lib/libxenlight.so.2.0(+0x3848f)[0xb76af48f]
>> /usr/lib/libxenlight.so.2.0(libxl_domain_remus_start+0x194)[0xb768f2bf]
>> xl[0x805045e]
>> xl[0x804d2be]
>> /lib/i686/nosegneg/libc.so.6(__libc_start_main+0xe6)[0xb7500ca6]
>> xl[0x804cb91]
>> ======= Memory map: =======>> 08048000-08068000 r-xp 00000000
08:01 753904 /usr/sbin/xl
>> 08068000-0806a000 rw-p 0001f000 08:01 753904 /usr/sbin/xl
>> 08dcc000-08f1c000 rw-p 00000000 00:00 0          [heap]
>> b7300000-b7321000 rw-p 00000000 00:00 0
>> b7321000-b7400000 ---p 00000000 00:00 0
>> b741a000-b744c000 rw-p 00000000 00:00 0
>> b744c000-b7469000 r-xp 00000000 08:01 2342915 /lib/libgcc_s.so.1
>> b7469000-b746a000 rw-p 0001c000 08:01 2342915 /lib/libgcc_s.so.1
>> b747d000-b747e000 rw-p 00000000 00:00 0
>> b747e000-b7491000 r-xp 00000000 08:01 2459916 /usr/lib/libz.so.1.2.3.4
>> b7491000-b7492000 rw-p 00013000 08:01 2459916 /usr/lib/libz.so.1.2.3.4
>> b7492000-b7493000 rw-p 00000000 00:00 0
>> b7493000-b74a3000 r-xp 00000000 08:01 2342947 /lib/libbz2.so.1.0.4
>> b74a3000-b74a4000 rw-p 00010000 08:01 2342947 /lib/libbz2.so.1.0.4
>> b74a4000-b74a6000 r-xp 00000000 08:01 2369149 
>> /lib/i686/nosegneg/libdl-2.11.3.so
>> b74a6000-b74a7000 r--p 00001000 08:01 2369149 
>> /lib/i686/nosegneg/libdl-2.11.3.so
>> b74a7000-b74a8000 rw-p 00002000 08:01 2369149 
>> /lib/i686/nosegneg/libdl-2.11.3.so
>> b74a8000-b74ab000 r-xp 00000000 08:01 2342976 /lib/libuuid.so.1.3.0
>> b74ab000-b74ac000 rw-p 00002000 08:01 2342976 /lib/libuuid.so.1.3.0
>> b74ac000-b74ae000 r-xp 00000000 08:01 2369159 
>> /lib/i686/nosegneg/libutil-2.11.3.so
>> b74ae000-b74af000 r--p 00001000 08:01 2369159 
>> /lib/i686/nosegneg/libutil-2.11.3.so
>> b74af000-b74b0000 rw-p 00002000 08:01 2369159 
>> /lib/i686/nosegneg/libutil-2.11.3.so
>> b74b0000-b74b6000 r-xp 00000000 08:01 648516 
>> /usr/lib/libblktapctl.so.1.0.0
>> b74b6000-b74b7000 rw-p 00005000 08:01 648516 
>> /usr/lib/libblktapctl.so.1.0.0
>> b74b7000-b74b8000 rw-p 00000000 00:00 0
>> b74b8000-b74bd000 r-xp 00000000 08:01 648500 
>> /usr/lib/libxenstore.so.3.0.1
>> b74bd000-b74be000 rw-p 00004000 08:01 648500 
>> /usr/lib/libxenstore.so.3.0.1
>> b74be000-b74c1000 rw-p 00000000 00:00 0
>> b74c1000-b74e9000 r-xp 00000000 08:01 648496 
>> /usr/lib/libxenguest.so.4.2.0
>> b74e9000-b74ea000 rw-p 00028000 08:01 648496 
>> /usr/lib/libxenguest.so.4.2.0
>> b74ea000-b762e000 r-xp 00000000 08:01 2369168 
>> /lib/i686/nosegneg/libc-2.11.3.so
>> b762e000-b7630000 r--p 00144000 08:01 2369168 
>> /lib/i686/nosegneg/libc-2.11.3.so
>> b7630000-b7631000 rw-p 00146000 08:01 2369168 
>> /lib/i686/nosegneg/libc-2.11.3.so
>> b7631000-b7634000 rw-p 00000000 00:00 0
>> b7634000-b7649000 r-xp 00000000 08:01 2369158 
>> /lib/i686/nosegneg/libpthread-2.11.3.so
>> b7649000-b764a000 r--p 00014000 08:01 2369158 
>> /lib/i686/nosegneg/libpthread-2.11.3.so
>> b764a000-b764b000 rw-p 00015000 08:01 2369158 
>> /lib/i686/nosegneg/libpthread-2.11.3.so
>> b764b000-b764d000 rw-p 00000000 00:00 0
>> b764d000-b7654000 r-xp 00000000 08:01 648489 /usr/lib/libyajl.so.1.0.8
>> b7654000-b7655000 rw-p 00006000 08:01 648489 /usr/lib/libyajl.so.1.0.8
>> b7655000-b7656000 rw-p 00000000 00:00 0
>> b7656000-b7676000 r-xp 00000000 08:01 647839
/usr/lib/libxenctrl.so.4.2.0
>> b7676000-b7677000 rw-p 0001f000 08:01 647839
/usr/lib/libxenctrl.so.4.2.0
>> b7677000-b76c6000 r-xp 00000000 08:01 648526 
>> /usr/lib/libxenlight.so.2.0.0
>> b76c6000-b76c8000 rw-p 0004f000 08:01 648526 
>> /usr/lib/libxenlight.so.2.0.0
>> b76c8000-b76d4000 r-xp 00000000 08:01 648530
/usr/lib/libxlutil.so.1.0.0
>> b76d4000-b76d5000 rw-p 0000b000 08:01 648530
/usr/lib/libxlutil.so.1.0.0
>> b76dd000-b76de000 ---p 00000000 00:00 0
>> b76de000-b76e1000 rw-p 00000000 00:00 0
>> b76e1000-b76e2000 ---p 00000000 00:00 0
>> b76e2000-b76e6000 rw-p 00000000 00:00 0
>> b76e6000-b76e7000 rw-p 00000000 00:00 0
>> b76e7000-b76e8000 rw-p 00000000 00:00 0
>> b76e8000-b76ec000 rw-p 00000000 00:00 0
>> b76ec000-b76ed000 r-xp 00000000 00:00 0          [vdso]
>> b76ed000-b7708000 r-xp 00000000 08:01 2342928 /lib/ld-2.11.3.so
>> b7708000-b7709000 r--p 0001b000 08:01 2342928 /lib/ld-2.11.3.so
>> b7709000-b770a000 rw-p 0001c000 08:01 2342928 /lib/ld-2.11.3.so
>> bff6e000-bff83000 rw-p 00000000 00:00 0          [stack]
>> Abgebrochen
>> root@DKDebian2:/etc/xen# xc: error: 0-length read: Internal error
>> xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal
error
>> xc: error: Error when reading batch size (0 = Success): Internal error
>> xc: error: error when buffering batch, finishing (0 = Success): 
>> Internal error
>> migration target: Remus Failover for domain 5
>>
>> I have no solution for this kind of problem and hope somebody can 
>> help me.
>>
>> Thanks to everybody who will answer me :).
>>
>> Best regards
>> Daniel
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>
> Hey Daniel,
>
> for me it looks like a libc6 related problem. Which version of libc6 
> do you use and have you tried to backport or install the libc6 version 
> from Wheezy or Sid?
>
> Best Regards


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

Xen users - Oct 2012 - Debian 6.0 with Remus(Xen 4.2) and Jeremy Kernel 2.6.32.57 does not work

Debian 6.0 with Remus(Xen 4.2) and Jeremy Kernel 2.6.32.57 does not work

Re: Debian 6.0 with Remus(Xen 4.2) and Jeremy Kernel 2.6.32.57 does not work

Re: Debian 6.0 with Remus(Xen 4.2) and Jeremy Kernel 2.6.32.57 does not work