[Differential] [Commented On] D1944: PF and VIMAGE fixes

2015-07-29 Thread rodrigc (Craig Rodrigues)
rodrigc added a comment.

@glebius: Nikos updated the patch.  Can you review it?


REVISION DETAIL
  https://reviews.freebsd.org/D1944

EMAIL PREFERENCES
  https://reviews.freebsd.org/settings/panel/emailpreferences/

To: nvass-gmx.com, bz, trociny, kristof, gnn, zec, rodrigc, glebius, eri
Cc: farrokhi, julian, robak, freebsd-virtualization-list, freebsd-pf-list, 
freebsd-net-list
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org


RE: MS DNS doesn't answer to CURRENT under Hyper-V

2015-07-29 Thread Wei Hu
Just committed the fix in releng/10.2 branch as r286058.

Wei


 -Original Message-
 From: Pavel Timofeev [mailto:tim...@gmail.com]
 Sent: Wednesday, July 29, 2015 3:48 PM
 To: Wei Hu w...@microsoft.com
 Cc: Slawa Olhovchenkov s...@zxy.spb.ru; freebsd-curr...@freebsd.org;
 freebsd-virtualization@freebsd.org
 Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V
 
 Hi!
 r285785 still isn't MFCed.
 RC2 is coming soon.
 
 2015-07-23 10:54 GMT+03:00 Pavel Timofeev tim...@gmail.com:
  Ok, sorry!
 
  2015-07-23 7:51 GMT+03:00 Wei Hu w...@microsoft.com:
  The TCP offloading is still working on these platforms. There is no flag to
 distinguish UDP and TCP offloading, so the RXCSUM and TXCSUM are still set.
 Let me know if there is any other way to show it properly.
 
  Thanks,
  Wei
 
 
  -Original Message-
  From: Pavel Timofeev [mailto:tim...@gmail.com]
  Sent: Wednesday, July 22, 2015 9:04 PM
  To: Wei Hu w...@microsoft.com
  Cc: Slawa Olhovchenkov s...@zxy.spb.ru; freebsd-
 curr...@freebsd.org;
  freebsd-virtualization@freebsd.org
  Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V
 
  Hi! I see you have done the code for disabling UDP checksum
  offloading when running on the Hyper-V on Windows Server 2012 and
  earlier hosts
 
  https://svnweb.freebsd.org/base?view=revisionrevision=285785
 
  I tried new CURRENT and it works. Thank you!
 
  A small note here: while it disables and works it still shows RXCSUM and
 TSCSUM in iface's options:
 
  root@proxy:/usr/src # ifconfig hn0
  hn0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric
 0 mtu 1500
 
 options=31bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,TSO6
  ether 00:15:5d:02:9c:09
  inet 192.168.25.26 netmask 0xffc0 broadcast 192.168.25.63
  nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
 
  Is it possible to hide it automatically if it's disabled by new code?
 
 
  2015-07-13 11:06 GMT+03:00 Wei Hu w...@microsoft.com:
  We have root caused the problem. This issue happens on the Hyper-Vs
 on Windows Server 2012 (Win 8.0) and earlier releases. On these releases,
 the UPD checksum offloading on host side does not work properly. The
 workaround is to disable UPD checksum offloading in the FreeBSD guest
 through 'ifconfig'. We are also working on a patch to turn off UPD checksum
 offloading in the netvsc driver when detecting the Hyper-V releases.
 
  The UDP checksum offloading works fine on Windows Server 2012R2 and
 Win 8.1 hosts.
 
  Thanks Pavel and Slawa for the support.
 
  Wei
 
 
  -Original Message-
  From: owner-freebsd-virtualizat...@freebsd.org
  [mailto:owner-freebsd- virtualizat...@freebsd.org] On Behalf Of
  Pavel Timofeev
  Sent: Wednesday, July 8, 2015 4:06 PM
  To: Slawa Olhovchenkov
  Cc: freebsd-curr...@freebsd.org; freebsd-virtualization@freebsd.org
  Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V
 
  Ok, r284746 is the root of the problem. MS DNS works under r284745
  and doesn't work under r284746.
  Slawa, what should I look at in wireshark output?
 
 
  2015-07-07 18:49 GMT+03:00 Slawa Olhovchenkov s...@zxy.spb.ru:
   On Tue, Jul 07, 2015 at 06:04:46PM +0300, Pavel Timofeev wrote:
  
   Well, turning off checksum offloading by `ifconfig hn0 -txcsum
   -rxcsum` definitely helps.
  
   As for tcpdump I'm not completely sure if I did it right, but I
   see bad udp cksum phrase:
  
   # tcpdump -i hn0 -vvv -nn udp dst port 53
   tcpdump: listening on hn0, link-type EN10MB (Ethernet), capture
   size
   262144 bytes
   18:01:19.139994 IP (tos 0x0, ttl 64, id 61218, offset 0, flags
   [none], proto UDP (17), length 51)
   192.168.25.26.45683  192.168.25.3.53: [bad udp cksum 0xb39e
   - 0xf210!] 52886+ A? ya.ru. (23)
   18:01:24.140544 IP (tos 0x0, ttl 64, id 17293, offset 0, flags
   [none], proto UDP (17), length 51)
   192.168.25.26.12575  192.168.25.3.53: [bad udp cksum 0xb39e
   - 0x7365!] 52886+ A? ya.ru. (23)
  
   tcpdump bad udp cksum is normal on FreeBSD host in case
   checksum offload (and may be need only for help finding issuse in
 code).
   Need wireshark capturing from MS DNS host (or from mirroring port).
  ___
  freebsd-virtualization@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
  To unsubscribe, send any mail to freebsd-virtualization-
  unsubscr...@freebsd.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org


