On 22/10/15 07:03, Martin Lucina wrote:
The main thing missing to be able to do something useful with rumprun on
GCE is the virtio-scsi driver
virtio-scsi is now available in rumprun with the hw_virtio_scsi (*)
configuration. Please report success or failure on GCE. The following
is a Rumprun dmesg for virtio-scsi with qemu:
virtio0 at pci0 dev 3 function 0
virtio0: Virtio SCSI Device (rev. 0x00)
vioscsi0 at virtio0: Features: 0x10000000<INDIRECT_DESC>
virtio0: allocated 43008 byte for virtqueue 0 for control, size 128
virtio0: using 34816 byte (2176 entries) indirect descriptors
virtio0: allocated 43008 byte for virtqueue 1 for event, size 128
virtio0: using 34816 byte (2176 entries) indirect descriptors
virtio0: allocated 43008 byte for virtqueue 2 for request, size 128
virtio0: using 34816 byte (2176 entries) indirect descriptors
vioscsi0: qsize 128
scsibus0 at vioscsi0 channel 0: 255 targets, 16383 luns per target
virtio0: interrupting at pausebreak
sd0 at scsibus0 target 1 lun 0: <QEMU, QEMU HARDDISK, 2.2.> disk fixed
sd0: 5120, 2 cyl, 16 head, 0 sec, 512 bytes/sect x 10 sectors
(yes, a very small file, at least accessing it works ;)
*) I'm not quite sure if the config should be separate from hw_virtio or
not. It pulls in the SCSI drivers, which is quite a lot of unnecessary
bulk in situations where virtio-scsi is not used. Opinions?
