Thanks, it works. However, I am having difficulty setting the block size to anything other than 512:
vmadm tells the block size is 8192, # vmadm get b175850d-92fd-cf81-d352-90d40e5076ce |json disks [ { "path": "/dev/zvol/rdsk/zones/b175850d-92fd-cf81-d352-90d40e5076ce-disk1", "boot": false, "model": "virtio", "media": "disk", "zfs_filesystem": "zones/b175850d-92fd-cf81-d352-90d40e5076ce-disk1", "zpool": "zones", "size": 65536, "compression": "on", "refreservation": 65536, "block_size": 8192 } ] but inside the VM, it says the block size is 512: > ffffff03d8df9700::print -t struct vioblk_softc sc_virtio.sc_features sc_blk_size sc_pblk_size uint32_t sc_virtio.sc_features = 0x10000454 int sc_blk_size = 0x200 int sc_pblk_size = 0x200 Quite confused .. Any thoughts? Thanks, --Youzhong On Mon, Jan 30, 2017 at 10:10 AM, Nahum Shalman <nshal...@omniti.com> wrote: > You can also create a SmartOS KVM VM on a SmartOS machine with a virtio > virtual disk. > > -Nahum > > On Mon, Jan 30, 2017 at 9:38 AM, Youzhong Yang <youzh...@gmail.com> wrote: > >> Hi All, >> >> A quick question - how can I make use of vioblk device driver? Creating a >> SmartOS VM using Linux KVM? >> >> The reason I am asking this is that I want to test a change in blkdev, to >> exercise some code path in it which can't be done using NVMe devices, such >> as the 'dump' functionality. >> >> Thanks, >> >> Youzhong >> >> > *smartos-discuss* | Archives > <https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/25077300-734ee1ca> | > Modify > <https://www.listbox.com/member/?&> > Your Subscription <http://www.listbox.com> > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com