Re: bhyve windows guest unable to ping default gateway or external networks
On Nov 15, 2016 5:58 AM, wrote: > > Hello, > > I am trying to get a windows server VM running under bhyve. So far I can use VNC to install Windows, but I've been unable to get the networking working. I will provide details below, and include a summary up here. On the guest, I have installed the latest version of winvirtio, and I have configured static IP addressing. The guest can ping itself, but not the host machine or anything external. It is worth noting that I am also currently running a CentOS guest, and this can connect to both the host and the outside world with no issues. > > Host: FreeBSD 11.0-RELEASE > Guest: Tried both Windows Server 2016 Essentials and Windows Server 2012 Standard > > bhyve command: > bhyve -c 1 -H -w -m 3G -s 0,hostbridge -s 3,ahci-cd,/iohyve/ISO// -s '4,ahci-hd,/dev/zvol/zroot/iohyve/win12/disk0,sectorsize=512' -s 10,virtio-net,tap2 -s '11,fbuf,tcp=0.0.0.0:5902,w=800,h=600,wait' -s 12,xhci,tablet -s 31,lpc -l com1,/dev/nmdm3A -l bootrom,/iohyve/Firmware/BHYVE_UEFI.fd/BHYVE_UEFI.fd ioh-win12 > > ifconfig output: > em0: flags=8843 metric 0 mtu 1500 > options=4219b > ether e0:69:95:a2:f1:d9 > inet 46.105.xxx.xxx netmask 0xff00 broadcast 46.105.124.255 > inet6 fe80::e269:95ff::f1d9%em0 prefixlen 64 scopeid 0x1 > inet6 2001:41d0:2:::1 prefixlen 56 > nd6 options=21 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 metric 0 mtu 16384 > options=63 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff00 > nd6 options=21 > groups: lo > bridge0: flags=8843 metric 0 mtu 1500 > ether 02:cf:0c:8f:13:00 > inet6 fd00:: prefixlen 112 > inet 10.0.0.254 netmask 0xff00 broadcast 10.0.0.255 > nd6 options=1 > groups: bridge > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap2 flags=143 > ifmaxaddr 0 port 7 priority 128 path cost 200 > member: tap1 flags=143 > ifmaxaddr 0 port 5 priority 128 path cost 200 > member: tap0 flags=143 > ifmaxaddr 0 port 4 priority 128 path cost 200 > pflog0: flags=0<> metric 0 mtu 33160 > groups: pflog > tap0: flags=8943 metric 0 mtu 1500 > description: iohyve-centos > options=8 > ether 00:bd:5d:d3:e8:00 > nd6 options=21 > media: Ethernet autoselect > status: active > groups: tap > Opened by PID 96206 > tap1: flags=8902 metric 0 mtu 1500 > description: iohyve-win16es > options=8 > ether 00:bd:61:ab:eb:01 > nd6 options=21 > media: Ethernet autoselect > status: no carrier > groups: tap > tap2: flags=8943 metric 0 mtu 1500 > description: iohyve-win12 > options=8 > ether 00:bd:c9:1a:59:02 > nd6 options=21 > media: Ethernet autoselect > status: active > groups: tap > Opened by PID 1911 > > It is using NAT with PF to reach the internet. It should not rely on NAT to be able to ping the host machine, but I will post the NAT configuration below anyway: > > /etc/pf.conf: > # Automatically NAT any VMs > nat on em0 inet from bridge0:network to any -> (em0) > > > (On the Guest) > == > > C:\Users\Administrator>ipconfig > > Ethernet adapter Ethernet: > > IPv4 Address: 10.0.0.3 > Subnet Mask: 255.255.255.0 > Default Gateway: 10.0.0.254 > > C:\Users\Administrator>ping 10.0.0.3 > > Pinging 10.0.0.3 with 32 bytes of data: > Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 > Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 > Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 > Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 > > C:\Users\Administrator>ping 10.0.0.254 > > Pinging 10.0.0.254 with 32 bytes of data: > Reply from 10.0.0.3: Destination host unreachable. > Reply from 10.0.0.3: Destination host unreachable. > Reply from 10.0.0.3: Destination host unreachable. > Reply from 10.0.0.3: Destination host unreachable. > > C:\Users\Administrator>arp -a > > Interface: 10.0.0.3 --- 0xc > Internet Address Physical AddressType > 10.0.0.255ff-ff-ff-ff-ff-ff static > 224.0.0.2201-00-5e-00-00-16 static > 224.0.0.252 01-00-5e-00-00-fc static > > (PF log testing) > > > I was curious to see if PF was seeing packets on the bridge interface, so I added the following to /etc/pf.conf: > pass log (all) all > > I then ran the following command, which had no results when I tried a test ping: > sudo tcpdump -n -e -ttt -i pflog0 host 10.0.0.3
Re: bhyve windows guest unable to ping default gateway or external networks
Hello, and thanks for the suggestion. I ran the following: sudo ifconfig em0 -rxcsum -txcsum -vlanmtu -vlanhwcsum -vlanhwtso -tso4 which resulted in ifconfig showing: em0: flags=8843 metric 0 mtu 1500 options=2098 It looks like it removed rxcsum, txcsum, vlanhwtso and tso, but vlanhwcsum and vlan_mtu were not removed. At this pointed I started up the VM and performed the same tests, but unfortunately the results were still the same. I then directly applied your config to my ifconfig_em0 line, resulting in this rc.conf entry: ifconfig_em0="inet 46.105.xxx.xxx netmask 0xff00 -rxcsum -txcsum -vlanmtu -vlanhwtso -tso4 -tso6 -vlanhwtso -vlanhwcsum" Upon rebooting my ifconfig output was still the same as before the reboot. Just to be sure it didn't fix it, I booted up the VM again and tried to ping the default gateway, and it failed. November 15, 2016 12:07 PM, "Rajil Saraswat" wrote: On Nov 15, 2016 5:58 AM, wrote: > > Hello, > > I am trying to get a windows server VM running under bhyve. So far I can use > VNC to install Windows, but I've been unable to get the networking working. I > will provide details below, and include a summary up here. On the guest, I > have installed the latest version of winvirtio, and I have configured static > IP addressing. The guest can ping itself, but not the host machine or > anything external. It is worth noting that I am also currently running a > CentOS guest, and this can connect to both the host and the outside world > with no issues. > > Host: FreeBSD 11.0-RELEASE > Guest: Tried both Windows Server 2016 Essentials and Windows Server 2012 > Standard > > bhyve command: > bhyve -c 1 -H -w -m 3G -s 0,hostbridge -s 3,ahci-cd,/iohyve/ISO// -s > '4,ahci-hd,/dev/zvol/zroot/iohyve/win12/disk0,sectorsize=512' -s > 10,virtio-net,tap2 -s '11,fbuf,tcp=0.0.0.0:5902 > (http://0.0.0.0:5902),w=800,h=600,wait' -s 12,xhci,tablet -s 31,lpc -l > com1,/dev/nmdm3A -l bootrom,/iohyve/Firmware/BHYVE_UEFI.fd/BHYVE_UEFI.fd > ioh-win12 > > ifconfig output: > em0: flags=8843 metric 0 mtu 1500 > options=4219b > ether e0:69:95:a2:f1:d9 > inet 46.105.xxx.xxx netmask 0xff00 broadcast 46.105.124.255 > inet6 fe80::e269:95ff::f1d9%em0 prefixlen 64 scopeid 0x1 > inet6 2001:41d0:2:::1 prefixlen 56 > nd6 options=21 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 metric 0 mtu 16384 > options=63 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff00 > nd6 options=21 > groups: lo > bridge0: flags=8843 metric 0 mtu 1500 > ether 02:cf:0c:8f:13:00 > inet6 fd00:: prefixlen 112 > inet 10.0.0.254 netmask 0xff00 broadcast 10.0.0.255 > nd6 options=1 > groups: bridge > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap2 flags=143 > ifmaxaddr 0 port 7 priority 128 path cost 200 > member: tap1 flags=143 > ifmaxaddr 0 port 5 priority 128 path cost 200 > member: tap0 flags=143 > ifmaxaddr 0 port 4 priority 128 path cost 200 > pflog0: flags=0 metric 0 mtu 33160 > groups: pflog > tap0: flags=8943 metric 0 mtu 1500 > description: iohyve-centos > options=8 > ether 00:bd:5d:d3:e8:00 > nd6 options=21 > media: Ethernet autoselect > status: active > groups: tap > Opened by PID 96206 > tap1: flags=8902 metric 0 mtu 1500 > description: iohyve-win16es > options=8 > ether 00:bd:61:ab:eb:01 > nd6 options=21 > media: Ethernet autoselect > status: no carrier > groups: tap > tap2: flags=8943 metric 0 mtu 1500 > description: iohyve-win12 > options=8 > ether 00:bd:c9:1a:59:02 > nd6 options=21 > media: Ethernet autoselect > status: active > groups: tap > Opened by PID 1911 > > It is using NAT with PF to reach the internet. It should not rely on NAT to > be able to ping the host machine, but I will post the NAT configuration below > anyway: > > /etc/pf.conf: > # Automatically NAT any VMs > nat on em0 inet from bridge0:network to any -> (em0) > > > (On the Guest) > == > > C:UsersAdministrator>ipconfig > > Ethernet adapter Ethernet: > > IPv4 Address: 10.0.0.3 > Subnet Mask: 255.255.255.0 > Default Gateway: 10.0.0.254 > > C:UsersAdministrator>ping 10.0.0.3 > > Pinging 10.0.0.3 with 32 bytes of data: > Reply from 10.0.0.3 (http://10.0.0.3): bytes=32 time Reply from 10.0.0.3 > (http://10.0.0.3): bytes=32 time Reply from 10.0.0.3 (http://10.0.0.3): > bytes=32 time Reply from 10.0.0.3 (http://10.0.0.3): bytes=32 time > C:UsersAdministrator>ping 10.0.0.254 > > Pinging 10.0.0.254 with 32 bytes of data: > Reply from 10.0.0.3 (http://10.0.0.3): Destination host unreachable. > Reply from 10.0.0.3 (http://10.0.0.3): Destination host unreachable. > Reply from 10.0.0.3 (http://10.0.0.3): Destination host unreachable. > Reply from 10.0.0.3 (http://10.0.0.3): Destination host unreachable. > > C:UsersAdministrator>arp -a > > Interface: 10.0.0
Re: bhyve windows guest unable to ping default gateway or external networks
On Tue, Nov 15, 2016 at 11:58:29AM +, free...@jonathanprice.org wrote: > Hello, > > I am trying to get a windows server VM running under bhyve. So far I can use > VNC to install Windows, but I've been unable to get the networking working. I > will provide details below, and include a summary up here. On the guest, I > have installed the latest version of winvirtio, and I have configured static > IP addressing. The guest can ping itself, but not the host machine or > anything external. It is worth noting that I am also currently running a > CentOS guest, and this can connect to both the host and the outside world > with no issues. > > Host: FreeBSD 11.0-RELEASE > Guest: Tried both Windows Server 2016 Essentials and Windows Server 2012 > Standard > > bhyve command: > bhyve -c 1 -H -w -m 3G -s 0,hostbridge -s 3,ahci-cd,/iohyve/ISO// -s > '4,ahci-hd,/dev/zvol/zroot/iohyve/win12/disk0,sectorsize=512' -s > 10,virtio-net,tap2 -s '11,fbuf,tcp=0.0.0.0:5902,w=800,h=600,wait' -s > 12,xhci,tablet -s 31,lpc -l com1,/dev/nmdm3A -l > bootrom,/iohyve/Firmware/BHYVE_UEFI.fd/BHYVE_UEFI.fd ioh-win12 > I noticed something here. In my setup phase for Windows 2016 DC , I used /usr/sbin/bhyve -A -c 4 -m 4G -w -H -s 3,ahci-cd,./.iso/virtio-win-0.1.96.iso -s 4,ahci-hd,windows2016.img -s 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd windows2016guest & Have you install the red-hat virtual ethernet driver? > ifconfig output: > em0: flags=8843 metric 0 mtu 1500 > > options=4219b > ether e0:69:95:a2:f1:d9 > inet 46.105.xxx.xxx netmask 0xff00 broadcast 46.105.124.255 > inet6 fe80::e269:95ff::f1d9%em0 prefixlen 64 scopeid 0x1 > inet6 2001:41d0:2:::1 prefixlen 56 > nd6 options=21 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 metric 0 mtu 16384 > options=63 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff00 > nd6 options=21 > groups: lo > bridge0: flags=8843 metric 0 mtu 1500 > ether 02:cf:0c:8f:13:00 > inet6 fd00:: prefixlen 112 > inet 10.0.0.254 netmask 0xff00 broadcast 10.0.0.255 > nd6 options=1 > groups: bridge > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap2 flags=143 > ifmaxaddr 0 port 7 priority 128 path cost 200 > member: tap1 flags=143 > ifmaxaddr 0 port 5 priority 128 path cost 200 > member: tap0 flags=143 > ifmaxaddr 0 port 4 priority 128 path cost 200 > pflog0: flags=0<> metric 0 mtu 33160 > groups: pflog > tap0: flags=8943 metric 0 mtu > 1500 > description: iohyve-centos > options=8 > ether 00:bd:5d:d3:e8:00 > nd6 options=21 > media: Ethernet autoselect > status: active > groups: tap > Opened by PID 96206 > tap1: flags=8902 metric 0 mtu 1500 > description: iohyve-win16es > options=8 > ether 00:bd:61:ab:eb:01 > nd6 options=21 > media: Ethernet autoselect > status: no carrier > groups: tap > tap2: flags=8943 metric 0 mtu > 1500 > description: iohyve-win12 > options=8 > ether 00:bd:c9:1a:59:02 > nd6 options=21 > media: Ethernet autoselect > status: active > groups: tap > Opened by PID 1911 > > It is using NAT with PF to reach the internet. It should not rely on NAT to > be able to ping the host machine, but I will post the NAT configuration below > anyway: > > /etc/pf.conf: > # Automatically NAT any VMs > nat on em0 inet from bridge0:network to any -> (em0) > > > (On the Guest) > == > > C:\Users\Administrator>ipconfig > > Ethernet adapter Ethernet: > > IPv4 Address: 10.0.0.3 > Subnet Mask: 255.255.255.0 > Default Gateway: 10.0.0.254 > > C:\Users\Administrator>ping 10.0.0.3 > > Pinging 10.0.0.3 with 32 bytes of data: > Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 > Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 > Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 > Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 > > C:\Users\Administrator>ping 10.0.0.254 > > Pinging 10.0.0.254 with 32 bytes of data: > Reply from 10.0.0.3: Destination host unreachable. > Reply from 10.0.0.3: Destination host unreachable. > Reply from 10.0.0.3: Destination host unreachable. > Reply from 10.0.0.3: Destination host unreachable. > > C:\Users\Administrator>arp -a > > Interface: 10.0.0.3 --- 0xc > Internet AddressPhysical Address
Re: bhyve windows guest unable to ping default gateway or external networks
Hi, A good spot, my launch command doesn't include the virtio-win ISO that contains the RedHat net-kvm driver. However, this is mostly just due to a limitation in iohyve (or my understanding of it at least) in that it can only mount a single CD at once. I did in fact install the driver, by running "iohyve install win16 virtio-win.iso" which then mounted it for that session. However, successive "iohyve start win16" invocations did not continue to mount this ISO. In particular, I used virtio-win-0.1.126.iso with driver net-kvm/windows 2k16/amd64 for my attempt with Server 2016 and the 2k12r2/amd64 driver for Server 2012 R2. Thanks, Jonathan. On 15/11/2016 15:00, The Doctor wrote: > On Tue, Nov 15, 2016 at 11:58:29AM +, free...@jonathanprice.org wrote: >> Hello, >> >> I am trying to get a windows server VM running under bhyve. So far I can use >> VNC to install Windows, but I've been unable to get the networking working. >> I will provide details below, and include a summary up here. On the guest, I >> have installed the latest version of winvirtio, and I have configured static >> IP addressing. The guest can ping itself, but not the host machine or >> anything external. It is worth noting that I am also currently running a >> CentOS guest, and this can connect to both the host and the outside world >> with no issues. >> >> Host: FreeBSD 11.0-RELEASE >> Guest: Tried both Windows Server 2016 Essentials and Windows Server 2012 >> Standard >> >> bhyve command: >> bhyve -c 1 -H -w -m 3G -s 0,hostbridge -s 3,ahci-cd,/iohyve/ISO// -s >> '4,ahci-hd,/dev/zvol/zroot/iohyve/win12/disk0,sectorsize=512' -s >> 10,virtio-net,tap2 -s '11,fbuf,tcp=0.0.0.0:5902,w=800,h=600,wait' -s >> 12,xhci,tablet -s 31,lpc -l com1,/dev/nmdm3A -l >> bootrom,/iohyve/Firmware/BHYVE_UEFI.fd/BHYVE_UEFI.fd ioh-win12 >> > > I noticed something here. > > In my setup phase for Windows 2016 DC , > > I used > > > /usr/sbin/bhyve -A -c 4 -m 4G -w -H -s > 3,ahci-cd,./.iso/virtio-win-0.1.96.iso -s 4,ahci-hd,windows2016.img -s > 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd windows2016guest & > > Have you install the red-hat virtual ethernet driver? > >> ifconfig output: >> em0: flags=8843 metric 0 mtu 1500 >> >> options=4219b >> ether e0:69:95:a2:f1:d9 >> inet 46.105.xxx.xxx netmask 0xff00 broadcast 46.105.124.255 >> inet6 fe80::e269:95ff::f1d9%em0 prefixlen 64 scopeid 0x1 >> inet6 2001:41d0:2:::1 prefixlen 56 >> nd6 options=21 >> media: Ethernet autoselect (100baseTX ) >> status: active >> lo0: flags=8049 metric 0 mtu 16384 >> options=63 >> inet6 ::1 prefixlen 128 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 >> inet 127.0.0.1 netmask 0xff00 >> nd6 options=21 >> groups: lo >> bridge0: flags=8843 metric 0 mtu 1500 >> ether 02:cf:0c:8f:13:00 >> inet6 fd00:: prefixlen 112 >> inet 10.0.0.254 netmask 0xff00 broadcast 10.0.0.255 >> nd6 options=1 >> groups: bridge >> id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 >> maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 >> root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 >> member: tap2 flags=143 >> ifmaxaddr 0 port 7 priority 128 path cost 200 >> member: tap1 flags=143 >> ifmaxaddr 0 port 5 priority 128 path cost 200 >> member: tap0 flags=143 >> ifmaxaddr 0 port 4 priority 128 path cost 200 >> pflog0: flags=0<> metric 0 mtu 33160 >> groups: pflog >> tap0: flags=8943 metric 0 >> mtu 1500 >> description: iohyve-centos >> options=8 >> ether 00:bd:5d:d3:e8:00 >> nd6 options=21 >> media: Ethernet autoselect >> status: active >> groups: tap >> Opened by PID 96206 >> tap1: flags=8902 metric 0 mtu 1500 >> description: iohyve-win16es >> options=8 >> ether 00:bd:61:ab:eb:01 >> nd6 options=21 >> media: Ethernet autoselect >> status: no carrier >> groups: tap >> tap2: flags=8943 metric 0 >> mtu 1500 >> description: iohyve-win12 >> options=8 >> ether 00:bd:c9:1a:59:02 >> nd6 options=21 >> media: Ethernet autoselect >> status: active >> groups: tap >> Opened by PID 1911 >> >> It is using NAT with PF to reach the internet. It should not rely on NAT to >> be able to ping the host machine, but I will post the NAT configuration >> below anyway: >> >> /etc/pf.conf: >> # Automatically NAT any VMs >> nat on em0 inet from bridge0:network to any -> (em0) >> >> >> (On the Guest) >> == >> >> C:\Users\Administrator>ipconfig >> >> Ethernet adapter Ether
Re: bhyve windows guest unable to ping default gateway or external networks
If it's a bug, I don't believe it's in the virtio stack. I'm using Chelsio NICs on my bhyve servers, and I don't have to disable anything for my guests to work, I even have TOE enabled. -Dustin On Tue, Nov 15, 2016 at 6:07 AM, Rajil Saraswat wrote: > On Nov 15, 2016 5:58 AM, wrote: >> >> Hello, >> >> I am trying to get a windows server VM running under bhyve. So far I can > use VNC to install Windows, but I've been unable to get the networking > working. I will provide details below, and include a summary up here. On > the guest, I have installed the latest version of winvirtio, and I have > configured static IP addressing. The guest can ping itself, but not the > host machine or anything external. It is worth noting that I am also > currently running a CentOS guest, and this can connect to both the host and > the outside world with no issues. >> >> Host: FreeBSD 11.0-RELEASE >> Guest: Tried both Windows Server 2016 Essentials and Windows Server 2012 > Standard >> >> bhyve command: >> bhyve -c 1 -H -w -m 3G -s 0,hostbridge -s 3,ahci-cd,/iohyve/ISO// -s > '4,ahci-hd,/dev/zvol/zroot/iohyve/win12/disk0,sectorsize=512' -s > 10,virtio-net,tap2 -s '11,fbuf,tcp=0.0.0.0:5902,w=800,h=600,wait' -s > 12,xhci,tablet -s 31,lpc -l com1,/dev/nmdm3A -l > bootrom,/iohyve/Firmware/BHYVE_UEFI.fd/BHYVE_UEFI.fd ioh-win12 >> >> ifconfig output: >> em0: flags=8843 metric 0 mtu 1500 >> > options=4219b >> ether e0:69:95:a2:f1:d9 >> inet 46.105.xxx.xxx netmask 0xff00 broadcast 46.105.124.255 >> inet6 fe80::e269:95ff::f1d9%em0 prefixlen 64 scopeid 0x1 >> inet6 2001:41d0:2:::1 prefixlen 56 >> nd6 options=21 >> media: Ethernet autoselect (100baseTX ) >> status: active >> lo0: flags=8049 metric 0 mtu 16384 >> options=63 >> inet6 ::1 prefixlen 128 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 >> inet 127.0.0.1 netmask 0xff00 >> nd6 options=21 >> groups: lo >> bridge0: flags=8843 metric 0 mtu > 1500 >> ether 02:cf:0c:8f:13:00 >> inet6 fd00:: prefixlen 112 >> inet 10.0.0.254 netmask 0xff00 broadcast 10.0.0.255 >> nd6 options=1 >> groups: bridge >> id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 >> maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 >> root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 >> member: tap2 flags=143 >> ifmaxaddr 0 port 7 priority 128 path cost 200 >> member: tap1 flags=143 >> ifmaxaddr 0 port 5 priority 128 path cost 200 >> member: tap0 flags=143 >> ifmaxaddr 0 port 4 priority 128 path cost 200 >> pflog0: flags=0<> metric 0 mtu 33160 >> groups: pflog >> tap0: flags=8943 metric 0 > mtu 1500 >> description: iohyve-centos >> options=8 >> ether 00:bd:5d:d3:e8:00 >> nd6 options=21 >> media: Ethernet autoselect >> status: active >> groups: tap >> Opened by PID 96206 >> tap1: flags=8902 metric 0 mtu 1500 >> description: iohyve-win16es >> options=8 >> ether 00:bd:61:ab:eb:01 >> nd6 options=21 >> media: Ethernet autoselect >> status: no carrier >> groups: tap >> tap2: flags=8943 metric 0 > mtu 1500 >> description: iohyve-win12 >> options=8 >> ether 00:bd:c9:1a:59:02 >> nd6 options=21 >> media: Ethernet autoselect >> status: active >> groups: tap >> Opened by PID 1911 >> >> It is using NAT with PF to reach the internet. It should not rely on NAT > to be able to ping the host machine, but I will post the NAT configuration > below anyway: >> >> /etc/pf.conf: >> # Automatically NAT any VMs >> nat on em0 inet from bridge0:network to any -> (em0) >> >> >> (On the Guest) >> == >> >> C:\Users\Administrator>ipconfig >> >> Ethernet adapter Ethernet: >> >> IPv4 Address: 10.0.0.3 >> Subnet Mask: 255.255.255.0 >> Default Gateway: 10.0.0.254 >> >> C:\Users\Administrator>ping 10.0.0.3 >> >> Pinging 10.0.0.3 with 32 bytes of data: >> Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 >> Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 >> Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 >> Reply from 10.0.0.3: bytes=32 time<1ms TTL=128 >> >> C:\Users\Administrator>ping 10.0.0.254 >> >> Pinging 10.0.0.254 with 32 bytes of data: >> Reply from 10.0.0.3: Destination host unreachable. >> Reply from 10.0.0.3: Destination host unreachable. >> Reply from 10.0.0.3: Destination host unreachable. >> Reply from 10.0.0.3: Destination host unreachable. >> >> C:\Users\Administrator>arp -a >> >> Interface: 10.0.0.3 --- 0xc >> Internet Address Physical AddressType >> 10.0.0.255ff-ff-ff-ff-ff-ff static >> 224.0.0.2201-00-5e-00-00-16
Re: bhyve windows guest unable to ping default gateway or external networks
Hi Jonathan, In particular, I used virtio-win-0.1.126.iso with driver net-kvm/windows 2k16/amd64 for my attempt with Server 2016 and the 2k12r2/amd64 driver for Server 2012 R2. I've not had any success with 0.1.126 - it installs, but doesn't appear to pass packets. I'd recommend going with 0.1.96 later, Peter. ___ 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: bhyve windows guest unable to ping default gateway or external networks
virtio-win-0.1.102.iso was the last version I've had any success with. (I haven't tried with bhyve, only VirtualBox Windows VMs). On 16 November 2016 at 08:43, Peter Grehan wrote: > Hi Jonathan, > > In particular, I used virtio-win-0.1.126.iso with driver net-kvm/windows >> 2k16/amd64 for my attempt with Server 2016 and the 2k12r2/amd64 driver >> for Server 2012 R2. >> > > I've not had any success with 0.1.126 - it installs, but doesn't appear > to pass packets. I'd recommend going with 0.1.96 > > later, > > Peter. > > > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubs > cr...@freebsd.org" > ___ 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: bhyve windows guest unable to ping default gateway or external networks
Peter, I'd recommend giving a try with 118. I had a lot of trouble getting a Win16 image running. Ultimately, it was 118 and a lot of tries with deleting the driver software and reinstalling from the virtio iso to get it to work. I sent a a few emails last month as I was working through the issues. In the end, I think it was mainly dropping back to 118 and many tries to convince new driver to install. -- Randy On Tue, Nov 15, 2016 at 4:30 PM, Matt Thyer wrote: > virtio-win-0.1.102.iso was the last version I've had any success with. > (I haven't tried with bhyve, only VirtualBox Windows VMs). > > On 16 November 2016 at 08:43, Peter Grehan wrote: > > > Hi Jonathan, > > > > In particular, I used virtio-win-0.1.126.iso with driver net-kvm/windows > >> 2k16/amd64 for my attempt with Server 2016 and the 2k12r2/amd64 driver > >> for Server 2012 R2. > >> > > > > I've not had any success with 0.1.126 - it installs, but doesn't appear > > to pass packets. I'd recommend going with 0.1.96 > > > > later, > > > > Peter. > > > > > > ___ > > freebsd-virtualization@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to "freebsd-virtualization-unsubs > > cr...@freebsd.org" > > > ___ > 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" > ___ 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: bhyve windows guest unable to ping default gateway or external networks
On 11/15/2016 03:51 PM, Dustin Marquess wrote: > If it's a bug, I don't believe it's in the virtio stack. > > I'm using Chelsio NICs on my bhyve servers, and I don't have to > disable anything for my guests to work, I even have TOE enabled. > > -Dustin > > Following is the bug i was referring to: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 I have tried 10gbe NICs (Mellanox ConnectX-2 SFP+, Intel 540-AT2), and both gave very poor speeds in the guests with offloading enabled. -Rajil ___ 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: bhyve windows guest unable to ping default gateway or external networks
Hi Peter, Thanks for suggesting that! I re-installed the VM, this time using 0.1.96 instead of 0.1.126 and it worked as soon as I gave it static addressing. As 0.1.96 doesn't contain a driver specifically for Server 2016 I just used the 2012R2 one and I don't appear to have any issues. Unfortunately I don't really have time to test the drivers one by one until I find where it breaks, but it looks like some others in this thread have already done so, which is useful. Thanks, Jonathan. November 15, 2016 10:14 PM, "Peter Grehan" wrote: > Hi Jonathan, > >> In particular, I used virtio-win-0.1.126.iso with driver net-kvm/windows >> 2k16/amd64 for my attempt with Server 2016 and the 2k12r2/amd64 driver >> for Server 2012 R2. > > I've not had any success with 0.1.126 - it installs, but doesn't appear to > pass packets. I'd > recommend going with 0.1.96 > > later, > > Peter. ___ 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: bhyve windows guest unable to ping default gateway or external networks
I'd recommend giving a try with 118. Thanks for the tip ! (and the testing). Worked fine with Win10: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.118-2/virtio-win-0.1.118.iso later, Peter. ___ 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: bhyve windows guest unable to ping default gateway or external networks
On 17 November 2016 at 06:49, Peter Grehan wrote: > I'd recommend giving a try with 118. >> > > Thanks for the tip ! (and the testing). Worked fine with Win10: > > Just a FYI, I've tested 118 solid on Win 10, 2012R2 and 2016 and haven't had an issue with testing workloads. Cheers! > https://fedorapeople.org/groups/virt/virtio-win/direct-downl > oads/archive-virtio/virtio-win-0.1.118-2/virtio-win-0.1.118.iso > > later, > > Peter. > > > > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubs > cr...@freebsd.org" > ___ 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: bhyve windows guest unable to ping default gateway or external networks
Hi Jason, I'd recommend giving a try with 118. Thanks for the tip ! (and the testing). Worked fine with Win10: Just a FYI, I've tested 118 solid on Win 10, 2012R2 and 2016 and haven't had an issue with testing workloads. Thanks for the report - good to know 2k12r2 is ok with 118. Win7 SP1 also works with 118, so I think this is now the recommended rev. later, Peter. ___ 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"