CONFIG_VIRTIO_BLK shouldnt be a module

[Chuck Short]

In the kernel config for pangolin CONFIG_VIRTIO_BLK=m it probably should be CONFIG_VIRTIO_BLK=y otherwise kernels without a ramdisk will not work on cloud images.

If you have any questions please let me know.

Regards
chuck

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 902951

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Scott Moser (smoser)]

Chuck,
  As shown below, at very least the current pangolin -virtual kernel *does* have VIRTIO_BLK=y, but the -server kernel does not.
  This *is* a change from oneiric, where both -server and -virtual of 3.0.0-14 have VIRTIO_BLK and VIRTIO_NET built in.
  So, I would say that unless there is a reason for this change in behavior, we should have these options built in.

$ grep VIRTIO /boot/config-3.2.0-4-virtual
CONFIG_NET_9P_VIRTIO=m
CONFIG_VIRTIO_BLK=y
CONFIG_VIRTIO_NET=y
CONFIG_VIRTIO_CONSOLE=m
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_BALLOON=m
CONFIG_VIRTIO_MMIO=m

$ grep VIRTIO /boot/config-3.0.0-14-server
CONFIG_NET_9P_VIRTIO=m
CONFIG_VIRTIO_BLK=y
CONFIG_VIRTIO_NET=y
CONFIG_VIRTIO_CONSOLE=m
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_BALLOON=m

[Joseph Salisbury (jsalisbury)]

So should this bug be marked as invalid, since the -virtual kernel does have CONFIG_VIRTIO_BLK=y

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Stefan Bader (smb)]

When looking over configuration mismatches during the Precise Ralley this was changed to be built-in for all x86 kernels.

[Stefan Bader (smb)]

Included in the Ubuntu-3.2.0-9.16 upload.