Bug 1085624

Hi Yan,

   Unfortunately this job could not pass even if I set 'ip link set dev macvtap$ allmulticast on' and got the same issue.Upload the latest HCK file to this bug.

build info
build79
kernel-3.10.0-121.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64

Thanks
Min

Created attachment 888705 [details]
win2012R2hckfile

Created attachment 888709 [details]
win2012-HCK-LOG

Hi

I have a couple of questions

1. How do you create macvtab devices? Would you mind to share the setup scripts?

2. It is possible that the test failures are caused by packet losses outside of the guest Windows. Do you set txqueuelen parameters? Please, notice that txqueuelen parameter has to be set both on macvtap device and bridge/interface where the macvtap device is created.


   Regards,

      Joseph Hindin

  Re-test the bug on build 109 with macvtap env,the issue still could be reproduced and upload the log to the bug as well.

(In reply to dengmin from comment #15)
>   Re-test the bug on build 109 with macvtap env,the issue still could be
> reproduced and upload the log to the bug as well.

When you say build 109, what do you mean?  What host kernel version did you use?

The original bug was filed agains 3.10.0-113.  The most recent rhel7.2 kernel
available is kernel-3.10.0-315.el7.

-vlad

(In reply to Vlad Yasevich from comment #17)
> (In reply to dengmin from comment #15)
> >   Re-test the bug on build 109 with macvtap env,the issue still could be
> > reproduced and upload the log to the bug as well.
> 
> When you say build 109, what do you mean?  What host kernel version did you
> use?
> 
> The original bug was filed agains 3.10.0-113.  The most recent rhel7.2 kernel
> available is kernel-3.10.0-315.el7.
> 
> -vlad

109 is the virtio-win build number (https://brewweb.devel.redhat.com/buildinfo?buildID=451410).

But definitely what interest us here is kernel version and not the driver version.

(In reply to Yan Vugenfirer from comment #18)
> (In reply to Vlad Yasevich from comment #17)
> > (In reply to dengmin from comment #15)
> > >   Re-test the bug on build 109 with macvtap env,the issue still could be
> > > reproduced and upload the log to the bug as well.
> > 
> > When you say build 109, what do you mean?  What host kernel version did you
> > use?
> > 
> > The original bug was filed agains 3.10.0-113.  The most recent rhel7.2 kernel
> > available is kernel-3.10.0-315.el7.
> > 
> > -vlad
> 
> 109 is the virtio-win build number
> (https://brewweb.devel.redhat.com/buildinfo?buildID=451410).
> 
> But definitely what interest us here is kernel version and not the driver
> version.

     The kernel version is kernel-3.10.0-3.10.0-300.el7.x86_64 and qemu-kvm-rhev-2.3.0-13.el7.x86_64 when I run this job,need QE re-run it on the latest one ? Thanks

Min

(In reply to dengmin from comment #19)
> (In reply to Yan Vugenfirer from comment #18)
> > (In reply to Vlad Yasevich from comment #17)
> > > (In reply to dengmin from comment #15)
> > > >   Re-test the bug on build 109 with macvtap env,the issue still could be
> > > > reproduced and upload the log to the bug as well.
> > > 
> > > When you say build 109, what do you mean?  What host kernel version did you
> > > use?
> > > 
> > > The original bug was filed agains 3.10.0-113.  The most recent rhel7.2 kernel
> > > available is kernel-3.10.0-315.el7.
> > > 
> > > -vlad
> > 
> > 109 is the virtio-win build number
> > (https://brewweb.devel.redhat.com/buildinfo?buildID=451410).
> > 
> > But definitely what interest us here is kernel version and not the driver
> > version.
> 
>      The kernel version is kernel-3.10.0-3.10.0-300.el7.x86_64 and
> qemu-kvm-rhev-2.3.0-13.el7.x86_64 when I run this job,need QE re-run it on
> the latest one ? Thanks
> 
> Min

  I will re-tested it on the latest kernel build&qemu-kvm-rhev build and will update the results as soon as finishing.

(In reply to dengmin from comment #20)
> (In reply to dengmin from comment #19)
> > (In reply to Yan Vugenfirer from comment #18)
> > > (In reply to Vlad Yasevich from comment #17)
> > > > (In reply to dengmin from comment #15)
> > > > >   Re-test the bug on build 109 with macvtap env,the issue still could be
> > > > > reproduced and upload the log to the bug as well.
> > > > 
> > > > When you say build 109, what do you mean?  What host kernel version did you
> > > > use?
> > > > 
> > > > The original bug was filed agains 3.10.0-113.  The most recent rhel7.2 kernel
> > > > available is kernel-3.10.0-315.el7.
> > > > 
> > > > -vlad
> > > 
> > > 109 is the virtio-win build number
> > > (https://brewweb.devel.redhat.com/buildinfo?buildID=451410).
> > > 
> > > But definitely what interest us here is kernel version and not the driver
> > > version.
> > 
> >      The kernel version is kernel-3.10.0-3.10.0-300.el7.x86_64 and
> > qemu-kvm-rhev-2.3.0-13.el7.x86_64 when I run this job,need QE re-run it on
> > the latest one ? Thanks
> > 
> > Min
> 
>   I will re-tested it on the latest kernel build&qemu-kvm-rhev build and
> will update the results as soon as finishing.

  Re-tested the bug on the following builds
  kernel-3.10.0-315.el7.x86_64
  qemu-kvm-rhev-2.3.0-22.el7.x86_64
  virtio-win-prewhql-0.1-109
  Still can reproduce the issue,thanks!

According to
https://bugzilla.redhat.com/show_bug.cgi?id=1413467

the problem is not reproduced on latest builds. Please clarify and close the bug if not actual

(In reply to ybendito from comment #23)
> According to
> https://bugzilla.redhat.com/show_bug.cgi?id=1413467
> 
> the problem is not reproduced on latest builds. Please clarify and close the
> bug if not actual

This bug track this issues under macvtap configuration;
bug1413467 is under bridge configuration,QE will try with latest build to check if it still can be reproduced.

keep the needinfo for me,will update it when finish.

This job can pass with latest 139 build.
So this issue has been fixed.

Closing based on comment #25