port-xen/59438: GENERIC content can't be in GENERIC.local because of XEN3_DOM* kernels

[campbell+netbsd%mumble.net@localhost]

>Number:         59438
>Category:       port-xen
>Synopsis:       GENERIC content can't be in GENERIC.local because of XEN3_DOM* kernels
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-xen-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 22 01:55:00 +0000 2025
>Originator:     Taylor R Campbell
>Release:        
>Organization:
The XenBSD.local
>Environment:
>Description:
Various content in GENERIC can't be moved to -- or drafted in -- GENERIC.local because it breaks XEN3_DOM0 and XEN3_DOMU kernels.  For example, there's no virtio in the Xen kernels, so you can't put

vio9p* at virtio?

in GENERIC.local or it will break the Xen kernel builds.

This is silly.

https://mail-index.netbsd.org/tech-kern/2024/08/11/msg029672.html
>How-To-Repeat:
put `vio9p* at virtio?' in GENERIC.local
>Fix:
Stop including GENERIC.local in XEN3_DOM0 and XEN3_DOMU kernels.  Start including XEN3_DOM0.local and XEN3_DOMU.local, respectively, instead.  (XEN3_DOMU.local is already used, but XEN3_DOM0.local is not.)

Yes, this may break some local custom kernel configurations.  I don't think NetBSD has, or has ever had, any compatibility guarantees for custom kernel configurations, so I don't think this objection holds water (and nobody who raised that objection demonstrated any breakage that would actually happen, when requested).