[Xen-users] Network buffering problem with remus

[agya naila <agya.naila@xxxxxxxxx>]

Dear all,

I used   Xen version: 4.2.2-pre compiled from sources with kernel 3.2.0-29-generic

~$ dmesg | grep Xen\ version

[    0.000000] Xen version: 4.2.2-pre (preserve-AD)

~$ uname -a

Linux comp1 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

I want to run remus, since 3.x kernel didn't have sch_plug module so I have to manually install it as suggested on this pages http://webcache.googleusercontent.com/search?q=cache:PO7wd7F6rksJ:benchmarktest.wordpress.com/2012/07/05/enabling-remus-on-xen-4-2-using-linux-3-x/+&cd=9&hl=en&ct=clnk&gl=id

However, the rems is running but the network buffering wasn't as I expected, it seem the network buffering not running properly. I found this discussion (http://remusha.wikidot.com/forum/t-459019) about sch_plug that have impact on network buffering, I try to apply the patch and even used the old sch_plug but seem its still not working.

 I have try to do simple measurement with ping command but still didn't got satisfying result.

Ping domU no migration :

C:\Users\rdc>ping 192.168.129.55 -t

Pinging 192.168.129.55 with 32 bytes of data:

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=2ms TTL=64

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=3ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=4ms TTL=64

Ping domU with migration but without network bufering :

C:\Users\rdc>ping 192.168.129.55 -t

Pinging 192.168.129.55 with 32 bytes of data:

Reply from 192.168.129.55: bytes=32 time=7ms TTL=64

Reply from 192.168.129.55: bytes=32 time=8ms TTL=64

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=11ms TTL=64

Reply from 192.168.129.55: bytes=32 time=3ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=3ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=3ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=2ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=2ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=12ms TTL=64

Ping domU with migration and network bufering :

C:\Users\rdc>ping 192.168.129.55 -t

Pinging 192.168.129.55 with 32 bytes of data:

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=6ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=4ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time=1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Reply from 192.168.129.55: bytes=32 time<1ms TTL=64

Here some sampe of remus output (with network buffering) :

user1@comp1:~$ sudo remus 1 10.10.10.3

WARNING: suspend event channel unavailable, falling back to slow xenstore signalling

PROF: suspending at 1362510384.568230

PROF: resumed at 1362510384.599588

PROF: flushed memory at 1362510384.625585

PROF: suspending at 1362510384.983182

PROF: resumed at 1362510385.008558

PROF: flushed memory at 1362510385.019639

PROF: suspending at 1362510385.399379

PROF: resumed at 1362510385.424484

PROF: flushed memory at 1362510385.429970

PROF: suspending at 1362510385.812891

PROF: resumed at 1362510385.841359

PROF: flushed memory at 1362510385.848946

PROF: suspending at 1362510386.223116

PROF: resumed at 1362510386.243883

PROF: flushed memory at 1362510386.254029

PROF: suspending at 1362510386.633252

PROF: resumed at 1362510386.660347

PROF: flushed memory at 1362510386.671028

PROF: suspending at 1362510387.045260

PROF: resumed at 1362510387.068308

PROF: flushed memory at 1362510387.078506

PROF: suspending at 1362510387.458226

Does anybody could help me with this problem?

Regards,

Agya

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