Comment 2 for bug 591666

If configure guest kernel correctly, it seems that virtio for block is OK!
Could you help or send me your configure file to have a second check

Thanks

======== version info ===============
QEMU 0.14.50 monitor
host kernel: 2.6.39
guest kernel: 2.6.32

======== config file for kernel info ===================
See attachment

=========Doing on qemu monitor ================
QEMU 0.14.50 monitor - type 'help' for more information
(qemu) pci_add auto storage file=/dev/ram0,if=virtio
OK domain 0, bus 0, slot 3, function 0

=========Doing on guest console ===============
1. ---see the disk on guest
root@qemux86-64:~# dmesg | grep 'vda'
[ 245.440217] vda: unknown partition table
root@qemux86-64:~# fdisk -l

Disk /dev/sda: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sda doesn't contain a valid partition table

Disk /dev/vda: 16 MB, 16777216 bytes
16 heads, 63 sectors/track, 32 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Disk /dev/vda doesn't contain a valid partition table

2. --- write content to virtio disk

root@qemux86-64:~# echo 'helloHypervisor' > /dev/vda
root@qemux86-64:~# head /dev/vda
helloHypervisor

=========Doing on host console =============

[root@oc8440477808 linux-2.6.39]# head /dev/ram0
helloHypervisor

========= conclusion ====================
Host get the data which is passed through virtio device on guest. The data is "helloHpervisor"

So, the kernel version 2.6.32 can support virtio block device with correct
config, especially the following must be choosen:

CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_BALLOON=y
CONFIG_VIRTIO_BLK=y