Re: VirtualBox network connectivity broken on recent -CURRENT
On Sun, Jun 05, 2016 at 12:35:29PM -0700, Don Lewis wrote: > On 4 Jun, To: mm...@nextbsd.org wrote: > > On 4 Jun, Matthew Macy wrote: > >> > >> > >> > >> On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund > >> wrote > >> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > >> > > It looks like something changed in -CURRENT to break network > >> > > connectivity to VirtualBox guests. This was last known to work > >> > > with r299139 (May 6th) and is definitely broken with r301229. > >> > > >> > I've been having VirtualBox networking problems as well. I can't > >> > get my VMs on the network recently, but I don't recall when it > >> > last worked. Everything looks right from the guest (the arp cache > >> > shows the VirtualBox NAT router), but tcpdump on the host shows no > >> > traffic. I haven't had time to investigate further :/ > >> > > >> > >> The odds of it being fixed will increase greatly if someone would do a > >> bisect and test. > > > > I started bisecting a bit earlier today. So far all I know is r300184 > > is also broken. > > The culprit turned out to be r300043. There seems to be some > sort of ABI compatiblity issue that was resolved when I rebuilt and > reinstalled virtualbox-ose-kmod. There should probably be note in > src/UPDATING if so. The .kmod files that I had been > running were probably built with r299139. Not ABI, bit KBI. The revision changed layout of the struct thread, which occurs semi-regularly on HEAD, but we maintain the layout for struct proc and struct thread for existing fields on stable. I also changes the layouts of struct proc and thread today, please see r301456. I am not sure about __FreeBSD_version bump for that changes, since they do not add or remove any consumable interfaces. The sole purpose of the bump would be to delineate the modules build time. > > I used to have PORTS_MODULES=emulators/virtualbox-ose-kmod in > /etc/make.conf, but took it out because pkg would also try to > intall/upgrade it from my local pkg repo. > > What is strange is that the kmods would successfully load even on very > recent kernels, but when I did a "pkg install -f virtualbox-ose-kmod" > to fetch a recently rebuilt version (just a few days old), it would not > load with a r300043 kernel. Is there a check to prevent a module with a > newer version from loading on an older kernel, but not the reverse? Yes, the __FreeBSD_version from the headers pack used for module build is embedded into module metadata, and module loader checks it against the version of the kernel. It makes sense on stable, but not much on HEAD, where only exact match would ever reasonable. Even on stable, we only guarantee partial KBI stability, mostly to interfaces relevant for device drivers, and not for e.g. ABI emulators. For such modules which are too tied to the kernel, I added the DECLARE_MODULE_TIED() declarator. Might be vbox kmods need to start using that (if not using _TIED already). ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: VirtualBox network connectivity broken on recent -CURRENT
On 4 Jun, To: mm...@nextbsd.org wrote: > On 4 Jun, Matthew Macy wrote: >> >> >> >> On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund >> wrote >> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: >> > > It looks like something changed in -CURRENT to break network >> > > connectivity to VirtualBox guests. This was last known to work >> > > with r299139 (May 6th) and is definitely broken with r301229. >> > >> > I've been having VirtualBox networking problems as well. I can't >> > get my VMs on the network recently, but I don't recall when it >> > last worked. Everything looks right from the guest (the arp cache >> > shows the VirtualBox NAT router), but tcpdump on the host shows no >> > traffic. I haven't had time to investigate further :/ >> > >> >> The odds of it being fixed will increase greatly if someone would do a >> bisect and test. > > I started bisecting a bit earlier today. So far all I know is r300184 > is also broken. The culprit turned out to be r300043. There seems to be some sort of ABI compatiblity issue that was resolved when I rebuilt and reinstalled virtualbox-ose-kmod. There should probably be note in src/UPDATING if so. The .kmod files that I had been running were probably built with r299139. I used to have PORTS_MODULES=emulators/virtualbox-ose-kmod in /etc/make.conf, but took it out because pkg would also try to intall/upgrade it from my local pkg repo. What is strange is that the kmods would successfully load even on very recent kernels, but when I did a "pkg install -f virtualbox-ose-kmod" to fetch a recently rebuilt version (just a few days old), it would not load with a r300043 kernel. Is there a check to prevent a module with a newer version from loading on an older kernel, but not the reverse? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: VirtualBox network connectivity broken on recent -CURRENT
On 5 Jun, Otacílio wrote: > Em 04/06/2016 23:04, Randy Westlund escreveu: >> On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: >>> It looks like something changed in -CURRENT to break network >>> connectivity to VirtualBox guests. This was last known to work with >>> r299139 (May 6th) and is definitely broken with r301229. >> I've been having VirtualBox networking problems as well. I can't get my >> VMs on the network recently, but I don't recall when it last worked. >> Everything looks right from the guest (the arp cache shows the >> VirtualBox NAT router), but tcpdump on the host shows no traffic. I >> haven't had time to investigate further :/ > > I'm running rev 301210 guest and here looks working. It doesn't appear to be a guest problem. Both recent FreeBSD 11.0-CURRENT and Debian on broken if the host is FreeBSD 11.0 HEAD >= r300184. The same FreeBSD guest works if the host is FreeBSD 10.3-STABLE r301231. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: VirtualBox network connectivity broken on recent -CURRENT
On 4 Jun, Matthew Macy wrote: > > > > On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund > wrote > > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > > > It looks like something changed in -CURRENT to break network > > > connectivity to VirtualBox guests. This was last known to work > > > with r299139 (May 6th) and is definitely broken with r301229. > > > > I've been having VirtualBox networking problems as well. I can't > > get my VMs on the network recently, but I don't recall when it > > last worked. Everything looks right from the guest (the arp cache > > shows the VirtualBox NAT router), but tcpdump on the host shows no > > traffic. I haven't had time to investigate further :/ > > > > The odds of it being fixed will increase greatly if someone would do a > bisect and test. I started bisecting a bit earlier today. So far all I know is r300184 is also broken. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: VirtualBox network connectivity broken on recent -CURRENT
Em 04/06/2016 23:04, Randy Westlund escreveu: On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: It looks like something changed in -CURRENT to break network connectivity to VirtualBox guests. This was last known to work with r299139 (May 6th) and is definitely broken with r301229. I've been having VirtualBox networking problems as well. I can't get my VMs on the network recently, but I don't recall when it last worked. Everything looks right from the guest (the arp cache shows the VirtualBox NAT router), but tcpdump on the host shows no traffic. I haven't had time to investigate further :/ I'm running rev 301210 guest and here looks working. [ota@nostromo /usr/home/ota]$ uname -a FreeBSD nostromo 11.0-ALPHA1 FreeBSD 11.0-ALPHA1 #0 r301210: Fri Jun 3 01:24:19 BRT 2016 ota@nostromo:/usr/obj/usr/src/sys/NOSTROMO amd64 [ota@nostromo /usr/home/ota]$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=91.683 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=67.433 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=52.106 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=153.091 ms ^C --- 8.8.8.8 ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 52.106/91.078/153.091/38.483 ms [ota@nostromo /usr/home/ota]$ wget bash: wget: comando não encontrado [ota@nostromo /usr/home/ota]$ telnet www.google.com 80 Trying 216.58.218.4... Connected to www.google.com. Escape character is '^]'. GET index.html HTTP/1.0 404 Not Found Content-Type: text/html; charset=UTF-8 Content-Length: 1561 Date: Sun, 05 Jun 2016 03:01:55 GMT Error 404 (Not Found)!!1*{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}404. That’s an error. The requested URL / was not found on this server. That’s all we know. Connection closed by foreign host. [ota@nostromo /usr/home/ota]$ []'s -Otacilio ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: VirtualBox network connectivity broken on recent -CURRENT
On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund wrote > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > > It looks like something changed in -CURRENT to break network > > connectivity to VirtualBox guests. This was last known to work with > > r299139 (May 6th) and is definitely broken with r301229. > > I've been having VirtualBox networking problems as well. I can't get my > VMs on the network recently, but I don't recall when it last worked. > Everything looks right from the guest (the arp cache shows the > VirtualBox NAT router), but tcpdump on the host shows no traffic. I > haven't had time to investigate further :/ > The odds of it being fixed will increase greatly if someone would do a bisect and test. -M ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: VirtualBox network connectivity broken on recent -CURRENT
On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > It looks like something changed in -CURRENT to break network > connectivity to VirtualBox guests. This was last known to work with > r299139 (May 6th) and is definitely broken with r301229. I've been having VirtualBox networking problems as well. I can't get my VMs on the network recently, but I don't recall when it last worked. Everything looks right from the guest (the arp cache shows the VirtualBox NAT router), but tcpdump on the host shows no traffic. I haven't had time to investigate further :/ signature.asc Description: PGP signature
Re: VirtualBox network connectivity broken on recent -CURRENT
On 4 Jun, Alan Somers wrote: > On Fri, Jun 3, 2016 at 6:43 PM, Don Lewis wrote: >> On 3 Jun, Don Lewis wrote: >>> It looks like something changed in -CURRENT to break network >>> connectivity to VirtualBox guests. This was last known to work with >>> r299139 (May 6th) and is definitely broken with r301229. The VirtualBox >>> port revisions are: >>> virtualbox-ose-4.3.38_1 >>> virtualbox-ose-kmod-4.3.38 >>> It looks like there was one change to the VirtualBox on May 9th, but it >>> looks unlikely to be the cause of the problem. >>> >>> The network settings are: >>> Attached to: Bridged Adapter >>> Name: re0 >>> Adapter Type: Paravirtualized Network (virtio-net) >>> Promiscuous Mode: Deny >>> MAC Address: [snip] >>> Ifconfig says that the interface is up, but I am unable to ping either >>> the host or anything else on the LAN from the guest. It looks like the >>> problem is with outbound traffic. If I attempt to ping the guest, the >>> source IP address and MAC address show up in the guest's arp table, but >>> ping reports: >>> ping: sendto: Host is down >>> That makes me think that the arp responses from the guest are not >>> getting transmitted. None of the machines involved are running >>> firewalls. If I ping from the guest, I don't see any arp requests on >>> the wire and the arp command shows the table entry as incomplete. >>> >>> The problem shows up with both FreeBSD -CURRENT and Debian guests. >> >> I see the same behaviour if I set: >> Attached to: NAT >> or >> Adapter Type: 82540EM >> > > Might be related to this routing bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207831 Doesn't look like it. The questionable commit there seems to be r293159. I didn't see breakage until after r299139. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: VirtualBox network connectivity broken on recent -CURRENT
On Fri, Jun 3, 2016 at 6:43 PM, Don Lewis wrote: > On 3 Jun, Don Lewis wrote: >> It looks like something changed in -CURRENT to break network >> connectivity to VirtualBox guests. This was last known to work with >> r299139 (May 6th) and is definitely broken with r301229. The VirtualBox >> port revisions are: >> virtualbox-ose-4.3.38_1 >> virtualbox-ose-kmod-4.3.38 >> It looks like there was one change to the VirtualBox on May 9th, but it >> looks unlikely to be the cause of the problem. >> >> The network settings are: >> Attached to: Bridged Adapter >> Name: re0 >> Adapter Type: Paravirtualized Network (virtio-net) >> Promiscuous Mode: Deny >> MAC Address: [snip] >> Ifconfig says that the interface is up, but I am unable to ping either >> the host or anything else on the LAN from the guest. It looks like the >> problem is with outbound traffic. If I attempt to ping the guest, the >> source IP address and MAC address show up in the guest's arp table, but >> ping reports: >> ping: sendto: Host is down >> That makes me think that the arp responses from the guest are not >> getting transmitted. None of the machines involved are running >> firewalls. If I ping from the guest, I don't see any arp requests on >> the wire and the arp command shows the table entry as incomplete. >> >> The problem shows up with both FreeBSD -CURRENT and Debian guests. > > I see the same behaviour if I set: > Attached to: NAT > or > Adapter Type: 82540EM > Might be related to this routing bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207831 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: VirtualBox network connectivity broken on recent -CURRENT
On 3 Jun, Don Lewis wrote: > It looks like something changed in -CURRENT to break network > connectivity to VirtualBox guests. This was last known to work with > r299139 (May 6th) and is definitely broken with r301229. The VirtualBox > port revisions are: > virtualbox-ose-4.3.38_1 > virtualbox-ose-kmod-4.3.38 > It looks like there was one change to the VirtualBox on May 9th, but it > looks unlikely to be the cause of the problem. > > The network settings are: > Attached to: Bridged Adapter > Name: re0 > Adapter Type: Paravirtualized Network (virtio-net) > Promiscuous Mode: Deny > MAC Address: [snip] > Ifconfig says that the interface is up, but I am unable to ping either > the host or anything else on the LAN from the guest. It looks like the > problem is with outbound traffic. If I attempt to ping the guest, the > source IP address and MAC address show up in the guest's arp table, but > ping reports: > ping: sendto: Host is down > That makes me think that the arp responses from the guest are not > getting transmitted. None of the machines involved are running > firewalls. If I ping from the guest, I don't see any arp requests on > the wire and the arp command shows the table entry as incomplete. > > The problem shows up with both FreeBSD -CURRENT and Debian guests. I see the same behaviour if I set: Attached to: NAT or Adapter Type: 82540EM ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
VirtualBox network connectivity broken on recent -CURRENT
It looks like something changed in -CURRENT to break network connectivity to VirtualBox guests. This was last known to work with r299139 (May 6th) and is definitely broken with r301229. The VirtualBox port revisions are: virtualbox-ose-4.3.38_1 virtualbox-ose-kmod-4.3.38 It looks like there was one change to the VirtualBox on May 9th, but it looks unlikely to be the cause of the problem. The network settings are: Attached to: Bridged Adapter Name: re0 Adapter Type: Paravirtualized Network (virtio-net) Promiscuous Mode: Deny MAC Address: [snip] Ifconfig says that the interface is up, but I am unable to ping either the host or anything else on the LAN from the guest. It looks like the problem is with outbound traffic. If I attempt to ping the guest, the source IP address and MAC address show up in the guest's arp table, but ping reports: ping: sendto: Host is down That makes me think that the arp responses from the guest are not getting transmitted. None of the machines involved are running firewalls. If I ping from the guest, I don't see any arp requests on the wire and the arp command shows the table entry as incomplete. The problem shows up with both FreeBSD -CURRENT and Debian guests. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
