Hello, Thanks for this, I got everything working including the new device types (nvme-ns, nvme-subsys). I think I have found a small bug and do not know where to report this.
The values for nvme device property zoned.append_size_limit are not sanity checked, you can set it to invalid values such as 128. This will latter result in errors when trying to initialize the device: Device not ready; aborting initialisation, CSTS=0x2 Removing after probe failure status: -19 Addtionally, `cat /sys/block/nvmeXnX/queue/nr_zones` reports 0 while `blkzone report /dev/nvmeXnX` clearly shows > 0 zones. Not sure if user error or bug. Also potentially kernel bug and not due to QEMU. Let me know if sharing this information is helpful or rather just annoying, don't want to bother anyone. Kind regards, Corne On 04-02-2021 19:30, Klaus Jensen wrote: > On Feb 4 14:32, i...@dantalion.nl wrote: >> Hello Dmitry, >> >> I tried to apply your patches to nvme-next with >> <20201104102248.32168-1-...@irrelevant.dk> as base but get quite a few >> 'does not apply errors'. >> >> Can you confirm that nvme-next is: >> git://git.infradead.org/qemu-nvme.git >> >> And the base <20201104102248.32168-1-...@irrelevant.dk> is at: >> 73ad0ff216d2e1cf08909a0597e7b072babfe9c4 >> >> Otherwise if I have made any mistake could you please indicate where, I >> am sure I am doing something wrong here. Sorry for being a nuisance. >> > > Hi, > > That series is already merged in nvme-next. Use the 'nvme-next' branch > from git://git.infradead.org/qemu-nvme.git. > > > Cheers, > Klaus >
