Hi Yin,

Sorry it took a while to respond.

I tried to test it on NanoServer.

A big problem we have is that the .NET framework isn't available in Nano. 
There are a few announcements around the topic, the most convincing one is:
https://windowsserver.uservoice.com/forums/295068-nano-server/suggestions/8106009-enable-full-net-framework-on-nano
 

Apparently, the go to .NET for Nano is .NET core:
https://docs.microsoft.com/en-us/dotnet/articles/core/index 
https://docs.microsoft.com/en-us/dotnet/articles/framework/docker/index 
https://docs.microsoft.com/en-us/dotnet/articles/framework/docker/console 

I tried compiling using .NET core, but unfortunately, I could not get it to 
compile. I think the infrastructure API's are missing. We could try using 
https://docs.microsoft.com/en-us/dotnet/articles/core/porting/ to see what is 
missing on all the versions (I only generated an output for version 1.1):
https://1drv.ms/u/s!ApveFU9IPhe1gxJVpaI_4fiufxNa

Build Output.
OvsDiscoveryService.cs(1,14): error CS0234: The type or namespace name 
'ServiceProcess' does not exist in the namespace 'System' (are you missing an 
assembly reference?)
OvsSwitchMonitor.cs(1,14): error CS0234: The type or namespace name 
'Management' does not exist in the namespace 'System' (are you missing an 
assembly reference?)
Program.cs(2,14): error CS0234: The type or namespace name 'ServiceProcess' 
does not exist in the namespace 'System' (are you missing an assembly 
reference?)
VirtualAdapter.cs(1,14): error CS0234: The type or namespace name 'Management' 
does not exist in the namespace 'System' (are you missing an assembly 
reference?)
VirtualAdapterManager.cs(3,14): error CS0234: The type or namespace name 
'Management' does not exist in the namespace 'System' (are you missing an 
assembly reference?)
VirtualAdapterMonitor.cs(3,14): error CS0234: The type or namespace name 
'Management' does not exist in the namespace 'System' (are you missing an 
assembly reference?)
WmiMonitor.cs(3,14): error CS0234: The type or namespace name 'Management' does 
not exist in the namespace 'System' (are you missing an assembly reference?)
WqlHelper.cs(2,14): error CS0234: The type or namespace name 'Management' does 
not exist in the namespace 'System' (are you missing an assembly reference?)
WqlObject.cs(2,14): error CS0234: The type or namespace name 'Management' does 
not exist in the namespace 'System' (are you missing an assembly reference?)
OvsDiscoveryService.cs(8,39): error CS0246: The type or namespace name 
'ServiceBase' could not be found (are you missing a using directive or an 
assembly reference?)
WqlObject.cs(38,59): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
WqlObject.cs(46,60): error CS0246: The type or namespace name 
'EventArrivedEventArgs' could not be found (are you missing a using directive 
or an assembly reference?)
WqlObject.cs(42,59): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
WqlObject.cs(50,59): error CS0246: The type or namespace name 
'EventArrivedEventArgs' could not be found (are you missing a using directive 
or an assembly reference?)
WmiMonitor.cs(20,16): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
OvsDiscoveryService.cs(52,33): error CS0115: 
'OvsDiscoveryService.OnStart(string[])': no suitable method found to override
OvsDiscoveryService.cs(62,33): error CS0115: 'OvsDiscoveryService.OnStop()': no 
suitable method found to override
WqlHelper.cs(11,23): error CS0246: The type or namespace name 
'ManagementEventWatcher' could not be found (are you missing a using directive 
or an assembly reference?)
WqlHelper.cs(15,23): error CS0246: The type or namespace name 
'ManagementEventWatcher' could not be found (are you missing a using directive 
or an assembly reference?)
WqlHelper.cs(20,23): error CS0246: The type or namespace name 
'ManagementEventWatcher' could not be found (are you missing a using directive 
or an assembly reference?)
WqlHelper.cs(33,23): error CS0246: The type or namespace name 
'ManagementObjectCollection' could not be found (are you missing a using 
directive or an assembly reference?)
WqlHelper.cs(38,23): error CS0246: The type or namespace name 
'ManagementObjectCollection' could not be found (are you missing a using 
directive or an assembly reference?)
WqlHelper.cs(42,23): error CS0246: The type or namespace name 
'ManagementObjectCollection' could not be found (are you missing a using 
directive or an assembly reference?)
WqlHelper.cs(46,23): error CS0246: The type or namespace name 
'ManagementObjectCollection' could not be found (are you missing a using 
directive or an assembly reference?)
WqlHelper.cs(68,81): error CS0246: The type or namespace name 'ManagementScope' 
could not be found (are you missing a using directive or an assembly reference?)
WqlHelper.cs(68,23): error CS0246: The type or namespace name 
'ManagementObject' could not be found (are you missing a using directive or an 
assembly reference?)
WqlHelper.cs(84,100): error CS0246: The type or namespace name 
'EventArrivedEventArgs' could not be found (are you missing a using directive 
or an assembly reference?)
WqlHelper.cs(84,29): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
WqlHelper.cs(84,51): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
WqlHelper.cs(103,41): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
WqlHelper.cs(103,73): error CS0246: The type or namespace name 
'ManagementScope' could not be found (are you missing a using directive or an 
assembly reference?)
WmiMonitor.cs(32,28): error CS0246: The type or namespace name 
'ManagementObjectCollection' could not be found (are you missing a using 
directive or an assembly reference?)
WmiMonitor.cs(33,28): error CS0246: The type or namespace name 
'ManagementEventWatcher' could not be found (are you missing a using directive 
or an assembly reference?)
WmiMonitor.cs(35,42): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
WmiMonitor.cs(141,63): error CS0246: The type or namespace name 
'EventArrivedEventArgs' could not be found (are you missing a using directive 
or an assembly reference?)
WmiMonitor.cs(191,19): error CS0246: The type or namespace name 
'ManagementEventWatcher' could not be found (are you missing a using directive 
or an assembly reference?)
VirtualAdapter.cs(21,16): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
Properties\Settings.Designer.cs(16,61): error CS0234: The type or namespace 
name 'Configuration' does not exist in the namespace 'System' (are you missing 
an assembly reference?)
OvsSwitchMonitor.cs(34,28): error CS0246: The type or namespace name 
'ManagementObjectCollection' could not be found (are you missing a using 
directive or an assembly reference?)
VirtualAdapterMonitor.cs(35,28): error CS0246: The type or namespace name 
'ManagementObjectCollection' could not be found (are you missing a using 
directive or an assembly reference?)
VirtualAdapterMonitor.cs(41,28): error CS0246: The type or namespace name 
'ManagementEventWatcher' could not be found (are you missing a using directive 
or an assembly reference?)
Properties\Settings.Designer.cs(26,25): error CS0234: The type or namespace 
name 'Configuration' does not exist in the namespace 'System' (are you missing 
an assembly reference?)
Properties\Settings.Designer.cs(28,25): error CS0234: The type or namespace 
name 'Configuration' does not exist in the namespace 'System' (are you missing 
an assembly reference?)
VirtualAdapterMonitor.cs(53,55): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
OvsSwitchMonitor.cs(45,50): error CS0246: The type or namespace name 
'ManagementBaseObject' could not be found (are you missing a using directive or 
an assembly reference?)
OvsSwitchMonitor.cs(66,28): error CS0246: The type or namespace name 
'ManagementEventWatcher' could not be found (are you missing a using directive 
or an assembly reference?)

