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

2015-07-30 Thread Wei Hu
-virtualizat...@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

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

2015-07-29 Thread Pavel Timofeev
; freebsd-current@freebsd.org; freebsd-virtualizat...@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

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

2015-07-29 Thread Wei Hu
...@zxy.spb.ru; freebsd-current@freebsd.org; freebsd-virtualizat...@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

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

2015-07-23 Thread Wei Hu
...@gmail.com] Sent: Wednesday, July 22, 2015 9:04 PM To: Wei Hu w...@microsoft.com Cc: Slawa Olhovchenkov s...@zxy.spb.ru; freebsd-current@freebsd.org; freebsd-virtualizat...@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

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

2015-07-23 Thread Pavel Timofeev
[mailto:owner-freebsd- virtualizat...@freebsd.org] On Behalf Of Pavel Timofeev Sent: Wednesday, July 8, 2015 4:06 PM To: Slawa Olhovchenkov Cc: freebsd-current@freebsd.org; freebsd-virtualizat...@freebsd.org Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V Ok, r284746 is the root

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

2015-07-22 Thread Pavel Timofeev
...@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

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

2015-07-22 Thread Pavel Timofeev
...@freebsd.org] On Behalf Of Pavel Timofeev Sent: Wednesday, July 8, 2015 4:06 PM To: Slawa Olhovchenkov Cc: freebsd-current@freebsd.org; freebsd-virtualizat...@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

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

2015-07-08 Thread Slawa Olhovchenkov
On Wed, Jul 08, 2015 at 11:05:39AM +0300, Pavel Timofeev wrote: 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? I think developers can want look at same packet before entering in NIC and after

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

2015-07-07 Thread Pavel Timofeev
No, I don't even know what VMDepot is, sorry! Didn't know ;) 2015-07-07 16:58 GMT+03:00 Glen Barber g...@freebsd.org: BTW, are you using the images from VMDepot? If so, this was MFC'd after the recent images. I can easily regenerate an updated image, if you are using those. Glen On Tue,

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

2015-07-07 Thread Slawa Olhovchenkov
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

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

2015-07-07 Thread Pavel Timofeev
Ok, I'll try r284745 and then r284746 and see what happens. 2015-07-07 16:06 GMT+03:00 Wei Hu w...@microsoft.com: -Original Message- From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd- virtualizat...@freebsd.org] On Behalf Of Pavel Timofeev Sent: Tuesday, July 7,

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

2015-07-07 Thread Pavel Timofeev
Wow, r284746 was MFCed to 10 STABLE! I should hurry up! 2015-07-07 16:26 GMT+03:00 Pavel Timofeev tim...@gmail.com: Ok, I'll try r284745 and then r284746 and see what happens. 2015-07-07 16:06 GMT+03:00 Wei Hu w...@microsoft.com: -Original Message- From:

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

2015-07-07 Thread Glen Barber
Sorry, I misread part of your email, and thought you were using Azure (which is Hyper-V based). Sorry for the noise. Glen On Tue, Jul 07, 2015 at 05:10:30PM +0300, Pavel Timofeev wrote: No, I don't even know what VMDepot is, sorry! Didn't know ;) 2015-07-07 16:58 GMT+03:00 Glen Barber

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

2015-07-07 Thread Slawa Olhovchenkov
On Tue, Jul 07, 2015 at 02:50:49PM +0300, Pavel Timofeev wrote: Hi! I have a test virtual machine which runs CURRENT under Hyper-V. It's amd64 r285198 now. It can't get any response from MS DNS server. Well, it could two or three weeks ago, but after upgrade it's not able to do it anymore.

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

2015-07-07 Thread Wei Hu
-Original Message- From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd- virtualizat...@freebsd.org] On Behalf Of Pavel Timofeev Sent: Tuesday, July 7, 2015 7:51 PM To: freebsd-current@freebsd.org; freebsd-virtualizat...@freebsd.org Subject: MS DNS doesn't answer to

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

2015-07-07 Thread Glen Barber
BTW, are you using the images from VMDepot? If so, this was MFC'd after the recent images. I can easily regenerate an updated image, if you are using those. Glen On Tue, Jul 07, 2015 at 04:55:39PM +0300, Pavel Timofeev wrote: Wow, r284746 was MFCed to 10 STABLE! I should hurry up!