Back to Home / #xen / 2022 / 05 / Prev Day | Next Day
#xen IRC Logs for 2022-05-02

---Logopened Mon May 02 00:00:01 2022
---Daychanged Mon May 02 2022
00:00-!-rocky198888 [~oftc-webi@240e:388:a103:b400:6138:a5d1:4cb8:41ca] has quit [Remote host closed the connection]
00:01-!-rocky1984 [~rocky@] has left #xen []
00:01-!-rocky1984 [~rocky@] has joined #xen
00:01-!-rocky1984 is "(optional)" on #xen
00:03-!-rocky1984 [~rocky@] has quit []
00:04-!-ChmEarl [] has quit [Quit: Leaving]
01:48-!-jgross_ is now known as jgross
07:36-!-mjt [] has quit [Quit: leaving]
10:52-!-ChmEarl [] has joined #xen
10:52-!-ChmEarl is "Mark Pryor" on #xen ##xen-packaging #mock #packaging #virt
11:23-!-XCPngXOTeam [~XCPngXOTe@2a01:240:ab08::2] has quit [Remote host closed the connection]
11:24-!-XCPngXOTeam [~XCPngXOTe@2a01:240:ab08::2] has joined #xen
11:24-!-XCPngXOTeam is "XCPngXOTeam" on #xen #xen-orchestra #xsxoteams #xcp-ng
20:03-!-Tonux [] has quit [Remote host closed the connection]
20:04-!-Tonux [~Tonux@] has joined #xen
20:04-!-Tonux is "Tonux" on #xen #oftc #kernelnewbies #fdroid
21:12-!-ClyneS [~ClyneS@] has joined #xen
21:12-!-ClyneS is "Unknown" on #xen
21:15<ClyneS>Good evening, Im having a problem running the FreeBSD based router OS OPNSense as a domU after I upgraded dom0 kernel to 5.15.32 from 5.15.26. I ended up testing every version until I found the failure at 5.15.29. In the changelog was two commits from xen-netback. I reverted those commits to my kernel and that fixed the problem.
21:24<dwfreed>you *reverted* these?
21:25<ClyneS>Yes sir
21:26<dwfreed>that seems odd, given they are themselves reverts
21:27<ClyneS>Yeah I saw that. But all I can say is bone stock 5.15.29 OPNSense has not network connectivity, and after I made the change so it was like 5.15.28 than it worked fine
21:32<ClyneS>I can watch OPNSense boot and at one point it resets the network adapters, so I believe that is why Im having a failure with this code, just reading the description. But I could be wrong; Im no programmer
21:38<dwfreed>having these particular commits should *fix* the issue, not break it, if that were the case
21:38<dwfreed>the initial report resulting in those commits was from ipxe, it looks like, which does the same kind of thing, in a way
21:39<dwfreed>brings up the adapter(s) so it can have network, and then tears them down so that the real guest kernel can initialize them during its boot
21:41<ClyneS>Yeah, for some reason it breaks mine. I dont know how to troubleshoot more or I would.
21:41<dwfreed>ClyneS: it would be interesting to see the output of xenstore ls for the backends and frontends for the vifs
21:42<dwfreed>with the broken kernel, mind
21:42<dwfreed>because the nodes would be missing on the fixed kernel
21:45<ClyneS>Ok I will get that next time I reboot. Hmm, guess Ill have to drop a 'broken' kernel in my boot selection.
22:10-!-jgross_ [~juergen_g@2a01:41e1:2eef:9400:a1ee:84ec:562d:3e2d] has joined #xen
22:10-!-jgross_ is "realname" on #xen
22:17-!-jgross [~juergen_g@2a01:41e1:2ebe:1e00:a4cf:89a0:214b:143a] has quit [Ping timeout: 480 seconds]
22:18-!-ClyneS [~ClyneS@] has quit [Quit: Lost terminal]
---Logclosed Tue May 03 00:00:03 2022