I set up a private bridge on dom0 and then have the VMX domain use that
bridge. I use the private bridge to limit the error, so no copying off
system. I'm using a 2GB file for the test. I'm running on 32 and 64bit
SMP systems. I'm using a rhel3u5 Linux guest image, which is a 2.4
kernel. If I add any debugging in pcnet_receive(), it slows it down
enough for the transfer to work.
What environment are you testing in? What is your test case? Are you not
seeing the error anymore?
Is anyone else still seeing the issue like I am?
Since I've applied your patch, it fails quicker now - a few mbs into the
transfer rather than hundreds of mbs before.
I will try a linux 2.6 guest today.
On Mon, 2006-02-27 at 08:19 -0800, Kamble, Nitin A wrote:
> Hi Dan,
> If you are scping from different host, then it is possible that you
> are seeing the dom0 network issue in the vmx guest. Can you try scping
> the file from dom0 to vmx guest?
> Thanks & Regards,
> Open Source Technology Center, Intel Corp
> >-----Original Message-----
> >From: Daniel Stekloff [mailto:dsteklof@xxxxxxxxxx]
> >Sent: Saturday, February 25, 2006 7:46 AM
> >To: Li, Xin B
> >Cc: Kamble, Nitin A; Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxx
> >Subject: RE: [Xen-devel] [PATCH] Fox for pcnet device model data
> >On Sat, 2006-02-25 at 14:51 +0800, Li, Xin B wrote:
> >> >> Hi Ian,
> >> >>
> >> >> The attached patch fixes pcnet data corruption for VMX guests
> >> >> reported by you.
> >> >
> >> >
> >> >Hi Nitin,
> >> >
> >> >This doesn't fix the problem for me. If I try to transfer, with scp,
> >> >2gb file to DomU from Dom0, the transfer is disconnected with the
> >> >following error:
> >> >
> >> >Received disconnect from 192.168.1.3: 2: Corrupted MAC on input.
> >> This fix is to VMX domain only.
> >> -Xin
> >Yeah.. sorry if I wasn't specific in my comment, referring to DomU and
> >not VMX domain. But the comment remains.
> >This patch does not completely fix the race in qemu-dm for VMX domains.
> >I tested this patch on my SMP system and the corruption still happens.
> >couldn't successfully transfer a 2 gb file from Dom0 to a VMX domain.
> >The VMX domain is still seeing corruption.
Xen-devel mailing list