When I use kvm's virtio devices: - -net nic,model=virtio - -drive file=foo.img,if=virtio the minimal CD does not recognize them. this is due to the lack of the virtio* modules. Reproducible: Always Steps to Reproduce: launch kvm with -net nic,model=virtio, -drive file=foo.img,if=virtio and -cdrom install-x86-minimal*.iso (or the amd64 one) Actual Results: The virtio disk /dev/vda (foo.img) is not seen and cannot be used at all. There is no network device found. Expected Results: The virtio disk /dev/vda (foo.img) is accessible and usable. The virtio network device is found and usable.
What are the CONFIG_* options? Doing a 'grep -i virtio' through a 2.6.28 kconfig doesn't turn up anything.
(In reply to comment #1) > What are the CONFIG_* options? Doing a 'grep -i virtio' through a 2.6.28 > kconfig doesn't turn up anything. > In my 2.6.28 and 2.6.29 gentoo-sources kernels, my virtual Gentoo uses: # grep VIRTIO /usr/src/linux/.config CONFIG_VIRTIO_BLK=y <- the -drive device (can be a module in the livecd) CONFIG_VIRTIO_NET=y <- the -net device (can be a module in the livecd) # CONFIG_VIRTIO_CONSOLE is not set <- I do not use it (it is for lguest and some other ones, not used in kvm as I remember) CONFIG_HW_RANDOM_VIRTIO=y <- HW random generator instead of Intel/AMD/VIA's one (can be a module) CONFIG_VIRTIO=y <- the base of all virtio framework CONFIG_VIRTIO_RING=y <- the communication with the host CONFIG_VIRTIO_PCI=y <- the blk and net devices live on this one CONFIG_VIRTIO_BALLOON=y <- the ability to control memory size in guest from the host while the guest is running (not needed in the livecd) Most of these options are labeled still as experimental.
Ah, these didn't show up in my .config because I didn't have CONFIG_VIRTUALIZATION enabled. I've updated the x86/amd64 installcd kconfigs. This will appear in the next round of autobuilds.
This appears to be a problema gain
This is such an old bug that you should have opened a new bug about this. $ grep -i virtio releases/weekly/kconfig/amd64/installcd-4.4.6.config CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m # Virtio drivers CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_PCI_LEGACY=y CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_INPUT is not set CONFIG_VIRTIO_MMIO=m # CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set $ grep -i virtio releases/weekly/kconfig/x86/installcd-3.18.12.config CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m # Virtio drivers CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set You didn't state in what version / arch you got this issue, but as you can see above, the latest kernel does have the virtio drivers enabled.