Re: MS DNS doesn't answer to CURRENT under Hyper-V

2015-07-29 Thread Pavel Timofeev
Hi!
r285785 still isn't MFCed.
RC2 is coming soon.

2015-07-23 10:54 GMT+03:00 Pavel Timofeev tim...@gmail.com:
 Ok, sorry!

 2015-07-23 7:51 GMT+03:00 Wei Hu w...@microsoft.com:
 The TCP offloading is still working on these platforms. There is no flag to 
 distinguish UDP and TCP offloading, so the RXCSUM and TXCSUM are still set. 
 Let me know if there is any other way to show it properly.

 Thanks,
 Wei


 -Original Message-
 From: Pavel Timofeev [mailto:tim...@gmail.com]
 Sent: Wednesday, July 22, 2015 9:04 PM
 To: Wei Hu w...@microsoft.com
 Cc: Slawa Olhovchenkov s...@zxy.spb.ru; freebsd-curr...@freebsd.org; 
 freebsd-virtualization@freebsd.org
 Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V

 Hi! I see you have done the code for disabling UDP checksum offloading when 
 running on the Hyper-V on Windows Server 2012 and earlier hosts

 https://svnweb.freebsd.org/base?view=revisionrevision=285785

 I tried new CURRENT and it works. Thank you!

 A small note here: while it disables and works it still shows RXCSUM and 
 TSCSUM in iface's options:

 root@proxy:/usr/src # ifconfig hn0
 hn0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
 options=31bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,TSO6
 ether 00:15:5d:02:9c:09
 inet 192.168.25.26 netmask 0xffc0 broadcast 192.168.25.63
 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL

 Is it possible to hide it automatically if it's disabled by new code?


 2015-07-13 11:06 GMT+03:00 Wei Hu w...@microsoft.com:
 We have root caused the problem. This issue happens on the Hyper-Vs on 
 Windows Server 2012 (Win 8.0) and earlier releases. On these releases, the 
 UPD checksum offloading on host side does not work properly. The workaround 
 is to disable UPD checksum offloading in the FreeBSD guest through 
 'ifconfig'. We are also working on a patch to turn off UPD checksum 
 offloading in the netvsc driver when detecting the Hyper-V releases.

 The UDP checksum offloading works fine on Windows Server 2012R2 and Win 8.1 
 hosts.

 Thanks Pavel and Slawa for the support.

 Wei


 -Original Message-
 From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd-
 virtualizat...@freebsd.org] On Behalf Of Pavel Timofeev
 Sent: Wednesday, July 8, 2015 4:06 PM
 To: Slawa Olhovchenkov
 Cc: freebsd-curr...@freebsd.org; freebsd-virtualization@freebsd.org
 Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V

 Ok, r284746 is the root of the problem. MS DNS works under r284745
 and doesn't work under r284746.
 Slawa, what should I look at in wireshark output?


 2015-07-07 18:49 GMT+03:00 Slawa Olhovchenkov s...@zxy.spb.ru:
  On Tue, Jul 07, 2015 at 06:04:46PM +0300, Pavel Timofeev wrote:
 
  Well, turning off checksum offloading by `ifconfig hn0 -txcsum
  -rxcsum` definitely helps.
 
  As for tcpdump I'm not completely sure if I did it right, but I
  see bad udp cksum phrase:
 
  # tcpdump -i hn0 -vvv -nn udp dst port 53
  tcpdump: listening on hn0, link-type EN10MB (Ethernet), capture
  size
  262144 bytes
  18:01:19.139994 IP (tos 0x0, ttl 64, id 61218, offset 0, flags
  [none], proto UDP (17), length 51)
  192.168.25.26.45683  192.168.25.3.53: [bad udp cksum 0xb39e
  - 0xf210!] 52886+ A? ya.ru. (23)
  18:01:24.140544 IP (tos 0x0, ttl 64, id 17293, offset 0, flags
  [none], proto UDP (17), length 51)
  192.168.25.26.12575  192.168.25.3.53: [bad udp cksum 0xb39e
  - 0x7365!] 52886+ A? ya.ru. (23)
 
  tcpdump bad udp cksum is normal on FreeBSD host in case checksum
  offload (and may be need only for help finding issuse in code).
  Need wireshark capturing from MS DNS host (or from mirroring port).
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to freebsd-virtualization-
 unsubscr...@freebsd.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org


