[Bug 206699] [Hyper-V]FreeBSD potential NULL pointer dereference in storage bounce buffer

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206699

Hongjiang  changed:

   What|Removed |Added

 CC||freebsd-virtualization@Free
   ||BSD.org,
   ||kyl...@microsoft.com,
   ||roy...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

RE: Hyper-V networking: problem after upgrade to 10.2

[Jac Backus]

Hello Dexuan,

Unfortunetely, no OACTIVE flag:

hn0: flags=8843 metric 0 mtu 1500
options=31b

With kind regards,

Jac

Van: Dexuan Cui [mailto:de...@microsoft.com]
Verzonden: woensdag 27 januari 2016 4:09
Aan: Sephe Qiao (Wicresoft); Jac Backus; Kylie Liang; 
'freebsd-virtualization@freebsd.org'; BSD Integration Components for Hyper-V
Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2

Hi Jac,
Please show 'ifconfig -a' when the issue happens (when you upgrade 10.1 from 
10.2).
We suspect it may be a known OACTIVE issue and "ifconfig -a' can confirm this, 
the output has the string "OACTIVE".

It looks somehow the issue doesn't happen when we use a 10.2 fresh installation.

Thanks,
-- Dexuan

From: Sephe Qiao (Wicresoft)
Sent: Wednesday, January 27, 2016 9:13
To: Jac Backus >; Dexuan 
Cui >; Kylie Liang 
>; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
Subject: RE: Hyper-V networking: problem after upgrade to 10.2

Oh, please ignore this, I think its solved :)

From: Sephe Qiao (Wicresoft)
Sent: Wednesday, January 27, 2016 9:10 AM
To: Jac Backus >; Dexuan 
Cui >; Kylie Liang 
>; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
Subject: RE: Hyper-V networking: problem after upgrade to 10.2

Hi Jac,

What's the output of 'ifconfig -a' when this happened?

Thanks,
sephe

From: Jac Backus [mailto:j.bac...@bugworks.com]
Sent: Tuesday, January 26, 2016 6:37 PM
To: Dexuan Cui >; Kylie Liang 
>; 
'freebsd-virtualization@freebsd.org' 
>;
 BSD Integration Components for Hyper-V 
>
Subject: RE: Hyper-V networking: problem after upgrade to 10.2


Hello Dexuan,



It seems, it is not completely correct, although the effect is as if it is not 
working.

Systat -ifstat 1 shows this:

[cid:image001.png@01D158E9.38DFF280]



So something is happening. But I can not reach anything. And the server can not 
be reached from the lan (hn0) or internet (hn1 and hn2).



I get a firewall message in /var/log/messages (first message from 11:18:55):

[cid:image002.png@01D158E9.38DFF280]

But this is just caused by the problem?



If I can help with further information, please let me know.



Regarding Bug 187006, all interfaces have fixed addresses.



With kind regards,



Jac







-Oorspronkelijk bericht-
Van: Dexuan Cui [mailto:de...@microsoft.com]
Verzonden: dinsdag 26 januari 2016 7:55
Aan: Kylie Liang; Jac Backus; 'freebsd-virtualization@freebsd.org'; BSD 
Integration Components for Hyper-V
Onderwerp: RE: Hyper-V networking: problem after upgrade to 10.2



Hi Jac,

BTW,  what do you mean by saying "networking does not work anymore" -- can you 
please check if your issue is the same as



Bug 187006 - [hyper-v] dynamic address (dhcp) obtaining doesn't work on HYPER-V 
OS 2012 R2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187006
 ?



Thanks,

-- Dexuan





> -Original Message-

> From: Dexuan Cui

> Sent: Tuesday, January 26, 2016 14:49

> To: Kylie Liang >; Jac 
> Backus

> >; 
> 'freebsd-virtualization@freebsd.org'

> >;
>  BSD Integration Components for

> Hyper-V >

> Subject: RE: Hyper-V networking: problem after upgrade to 10.2

>

> Hi Jac,

> Kylie meant disabling TSO. Please try this ("ifconfig hn0 -tso").

>

> The message " hn0: unknown status 1073872902 received" should be an

> unnecessary warning only.

> My 10.2 VM can work fine even if I see the message too.

>

> Can you please install a 10.2 VM from the 10.2 .ISO file directly as I

> did and see if it works for you?

>

> I guess we never tried upgrading 10.1 from 10.2.

> Can you