Hi all,
I have an interesting problem derivated from my other threads:
https://www.redhat.com/archives/rhelv5-list/2008-April/msg00111.html
https://www.redhat.com/archives/rhelv5-list/2008-April/msg00116.html
I have installed a new server with rhel5.1 x86_64 and xen. Afterwards, I have
installed another rhel5.1 x86_64 as a domU (paravirtualized).
When I try to copy a 465MB's or 650MB's file to domU, md5sum is ok. But when I
try to copy a 1GB file or more, md5sums are wrong. Same result if I try to copy
from domU. for example:
Original file md5sum is 89fbc4c7baafc0b0c05f0fa32c192a17 and it is ok.
- Launching scp command from my laptop to domU and destination is a folder on
domU:
2767e3c839a7a1688323f85826e3b442 win2k8stdeval.iso (it is wrong)
- launching scp command from domU to my laptop and destination is a folder on
domU:
b125e99f5c0c46bee71b1ef5cc1c039d win2k8stdeval.iso (it is wrong)
tx flag on domU is off.
Ok, If i try to copy the same iso file to dom0 or form dom0 like I explain for
domU, results are the same: md5sums are wrong. But If I start this server using
normal kernel (not xen enabled) all md5sums are ok (from host and to host).
Please, somebody from redhat can confirms me that this is a bug?? is it or
would be resolved on rhel5.2?? IMHO until this issue is not resolved, it isn't
safe to use rhel5-xen on production environments ....
Many thanks.
--
CL Martinez
carlopmart {at} gmail {d0t} com
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