Re: troubles booting OpenBSD 5.7 or NetBSD 6.1.5 w/ grub2-bhyve

2015-07-29 Thread John-Mark Gurney
John-Mark Gurney wrote this message on Tue, Jul 28, 2015 at 12:36 -0700:
 I'm trying to run either Net or Open for some testing, and I'm not
 having luck.
 
 After first figuring out that the README on github doesn't include that
 you need to include the boot device to load the files from, I finally
 got kopenbsd and knetbsd loading, but when I run boot, it just drops
 me to a prompt w/o doing anything.

With a little bit of help (thanks @nahannisys), I managed to fix my
issues... I put up a blog entry at:
http://blog.funkthat.com/2015/07/installing-and-running-netbsd-and.html

that describes how I did both an install and boot of both NetBSD and
OpenBSD...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 All that I will do, has been done, All that I have, has not.
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org


RE: MS DNS doesn't answer to CURRENT under Hyper-V

2015-07-29 Thread Wei Hu
It is already in stable/10 branch. I am just about to send the request to
re@ for releng/10.2 commit approval.

Wei


-Original Message-
From: Pavel Timofeev [mailto:tim...@gmail.com] 
Sent: Wednesday, July 29, 2015 3:48 PM
To: Wei Hu w...@microsoft.com
Cc: Slawa Olhovchenkov s...@zxy.spb.ru; freebsd-curr...@freebsd.org; 
freebsd-virtualization@freebsd.org
Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V

Hi!
r285785 still isn't MFCed.
RC2 is coming soon.