> -----Original Message-----
> From: Yin Lin [mailto:[email protected]]
> Sent: Friday, January 13, 2017 9:17 PM
> To: Alin Serdean <[email protected]>;
> [email protected]
> Subject: RE: [ovs-dev] [PATCH] Windows: Implement Hyper-V VIF discovery
> agent.
> 
> Hi Alin,
> 
> No, I do not have a Nano server at hand. In fact, last time when I tested, our
> OVS driver doesn't work with Windows Server 2016. No traffic was going
> through and I hit BSOD frequently.
> 
> Best regards,
> Yin Lin
> 
> -----Original Message-----
> From: Alin Serdean [mailto:[email protected]]
> Sent: Thursday, January 12, 2017 8:30 AM
> To: Yin Lin <[email protected]>; [email protected]
> Subject: RE: [ovs-dev] [PATCH] Windows: Implement Hyper-V VIF discovery
> agent.
> 
> Thanks for the patch Yin.
> 
> It would be nice to add a commit message on why the agent is useful.
> 
> A quick question: did you test it with Nano?
> 
> Alin.
> 
> > -----Original Message-----
> > From: [email protected] [mailto:ovs-dev-
> > [email protected]] On Behalf Of Yin Lin
> > Sent: Wednesday, January 11, 2017 1:14 AM
> > To: [email protected]
> > Cc: Yin Lin <[email protected]>
> > Subject: [ovs-dev] [PATCH] Windows: Implement Hyper-V VIF discovery
> > agent.
> >
> > Signed-off-by: Yin Lin <[email protected]>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to