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, Jul 07, 2015 at 04:55:39PM +0300, Pavel Timofeev wrote:
>> 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: 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-curr...@freebsd.org; freebsd-virtualization@freebsd.org
>> >>> Subject: MS DNS doesn't answer to CURRENT under Hyper-V
>> >>>
>> >>> 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.
>> >>> Google DNS answers without problems meanwhile (sic!).
>> >>>
>> >>> What I do:
>> >>> # host google.ru 192.168.25.3
>> >>> I see that MS DNS (192.168.25.3) server receives these packets, but 
>> >>> ignores
>> >>> them.
>> >>> And no matter how my system asks MS DNS. Every daemon can't get
>> >>> response too.
>> >>>
>> >>> I know that nothing was changed in MS DNS server. No doubt.
>> >>> Then I tried different available CURRENT snapshot ISOs.
>> >>>
>> >>> FreeBSD-11.0-CURRENT-amd64-20150630-r284969-disc1.iso - MS DNS does
>> >>> not answer.
>> >>>
>> >>> FreeBSD-11.0-CURRENT-amd64-20150625-r284814-disc1.iso - MS DNS does
>> >>> not answer.
>> >>>
>> >>> FreeBSD-11.0-CURRENT-amd64-20150618-r284544-disc1.iso - MS DNS
>> >>> answers!
>> >>>
>> >>> So something was committed to CURRENT between 20150618 and 20150625.
>> >>> This something ruins communication with MS DNS.
>> >>>
>> >> There was a commit for Hyper-V TSO and checksum offloading support  
>> >> (r284746) on
>> >> June 24th. I think this commit is the cause. Can you verify the MS DNS 
>> >> behavior between
>> >> The builds of June 23rd and 24th? I will take a look of this issue 
>> >> tomorrow.
>> >>
>> >> Thanks,
>> >> Wei
>> >>
>> >>
>> >>
>> _______________________________________________
>> 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"

Reply via email to