2015-07-23 10:54 GMT+03:00 Pavel Timofeev tim...@gmail.com:
 Ok, sorry!

 2015-07-23 7:51 GMT+03:00 Wei Hu w...@microsoft.com:
 The TCP offloading is still working on these platforms. There is no flag to 
 distinguish UDP and TCP offloading, so the RXCSUM and TXCSUM are still set. 
 Let me know if there is any other way to show it properly.

 Thanks,
 Wei


 -Original Message-
 From: Pavel Timofeev [mailto:tim...@gmail.com]
 Sent: Wednesday, July 22, 2015 9:04 PM
 To: Wei Hu w...@microsoft.com
 Cc: Slawa Olhovchenkov s...@zxy.spb.ru; freebsd-curr...@freebsd.org; 
 freebsd-virtualization@freebsd.org
 Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V

 Hi! I see you have done the code for disabling UDP checksum 
 offloading when running on the Hyper-V on Windows Server 2012 and 
 earlier hosts

 https://svnweb.freebsd.org/base?view=revisionrevision=285785

 I tried new CURRENT and it works. Thank you!

 A small note here: while it disables and works it still shows RXCSUM and 
 TSCSUM in iface's options:

 root@proxy:/usr/src # ifconfig hn0
 hn0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
 options=31bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,TSO6
 ether 00:15:5d:02:9c:09
 inet 192.168.25.26 netmask 0xffc0 broadcast 192.168.25.63
 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL

 Is it possible to hide it automatically if it's disabled by new code?


 2015-07-13 11:06 GMT+03:00 Wei Hu w...@microsoft.com:
 We have root caused the problem. This issue happens on the Hyper-Vs on 
 Windows Server 2012 (Win 8.0) and earlier releases. On these releases, the 
 UPD checksum offloading on host side does not work properly. The workaround 
 is to disable UPD checksum offloading in the FreeBSD guest through 
 'ifconfig'. We are also working on a patch to turn off UPD checksum 
 offloading in the netvsc driver when detecting the Hyper-V releases.

 The UDP checksum offloading works fine on Windows Server 2012R2 and Win 8.1 
 hosts.

 Thanks Pavel and Slawa for the support.

 Wei


 -Original Message-
 From: owner-freebsd-virtualizat...@freebsd.org 
 [mailto:owner-freebsd- virtualizat...@freebsd.org] On Behalf Of 
 Pavel Timofeev
 Sent: Wednesday, July 8, 2015 4:06 PM
 To: Slawa Olhovchenkov
 Cc: freebsd-curr...@freebsd.org; freebsd-virtualization@freebsd.org
 Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V

 Ok, r284746 is the root of the problem. MS DNS works under r284745 
 and doesn't work under r284746.
 Slawa, what should I look at in wireshark output?


 2015-07-07 18:49 GMT+03:00 Slawa Olhovchenkov s...@zxy.spb.ru:
  On Tue, Jul 07, 2015 at 06:04:46PM +0300, Pavel Timofeev wrote:
 
  Well, turning off checksum offloading by `ifconfig hn0 -txcsum 
  -rxcsum` definitely helps.
 
  As for tcpdump I'm not completely sure if I did it right, but I 
  see bad udp cksum phrase:
 
  # tcpdump -i hn0 -vvv -nn udp dst port 53
  tcpdump: listening on hn0, link-type EN10MB (Ethernet), capture 
  size
  262144 bytes
  18:01:19.139994 IP (tos 0x0, ttl 64, id 61218, offset 0, flags 
  [none], proto UDP (17), length 51)
  192.168.25.26.45683  192.168.25.3.53: [bad udp cksum 0xb39e
  - 0xf210!] 52886+ A? ya.ru. (23)
  18:01:24.140544 IP (tos 0x0, ttl 64, id 17293, offset 0, flags 
  [none], proto UDP (17), length 51)
  192.168.25.26.12575  192.168.25.3.53: [bad udp cksum 0xb39e
  - 0x7365!] 52886+ A? ya.ru. (23)
 
  tcpdump bad udp cksum is normal on FreeBSD host in case 
  checksum offload (and may be need only for help finding issuse in code).
  Need wireshark capturing from MS DNS host (or from mirroring port).
 ___
 freebsd-virtualization@freebsd.org mailing list 
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to freebsd-virtualization- 
 unsubscr...@freebsd.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org