When I use VirtualBox on 13-CURRENT r363508, and attempt to use a bridged network, I get a kernel panic. This issue doesn't exist on 12.x.
HP Spectre x360 13-ap0053dx
Intel Core i7-8565U
512GB NVMe + Intel Optane
13" 4K Touchscreen
Intel AC-9560 (iwm)
Stack trace is attached as a jpg.
*** Bug 244819 has been marked as a duplicate of this bug. ***
Created attachment 216847 [details]
@Neel Can you include your latest comment and attachment to bug 244819 please
*** This bug has been marked as a duplicate of bug 244819 ***
Created attachment 216848 [details]
VirtualBox does not use EPOCH on 13, so this patch adds support for EPOCH in VirtualBox.
Accidentally closed this.
(In reply to Neel Chauhan from comment #5)
well, didn't read your comment, sorry.
Bug 244819 is a report of a freeze, not panic, not technically a duplicate. Are the freeze symptoms still reproducible, or is it *now* a crash?
It technically is a panic, it just appears as a freeze with Nvidia graphics which my desktop use (the prior ProDesk mentioned and my current HP Omen).
I called a freeze since I didn't investigate further. I now know it is a panic.
BTW the patch is for emulators/virtualbox-ose-kmod.
Created attachment 216862 [details]
Patch (Revision 2)
The patch should go into emulators/virtualbox-ose, as emulators/virtualbox-ose-kmod picks up the former's files.
This is a full patch.
I confirm this working, even on the previously "freezing" computers (Nvidia graphics) and the panic computers (Intel graphics).
… reading this alongside emulators/virtualbox-ose-kmod kernel panic bug 249326
This was fixed in r560502 (yay, Ports commit bit!).