| 2014-12-04 09:12:35 |
Paolo Pisati |
description |
Hi,
The current armmp (linux-image-3.16.0-26-generic_3.16.0-26.34_armhf.deb) could have virtio-mmio enabled for faster vm guests. Currenlty it seems to have:
CONFIG_NET_9P_VIRTIO=m
CONFIG_VIRTIO_BLK=y
CONFIG_SCSI_VIRTIO=m
CONFIG_VIRTIO_NET=y
CONFIG_CAIF_VIRTIO=m
CONFIG_VIRTIO_CONSOLE=y
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_PCI=y
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_VIRTIO_MMIO is not set
Now using virtio net and block is not possible, and you have to revert to emulated devices. |
[Impact]
Degraded performance during network and disk activity in a kvm guest.
[Test case]
Try booting a vm and do some disk/net activity with and without this driver.
[Regression potential]
In case of regressions, it will just hit people using kvm on 32bit armhf hardware (the lpae variant in particular): we already had this driver on in the past, it's on by default on every arch, it's widely used and upstream is very active - i say it's a low potential regression.
--
Hi,
The current armmp (linux-image-3.16.0-26-generic_3.16.0-26.34_armhf.deb) could have virtio-mmio enabled for faster vm guests. Currenlty it seems to have:
CONFIG_NET_9P_VIRTIO=m
CONFIG_VIRTIO_BLK=y
CONFIG_SCSI_VIRTIO=m
CONFIG_VIRTIO_NET=y
CONFIG_CAIF_VIRTIO=m
CONFIG_VIRTIO_CONSOLE=y
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_PCI=y
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_VIRTIO_MMIO is not set
Now using virtio net and block is not possible, and you have to revert to emulated devices. |
|
