[smartos-discuss] Weird msr instructions

Does anyone know what kind of MSR instructions are these: unhandled rdmsr: 0xc unhandled wrmsr: 0x50cc47 data 90 Because every time this happens, the KVM VM crashes without any trace or activity in kvmstat. --- smartos-discuss Archives:

Re: [smartos-discuss] vioblk driver

Only setting: "qemu_extra_opts": "-global virtio-blk-pci.physical_block_size=4096" appeared to work. diskinfo reported the correct size, creating a pool on it succeeded, and it had an ashift of 12. Not sure where that will leave you. -Nahum On Mon, Jan 30, 2017 at 2:30 PM, Nahum Shalman

Re: [smartos-discuss] vioblk driver

I wonder if I've just stumbled on a bug. I provisioned a VM with a zvol of 8GB, and with those qemu_extra_opts, but "diskinfo" thinks the disk is 64GB in size... I don't know the full mdb-fu you used to find that address and dump out those properties. Something seems a little fishy here. -Nahum

Re: [smartos-discuss] vioblk driver

That's only modifying the volblocksize of the underlying zvol. Getting QEMU to advertise a different blocksize might be trickier which is probably what's necessary. I found reference to "-global ide-drive.physical_block_size=4096" in http://wiki.qemu.org/download/qemu-doc.html#sec_005finvocation

Re: [smartos-discuss] vioblk driver

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":

Re: [smartos-discuss] vioblk driver

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 wrote: > Hi All, > > A quick question - how can I make use of vioblk device driver? Creating a > SmartOS VM using Linux KVM? > > The

[smartos-discuss] vioblk driver

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,