On 20.08.2017 08:17, Neil Bothwick wrote:

> I'd try again with a clean kernel tree but using make oldconfig. It's
> possible the automagic stuff answered n somewhere where you need a y.

As https://wiki.gentoo.org/wiki/Kernel/Upgrade/en#make_silentoldconfig
describes, "make silentoldconfig" (which I used) asks for a decision for
all newly introduced kernel options.

Most default to "no" anyway, but I have painstakingly read each of the
new descriptions to figure out if I might need the options. I've done it
several times, and I still cannot figure out if I missed anything. Here
is a subset of the options I have configured, perhaps you can spot if
something is amiss? Of course, grep VIRT is not exactly the most precise
approach...

  ### Server 1 (high volume traffic)
  $ grep VIRT .config | sort
  CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
  CONFIG_BLK_MQ_VIRTIO=y
  # CONFIG_DEBUG_VIRTUAL is not set
  # CONFIG_DMA_VIRT_OPS is not set
  CONFIG_DMA_VIRTUAL_CHANNELS=y
  # CONFIG_DRM_VIRTIO_GPU is not set
  # CONFIG_FB_VIRTUAL is not set
  CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
  CONFIG_HW_RANDOM_VIRTIO=y
  CONFIG_PARAVIRT_CLOCK=y
  # CONFIG_PARAVIRT_DEBUG is not set
  CONFIG_PARAVIRT_SPINLOCKS=y
  # CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
  CONFIG_PARAVIRT=y
  CONFIG_SCSI_VIRTIO=y
  # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
  # CONFIG_VIRT_DRIVERS is not set
  CONFIG_VIRTIO_BALLOON=m
  # CONFIG_VIRTIO_BLK_SCSI is not set
  CONFIG_VIRTIO_BLK=y
  CONFIG_VIRTIO_CONSOLE=y
  # CONFIG_VIRTIO_INPUT is not set
  # CONFIG_VIRTIO_MMIO is not set
  CONFIG_VIRTIO_NET=y
  CONFIG_VIRTIO_PCI_LEGACY=y
  CONFIG_VIRTIO_PCI=y
  CONFIG_VIRTIO=y
  CONFIG_VIRT_TO_BUS=y
  # CONFIG_VIRTUALIZATION is not set

I have since updated a second virtual Gentoo server to Kernel 4.12. This
server sees a lot less network traffic, but after a couple of hours it
runs into the same timeouts when attempting to contact resolvers. Kernel
settings include:

  ### Server 2 (low volume traffic)
  $ grep VIRT .config | sort
  CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
  CONFIG_BLK_MQ_VIRTIO=y
  # CONFIG_DEBUG_VIRTUAL is not set
  # CONFIG_DMA_VIRT_OPS is not set
  CONFIG_DMA_VIRTUAL_CHANNELS=y
  # CONFIG_DRM_VIRTIO_GPU is not set
  # CONFIG_FB_VIRTUAL is not set
  CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
  CONFIG_HW_RANDOM_VIRTIO=y
  CONFIG_PARAVIRT_CLOCK=y
  # CONFIG_PARAVIRT_DEBUG is not set
  CONFIG_PARAVIRT_SPINLOCKS=y
  # CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
  CONFIG_PARAVIRT=y
  CONFIG_SCSI_VIRTIO=y
  # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
  # CONFIG_VIRT_DRIVERS is not set
  CONFIG_VIRTIO_BALLOON=m
  # CONFIG_VIRTIO_BLK_SCSI is not set
  CONFIG_VIRTIO_BLK=y
  CONFIG_VIRTIO_CONSOLE=y
  # CONFIG_VIRTIO_INPUT is not set
  # CONFIG_VIRTIO_MMIO is not set
  CONFIG_VIRTIO_NET=y
  CONFIG_VIRTIO_PCI_LEGACY=y
  CONFIG_VIRTIO_PCI=y
  CONFIG_VIRTIO=y
  CONFIG_VIRT_TO_BUS=y
  CONFIG_VIRTUALIZATION=y

As you can see, I used CONFIG_VIRTUALIZATION=y in this case, even though
I believe this only affects running as a VM host. I carried this option
over from the previous 4.9 kernel.

-Ralph

Reply via email to