Perhaps try an older VirtIO driver in your zone; we’re using both Server 2016 and Windows 10 with VirtIO without any issues.
> On 22 Mar 2017, at 02:18, Patrick O'Sullivan via smartos-discuss > <[email protected]> wrote: > > Has anyone seen any issues with SmartOS, Windows 10, and a virtio NIC? > > Long story short... considering a virtualized instance of Windows 10 > for something at home and ran into issues with the NIC. Latest Red Hat > provided driver installed without issue but I can't pass any > meaningful traffic over the NIC. I removed all the spoofing, etc. > restrictions to rule out issues but still no dice. When I snoop the > traffic coming out of the zone, I just get a bit of IPv6 "background > radiation": > > [root@visor1 ~]# snoop -d net0 -z 93898b23-8656-e592-cf34-c1c493d4dba4 > 0a2:e4:2e:11:68:5b > Using device net0 (promiscuous mode) > UNSPECIFIED -> ff02::1:ffa3:e975 ICMPv6 Neighbor solicitation > fe80::7d64:d884:fa3:e975 -> ff02::2 ICMPv6 Router solicitation > fe80::7d64:d884:fa3:e975 -> ff02::16 ICMPv6 Group membership report - > MLDv2 > > No IPv4 traffic emanates from the zone when I inspect it this way. > > If I stop the zone/VM and change the NIC type to e1000, it works perfectly. > > I plan to start from scratch and make sure I didn't inadvertently do > anything odd, but if someone says "me too" it could be useful. > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
