Has anyone experimented with enabling CONFIG_HYPERV on the 4.19.19 kernel?
I grabbed the docker repository for building drivers and updated it to build the kernel on a debian VM. I attempted to to swap out the running kernel on a HyperV guest, however I hadn't planned on the ata_piix.c disabling gen1 ATA devices when CONFIG_HYPERV_STORAGE was present.. Oops 
I'd really like to get Gen2 VMs running (or even just the modern network adapters) running on HyperV for a situation where I have a constrained amount of datacenter space -- and would love to create a 2nd XenServer node for replication on top of my existing HyperV host.
I'm curious if I should keep experimenting with building the HyperV kernel extensions into xcp-ng, or if there is some large known issue which prevents them from working. Happy to continue down the path, but just curious if anyone has tried this before.
Ended up building with..
CONFIG_HYPERV=y
CONFIG_HYPERV_UTILS=y
CONFIG_PCI_HYPERV=y
CONFIG_HYPERV_NET=y
CONFIG_HYPERV_STORAGE=y
CONFIG_SCSI=y
Thanks!