Closed hailfinger closed 6 years ago
This comes from Keith's qemu-nvme.
If you reproduce the error only using the nvme driver without LightNVM, you can open an issue on his qemu tree. Otherwise, this is mostly out of our realm (at least for now).
This is the output from the "make check" command run in the qemu tree directly, i.e. the official builtin qemu self-test. To remove any LightNVM stuff I'd have to edit hw/block/nvme.c.
It seems Keith doesn't host qemu-nvme on his github page. Do you happen to know where I can find his qemu-nvme?
I think the most updated one is here.
The
broken pipe
is actually what triggers the test failure. The vmxnet3 message is harmless.bisection result: First bad commit ff646a5841f743fdd9cfef138ac6be1f0ba4fbfb Author: Keith Busch keith.busch@intel.com 2014-10-23 20:02:44 Committer: Keith Busch keith.busch@intel.com 2014-10-23 20:02:44 Parent: 4bee77be4ba07de204389ef054358347f8d69d74 (NVMe: Updates for google extension) Parent: e40830afa1cff3ffdc37bdfdd40d80860074636c (Merge remote-tracking branch 'remotes/mdroth/tags/qga-pull-2014-10-22-tag' into staging) Merge remote-tracking branch 'upstream/master'